Modify Component Size; Open/Close Install.log - Symantec WISESCRIPT EDITOR 7.0 SP2 - FOR NS V1.0 Manual

Hide thumbs Also See for WISESCRIPT EDITOR 7.0 SP2 - FOR NS V1.0:
Table of Contents

Advertisement

Modify Component Size

Open/Close Install.log

WiseScript Editor Reference
Retain Duplicates in Path
By default, version checking removes existing copies of .DLLs that are found in the
path list. To suppress this feature, mark this check box.
For files within the installation .EXE, the amount of required disk space is automatically
tracked. However, if you call external .EXEs that install more files, the space those files
require is not accounted for. Use this action to increase the amount of required disk
space. Then use the Check Disk Space action to make sure that enough space exists.
Use this action inside an If block that checks whether the affected component is being
installed. Example:
If COMPONENTS Contains Any Letters in "A" then
Modify Component Size: 1024
End
The COMPONENTS variable is populated with a letter of the English alphabet for each
component set to be installed, starting with A for the first component, B for the second,
and so on.
To complete the dialog box
Size (Kbytes)
Enter the amount of additional disk space to reserve.
Dest. Path
Enter the directory where the files will be installed (example:
%MAINDIR%\Pictures).
Use this action to create an installation log.
Normally, every file that is installed is recorded in the install.log. The uninstall works by
reading Install.log from bottom to top and reversing each recorded action.
The Open/Close Install.log action lets you customize the uninstall, by turning logging off
and on at key points to prevent some actions from being recorded in the log. If you use
this action to stop logging, you must also use it to resume logging or no log file is
created.
To complete the dialog box
Select one of the following options for each Open/Close Install.log action that you add to
the script.
Resume/Start writing entries into installation log
Pause writing entries into installation log
This must be followed, at some point, by another Open/Close Install.log action that
resumes writing, or no log file is created.
Open new installation log
Mark this to create an installation log. Then enter the complete path or just the file
name of the new log to the right (examples: %MAINDIR%\Speciallog.log or
76

Advertisement

Table of Contents
loading

Table of Contents