Hi Sofia, thanks for your quck reply. Although my problem is not with those files what installation program wants to install. Opposite that problem is with file what my application wants to use supplied by WINDOWS.
I made some more "research" on this issue and I found the following. The only file on my test system which is really out of date is OLEAUT32.DLL staying in WINDOWS/SYSTEM32 dir. During creation of my package I cannot modify its path because on list it isn't. (This file is only picked up from developing machine to store in package and if during installation on the target machine the same file older, install program try to update it) Opposite that file name in pakage wizard I just can see this: "VB6 Runtime and OLE automation" and I think really behind this name is the OLEAUT32.DLL file. Unfortunately this is not modificable during package building. (I can remove it from include list but if I add OLEAUT32.DLL it appears again with VB6 Runtime...name) So seems to be no way to fix my problem here. :( (Package wizard says to the system, this file will use from WINDOWS/SYSTEM32 dir) So my quick solution was: I took OLEAUT32.DLL from my original developing machine. I removed write protection temporarily from SYSTEM32 dir on test machine. Renamed old OLEAUT32.DLL Then I copied to there the newer file After this manual action installation program has run well, and installed aplication is working well. Any other, automated solution would be good and welcomed! (Maybe we should say to users: they should keep up-to-dated their XP :)) regards George > ----- Original Message ----- > From: "Sonya Nikosky" <[EMAIL PROTECTED]> > To: "rugo" <[EMAIL PROTECTED]> > Sent: Wednesday, December 17, 2003 10:54 PM > Subject: Re: MI-L running of integrated application > > > > I had the same problem, which results from system not letting you > > overwrite system drivers, DLLs, EXEs etc. I crudely solved it by > > selecting AppPath in the packager screen that asks where to install > > your DLLs, OCXs etc, and setting all the "shared files" checks to off . > > It results in larger installation package and duplication of DLLs, but > > it lets you install the thing. Any better solutions will be welcome. > > > > -- > > Sofia Nikolsky > > > > JCH GeoInfo Solutions > > (919) 493-9339 > > www.jchgis.com > > > > > > rugo wrote: > > > > >Dear list! > > > > > >Again I need your help. > > >I just have finished with my application developing (it is a VB > application using OLE) > > >I made it in Visual Studio 6.0 environment. > > >I used its "Package and Deployment Wizard" to create an installation > package of my application. > > > > > >If I install it on my own machine (XP) it is OK, and installed > application running well. > > > > > >If I install the same package on another XP machine, during installation > I get message something like this: > > > > > >" Installation can not continue because some system files are out of > date" > > > > > >And install program asks whether I want to update system files? > > >I answer YES, then it asks me to restart the machine... > > >OK I do it, then I want to repeat the installation. > > >Message is same. "out of date... do you want to update..." > > > > > >Well, first I thought Install can not update system files because WINDOWS > directories are secured by XP, they are write protected so I removed write > protection and I repeated. > > >Unfortunately situation is same. > > > > > >What the problem can be? > > > > > >Can somebody give me any idea what to do? > > > > > >Thank you indeed. > > > > > >George > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 9612
