WiseScript Editor Reference 154
Chapter 7
Troubleshooting WiseScripts
This chapter includes the following topics:
z About Troubleshooting a WiseScript on page 154
z Using the Installation Log on page 154
z File Replacement Problems in System32 on page 154
About Troubleshooting a WiseScript
Use the following features to troubleshoot a WiseScript:
Using the 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 on page 42.
File Replacement Problems in System32
Following are file replacement problems you might encounter:
z Files that you assign to the application directory or to the Windows directory
incorrectly install to the System or System32 directory.
z A later version of a system file does not replace an earlier version.
Installation log Lets you determine what happens during the installation,
including what fails.
See Using the Installation Log on page 154.
Compiler variables Let you build a debug version of your installation .EXE that
displays values of variables and other useful information
while it is executing. The compiler itself helps ensure
stability because it checks that all required information is
present before it builds an installation .EXE.
See Compiler Variables on page 17.
To Next Page
Loading...