Printable View
when my vb app tries to install, I get an error message saying that some "system files are out of date - would you like to upgrade these files and restart?"
I click Yes and it does some stuff and restarts, but it comes back to the same place with the same problem and won't install. The operating sysyem is 2000 - I know there was an install bug with Access app and Windows 2000 - is there on for VB also?
How would I fix this?
Thanks
We had to develop on a Win2K machine, create the setup package there, etc.
Then it worked just fine.
I had the same problem with WinME. Make sure you have the latest service pack for VB.
See this post for a little more info:
http://www.vbforums.com/showthread.p...hreadid=156206
http://support.microsoft.com/default...;en-us;Q279764
Thanks for your help!
That microsoft link you have posted is wrong. I tried it and it doesn't work. See my post from earlier for that actual fix (the one indicated by Si_the_geek ).
I worked with Microsoft on this and the tech I was working with got my app to install on every version of 32-bit windows. The machines he used were "clean" machines meaning all they had on them was a Windows version.
The link I posted doesn't fix the problem - I followed your directions and it worked perfect - Thanks alot!
You're welcome.
I have same problem with windows XP.
I have created the package in Vista with latest updates service pack 6 for VB6 , but when i try to install package in windows xp, the problem is that some files are are out of date - would you like to upgrade these files and restart.
When it restarts the message stays the same and i cannot get it work..
Help !
Problem: After installation you receive an error when your app starts up such as "Failed to initialize application" along with a bunch of numbers in parenthesis. This means that you have installed a file that users do not have permission to access. This is usually a DLL of some sort in the System32 folder.
ResolutiON: Run Filemon (you have to download it) and find out when the error is occurring. You have to log on as an administrator to do one of the following:
1) Give all users permissions to all files in the system32 folder. (Easier, but probably not a good idea)
2) Give all users permissions to the files causing the problem in the System32 folder.
------------------------
Problem: Endless reboots. There is a lot of info on the Microsoft site about this problem. Unfortunately, it's convoluted and doesn't resolve the problem anyway. Essentially what happens is you attempt to install your app and then receive a message that WINDOWS must be restarted to replace system files. Then you reboot and run setup.exe again. You continue to receive the same message ad infinitum and the application is never installed. Plus you end up with a bunch of duplicate cab files in the windows folder.
Resolution: Don't install files that are standard equipment with Windows.
1) You can remove MSCVRT.DLL safely altogether when using PDW. It does not need to be installed because windows already has it.
2) You can not remove OLEAUT32.DLL from the setup package for some reason. However, you must remove it from your setup.lst file and re-number the remaining files so they remain sequential. OLEAUT32.DLL is usually listed in the BOOTSTRAP section. For example, if there are 9 files in your bootstrap section and OLEAUT32.DLL is number 7 then renumber files 8 and 9 to 7 and 8 respectively. The file will still be in your CAB file but it won't get installed. I would like to find a way to remove it from the cab altogether because it just makes the cab bigger. Unfortunately, I haven't found a way to do so.
This will resolve the endless reboots.
This thing about packeting and developing is so complicated that it is not worth it.
I have created simple program with one dll and now I cannot get it work on win xp. You have to have same MDAC version installed, and tell me witch version is same with vista and xp ? None.. Then you get some other problems with rebooting and I dont know what else.
Is there any other way to make programs work on other computers and other systems like win 98, 2000, milenium, xp, vista, withouth so many complications ?
I just want to make programs to be fast and easy instaled or. copied and used.
Deployment is hard.
One thing to be careful of is to avoid deploying items you shouldn't. Things on the "do deploy" list back in 1998 are now "do not deploy" because of changes over the years. The list PDW uses to know this does not get updated - you must update it yourself, or each time you package you have to uncheck those items PDW picks up. How do you know what is "do not deploy?" You have to go through the related MS KB articles.
If you want to support Win9x you pretty much have to package MDAC and the VB6 runtimes because you can't count on those old OSs having decent versions. My suggestion is to package MDAC_TYP.exe 2.5, and if a target system has a newer MDAC nothing will get installed.
If you stick to ADO, you can use a reference to ADODB 2.5 in your program and it will work with MDAC 2.5 or any later version automatically. If you use ADOX too always late bind, i.e. don't reference any version of ADOX and declare all ADOX objects As Object and use CreateObject() instead of New.
If you need a feature that's in ADO 2.6 or 2.7 you'll have to adjust upward and package the corresponding MDAC_TYP.exe.
If you are using DAO good luck. DAO does not have the "auto adjust" typelibs that ADO does.
For targeting XP, Vista, and Win7 you can safely use ADO 2.5 because they all have the proper typelib in place. If 2.5 is not good enough (some later MDACs are required for recent SQL Server versions) you might still have to deploy MDAC_TYP.exe 2.6, 2.7, or 2.8 to XP. Vista and Win7 have DAC 6.0 but also have adapter typelibs for the earlier 2.x interfaces (again, ADO only).
Right now MDAC 2.8 SP1 is probably the only one you'd want to deploy if you had to.
Thread Moved