I am developing a program using the 16-bit VB4 Enterprise Edition, on a
Windows 95 platform.  When an exe file is created it runs OK on all the
Windows 95 computers around the place with absolutely no problems (no
special setup is needed).  However, when the setup wizard is used to
generate a series of setup disks containing all the needed libraries etc,
it will not run (or even load properly) on Windows 3.1 computers.  

What am I doing wrong?

Help appreciated.

Bruce

I too had this problem. It appears that 3 of the .dll's created on your
install disks are Win95 only, yet have the same name as their 16-bit
counterparts. During setup on the 16-bit machine these 32-bit only dll's
overwrite the 16-bit dll's (as they are a newer version). You then get
errors as the calls to the dll's are invalid. The solution is to copy the
16-bit versions of the dll's to your hard drive on the 32-bit machine
(don't put them in windows\system). Then manually write your setup.lst to
include these files instead of the 32-bit versions. The three dll's in
question are ;

compobj.dll
ole2.dll
storage.dll

Make sure you replace these dll's on the 16-bit machines that you tried
your install on, otherwise you will find (like I did!) that other programs
that require these dll's will stop running (Word, Excel, Lotus Notes amoung
others).

Hope this helps

Chris Santer, Lucas County Data Processing, Toledo OH

There is an easire way -- make sure that the Setup Lizard points to the correct
files. They are in the SetupKit\Sys16 directory of VB4-16.

  >I too had this problem. It appears that 3 of the .dll's created on your
  >install disks are Win95 only, yet have the same name as their 16-bit
  >counterparts. During setup on the 16-bit machine these 32-bit only dll's
  >overwrite the 16-bit dll's (as they are a newer version). You then get
  >errors as the calls to the dll's are invalid. The solution is to copy the
  >16-bit versions of the dll's to your hard drive on the 32-bit machine
  >(don't put them in windows\system). Then manually write your setup.lst to
  >include these files instead of the 32-bit versions. The three dll's in
  >question are ;
  >
  >compobj.dll
  >ole2.dll
  >storage.dll
  >
  >Make sure you replace these dll's on the 16-bit machines that you tried
  >your install on, otherwise you will find (like I did!) that other programs
  >that require these dll's will stop running (Word, Excel, Lotus Notes amoung
  >others).
  >
  >Hope this helps
  >
  >Chris Santer, Lucas County Data Processing, Toledo OH
  >


  >> I am developing a program using the 16-bit VB4 Enterprise Edition, on a
  >> Windows 95 platform.  When an exe file is created it runs OK on all the
  >> Windows 95 computers around the place with absolutely no problems (no
  >> special setup is needed).  However, when the setup wizard is used to
  >> generate a series of setup disks containing all the needed libraries etc,
  >> it will not run (or even load properly) on Windows 3.1 computers.  
  >>
  >> What am I doing wrong?
  >>
  >> Help appreciated.
  >>
  >> Bruce
  >>