File Replacement Problems In System32 - Symantec WISESCRIPT PACKAGE EDITOR 7.0 SP2 - FOR WISE INSTALLATION STUDIO V1.0 Installation Manual

File Replacement Problems in System32

WiseScript Package Editor Reference
Use the installation log to determine where problems occur and why. Quality assurance
can use it to check the accuracy of the installation. It also helps technical support
because end users who have problems installing can email the installation log.
Use the Add Text to Install.log script action to add your own commands to the log. You
can use it to comment the install log or to customize your uninstall.
See Add Text to INSTALL.LOG
(WiseScript Package Editor only) You can enable or disable the installation log and
choose its location on the Installation Log page.
See Installation Log on page 60.
Following are file replacement problems you might encounter:
Files that you assign to the application directory or to the Windows directory
incorrectly install to the System or System32 directory.
A later version of a system file does not replace an earlier version.
Both of these symptoms can be caused by version checking code, which is executed if a
file is set to be replaced based on version number. The code that does version checking
also checks such things as operating system (OS) type and language, and it won't
replace files if the OS or language does not match, regardless of version.
To check if a file is replaced based on version, double-click its Install File(s) script line.
(In WiseScript Package Editor, double-click the file on the Files page.) In the Install File
Settings dialog box that appears, if Check File is selected from the Replace Existing
File drop-down list, then version checking occurs for the file.
To troubleshoot file replacement problems, you can do one of the following:
If the problem occurs because your file coincidentally has the same name as an
already existing system file, rename your file.
If the problem occurs because your file is a later version of a system file, but you
are trying to install it to a different location than the existing system file, consider
installing it to the existing location and changing your application to look for it in the
existing location.
You can turn off version checking for the file (not recommended). Do this by
selecting an option from the Replace Existing File drop-down list other than
Check File.
Bypass the default version checking code. By default, WiseScript calls a Microsoft
.DLL for version checking. You can use the WiseScript Package Editor version
checking method instead of Microsoft's. To change the version checking method to
the WiseScript Package Editor method, set the variable VER_CHECK_TYPE to 1
directly before the Install File(s) line that exhibits the problem. Then reset
VER_CHECK_TYPE to null after the line, which re-enables Microsoft version
checking.
Example:
Set Variable VER_CHECK_TYPE to 1
Install File C:\Program Files\Application\Country.sys
Set Variable VER_CHECK_TYPE to
on page 43.
Troubleshooting WiseScripts
156