How to use the Entries tab

Use the entries tab to specify the instructions regarding what should happen during the application's installation. For example, an application or library and its associated files are copied over to the target device. This can be accomplished by adding "Copy file" entries to the tab, but there are also several other entry types, which could be needed in more complicated install scenarios. The different entry types are listed below:

The Entries entry is the root node of the tree, and it cannot be moved or deleted. Entries for all other types can be added, deleted, and moved through the use if a context menu associated to each node. To add a new entry:

1. Select the Entries node, right click or enter to bring up the context menu and select Add child

2. Select the entry type from one of the following, and specify details for the new entry type in that entries dialog:

   • Copy file

   • Show file

   • Application created file

   • Open file

   • Execute file

   • Group

   • Comment

   • Embedded SIS

   • Options

   • Conditional

You can use Add sibling to add a new node of the selected type, so that the selecetd node and the new node will have the same parent.

Use this entry type to copy your source file to the specified destination location on the target device. Use the edit "copy file" entry dialog to:

1. Select your source file location: choose either a locale-independent file or a locale dependent file. If a locale-dependent file is selected, the supported locale can only be changed in the Name tab

2. Select the drive and destination path for your file.

   Note that Sisar does not have the capability to browse the target device, the destination path is selected from standard locations for common file types.

Use this entry type to copy your source file to the specified destination location on the target device and show a text file whose contents will be displayed in a dialog box during installation. Use the edit "show text file" entry dialog to:

1. Select your source file location: choose either a locale-independent file or a locale dependent file. If a locale-dependent file is selected, the supported locale can only be chnaged in the Name tab

2. Select the drive and destination path for your file

3. Select the button to be displayed in the dialog box from list provided:

   • Continue only

   • Skip next with No

   • Abort and undo with No

   • Abort with No

Text files are not installed on the target machine.

Use this entry type to specify the target drive and path for a file that is created by the running application (not included in the .sis file) on the target device. Use the edit "application created file" entry dialog to select the drive and destination path for the file.

This file is deleted when the appliation is removed. Note that such files will not be deleted when upgrading to a later version. This ensures that such files as .ini files, which store application preferences, are not lost in an upgrade.

Use this entry type to instruct the installer to pass the given file to the default application associated with a specified MIME type. Use the edit "open file" entry dialog to:

1. Select your source file location: choose either a locale-independent file or a locale dependent file. If a locale-dependent file is selected, the supported locale can only be chnaged in the Name tab

2. Select the drive and destination path for your file

3. Choose the close option for the file, from one of the following:

   • Wait until closed

   • When installation complete

4. Specify the MIME type. This instructs the installer to pass the given file to the default application associtaed with that given MIME type. The default is application/octet-stream.

Use this entry type to copy your source file to the target device and install a file and, to be displayed run during installation and/or removal. For example, on installation, you may want to open a Word document providing information about the new application. Use the edit "execute file" entry dialog to:

1. Select your source file location: choose either a locale-independent file or a locale dependent file. If a locale-dependent file is selected, the supported locale can only be chnaged in the Name tab

2. Select the drive and destination path for your file

3. Choose the close option for the file, from one of the following:

   • Wait until closed

   • When installation complete

4. Choose to run to run the file:

   • During installation: this is the default

   • During uninstallation

   • Both

Use this entry type to group together associated files, such as a text file for a license agreement and the license file. Set a name for the group in the edit group dialog.

Any of the entry types can be added to the Group entry.

Use this entry type to add a comment. Comments are ignored by Sisar

Use this entry type to specify the location of the .sis file to be embedded in your component.

Use this entry type to display a list of options to the user. The user selects the required option, which will usually control the installation of optional components later on in the .sis file.

Table entries can be added, deleted and moved using the Insert before, Insert after, Delete, Move up and Move down buttons.

To set options:

1. Set an optional nickname: this must be a unique identifier. This can be used to identify the option in a condition (see below).

2. Set the description of the option, that is the description that will appear to the user, by:

   • Select the cell the description is to be entered for to bring up the component name editor and specify the description

   • Select the required locale for the name.

Conditions that follow the options may test and act upon these selections.

Use this entry type to control the installation according to a set of specified conditions.

• Set your conditions; If, Else if and Else for each condition, specifying attributes, to test for certain conditions such as device and application capabilites.

• Add an entry type for each condition using Add children.

• Package file format