>>I have created distribution disks for a 32-bit VB 4.0 application using Installshield3 instead of Microsoft's
>>Setup Wizard, and I get some strange behaoviour from some of my PCs.
>>
>>Anybody used that tool before? I would really need some help about this.
>
>Yes, I use it. What is the problem excatly?

(1) How can I determine which files need to be included in the distribution
disks. Until now I use the information contained in the swdepend.ini
file and the setup.lst generated by the Microsoft's Setup wizard, but there
are cases that some dlls(i.e. MFC42.DLL) that certain 3rd party OCX controls depend on, which do not appear in the above files.

(2)I'm a little confused with the information contained in SETUP.LST.
Most of the files have a WinSysPath parameter, but there are some with a
WinSysPathSysFile parameter. I'm wondering whether these file need any special handling during installation.

Thanks for your promptly response

Marios