problem with system updates from Package 3

[kennm]

Greetings.

I've used the Package and Deployment wizard to create a package. When I try to install it on another computer (and I've tried on both XP and 2000), I get the message that the system files are out of date and need to be updated. It says to continue to update the system, then reoot. I do that, then reboot, but then I get the same error again. Over and Over.

What's wrong here? What have I done wrong?

Any and all advice appreciate.

Thanks,

Kenn

 

[zemp]

See thread222-445231.

zemp

 

[ChrisFC]

I got stuck in this loop too. The easy way out is to edit the version number of the file causing the problem the setup.lst file. It'll be one of the boot strap files (usually about 7 at the start of the lst). Just lower the number a the end and it should install fine. I'm not sure what the proper soluion is, but this worked fine for me!

 

[zemp]

kennm, BTW welcome to Tek-Tips!

When you have time take a look at faq222-2244 for information on nhow to get the most from the Tek-Tips forums.


zemp

 

[kennm]

Thanks to both of you.

Actually, the error message does not tell me what file is causing the problem but instead says, "Setup cannot continue because some system files are out of date on your system. Click ok if you want setup to update these files."

In your experience, is there one that's most likely to be the problem? If so, what do I change the number to? I'm not sure I quite understand.

thanks again.

Kenn

 

[ChrisFC]

When it setup executable starts it usually has a grey box that says something like:
"Adding file 1 of 7"

And his count goes up. If you can work out at which number it falls over at then open up the file called setup.lst in notepad. About the tenth line down you should find a tag:
[Bootstrap Files]
Under that you'll have a few lines (normally 7) that look a bit like this:

File1=@VB6STKIT.DLL,$(WinSysPathSysFile),,,3/25/99 11:00:00 PM,101888,6.0.84.50
File2=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,5/30/98 11:00:00 PM,22288,4.71.1460.1
File3=@STDOLE2.TLB,$(WinSysPathSysFile),$(TLBRegister),,8/31/99 3:55:18 PM,17920,2.40.4277.1
File4=@ASYCFILT.DLL,$(WinSysPathSysFile),,,8/31/99 3:55:18 PM,147728,2.40.4277.1
File5=@OLEPRO32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,8/31/99 3:55:18 PM,164112,5.0.4277.1
File6=@OLEAUT32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,8/31/99 3:55:18 PM,598288,2.40.4277.1
File7=@MSVBVM60.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,5/10/99 1:01:14 PM,1384448,6.0.84.95


The last bit on each line (eg: 6.0.84.50) is the version number of the dll. If you lower this a bit (eg: to 3.0.84.50) it should fix the problem.

It's proabably not the proper way to do it, but it's worked fine for me!

 

[ChrisFC]

One other thing I forgot to say, it was MSVBVM60.DLL that
caused me the problems.

 

[kennm]

Problem solved.

As it turns out (and it took a fair amount of googling to discover this), the issue is a known bug and is fixed by SP3 (I think) ... Anyway, I installed the latest service pack, and the problem went away.

Thanks to everyone.

kenn