-
I'm running into a problem on an installation, when my setup file goes to install the run time files oleaut32.dll(sometimes others to) is write protected on the end user's PC, i know you can just change the read only property of the .dll itself and then re-run the setup but i don't want the end user to have to do this, is there any way to have it overwrite the older version anyway???
The .dll versions i'm installing are more recent than the existing ones in the couple of PC's i've ran into this problem on
-
If you knew the file names you could of course..
Code:
SetAttr yourfilepath, int(getattr(yourfilepath)/2)*2
-
I know the filenames but i won't know the file versions in advance, will it still overwrite??
Odd thing to the only PC's i've ran into the run time files being write protected on are ones with AOL installed on them, wonder if there's any relationship...
-
I haven't checked it out but oleaut32.dll may be a component of Aol, and if the installed version is old, or if there's no automatic upgrade to oleaut32 then it may be old. But i'm almost sure the problem is that oleaut32 isn't readonly but instead running?
-
well the thing is, for the rest of the runtime files it will reboot the computer and update them, other times there's no problem and all of them are updated with the new versions after re-boot, the only thing i could think of is AOL possibly customized the run-time files to be read only when installed(that's just me guessing). I'm buying Installshield Express 3.0 within the next day or 2 and i'm hoping that will help with some of the problems.
I have run into instances where some of the files were running, and of course woke up and shutdown any programs that were running at the time...
[Edited by PJB on 09-18-2000 at 08:14 AM]
