|
Subject:
|
Installing a WinXP VB6 application on others O.S.
|
|
Posted By:
|
MarcoV
|
Post Date:
|
9/9/2003 9:31:54 AM
|
Hi,
I am Italian and my English is terrible, so I hope you can understand what I am writing.
I have a VB6 sp5 application running from years.
I was developing on Win 98 and Win 2000 pro.
The installation kit builded by VB6 tool was working fine.
Some week ago I upgraded a development machine to Win XP pro.
Inside the project I have changed the reference from ADO 2.6 to ADO 2.7, since WinXP come with MDAC 2.7
After rebuilding my installation kit on Win XP, if I try to install it on PC with Win 98, 2000 or NT it destroys something of the O.S. so that it is impossible reboot the PC. On another Win 2000 PC it asks to reboot the system, continuously without installing the application.
Any tip ? Can you help me ?
thanks in advance for any help.
Marco Veniani
|
|
Reply By:
|
Yehuda
|
Reply Date:
|
9/11/2003 5:13:20 PM
|
Marco,
Do you use the Packaging Wizard that comes with VB. If so, the packaging wizard seeks to update the system files based on the computer it is compiled on. The fix for this is:
The first place the packaging wizard looks is C:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\Redist. Put the system files for the system you are compiling for in this folder and everything will be fine (the system files I remember offhand are SCRRUN.dll, MSVcrt.dll, stdole32.tlb and OLEAUT32.dll I am sure there are more).
If you don't do this, it takes the files from your system folder, which causes this behavior.
Yehuda
|
|
Reply By:
|
MarcoV
|
Reply Date:
|
9/19/2003 4:20:49 AM
|
Yehuda,
thanks for you answer!
Yes, I use the standard VB Packaging wizard.
Since I saw that building the kit on Win 98, it works fine on every
O.S. aside win XP, at the end I decided to build 2 different kit,
one for XP (on a XP machine) and the other for all the other O.S. (on a PC with Win 98).
Thiw way solves my problem.
Bye,
Marco Veniani
|
