User manual SYMANTEC WISESCRIPT PACKAGE EDITOR 7.0 SP2 FOR WISE INSTALLATION STUDIO V1.0

[. . . ] WiseScript Package Editor Reference WiseScript Package Editor The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version 7. 0 SP2 Legal Notice Copyright © 2010 Symantec Corporation. Symantec, the Symantec Logo, and Altiris are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U. S. Other names may be trademarks of their respective owners. [. . . ] The Import button adds an ODBC data source from your computer and populates the fields. Driver Name Enter the name of the ODBC driver used by this data source. The driver, along with its support files, must already have been installed on the destination computer. Install Data Source for Select Win16 or Win32 APIs. Data Source Attributes Either enter attributes, or use the Import button to import them from an ODBC data source installed on your computer. Display Configuration Dialogs Mark this to display standard data source configuration dialog boxes to the end user. Otherwise, the data source is configured with default settings. System DSN Mark this check box to make the data source available to all user accounts on the destination computer. See also: ODBC on page 63 Copy Local File(s) This action copies uncompressed files from a floppy disk, CD, the destination computer, or a network drive. In WiseScript Package Editor, it also can copy files from an FTP or HTTP server. 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. Therefore, you must provide a way to uninstall or repair such changes. See Uninstalling Changes Made by a WiseScript in the Windows Installer Editor Help. To complete the dialog box Source Specify the path of the file or files to be copied at installation time. Specify the path using a variable, such as %INST% for the directory where the installation . EXE is running. The value of the field should evaluate to a valid directory, file, or files. To copy more than one file, do one of the following: 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 WiseScript Package Editor Reference 60 WiseScript Actions Path. Specifying a wildcard in both the Source field and the Local Path field results in a compile error. If you don't need the progress bar to update correctly, use wildcards in Source (example: %INST%\Pictures\*. jpg), specify a directory in Destination, and leave Local Path blank. Note (WiseScript Package Editor only) If you are copying from an FTP or HTTP server, you cannot use wildcards. Destination Specify the location on the destination computer. If a single file is being copied, this should contain a full file path. [. . . ] Additional compiler variables require additional /d switches. Do not put a space between the /d and the compiler variable name. Defines compiler variables from a text file for this run only. The format for the text file is _VAR_=value, with one entry per line. [. . . ]