1. Manuals
  2. Brands
  3. Symantec Manuals
  4. Software
  5. WISESCRIPT EDITOR 8.0 - REFERENCE FOR WISE PACKAGE STUDIO...
  6. Reference

Symantec WISESCRIPT EDITOR 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference

Hide thumbs
Table of Contents

Advertisement

Quick Links

WiseScript Editor Reference

Advertisement

Table of Contents
loading

Related Manuals for Symantec WISESCRIPT EDITOR 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0

Summary of Contents for Symantec WISESCRIPT EDITOR 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0

  • Page 1 WiseScript Editor Reference...
  • Page 2 Copyright © 2009 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, and Altiris are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

  • Page 3: Technical Support

    The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates.
  • Page 4 Licensing and registration If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/techsupp/ Customer service Customer service information is available at the following URL: www.symantec.com/techsupp/ Customer Service is available to assist with the following types of issues:...
  • Page 5 Consulting Symantec Consulting Services provide on-site technical Services expertise from Symantec and its trusted partners. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment, design, implementation, monitoring, and management capabilities. Each is focused on establishing and maintaining the integrity and availability of your IT resources.

  • Page 6: Table Of Contents

    Contents Technical Support ............3 Chapter 1: Introduction .
  • Page 7 DLL Parameter Settings........... 47 Passing Complex Structures to a .DLL: An Example .
  • Page 8 Get Temporary Filename ........... . . 89 Get Windows Installer Property .
  • Page 9 Editing Dialog Boxes ........... . 120 Setting Dialog Box Properties.
  • Page 10 Command-Line Options ........... . . 165 WiseScript Command-Line Options .

  • Page 11: Chapter 1: Introduction

    Chapter 1 Introduction This chapter includes the following topics: About WiseScript on page 11 WiseScript Benefits on page 11 Starting the Software on page 12 The Product Interface on page 13 Using WiseScripts in a Windows Installer Installation on page 13 Compiling, Testing, and Running a WiseScript on page 14 Product Documentation...

  • Page 12: Starting The Software

    Introduction Built-in rollback WiseScripts can be rolled back after they are executed on the destination computer. User interface WiseScripts can incorporate any type of dialog box to either inform the end user or prompt for input. WiseScript is powerful In addition to the dozens of predefined actions, WiseScripts can call VBScripts and DLL functions, making it possible to use any Windows system call.

  • Page 13: The Product Interface

    Introduction To open an existing script, select Edit Existing WiseScript from the button menu. You can begin to add or edit script actions. For information on adding script actions, see Adding an Action to a Script on page 25. For a description of each script action, see About WiseScript Actions on page 39.

  • Page 14: Compiling, Testing, And Running A Wisescript

    Introduction Evaluate Windows Installer Condition on page 76. The disadvantage of using a WiseScript .EXE is that Windows Installer does not know about or manage system changes performed by a WiseScript .EXE (example: installation of a file). See Uninstalling Changes Made by a WiseScript in the Windows Installer Editor Help. Compiling, Testing, and Running a WiseScript To test an installation, use the Compile, Test, and Run buttons at the bottom of the main window.

  • Page 15: Product Documentation

    The product release notes cover new features, enhancements, bug fixes, and known issues for the current version of this product. To access the release notes, select Release Notes from the Symantec program group on the Windows Start menu. WiseScript Editor Reference...

  • Page 16: Chapter 2: Project Settings For Script Support

    Chapter 2 Project Settings for Script Support This chapter includes the following topics: About Project Settings on page 16 About the Project Settings View on page 16 Compiler Variables on page 17 Digital Signature on page 19 General Information on page 20 About Project Settings Several script actions require information that is defined outside Script Editor.

  • Page 17: Compiler Variables

    Project Settings for Script Support Page Groups Page Area View Navigation Compile, Test, and Run Page Area When you click a page name in a page group, this area displays the page’s options. Each page lets you define information that is required by a specific script action. Use ( ) on the toolbar to navigate from page to page, or click the page name in the list of pages.
  • Page 18 Project Settings for Script Support Compiler variables are surrounded by % characters in the script. (Example: %_DEBUG_%) You can change the value of compiler variables when you compile. The sample script Compvar.wse uses compiler variables. For details on sample scripts, see ScriptHelp.htm in the Samples subdirectory of this product’s installation directory.

  • Page 19: Digital Signature

    Project Settings for Script Support See also: Automatic Compiler Variables on page 156 Digital Signature Use the Digital Signature page to add an Authenticode digital signature to an installation file so its integrity and authenticity can be verified. Digital signature methods The file signing tool that is used to digitally sign a file depends on the type of your digital certificate: Public/private key pair files...

  • Page 20: General Information

    Project Settings for Script Support Web URL Enter your company’s Web site address. Descriptive Name Enter the name of your application. This name is embedded in your Authenticode certificate to let end users verify the name of the application they are installing.

  • Page 21: Chapter 3: Using Script Editor

    Chapter 3 Using Script Editor This chapter includes the following topics: About Script Editor on page 21 The Script Editor Window on page 21 Types of Scripts on page 24 Adding an Action to a Script on page 25 Editing Scripts on page 25 About User-Defined Actions on page 27...
  • Page 22 Using Script Editor Event and Title Language drop- down lists Script list Actions list Tabs for the main script and each include script or VBScript View Navigation Compile, Test, and Run Title This field contains the script’s name. When you run the installation, this name appears at the top of the splash dialog box (the Initializing Wise Installation wizard dialog box), and in the title bar of the installation screen.

  • Page 23: Customizing The List Of Actions

    Using Script Editor while the Custom group is by default empty. You can also create your own action groups. Customizing the List of Actions on page 23. Script List This list contains the script that is executed when an end user runs the .EXE. For information on working with scripts, see Adding an Action to a Script on page 25 and...

  • Page 24: Types Of Scripts

    Using Script Editor To edit an action group Click the title bar of the action group. You cannot edit or remove the All Items group. Right-click below the action group title bar and select Add/Remove Items. The Select Items for Group dialog box appears. Add, delete, or move group items and click OK.

  • Page 25: Adding An Action To A Script

    Using Script Editor Execute VBScript on page 77. VBScripts can be included either in the main installation script or in include scripts. At run time, VBScripts are run when the Execute VBScript action that references them is encountered. For each Execute VBScript action in a WiseScript, a new tab appears at the bottom of the Installation Script pane.

  • Page 26: Finding And Replacing Text In A Script

    Using Script Editor Copying and Pasting Script Lines Select one or more script lines. Select Edit menu > Cut or Copy. If you’re copying the lines to another installation, open that installation script in Script Editor. You cannot open multiple scripts in the same instance of WiseScript Editor unless it is an include script or VBScript.

  • Page 27: About User-Defined Actions

    Using Script Editor You can replace a command’s parameters and editable text, but not the command itself. To search for the text across all WiseScripts, mark Search Across Include Scripts. For information on include scripts, see Customizing the List of Actions on page 23.

  • Page 28: Creating A User-Defined Action

    Using Script Editor Adding an Action to a Script on page 25 Creating a User-Defined Action This procedure describes the general steps for creating a user defined action. It does not contain details on what kind of action to create, or what to enter for the parts of the user-defined action.

  • Page 29: Creating A User-Defined Action: Tutorial

    Using Script Editor Open WiseScript Editor and select File menu > New > Empty Project. In Script Editor, double-click your user-defined action in the Actions list. If it includes a dialog box, the dialog box opens. Complete the dialog box and click Save the project and click Test to test your script.
  • Page 30 Using Script Editor The Push Button Control Settings dialog box appears. Enter the following on the dialog box and click OK. In Label, enter OK Mark the Return to Previous Dialog action. Mark Default Button. 10. Click the Push Button tool on the toolbar again. The Push Button Control Settings dialog box appears.

  • Page 31: Basic Scripting Concepts

    Using Script Editor Click OK on the DLL Parameter Settings dialog box. Click OK on the Call DLL Function dialog box. In Title (located above the Actions list), enter “Wait %WAIT_TIME% Milliseconds.” This determines how the script line looks in the script. Save the script.

  • Page 32: Conditions And Loops

    Using Script Editor Conditions and Loops on page 32 Variables and Expressions on page 33 Compiler Variables and Run-time Variables on page 34 Anatomy of an Installation Script on page 35 Conditions and Loops Normally, script actions are executed in the order in which they appear in the script. However, the order of execution can be changed by special script actions called conditions and loops.

  • Page 33: Variables And Expressions

    Using Script Editor Variables and Expressions Variables Variables are named storage locations that hold information about the system, information entered by the end user, or information derived or calculated from either of these sources. You can define up to 400 variables using the Set Variable action. You can then gather data from the end user or read data from files to put into variables.

  • Page 34: Compiler Variables And Run-Time Variables

    Using Script Editor Compiler Variables and Run-time Variables When They Are Set WiseScript uses two kinds of variables: compiler and run-time. When you start a compile by clicking the Compile, Test, or Run button, the values of compiler variables are set immediately, either by prompting you or by reading the values from the Compiler Variables page.

  • Page 35: Anatomy Of An Installation Script

    Using Script Editor compiler variable conditions, you can easily remove them when the installation has been debugged by changing the value of a compiler variable. The debugging actions are not compiled into the final build. When to Use Variable substitution can use either type of variable. When a script action places a value into a variable, use a run-time variable.

  • Page 36: Chapter 4: Wisescript Actions

    Chapter 4 WiseScript Actions This chapter includes the following topics: About WiseScript Actions on page 39 About SVS Script Actions on page 39 Activate SVS Layer on page 40 Add Directory to PATH on page 41 Add File to SVS Layer on page 41 Add Text to INSTALL.LOG on page 42...
  • Page 37 WiseScript Actions Custom Dialog on page 66 Deactivate SVS Layer on page 66 Delete File from SVS Layer on page 66 Delete File(s) on page 67 Delete SVS Layer on page 67 Display Billboard on page 68 Display Message on page 69 Display Progress Message on page 70 Display Text File...
  • Page 38 WiseScript Actions Insert Line Into Text File on page 92 Install File(s) on page 93 Install SVS Package on page 95 Install Windows Mobile Application on page 98 Install WiseUpdate Client on page 95 Modify Component Size on page 98 Open/Close Install.log on page 99 Parse String...

  • Page 39: About Wisescript Actions

    SVS Items title bar. For more information about Software Virtualization Solution (SVS), search for Workspace Virtualization on the symantec.com Web site. Script Actions for Managing a Layer Use these script actions to change the state of layers, gather information about layers, create archive files from layers, and install and remove layers.

  • Page 40: Activate Svs Layer

    WiseScript Actions when the layer is reset. The exception is the Delete File from SVS Layer action that makes changes to the writeable sublayer. The Remove SVS Exclude Entry and Set SVS Exclude Entry actions set or remove an exclude entry for a single layer or for all layers on a computer. Add File to SVS Layer Capture Application to SVS Layer Change SVS Layer GUID...

  • Page 41: Add Directory To Path

    WiseScript Actions To complete the dialog box Layer GUID Enter the layer’s GUID (globally unique identifier) or a variable that represents the layer’s GUID. If you enter the layer’s GUID, do not include the { } brackets. For information on creating a variable for a layer’s GUID, see Create SVS Layer page 65 and Find SVS Layer GUID...

  • Page 42: Add Text To Install.log

    WiseScript Actions SVS variables or WiseScript variables that resolve to a valid SVS path. Example: [PROGRAMFILES]\Application\Readme.txt. SVS Variables on page 161. Return variable (Optional.) Enter a name for the return variable. When this script action runs successfully, either 0 or 1 is placed in this variable. See also: About SVS Script Actions on page 39...

  • Page 43: Add To Autoexec.bat

    WiseScript Actions If you want the uninstall to remove not only files that were installed, but also files that were added later, you can remove all the files and sub-directories within a specified directory. Use this option with caution because end users might have stored their own files in the directory.

  • Page 44: Add To Config.sys

    WiseScript Actions Insert Action Select where to insert the new line in relation to the found line. Match Criteria Select how the found line matches the Search for Text. Ignore White Space Mark this to ignore spaces and tab characters. Case Sensitive Mark this to match case.

  • Page 45: Add To System.ini

    WiseScript Actions Make Backup File Mark this to make a copy of Config.sys before editing it. Add to SYSTEM.INI (Windows 3.1x or Windows 9x only) This action adds a device entry to the 386Enh section of the System.ini file. The destination computer is restarted automatically to force the new device driver to be loaded.

  • Page 46: Call Dll Function

    WiseScript Actions Call DLL Function This action calls a .DLL function from a .DLL on the destination computer. They can be be .DLLs you have written, .DLLs developed for WiseScript, or Windows .DLLs. You can branch the script based on the returned results of a .DLL by setting the Action to Start Block if Return Value True or Start While Loop.

  • Page 47: Dll Parameter Settings

    WiseScript Actions Start block if function returns true If the .DLL function returns non-zero, all actions between this action and its matching End action are executed. Otherwise these actions are skipped. Loop while function returns true The actions between this action and the matching End action (including the .DLL call) are executed repeatedly until the .DLL function returns zero.
  • Page 48 WiseScript Actions To complete the dialog box Parameter Type Check the table below for alternate names for data types. WiseScript Corresponds to Win32 Corresponds to Description SDK type Visual Basic type short SHORT Integer 16-bit, signed integer data type word WORD Integer 16-bit, unsigned integer data type...

  • Page 49: Passing Complex Structures To A .Dll: An Example

    WiseScript Actions and select Contained within structure for all subsequent elements of the structure. You do not pass the structure name, just the elements inside it. Passing Complex Structures to a .DLL: An Example on page 49 Value Source Select the type of value to be passed: Variable (pass by reference), constant (pass by value), constant with null value, or constant with window handle (pointing to the installation window).

  • Page 50: Capture Application To Svs Layer

    WiseScript Actions To call the function NewEmployee from an installation script, you add six parameters in the Call DLL Function dialog box: the three elements of the first structure, the integer, and the two elements of the second structure. To add parameters, see DLL Parameter Settings on page 47.

  • Page 51: Change Svs Layer Guid

    WiseScript Actions Parameters (Optional) Enter parameters for running the .EXE. If you specified .msiexec.exe in Program path, use Windows Installer command-line options. You can use these command-line options to create a WiseScript that captures an application by performing a silent installation of an .MSI. Example: /package “C:\Application.msi” / Return variable (Optional.) Enter a name for the return variable.

  • Page 52: Check Disk Space

    WiseScript Actions To complete the dialog box If System Use the drop-down lists to build a statement of what to check for. Note When you check for an operating system, this action looks for the minimum operating system of the type for which you’re checking. Example: If you check for Windows XP, this action returns TRUE if Windows XP or later is running.
  • Page 53 WiseScript Actions To complete the dialog box Component Variable(s) If a WiseScript installs files based on whether a component in the .MSI is set to be installed, specify the name of the variable that contains the list of components that are set to be installed.

  • Page 54: Check Http Connection

    WiseScript Actions Add an Evaluate Windows Installer Condition action that determines whether the Plus feature is to be installed ($Plus.exe = 3) and places the result into the variable CHECK. Add an If Statement action that determines if the variable CHECK equals 1, that is, if it is to be installed, and add a Set Variable action that then sets the variable COMPONENTS to the value Plus.exe.

  • Page 55: Check If File/Dir Exists

    WiseScript Actions Note If the Web server redirects URLs that are not valid to another internal Web page, no error is detected by this action. To complete the dialog box URL to Check Include “http://” in the URL. Win32 Error Text Variable Select or enter a variable to store the error text returned by the 32-bit winsock.dll.

  • Page 56: Check In-Use File

    WiseScript Actions Display Message Only Abort Installation Start Block Begins a conditional block. All actions between this action and the next Else or End action are executed. Start While Loop Begins a loop block. All actions between this action and the next End action are executed repeatedly as long as the condition is true.

  • Page 57: Compiler Variable Actions

    WiseScript Actions Compiler Variable Actions Compiler Variable If, Else, and End actions are used in an If block to let you compile different versions of an installation. You set the value of a compiler variable at compile time, and the actions inside a compiler variable If block are added to the script according to the value of the compiler variable You create compiler variables on the Compiler Variables page.

  • Page 58: Config Odbc Data Source

    WiseScript Actions See also: Compiler Variables and Run-time Variables on page 34 Config ODBC Data Source This action configures an ODBC data source for use with an existing ODBC (Open Database Connectivity) driver. To complete the dialog box Data Source Name This name will be displayed in the ODBC data sources list on the destination computer.
  • Page 59 WiseScript Actions If you want the progress bar to update correctly, specify a directory in Source without wildcards (example: %INST%\Pictures\), a directory in Destination, and a directory ending with a wildcard in Local Path (example: C:\My Pictures\*.jpg). The Source field will pick up the wildcard specified in Local Path.

  • Page 60: Create Directory

    WiseScript Actions Always The new file always replaces the old file. Never The file never overwrites an existing file. Select this for files that should be installed if they are not present, but that might be customized by the end user and should therefore not be replaced on re-installation (example: configuration files).

  • Page 61: Create Directory In Svs Layer

    WiseScript Actions To complete the dialog box Pathname Enter the directory path to create. Start the path with a variable (example: %MAINDIR%). Create Directory in SVS Layer This SVS script action creates a directory in a virtual software layer. You can create a directory in an existing layer or in the layer that the WiseScript creates.

  • Page 62: Create Shortcut

    WiseScript Actions Display Name Enter the name to appear in the Services control panel. Executable Path Specify the complete path to the executable file as it will be on the destination computer. Start the path with a variable (example: %MAINDIR%). Login Username, Login Password Enter the user name and password under which the service should run.
  • Page 63 WiseScript Actions When a WiseScript is called by a Windows Installer installation, you also can create a shortcut on the Features or Components tabs of Setup Editor in Windows Installer Editor. Note When a WiseScript is called by a Windows Installer installation, the Windows Installer installation does not recognize changes that the WiseScript makes to the destination computer and will not uninstall them.

  • Page 64: Create Shortcut In Svs Layer

    WiseScript Actions Create Shortcut in SVS Layer This SVS script action creates a shortcut in the virtual software layer. The shortcut can reference a program outside the layer. Common locations for shortcuts include the Start menu, the Startup directory, the installation directory, and the desktop. Note Use this action on a deactivated SVS layer only.

  • Page 65: Create Svs Layer

    WiseScript Actions See also: About SVS Script Actions on page 39 Create SVS Layer This SVS script action creates an empty virtual software layer. You can then use the Capture Application to SVS script action to add an application to the layer, or use other SVS script actions to add directories, files, registry keys, and shortcuts to the layer.

  • Page 66: Custom Dialog

    WiseScript Actions Custom Dialog Use this action to create your own dialog box or dialog box set. See About Dialog Boxes on page 119. To add a new dialog box within a wizard loop, see Adding a Dialog Box to the Installation on page 120.

  • Page 67: Delete File(S)

    WiseScript Actions File path Enter the path and file name of the file to delete. You can use SVS variables or WiseScript variables that resolve to a valid SVS path. SVS Variables on page 161. Return variable (Optional.) Enter a name for the return variable. When this script action runs successfully, either 0 or 1 is placed in this variable.

  • Page 68: Display Billboard

    WiseScript Actions To complete the dialog box Layer GUID Enter the layer’s GUID (globally unique identifier) or a variable that represents the layer’s GUID. If you enter the layer’s GUID, do not include the { } brackets. For information on creating a variable for a layer’s GUID, see Create SVS Layer page 65 and Find SVS Layer GUID...

  • Page 69: Display Message

    WiseScript Actions Hide Progress Bar Mark this to hide the progress bar during graphic display. Center Vertical Place at Bottom Tile Background Mark this to repeat the graphic edge-to-edge to fill the entire screen. Erase All Mark this to remove all previous graphics from the screen before displaying the new one.

  • Page 70: Display Progress Message

    WiseScript Actions The sample scripts CheckDiskSpace.wse and Search.wse use this action. For details on sample scripts, see ScriptHelp.htm in the Samples subdirectory of this product’s installation directory. Display Progress Message This action displays a small dialog box during installation, typically to indicate the computer is still working during a long operation.

  • Page 71: Edit Ini File

    WiseScript Actions Edit INI File This action edits an .INI file on the destination computer. To edit SYSTEM.INI, use the Add to SYSTEM.INI action instead. When a WiseScript is called by a Windows Installer installation, you also can edit an .INI file on the Features or Components tabs of Setup Editor in Windows Installer Editor.

  • Page 72: Registry Key Settings Dialog Box

    WiseScript Actions To complete the dialog box Registry Keys This field shows root registry keys and the keys added by this action. Select a root before adding or importing a key. Value Names This field shows values being added or changed that reside under the key selected on the left.
  • Page 73 WiseScript Actions Create/update key and value The value is updated if it already exists. If the key or value does not exist, it is created. Create empty key Creates the key but does not add any values. Remove key and all subkeys Deletes the key, its subkeys, and all named values associated with the key and its subkeys on the destination computer.

  • Page 74: Edit Registry For Svs Layer

    WiseScript Actions Double Word (REG_DWORD prefix) Identifies a value entry as a 32-bit (DWORD) entry. Binary/Hex (REG_BINARY prefix) Identifies a value entry as binary. Each byte should be separated by at least one blank space. For instance: AD 30 C0 A9 40 20 A8 FC 4C 00 08.

  • Page 75: Else Statement

    WiseScript Actions New Value To add a new value, select the parent key in Registry Keys, then click the New Value button. A dialog box appears, where you enter information about the new value. Delete Value Removes the selected value from the current installation. This does not remove it from the destination computer.

  • Page 76: End Statement

    WiseScript Actions The variable is ignored and can be left blank. The result is considered true if it evaluates to a non-zero result. Valid Password and Invalid Password evaluate according to the password that is entered on the Passwords page. (The password comparisons are not applicable in this product.) The Value Enter the value to be used in the comparison, or an expression if the comparison is...

  • Page 77: Execute Program

    WiseScript Actions Execute Program This action runs another .EXE. The .EXE can be a file that is already installed on the destination computer, a file you installed as part of the installation, or a file you provide on a separate disk. When a WiseScript is called by a Windows Installer installation, you can also use the Execute Program custom actions in MSI Script in Windows Installer Editor.

  • Page 78: Editing A Vbscript

    WiseScript Actions VBScript (example: arrays and subfunctions). Adding VBScripts can also save you time because you can use scripts that others have created. For each VBScript action in a script, a new tab appears at the bottom of the Installation Script pane.

  • Page 79: Vbscript Actions

    WiseScript Actions Display Options Use the buttons and drop-down list at the top of the Installation Script pane to display different portions of the VBScript. Event View Click this button and select a method from the drop- down list to display one method at a time. Full Module View Click this button to display the entire script.

  • Page 80: Calling A Com Object In A Vbscript

    WiseScript Actions Call COM Object Use this action to create a script to call a COM object in the VBScript. You can manually enter the script to call a COM object, but the Call COM Object action facilitates this process by providing information about the COM objects. If the object is registered on your computer, this action can provide the following functionality: The object appears in the List Objects drop-down list that is accessed from the right-click menu.

  • Page 81: Exit Installation

    WiseScript Actions appears. In the VBScript, you can call a COM object and then use the functions and properties that are exposed by this object. To call a COM object in a VBScript Use the Execute VBScript action to add a VBScript to the WiseScript. Execute VBScript on page 77.

  • Page 82: Export Svs Layer

    WiseScript Actions No message appears unless you also set the RESTART variable. Automatic Run-time Variables on page 157. Note When a WiseScript is called by a Windows Installer installation, this does not exit the MSI installation. It only exits the WiseScript .EXE. To complete the dialog box Application Exit Code If this script is called by another application, this is the return code to the calling...

  • Page 83: Find First Svs Layer

    WiseScript Actions To complete the dialog box File Name Enter just the file name, not a full path. Wildcard characters (*, ?) are not allowed. Variable Name Enter a variable in which to store the path of the file if it is found. If the file is not found, this variable stores the Default Value specified below.

  • Page 84: Find Svs Layer Guid

    WiseScript Actions To complete the dialog box Layer GUID Variable Enter a name for a variable in which to place the layer’s GUID. Return variable (Optional.) Enter a name for the return variable. When this script action runs successfully, either 0 or 1 is placed in this variable. See also: About SVS Script Actions on page 39...

  • Page 85: Get Name/Serial Number

    WiseScript Actions %COMMAND% in the EXE Path field. Specify the file to open in the Command Line field. Add the /c command-line option to cause the command-line window to close when your program finishes execution. Get Name/Serial Number This action displays a dialog box that requests the end user’s name, company name, and a product serial number.

  • Page 86: Get Svs Layer Info

    If the layer is deactivated when the computer starts, 1 is placed in this variable. If the layer is activated when the computer starts, 2 is placed in this variable. Layer Name Variable The name of the layer as it appears in the Symantec SVS applet is placed in this variable. Layer Type Variable If the layer is read-only, 0 is placed in the variable.

  • Page 87: Get System Information

    WiseScript Actions Reg Redir Path Variable The registry redirect path where the layer’s registry keys are stored is placed in this variable. Creation, Activate, and Reset Time Variables The time the layer was created, activated, or reset is placed in these variables. The time is reported as the number of seconds since midnight (00:00:00), January 1, 1970.
  • Page 88 WiseScript Actions First Network Drive The letter of the first network drive, followed by a colon If there are no network drives, the response is blank. First CD-ROM Drive The letter of the first CD-ROM drive, followed by a colon. If there is no CD-ROM drive, the response is blank.

  • Page 89: Get Temporary Filename

    WiseScript Actions Pathname Use this field only for operations that retrieve information on files or directories. Specify the full path of the file or directory to retrieve information from. You can use variables (example: %MAINDIR%\Readme.txt). You also can enter a hardcoded path (example: C:\Program Files\File.exe) but it is not recommended.

  • Page 90: If Statement

    WiseScript Actions To complete the dialog box Message Text Enter a message to display to the user if the compile is stopped. Example: You develop a script that uses runtime files. On your own computer, you have the correct runtime files to pull into the installation. However, you want to prevent compilation on other computers if they lack correct runtime files because the resulting installation could damage runtime installations on destination computers.

  • Page 91: Import Svs Layer

    WiseScript Actions See also: Else Statement on page 75 ElseIf Statement on page 75 End Statement on page 76 Import SVS Layer To complete the dialog box Archive path Specify the path and file name for the archive file. You can use WiseScript variables. GUID variable (Optional) Enter a name for a variable in which to place the layer’s GUID.

  • Page 92: Initialize Svs

    WiseScript Actions Include Script C:\Scripts\OpensWord.wse Example of what a short include script might look like: Execute %PROGRAM_FILES%\winword.exe Initialize SVS This action initializes the SVS Driver (Software Virtualization Agent) so that you can communicate with it. It takes no parameters, and selecting it from the Action list inserts it directly into the script with no further dialog boxes or prompts.

  • Page 93: Install File(S)

    WiseScript Actions Ignore White Space Mark this to ignore spaces and tab characters. Case Sensitive Mark this to make the match case-sensitive. Make Backup File Mark this to make a copy of the text file before editing it. A number is appended to the end of the file name for the backup copies (example: text.001, text.002, and so on).
  • Page 94 WiseScript Actions The password prompt appears only once, for the first password-protected file in an installation, regardless of the number of password-protected files. If no password- protected files are slated for installation, the prompt does not appear. Include Sub-Directories If you specify a directory in Source Pathname, mark this to include all subdirectories and their contents.

  • Page 95: Install Svs Package

    WiseScript Actions 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. Install SVS Package This action installs a Virtual Software Package (VSP) on a destination computer. You can use this action to create a WiseScript that installs any number of VSPs.

  • Page 96: About Windows Mobile Installations

    WiseScript Actions Note The host must be accessible through both FTP and HTTP. You use an FTP client to transfer files to it, and WiseUpdate Client (on the destination computers) uses HTTP to read and download files. Sever Username, Server Password If necessary, enter the user name and password that are required to connect to the server.

  • Page 97: Process For Adding Mobile Device Support To A Wisescript

    WiseScript Actions keys, and shortcuts) that comprise the application. The Setup.dll file provides functions for performing certain operations during the installation and removal of your application. Mobile device .CAB files are generated by the CabWiz program from an information file (.INF).

  • Page 98: Install Windows Mobile Application

    WiseScript Actions About Windows Mobile Installations on page 96 Install Windows Mobile Application on page 98 Install Windows Mobile Application This action adds mobile device support for the Microsoft® Windows Mobile™ platform for Pocket PC and Smartphone devices. Use it to configure a WiseScript to install files that support a Windows Mobile device application.

  • Page 99: Open/Close Install.log

    WiseScript Actions If COMPONENTS Contains Any Letters in “A” then Modify Component Size: 1024 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.

  • Page 100: Parse String

    WiseScript Actions Parse String This action splits a text string and places the results in two variables. You can split the string at a character or substring that you specify, which discards the character or substring you specified. Example: If you split the string “ONE,TWO” at the first occurrence of a comma, “ONE”...

  • Page 101: Play Multimedia File

    WiseScript Actions Play Multimedia File This action plays an audio (.WAV) or video (.AVI) file during installation. Playback is asynchronous, which means the sound or movie can play while the installation continues. The multimedia file must be installed on the destination computer before this action is called.

  • Page 102: Prompt For Filename

    WiseScript Actions Error Handling Specify how to handle errors in the posting operation. Ignore Errors The script continues regardless of any errors. Abort Installation The installation stops if the post cannot be completed. Start Block The Post to HTTP Server action begins a conditional block. The statements between this action and the next End statement are executed only in the event of an error.

  • Page 103: Prompt For Text

    WiseScript Actions Skip write permissions test If you selected Save As for Dialog Type, and you clear this check box, the installation tries to create the file that the end user specified in the Save As dialog box to verify write permissions. If you mark this check box, the installation does not try to create the file.

  • Page 104: Read Ini Value

    WiseScript Actions Dest. Variable Enter a variable to store the letters corresponding to the button the end user clicks.The button clicked by the end user is returned as a letter: A for the first radio button, B for the second, and so on. If the script sets this variable to a letter before this action runs, the corresponding button appears selected by default.

  • Page 105: Read/Write Binary File

    WiseScript Actions To complete the dialog box Pathname Specify the full path to the text file to be edited on the destination computer (example: %WIN%\Sample.txt). Variable Specify the variable in which to store each line of the text file (example: TEXTLINE). Action Select an action: Read lines of file into variable...

  • Page 106: Reboot System

    WiseScript Actions Max. Length Enter the maximum number of bytes to be written to or read from the file. When writing, if the length of the variable exceeds this value, the string is truncated. When reading, any trailing spaces are trimmed. Transfer Direction Select whether to write to or read from the file.

  • Page 107: Remove Svs Exclude Entry

    WiseScript Actions Remove SVS Exclude Entry This SVS script action removes an SVS exclude entry on the destination computer. You can remove a layer exclude entry or a global exclude entry. A layer exclude entry applies to a specific layer on a computer, while a global exclude entry applies to every layer on a computer.

  • Page 108: Rename File Or Directory In Svs Layer

    WiseScript Actions New File Name Enter the new file name or directory name (examples: picture2.jpg or Photos). Rename File or Directory in SVS Layer This SVS script action renames a file or directory a virtual software layer. This can be an existing file or directory, or a file or directory that the WiseScript installs.

  • Page 109: Search For File

    WiseScript Actions New name Enter the new name for the virtual software layer. Return variable (Optional.) Enter a name for the return variable. When this script action runs successfully, either 0 or 1 is placed in this variable. See also: About SVS Script Actions on page 39 Search for File...

  • Page 110: Self-Register Ocxs/Dlls

    WiseScript Actions The sample script Search.wse uses this action. For details on sample scripts, see ScriptHelp.htm in the Samples subdirectory of this product’s installation directory. Self-Register OCXs/DLLs Use this action to self-register all queued .OCX, .DLL, and .EXE files or to add an existing file to the queue.

  • Page 111: Set Control Text

    WiseScript Actions To access this action Double-click a Custom Dialog script line. The dialog box appears in the Custom Dialog Editor. Select View > Dialog Script Editor. A smaller list of actions appears in the Actions list, including this action. Double-click Set Control Attributes.

  • Page 112: Set Current Control

    WiseScript Actions Set Current Control This action appears only when you are in a dialog box script. This action sets a control to be the current control in a dialog box. The current control is the one to which keyboard operations apply. (Example: If the OK button is the current control, and you press Enter, the OK button is activated.) Controls without names cannot be manipulated with this action.

  • Page 113: Set Svs Exclude Entry

    WiseScript Actions To complete the dialog box Minimum Files The minimum number of files to be specified by FILES= in Config.sys. Set this to zero or leave blank to leave FILES= unchanged. Minimum Buffers The minimum number of buffers to be specified by BUFFERS= in Config.sys. Set this to zero or leave blank to leave BUFFERS= unchanged.
  • Page 114 WiseScript Actions To complete the dialog box Variable Specify a variable. A variable name must begin with a letter, must contain only numbers, letters, and underscore characters, and must be 28 characters or less. It should not be enclosed in % signs. New Value Enter the new value of the variable.

  • Page 115: Set Web Permissions

    WiseScript Actions Set Web Permissions This script action sets permissions for an existing virtual directory of a Web site or a virtual directory that you create with the Create Virtual Directory script action. Create Virtual Directory on page 65. To complete the dialog box Computer Enter the name of the computer where the Web site resides.

  • Page 116: While Statement

    WiseScript Actions When a WiseScript is called by a Windows Installer installation, you can also start and stop services by using the Services page in Windows Installer Editor. After you try to stop a service, the script pauses to give the service time to stop. The currently logged-in end user must have the appropriate privileges to start and stop services.

  • Page 117: Win32 System Directory

    WiseScript Actions Below the While Statement, add one or more actions to perform if the variable has the specified value. Add an End Statement. The sample scripts Division.wse and Application kill.wse use this action. For details on sample scripts, see ScriptHelp.htm in the Samples subdirectory of this product’s installation directory.
  • Page 118 WiseScript Actions variable is ignored and can be left blank. The result is considered true if it evaluates to a non-zero result. (The password comparisons are not applicable in this product.) WiseScript Editor Reference...

  • Page 119: Chapter 5: Creating Custom Dialog Boxes

    Chapter 5 Creating Custom Dialog Boxes This chapter includes the following topics: About Dialog Boxes on page 119 About the Custom Dialog Editor on page 119 About Dialog Box Controls on page 121 Solutions for Dialog Box Problems on page 140 About Custom Dialog Box Sets on page 142 Creating a Custom Dialog Box Script...

  • Page 120: Adding A Dialog Box To The Installation

    Creating Custom Dialog Boxes Adding a Dialog Box to the Installation When you add a dialog box, the dialog box is empty, and nothing is preconfigured. You must design and configure it yourself. To create a new dialog box In Script Editor, double-click the Custom Dialog script action in the Actions list. The Dialog Box Properties dialog box appears.

  • Page 121: About Dialog Box Controls

    Creating Custom Dialog Boxes Editing Dialog Boxes on page 120. Select Edit menu > Dialog Box Properties. The Dialog Box Properties dialog appears. (This dialog box also appears when you click Add on the Dialogs page.) Complete the dialog box: Dialog Title Enter the title for the dialog box.

  • Page 122: Adding And Editing Dialog Box Controls

    Creating Custom Dialog Boxes Graphic A non-editable bitmap graphic. Adding Graphic Controls on page 127. Group Box A boundary box drawn around related controls. Adding Group Box Controls on page 128. Hot Text Text that you can link to actions or a Web page. Adding Hot Text Controls on page 129.

  • Page 123: Adding Check Box Controls

    Creating Custom Dialog Boxes For information about the settings dialog box for each control, see About Dialog Box Controls on page 121. Click OK to add the new control to the dialog box. You can resize and move the control using its handles. To select multiple controls, use Shift+click.

  • Page 124: Adding Combo Box Controls

    Creating Custom Dialog Boxes Note A dialog unit is based on the size of the dialog font, usually 8-point MS Sans Serif. A horizontal dialog unit is 1/4 the average width of the font and a vertical dialog unit is 1/8 the average height of the font. Width / Height Specify the exact dimensions of the control in dialog units.
  • Page 125 Creating Custom Dialog Boxes Auto HScroll Mark this to scroll the text entry field horizontally if more text is entered than fits. ProgMan Groups Mark this to have the items in the Programs group of the Windows Start menu appear in the combo box. Drive List Mark this to display the end user’s available drives in the combo box.

  • Page 126: Adding Edit Text Controls

    Creating Custom Dialog Boxes Note A combo box field should be at least as wide as the longest option in the list. Adding Edit Text Controls An edit text control lets the end user enter and edit text information. You can also use it to display text (example: license agreements or ReadMe files).

  • Page 127: Adding Graphic Controls

    Creating Custom Dialog Boxes Border Mark this to include a border around the edit field. Uppercase / Lowercase Mark one of these check boxes to convert all entered characters to a different case. Read Only Mark this to prevent end users from entering data into the field. Tab Stop Mark this to let end users use the Tab key to give focus to this field.

  • Page 128: Adding Group Box Controls

    Creating Custom Dialog Boxes Select Add menu > Graphic in the Custom Dialog Editor. The Graphic Control Settings dialog box appears. Complete the dialog box: Graphic Pathname Specify the path for the bitmap graphic to add to the dialog box. Control Name Enter the name by which you will refer to this control in the dialog box script.

  • Page 129: Adding Hot Text Controls

    Creating Custom Dialog Boxes X-Position / Y-Position Specify the exact location of the control on the dialog box. You can also use the alignment commands to precisely arrange controls on the dialog box. Aligning and Spacing Dialog Box Controls on page 139. Note A dialog unit is based on the size of the dialog font, usually 8-point MS Sans Serif.
  • Page 130 Creating Custom Dialog Boxes Display Dialog Displays the selected dialog box from the current set. Abort Installation The end user is asked to confirm that the installation should be aborted. Display Help Context If the HELPFILE variable points to a valid copy of a Windows help file, the specified numeric help context is displayed.

  • Page 131: Adding List Box Controls

    Creating Custom Dialog Boxes Adding List Box Controls A list box is a list of values from which the end user can choose. The control can return either the actual string the end user selected, or its position in the list as a letter. If it returns letters, it returns A if the first item is selected, B if the second item is selected, and so on.

  • Page 132: Adding Play Avi Controls

    Creating Custom Dialog Boxes Return Letters Mark this to cause the control to return a list of letters representing the item selected (that is, A for the first, B for the second, etc.) rather than the item text itself. Don’t Append Mark this to not append the “Program Files”...

  • Page 133: Adding Push Button Controls

    Creating Custom Dialog Boxes Control Name Enter the name by which you will refer to this control in the dialog box script. Leave this blank if you will not manipulate this control with a script. X-Position / Y-Position Specify the exact location of the control on the dialog box. You can also use the alignment commands to precisely arrange controls on the dialog box.
  • Page 134 Creating Custom Dialog Boxes Action Select an action for the control: Return to Previous Dialog Displays the previously-displayed dialog box in the dialog box set. (Exception: The Back buttons on wizard dialog boxes do not use this option. They are controlled by the Wizard Loop script action.) If this is the first dialog box in the set, it returns to the installation script.

  • Page 135: Adding Radio Button Controls

    Creating Custom Dialog Boxes The sample script Event Handler.wse uses scripting to handle push button controls. For details on sample scripts, see ScriptHelp.htm in the Samples subdirectory of this product’s installation directory. Adding Radio Button Controls A group of radio buttons is considered a single control. The end user can select only one button from the group.

  • Page 136: Adding Rectangle Controls

    Creating Custom Dialog Boxes Width / Height Specify the exact dimensions of the control in dialog units. You can also resize controls by dragging their handles, though this is not as precise. Click OK. The sample script License Agreement.wse uses scripting to handle radio button controls. For details on sample scripts, see ScriptHelp.htm in the Samples subdirectory of this product’s installation directory.

  • Page 137: Adding Text Controls

    Creating Custom Dialog Boxes Adding Text Controls Use text controls to display information on a dialog box. Text controls are static controls, which means that the end user cannot change them. Open the dialog box in the Custom Dialog Editor. Editing Dialog Boxes on page 120.

  • Page 138: Specifying Execute Program Settings

    Creating Custom Dialog Boxes Components This variable represents the Disk Space Required by the selected component set. Select the COMPONENTS variable, as it calculates the total space requirements for the currently-selected component set. Disk This variable represents the Disk Space Remaining on the installation drive. Select the MAINDIR variable, as it keeps track of free space in the installation directory.

  • Page 139: Aligning And Spacing Dialog Box Controls

    Creating Custom Dialog Boxes Variables Added Any script variables that were added by the executable program using a DDE link are displayed. Note This field is retained for backward compatibility only. Window Size You can force the application to run in a maximized or minimized window, or allow it to run in its default (normal) window.

  • Page 140: Solutions For Dialog Box Problems

    Creating Custom Dialog Boxes Open the dialog box in the Custom Dialog Editor. Editing Dialog Boxes on page 120. Select Layout menu > Set Tab Order. A blue number appears next to each dialog box control, showing the current tab sequence.

  • Page 141: Changing The Default Graphic On Wizard Dialog Boxes

    Creating Custom Dialog Boxes Dialog boxes can exhibit different behaviors based on end user input. See ScriptHelp.htm in the Samples subdirectory of this product’s installation directory. Changing the Default Graphic on Wizard Dialog Boxes By default, wizard dialog boxes contain a graphic that is not part of the individual dialog boxes.

  • Page 142: About Custom Dialog Box Sets

    Creating Custom Dialog Boxes variable is set to “A.” That is why all four radio buttons are enabled when the end user backs up, because the variable does not contain “a,” “b,” “c,” or “d.” About Custom Dialog Box Sets A single Custom Dialog script action can display a set of related dialog boxes.

  • Page 143: Creating A Custom Dialog Box Script

    Creating Custom Dialog Boxes Select Edit menu > Dialog Set Properties. The Dialog Set Properties dialog box appears. Complete the dialog box: Dialog Set Name Enter the name of this dialog box set. If this dialog box set is comprised of only one dialog box, then this is usually the same name as the dialog box.

  • Page 144: Dialog Box Script Actions

    Creating Custom Dialog Boxes To create a custom dialog box script Note Before you write a custom dialog box script, review the introductory material in About Script Editor on page 21. Also see Conditions and Loops on page 32 and Variables and Expressions on page 33.
  • Page 145 Creating Custom Dialog Boxes The dialog box opens in the Custom Dialog Editor. Select View menu > Dialog Script Editor. The script for the dialog box appears in the Dialog Script Editor. How you might use a dialog box script: Have the INIT event enable buttons on the current dialog box if the end user answers a previous dialog box in a certain way.

  • Page 146: Chapter 6: Creating Custom Billboards

    Chapter 6 Creating Custom Billboards This chapter includes the following topics: About Billboards on page 146 Accessing the Custom Billboard Editor on page 146 About the Custom Billboard Editor on page 147 Opening and Saving Custom Billboards on page 148 Adding Objects to a Billboard on page 148 About Billboards...

  • Page 147: About The Custom Billboard Editor

    Creating Custom Billboards The tools you need to work in the Custom Billboard Editor are accessible from its menu bar or the icons on the toolbar. About the Custom Billboard Editor The Custom Billboard Editor provides a basic set of drawing tools for creating billboards. You can create scalable, vector-based artwork that can be added to the billboards and displayed during installation.

  • Page 148: Opening And Saving Custom Billboards

    Creating Custom Billboards Opening and Saving Custom Billboards You can access the commands for creating, saving, exporting, and importing billboards from the File menu in the Custom Billboard Editor. There is no New command on the File menu because a new blank billboard screen appears when you open the Custom Billboard Editor.

  • Page 149: Editing Billboard Line Objects

    Creating Custom Billboards Access the Custom Billboard Editor. Accessing the Custom Billboard Editor on page 146. Select Add menu > Text and drag the dimensions of the object in the billboard editor. The Text Settings dialog box opens. Complete the dialog box: Text Enter the text to display.

  • Page 150: Editing Billboard Rectangles And Ellipses

    Creating Custom Billboards Line Direction Determines whether the line should connect the lower-left corner of the bounding rectangle to the upper-right corner, or the upper left to the lower right. Line Width The width of the line in pixels. Line Color Click Pick to choose a color for the line.

  • Page 151: Editing Billboard Bitmap Objects

    Creating Custom Billboards Closing the polygon. When you double-click the mouse button, the Polygon Settings dialog box opens. Complete the dialog box: Line Style Choose the texture for the line that outlines the polygon. Fill Style Select a pattern to fill the object. Line Width The width of the object’s outline in pixels.

  • Page 152: Resizing, Moving, And Aligning Billboard Objects

    Creating Custom Billboards Transparent Mark this to make the color in Transparent Color transparent. Transparent Color Click Pick to choose which color in the bitmap will be transparent. Every pixel in the image with this color becomes transparent. Placement Specify the size and location of the object. For best results, make the width and height equal to the actual width and height of the image.
  • Page 153 Creating Custom Billboards Open the billboard in the Custom Billboard Editor by double-clicking its custom action in Script Editor. Select Edit menu > Graphic Properties. The Billboard Settings dialog box appears. The options on this dialog box are a subset of the settings for the Display Billboard script action. Complete the dialog box: X Position, Y Position Indicate the location on a 640 x 480 screen to place images.

  • Page 154: Chapter 7: Troubleshooting Wisescripts

    Chapter 7 Troubleshooting WiseScripts This chapter includes the following topics: About Troubleshooting a WiseScript on page 154 Using the Installation Log on page 154 File Replacement Problems in System32 on page 154 About Troubleshooting a WiseScript Use the following features to troubleshoot a WiseScript: Installation log Lets you determine what happens during the installation, including what fails.
  • Page 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.

  • Page 156: Chapter 8: Quick Reference

    Chapter 8 Quick Reference This chapter includes the following topics: Automatic Compiler Variables on page 156 Automatic Run-time Variables on page 157 Run-time Variables on page 159 SVS Variables on page 161 Expression Operators on page 163 Command-Line Options on page 165 Automatic Compiler Variables Compiler variables are set before the installation is built and cannot be changed by an installation script.

  • Page 157: Automatic Run-Time Variables

    Quick Reference Variable Description _VB4WIN32DAO_ Visual Basic DAO directory _VB4WIN32DIR_ Visual Basic directory for 32-bit systems _VB4WIN32OPT_ Visual Basic options for 32-bit systems _VFOXPRODIR_ Visual FoxPro directory _VFPOPTIONS_ Visual FoxPro options _WIN_ Windows directory on the build computer _WISE_ The directory containing WiseScript Editor See also: Automatic Run-time Variables on page 157...
  • Page 158 Quick Reference Variable Description INST_LOG_PATH Full path in which to place Install.log at end of installation. INSTALL_RESULT Holds the result of the last action performed for Install (read-only) File(s), Copy Local File(s), Edit INI, and Execute Program actions. (This variable is similar to PROCEXITCODE.) Install File(s) and Copy Local File(s) return: V = Version.

  • Page 159: Run-Time Variables

    Quick Reference Variable Description Windows System directory path. We recommend that you do not change this variable. SYS32 Path to the system directory for Win32 files. We recommend that you do not change this variable. TEMP Windows temporary directory path. We recommend that you do not change this variable.
  • Page 160 Quick Reference Variable Description DISPLAY Holds the name of the current wizard dialog box (read- only). DOBACKUP Holds the end user’s choice as to whether to back up replaced files. DOBRAND If this is set to 1, this is the first time the installation has been branded and user information is written to CUSTDATA.INI.

  • Page 161: Svs Variables

    Quick Reference Automatic Compiler Variables on page 156 Automatic Run-time Variables on page 157 SVS Variables You can use the following SVS variables in some of the SVS script actions. About SVS Script Actions on page 39. System Variables System variables are static properties of a layer. Variable Description Example Value...
  • Page 162 Quick Reference Variable Description Example Value COMMONVIDEO C:\Documents and Settings\All Users\Documents\My Videos PROGRAMFILES C:\Program Files MEDIAPATH C:\Windows\Media COMMONFILES C:\Program Files\Common Files MSSHAREDTOOLS C:\Program Files\Common Files\Microsoft Shared Per User Variables Per user variables are static properties of a layer. Variable Description Example Value ADMINTOOLS C:\Documents and Settings\User\Start...

  • Page 163: Expression Operators

    Quick Reference Variable Description Example Value SENDTO C:\Documents and Settings\User\SendTo STARTMENU C:\Documents and Settings\User\Start Menu STARTUP Folder that contains user C:\Documents and Settings\User\Start specific items to be run on Menu\Programs\Startup startup on the destination computer. TEMPLATES C:\Documents and Settings\user\Templates. TEMP Folder where temporary C:\DOCUME~1\User\LOCALS~1\Temp files can be created.
  • Page 164 Quick Reference Right$(str,position) Returns the right portion of a string, where str is the string, and position is the number of characters from the right to return. Example: Right$(“windows”,3) returns “ows.” Mid$(str,position, Returns the middle portion of a string, where str is the length) string, position is the number of characters from the left to start, and length is the number of characters to return.

  • Page 165: Command-Line Options

    Quick Reference Command-Line Options You can set command-line options when you run WiseScript Editor, the installation executable, and the uninstaller executable. These are especially useful for running an installation as part of a batch file or other automated installation system. If you compile from the command line, compile errors generate return codes.

  • Page 166: Wisescript Installations Command-Line Options

    Quick Reference Note To test the options without the scheduling program, select Windows Start menu > Run, type cmd, click OK, and type a command-line statement in the command-line window. WiseScript Installations Command-Line Options You can apply the following command-line options to .EXE files that you compile from WiseScript Editor projects.
  • Page 167 Quick Reference Silent mode. The uninstall proceeds silently with no splash screen, no dialog boxes, and no end user choices. Rollback mode. Removes the Select Uninstall Method dialog box, which means the end user does not see options for a custom, automatic, or repair uninstall.

  • Page 168: Index

    Index Symbols After$ 164 timing the display 153 transition 152 animation on dialog box 132 % sign with compiler variable 34 working with 147 append data to registry key 74 _ALIASNAME_ 156 binary file application _ALIASPATH_ 156 reading from 105 executing 77 _ALIASTYPE_ 156 writing to 105...
  • Page 169 code signing editing 44 See digital signature connection lines in script 23 data source, ODBC 58 color, in script 23 Contained within structure 49 date/time file modified combo box control control getting 87 adding to dialog box 124 attributes 110 getting four-digit year 88 pre-selected option 125 changing text 111...
  • Page 170 adding 19 Evaluate Windows Installer long 114 Condition 76 prompting for 102 Digital Signature page 19 short 114 event script DIRECTION 159 cancel 24 file, CAB (mobile device) directory exit script 24 about 96 checking existence 55 mainline 24 adding 98 creating empty 60 selecting 22 Find File in Path 82...
  • Page 171 using 15 troubleshooting 154 mobile device installation version 20 about 96 HELPFILE 157 Also see Windows Mobile installation log hot text control installation adding text 42 adding to dialog box 129 opening, closing 99 Modify Component Size 98 link to Web 130 using 154 movie on dialog box 132 HTTP...
  • Page 172 executing from dialog box 138 Remove SVS Exclude Entry 107 window 21 running silently 77 Rename File or Directory in SVS Search for File 109 PROGRAM_FILES 160 Layer 108 self-register files 59, 94 progress message 70 Rename File/Directory 107 Self-Register OCXs/DLLs 110 Project Settings Rename SVS Layer 108 serial number...
  • Page 173 WiseScript Editor 12 text file editing 78 displaying in dialog box 70 executing from WiseScript 77 Start menu 62, 131 editing 92 functions, viewing 79 Start/Stop Service 115 getting WiseScript variable 80 TLB, self-registering 59, 94 STARTMENUDIR 160 objects, viewing 79 troubleshooting STARTUPDIR 160 setting WiseScript variable 80...
  • Page 174 Windows Mobile about 96 Windows Mobile installation about 96 Also see mobile device installation CAB file 96 INF file 97 process for adding 97 Setup.dll 97 uninstalling 97 Windows service adding 61 checking 56 controlling behavior 61 creating 61 starting, stopping 115 WinSock 54 Wise scripting language 11 WISE_ERROR_RTN 82, 160...

This manual is also suitable for:

Wisescript editor 8.0

Table of Contents