WiseScript Editor Reference
155
Troubleshooting WiseScripts
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 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:
z
If the problem occurs because your file coincidentally has the same name as an
already existing system file, rename your file.
z
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.
z
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.
z
Bypass the default version checking code. By default, WiseScript calls a Microsoft
.DLL for version checking. You can use the WiseScript Editor version checking
method instead of Microsoft’s. To change the version checking method to the
WiseScript 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
