[RESOLVED] Project won't install built on VM

[dlscott56]

I am having to go back and work on an old VB6 project that gets installed on Windows XP computers. I've got VB6 development set up on my Windows 10 computer in a Windows XP VM. Prior to doing any changes to it I wanted to make sure I could successfully use the Package and Deployment Wizard to build the installation files, take it to one of the Windows XP computers and install. It will copy the files to the computer and then the message comes up saying it can't continue because some of the system files are out of date. Asking if it wants me to have it update them and restart the computer. It does this, reboots and then, when trying to install again, does the exact same thing.

Any suggestions would be appreciated.

[dlscott56]

Forgot to add this, not sure if it would help identify the trouble. Here is the Setup.lst -

[Bootstrap]
SetupTitle=Install
SetupText=Copying Files, please stand by.
CabFile=DipSpinBarCode.CAB
Spawn=Setup1.exe
Uninstal=st6unst.exe
TmpDir=msftqws.pdw
Cabs=1

[Bootstrap Files]
[email protected],$(WinSysPathSysFile),,,6/17/98 11:00:00 PM,102912,6.0.81.69
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,5/30/98 11:00:00 PM,22288,4.71.1460.1
[email protected],$(WinSysPathSysFile),$(TLBRegister),,4/14/08 7:00:00 AM,16896,5.1.2600.5512
[email protected],$(WinSysPathSysFile),,,3/5/10 9:37:40 AM,65536,5.1.2600.5949
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,4/14/08 7:00:00 AM,84992,5.1.2600.5512
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,12/20/10 12:32:15 PM,551936,5.1.2600.6058
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,4/14/08 7:00:00 AM,1384479,6.0.98.2

[IconGroups]
Group0=Process Control Data
PrivateGroup0=False
Parent0=$(Programs)

[Process Control Data]
Icon1="DipSpinBarCode.exe"
Title1=Process Control Data
StartIn1=$(AppPath)

[Setup]
Title=Process Control Data
DefaultDir=$(ProgramFiles)\Process Control Data
AppExe=DipSpinBarCode.exe
AppToUninstall=DipSpinBarCode.exe

[Setup1 Files]
[email protected],$(AppPath),,,8/11/15 3:05:08 PM,1308,0.0.0.0
[email protected],$(AppPath),,,7/27/04 10:46:56 AM,15,0.0.0.0
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/23/98 11:00:00 PM,108336,6.0.81.69
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/25/98 11:00:00 PM,644400,6.0.81.77
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),5/22/00 5:58:10 PM,1066176,6.0.88.62
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/23/98 11:00:00 PM,103744,6.0.81.69
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),8/14/00 5:28:12 PM,419240,7.0.0.78
[email protected],$(WinSysPathSysFile),,,4/14/08 7:00:00 AM,343040,7.0.2600.5512
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),5/9/08 5:53:40 AM,172032,5.7.0.18066
[email protected],$(AppPath),,,11/9/16 3:19:52 PM,372736,5.1.0.115

[DEXWERX]

There's a lot of files in there that shouldn't be installed - as they're actually integrated parts of the OS now.

not sure why stdole2.tlb is in there...
but you definitely shouldn't be installing these:

msvcrt.dll
asycfilt.dll
olepro32.dll
oleaut32.dll
msvbvm60.dll

[dlscott56]

I just removed these from the installation and was able to install the project and run the program.

[DEXWERX]

awesome. Basically as long as the XP machines have the latest service pack and security updates - you won't need to update those DLLs.

Not sure about XP but Later Windows versions actively try to prevent those DLLs from being "updated" by installers.

[dilettante]

The msvcrt.dll file is the culprit.

The others don't get installed, Windows just chuckles at you and says "yeah, ok there buddy wink wink." They protected parts of Windows and have been for a long time.

This is why the PDW has its VB6DEP.INI file. You are supposed to update this yourself to exclude files that should no longer be deployed. If you have to support very downlevel OSs like Win9x or NT4.0 you'd have different copies of this file for different setup builds.

[dday9]

Moderator Action: Moved from VB6 and Earlier to Application Deployment.

[dlscott56]

Thanks for help! Really appreciate it.