Chapter 6: Troubleshooting Wisescripts; About Troubleshooting A Wisescript; Using The Installation Log; File Replacement Problems In System32 - Symantec WISESCRIPT EDITOR 7.0 SP2 - FOR NS V1.0 Manual

Chapter 6
Troubleshooting WiseScripts

About Troubleshooting a WiseScript

Using the Installation Log

File Replacement Problems in System32

WiseScript Editor Reference
This chapter includes the following topics:
About Troubleshooting a WiseScript
Using the Installation Log
File Replacement Problems in System32
Use the following to troubleshoot a WiseScript:
Installation log
The installation log is a text file that helps you debug your script. The log is the most
complete record of what the installation did. As your script runs on the destination
computer, each action it performs is logged in Install.log. This includes: failures of
actions to execute, the reasons for the failure, and what changes on your system.
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
See also:
About Troubleshooting a WiseScript
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
on page 129
on page 129
on page 129
Lets you determine what happens during the installation,
including what fails.
See Using the Installation Log
on page 35.
on page 129
on page 129.
129