ckurt99
asked on
Package and Deployment Wizard-prepared install fails under Win2k
Greetings,
We distribute some Visual Basic 6 applications that we prepare with the Visual Studio Packaging & Deployment Wizard (PDW). Since switching over to XP for our VB development, our customers on Windows 2000 have had problems installing the applications prepared by PDW; when they run setup.exe, they are told that some system files are out of date, and that they must reboot. When they reboot and run setup again, they get the same message again, endless loop. This Microsoft knowledgebase article appears relevant: http://support.microsoft.com/default.aspx?scid=kb;en-us;279764&Product=vbb , however, unfortunately the fixes suggested do not work. The latest service pack for Windows 2000 is SP4, and this still does not bring OLEAUT32.dll up to the level that setup has from XP in the cabs prepared by PDW. Applying the visual studio service pack on the development computer likewise does not eliminate the problem.
Are our only two choices to either go back to Windows 2000 for development, or forego using the Packaging & Deployment Wizard?
Thanks for your advice.
Kurt
We distribute some Visual Basic 6 applications that we prepare with the Visual Studio Packaging & Deployment Wizard (PDW). Since switching over to XP for our VB development, our customers on Windows 2000 have had problems installing the applications prepared by PDW; when they run setup.exe, they are told that some system files are out of date, and that they must reboot. When they reboot and run setup again, they get the same message again, endless loop. This Microsoft knowledgebase article appears relevant: http://support.microsoft.com/default.aspx?scid=kb;en-us;279764&Product=vbb , however, unfortunately the fixes suggested do not work. The latest service pack for Windows 2000 is SP4, and this still does not bring OLEAUT32.dll up to the level that setup has from XP in the cabs prepared by PDW. Applying the visual studio service pack on the development computer likewise does not eliminate the problem.
Are our only two choices to either go back to Windows 2000 for development, or forego using the Packaging & Deployment Wizard?
Thanks for your advice.
Kurt
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The problems arise during install on a win2k box, and I think it is on every win2k box, but it is hard to be sure - some customers might download it, and have no reason to tell me it works. I hear about the ones that don't work (install)!
Like you say, maybe I'll have to do my builds on win2k...
Kurt
Like you say, maybe I'll have to do my builds on win2k...
Kurt
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
participate
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you for your comments... I won't be able to try this until Monday, but I will report back on results then.
Kurt
Kurt
ASKER
Well, this Package and Deployment Wizard is a swamp... never could it get it work... thank you one and all for advice. In the end, we bought the Wise installer (www.wise.com ), and it works like a champ. Goodbye, P&DW!
Kurt
Kurt
Ive fought the 2000 and XP bear for a while now, I share your pain.