If you get a message saying "Setup cannot continue because some system files are out of date on your system." and asking you to update the files, click OK. The new version files will not hurt your system. If you continue to get this message after clicking OK, one of the following procedures should fix the problem.
This error occurs when system files that are required by Visual Basic applications cannot be copied. All the base files that an application created with Visual Basic needs to run with can be found at Microsoft Support Service Article 192461. If you run the .exe file that is available on that page, your run-time files should be updated. You may wish to attempt this before examining the log file created by our ISA F/T software package.
If you wish to manually install the file(s) which failed to copy correctly, look for a file called 'st6unst.log'. There may be several copies of this file on your machine, since any application package created using the software we use to create our application packages will create a file named 'st6unst.log'. Most probably, the log file created by the ATI package will be the most recently modified file. This log file will tell you what files were copied correctly and which ones failed.
If you cannot find a file named 'st6unst.log', look for the file 'setup.lst' which is included with our software package. All the files which can cause the "System files are out of date" error are listed in the "Bootstrap" section of this file. These are the same files that are available at Microsoft article 192461.
The following solutions are taken from Microsoft Product Support Services Article Q191096, and are ©2003 Microsoft Corporation. If none of these work, and you are using Windows 95, see the bottom of the page.
1.
Copy the TEMP and TMP environment variables to a folder that is in the same drive partition as the Windows system files. To do this, open a command prompt window and type the following at the prompt:
Set TMP=C:\TEMP
Set TEMP=C:\TEMP
This will save the TEMP and TMP environment variables to a folder named "Temp" that resides on the C: drive.
NOTE: The folder must exist prior to carrying out these steps.
Once these environment variables are set, the application should then install and continue past the message on reboot.
2.
If your Autoexec.bat file contains the following line (or similar):
If exists c:\temp\*.tmp del
c:\temp\*.tmp
comment it out by placing "REM" in front of it.
3.
Disable any Anti-virus software (or other memory resident programs) and try running Setup again. Often the best way to accomplish this is to run setup in Safe Mode. It may also be necessary to copy all of the setup files to a temporary folder on the hard drive disk and run Setup.exe from there.
4.
Leftover files from a failed Setup attempt can also cause this problem. If found, delete the msftqws.pdw subfolder and its contents from the Temp folder. Also look in the Windows or Winnt folder for Setup1.exe and any *.CAB files from previous installs, and delete them. This should be done after each failed install.
5.
Some logon scripts can cause this problem, so try to run Setup before logging on to the network.
6.
The system files that may need to be updated are listed in the Bootstrap or Bootstrap Files section of the Setup.lst file created with your package. These files can also be installed separately from self-extracting files found on Microsoft's support web site. Please see the References section for information about obtaining these files.
7.
You can also edit the Setup.lst file. Look in the Setup1 Files or Files section for files to be copied to either $(WinSysPath) or $(WinSysPathSysFile). For example, Msvcrt.dll and Mfc42.dll. You can copy these lines to the end of the Bootstrap or Bootstrap Files section. You must renumber these lines so that the File numbers are sequential, for example "File1=...", File2=..." and so on. If these lines are removed from their original section, the remaining lines must be renumbered to maintain a sequential list.
If none of the above work, and you are using Windows 95, the file MFC42.dll may not be copying correctly. You can find MFC42.dll in one of the .cab files you downloaded with the setup package (the .cab files will open with WinZIP or a compatible archive tool). Extract the MFC42.dll file and restart your computer in MS-DOS mode. Copy the new MFC42.dll file you just extracted over the current copy in your Windows\System directory, and restart your computer in Windows mode.
|