Specify the files to include in the application image. Identify the directories into which the files are copied.

Each file or directory of files in the installation set needs a File command associated with it. You can create an individual File command for each file, or use wildcards to combine File commands. The order of the File commands determines the order in which files are copied.

Your File options include:

  • Including individual files or directories of files.
  • Specifying where the installation files are located on the distribution source media. If no value is specified, files are installed from where the installation program was executed. The source function is commonly used to install from a CD-ROM or network drive, or to backup files on the user's system.
  • Specifying where to install files. This is not the same as the default directory. The most common use for the Destination box is to create a subdirectory in the default directory. To install files in the Windows directory or other special directory, enter a variable in the Destination box, such as $WINDIR$, $WINSYSDIR$, $WINTEMPDIR$, $PROGFILESDIR$, $DIRn$, $SOURCEDIR$, $LOCATEDIR$, or $ASKn$. Click System Variable to display a list of variable names.

You can also specify a directory path in the Destination box. For example, c:\ installs the files to the root directory on the C drive. Use \ to install the files on the root of the default directory. Use .. to install files to the directory above the default directory. Only use a path you are sure already exists on the user's system.

  • Specifying whether to overwrite a file if it already exists on the user's system. Click Yes to overwrite existing files. Click No to leave existing files intact. You can also choose to ask the user whether to overwrite existing files using the Ask parameter. When you select New, an overwrite occurs only if the existing file is older (based on time/date stamp) than the file in the installation set. If the file is a .vbs, .dll., exe, or .ocx file, the age is based on the internal version number instead of the time/date stamp.
  • Selecting the file's DOS attribute after installation: read only, archive, hidden, or system. If you do not select an attribute, the default is to Normal, which allows read/write access.
  • Installing a file only if the user selects certain parameters, such as the Group ID.
  • Displaying a pop-up message as files are copied. This message remains on the screen until the next file with a Pop ID is specified or until the end of file copying.
  • Displaying a bitmap on the left, middle side of the background screen. You can also specify a wave sound.
  • The following advanced settings are also available:
    No shrink
    Removes the file compression. This is common when the installation files are on a CD-ROM and you want the files to be accessible to the user without using the installation program.
    No bind
    Prevents combining the specified file with the .exe file, leaving them as independent files that are accessible outside the installation program. If unchecked, the installation program combines all files into a single file and binds it to the installation executable.
    No uninstall
    Leaves the specified file on the user's system when the user runs the uninstall program.
    Installs the file to the font directory and registers it in Windows. This automatically sets up the new font.
    Adds a ShareDLL specification to the file, on installation is registers this file as a shared dll in the registry key, HKLM\Software\Microsoft\Windows\CurrentVersion\Shared DLLs. Uninstalling this package unregisters this file.
    Registers the file in the Windows registry during the installation. The file must be an autoregistering file, such as a .dll, .ocx, or .vbx file. If the file does not autoregister, use the Registry command to manually specify the registration parameters.
    Specifies that the file is copied to the Windows temp directory for use during installation. It is removed after installation.