VB 4.0 Setup Problem - OLEAUT32.DLL 1

[ag]

Has anyone come across the following problem:<br>
<br>
I am installing a VB4.0 app onto a Win95 OSR2 machine with the latest version of OLEAUT32.DLL (i.e. MS OLE Update applied). The master development machine (VB4) contains the OLE versions as at the time of the VB 4.0 CD (i.e. earlier). <br>
<br>
When the setup.exe is run, all runs fine until OLEAUT32.DLL is to be copied. I understood (and the log files seem to confirm) that only newer files are copied from installation disks. However, the error message 'Access violation' is displayed on OLEAUT32.DLL and setup is aborted. <br>
<br>
If you ignore the error, the OCX's then fail to regoster.<br>
<br>
Any ideas?<br>
<br>
TIA<br>
<br>
Andrew<br>

 

[databarn]

Andrew,<br>
<br>
The most likely problem (although not the only one) is that there is a VB app already running, probably one with an icon in the system tray if you've already closed other running applications.<br>
<br>
Typically 'Access violation' is encountered when the file to be replaced is already in use by an application running, although it can be encountered when a closed application failed to clean up after itself and remove oleaut32 from memory. That latter condition usually indicates memory problems that require a restart of Windows to clear (not necessarily a machine reboot, just 'logon as new user' restart of Windows).<br>
<br>
There is another possibility, that being a mismatch of versions in the OLE dll set. There are several different versions of the OLE libraries, but they do not coexist well - or at all!. <br>
<br>
One last thing to check - this drove me crazy for about a week - is what version(s) of oleaut32 exist on the target machine and where they are in the path. This one's not very common, but its _very_ sneaky &lt;grin!&gt;.

 

[ag]

Thanks for the reply....I'll check these out next week.<br>
<br>
<br>
Andrew<br>