Problem with VB Application setup on fresh Win ME 4.90.3000 1

[rm2000]

Hi,

I am having problem with the setup of my application on a fresh install of Windows ME 4.90.3000. The setup is created using VB's P & D wizard and works fine on Win 95/98/2000/XP. On a new Win ME machine, the setup prompts for a System Files update and on agreeing to that it appears to copy the system files and then reboot the machine (the same sequence is also executed on a fresh Win 95/98 machine). The problem on Win ME is that after the reboot when setup is run again, the system again prompts for the out of date system files. This way the application does not get setup and the user is taken through a loop of execute setup, prompt for "System Update", reboot and again execute setup.

The question is, has it something to do with Win ME's "System File Protection" feature?

If yes, what measures do I have to take in my deployment package to circumevent it?

If not, what else could be wrong and how do I fix it?

Thanks in advance for all your help.

RM

 

[CajunCenturion]

I have seen this problem a couple of times, and it usually revolves around 3 files (OLDAUT32.DLL, OLEPRO32.DLL, and STDOLE2.TLB). I got around this problem by putting older version of these three files in the following directory:

C:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\Redist

Then I rebuild the project using PDW, but since these are older files that one would find on the target machine, no attempt is made to replace them during the install process.

Rebooting doesn't solve this problem because these are loaded by Windows during the boot, before the installation procedure resumes.
Good Luck
--------------
As a circle of light increases so does the circumference of darkness around it. - Albert Einstein

 

[rm2000]

Thanks CajunCenturion, I'll give that a try.

Now the question is where do I find old OLDAUT32.DLL, OLEPRO32.DLL and STDOLE2.TLB files. Will my application still work with the old files as expected with the new files? How do I find what is the difference between old and new files so that I can take appropriate measures in the code to make it work with the old files also?

I am using VB 6 SP3.

 

[CajunCenturion]

I memory serves correctly, I copied them from an old win95 machine Good Luck
--------------
As a circle of light increases so does the circumference of darkness around it. - Albert Einstein

 

[rm2000]

I have a feeling that this will work. I just need to ascertain the application still works with the old files (or the system default files) as expected.

Thanks for all your help. RM
=============================
Complete solution for digital photos (FREE) @

http://www.exapower.com

 

[rm2000]

Hi CajunCenturion,

Your suggestion did work. I took the three files from old Win98 CD and put them in my Redist folder so that PDW takes the old files while packaging. This way the setup does not prompt for the "Out of date" system files now.

Thanks again.

For the benefit of the other the three files are OLEAUT32.DLL (not OLDAUT32.DLL, it's a typo), OLEPRO32.DLL, and STDOLE2.TLB
RM
=============================
Complete solution for digital photos (FREE) @

http://www.exapower.com