VB Package Deployment issues

I realized that many people, just like myself, were having problems with the Package and Deployment Wizard for VB 6.0 and when trying to install their program on another PC they were getting the following message:

“Setup cannot continue because some system files are out of date on your system. Click OK if you would like setup to update these files for you now. You will need to restart Windows before you can run setup again. Click cancel to exit setup without updating system files.”

Microsoft addresses this issue in their Help and Support (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q191/0/96.ASP&NoWebContent=1) and proposes 8 solutions.

However, I found out that the problem was coming from the Bootstrap files in the Setup.LST file.
If you open Setup.LST (generated with the wizard) you’ll see something like this:

File1=@VB6STKIT.DLL,$(WinSysPathSysFile),,,3 25 99 11:00:00 PM,101888,6.0.84.50
File2=@MSVCRT40.DLL,$(WinSysPathSysFile),,,5 30 98 11:00:00 PM,326656,4.21.0.0
File3=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,5 30 98 11:00:00 PM,22288,4.71.1460.1
File4=@stdole2.tlb,$(WinSysPathSysFile),$(TLBRegister),,8 23 01 1:00:00 PM,17920,3.50.5014.0
File5=@asycfilt.dll,$(WinSysPathSysFile),,,8 4 04 8:56:41 AM,65024,5.1.2600.2180
File6=@olepro32.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,8 4 04 8:56:44 AM,83456,5.1.2600.2180
File7=@oleaut32.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,8 4 04 8:56:44 AM,553472,5.1.2600.2180
File8=@msvbvm60.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,8 4 04 8:56:43 AM,1392671,6.0.96.90

Files 1 through 3 are needed to run your VB 6.0 program, but Files 4 through 8 were the ones that were “out of date” and caused the error. Since the host PC will most certainly have these files, there is no need for your program to install them (or even update them). So you can just insert a colon “;” in front of the lines for File 4 through 8 for the installation to ignore these commands.

So open your Setup.LST and change it like this:

[Bootstrap Files]
File1=@VB6STKIT.DLL,$(WinSysPathSysFile),,,3 25 99 11:00:00 PM,101888,6.0.84.50
File2=@MSVCRT40.DLL,$(WinSysPathSysFile),,,5 30 98 11:00:00 PM,326656,4.21.0.0
File3=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,5 30 98 11:00:00 PM,22288,4.71.1460.1
;File4=@stdole2.tlb,$(WinSysPathSysFile),$(TLBRegister),,8 23 01 1:00:00 PM,17920,3.50.5014.0
;File5=@asycfilt.dll,$(WinSysPathSysFile),,,8 4 04 8:56:41 AM,65024,5.1.2600.2180
;File6=@olepro32.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,8 4 04 8:56:44 AM,83456,5.1.2600.2180
;File7=@oleaut32.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,8 4 04 8:56:44 AM,553472,5.1.2600.2180
;File8=@msvbvm60.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,8 4 04 8:56:43 AM,1392671,6.0.96.90

Save it, close it, and try installing your program again.

[B]Note: You may have other DLL files than those listed above, so you have to make sure which ones are the one out of date.

Advertisements

3 thoughts on “VB Package Deployment issues

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s