OS/2 Shareware BBS: 8 Other/08-Other.zip/firunpkg.zip/wpinsdev.hlp

OS/2 Help File | 1997-11-13 | 91KB | 3,928 lines

ΓòÉΓòÉΓòÉ 1. Feature Install Folder ΓòÉΓòÉΓòÉ

The Feature Install program provides a general purpose development environment
for assisting in the development of install objects.  The Feature Install
folder contains the following objects:

      Developer
      Feature Install Object
      Feature Install Samples
      Install Helper
      TEMPLATE
      TOOLKIT
      Uninstall Feature Install Toolkit
      User


ΓòÉΓòÉΓòÉ 2. The Action Section ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> Dependencies Page ΓòÉΓòÉΓòÉ

The action section, titled Then perform this action, specifies an action to
take if the expression defined on the page is true.  If an action requires
parameters, a set of controls specific to the action desired is displayed to
collect the required information.

The controls for selecting, deselecting or uninstalling features are:

  Then perform this action:
  Feature ID

 The controls for setting a variable's value are:

  Then perform this action:
  Feature ID
  Variable
  Value

 The controls for displaying warning or error messages are:

  Then perform this action:
  Warning/error text

 The following table lists the actions that may be selected from the action
 drop-down-list box:

  ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
  ΓöéOption           ΓöéDescription                                  Γöé
  Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
  ΓöéSelect feature   ΓöéChange selection status of the install objectΓöé
  ΓöéDeselect feature Γöéspecified in the Feature ID field.           Γöé
  Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
  ΓöéUninstall featureΓöéUninstall the install object specified the   Γöé
  Γöé                 ΓöéFeature ID field.                            Γöé
  Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
  ΓöéDisplay warning  ΓöéDisplay a warning message box using the      Γöé
  Γöé                 Γöéspecified message text.  The message box willΓöé
  Γöé                 Γöéhave OK and Cancel buttons.  If the user     Γöé
  Γöé                 Γöépresses OK, the function that was in progressΓöé
  Γöé                 Γöéis allowed to continue.  If the user presses Γöé
  Γöé                 ΓöéCancel, the function in progress is aborted; Γöé
  Γöé                 Γöéno more dependency pages are processed.      Γöé
  Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
  ΓöéDisplay error    ΓöéDisplay an error message box using the       Γöé
  Γöé                 Γöéspecified message text.  The message box willΓöé
  Γöé                 Γöéhave a Cancel button.  When the user presses Γöé
  Γöé                 ΓöéCancel, the function in progress is aborted; Γöé
  Γöé                 Γöéno more dependency pages are processed.      Γöé
  Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
  ΓöéSet variable     ΓöéSet the variable of the specified install    Γöé
  Γöé                 Γöéobject to the given value.                   Γöé
  ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

 The Resolve variables in 'Value' before setting check box allows you to
 resolve a variable before setting it.  If the value of the variable is another
 variable, resolve it before setting the variable value.

 A dependency action which affects another object will trigger the immediate
 resolution of appropriate dependency conditions in that other object.  For
 instance, when one object selects another, the other's selection-time
 dependencies will be checked.  This process may cascade to other objects,
 affecting arbitrary parts of the install hierarchy.


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Related topics:

The Condition Section
The Evaluation Time Section


ΓòÉΓòÉΓòÉ 3. Configure Page 1 (ASCII File Updates) ΓòÉΓòÉΓòÉ

Use the Configure page 1 (ASCII File Updates) to specify updates to be made to
ASCII files (such as the user's CONFIG.SYS file) during installation.

Each line in the list box represents a line to add or update in an ASCII file
at installation time.

Add

Add a configuration entry to the list box by selecting the Add button.  This
brings up the Update ASCII File dialog.

Delete

Delete entries from the list box by highlighting the entry to be deleted and
selecting the Delete button.  When the Delete button is selected, a message box
is displayed requiring confirmation to delete the entry.  You may select Delete
to delete the entry or Cancel to cancel the delete operation.

Update or View

Update or view entries by highlighting the entry and selecting the Update
button.  This brings up the same Update ASCII File dialog as for the Add
button.

Copy

Copy another ASCII file entry to the list box by selecting the Copy button.
This will copy the highlighted entry in the list box.


ΓòÉΓòÉΓòÉ 4. Class Name to Replace ΓòÉΓòÉΓòÉ

This specifies the name of the object's class, such as WPProgram, WPFolder, or
WPShadow.

Note:  If you specify Class Name to replace, the Class Name is preceded by an
       asterisk (*).


ΓòÉΓòÉΓòÉ 5. Class Registration Dialog ΓòÉΓòÉΓòÉ

Each field in the Class Registration dialog corresponds to a parameter in the
WinRegisterObjectClass() system call.

 Class name
           Name of the class to register

 DLL name
           Pathname of the corresponding DLL file

 Class Name to Replace
           Name of registered object class to replace.

           Note:  If you specify Class Name to replace, the Class Name is
                  preceded by an asterisk (*).

 After the class name and DLL name is defined, the entry is added to the Class
 Registration list.


ΓòÉΓòÉΓòÉ 6. Class Registration Page ΓòÉΓòÉΓòÉ

Use this page to specify the class names to register during installation.

Add

Define a new class registration by selecting the Add button.  This brings up
the Class Registration dialog.

Delete

Delete a class registration entry from the list by highlighting the entry to be
deleted and selecting the Delete button.  A message box is displayed requiring
confirmation to delete the record. You may select Delete to delete the class
registration record or Cancel to cancel the delete operation.

Update or View

Update or view a class registration entry by highlighting the entry to be
modified or viewed and selecting the Update button.  This brings up the Class
Registration dialog.

Copy

Copy another class entry to the list box by selecting the Copy button.  This
will copy the highlighted entry in the list box.


ΓòÉΓòÉΓòÉ 7. The Condition Section ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> Dependencies Page ΓòÉΓòÉΓòÉ

The condition section, titled If this condition is met, consists of the Feature
ID of an install object, the title of a setting in that object, a condition,
and a value to compare the setting value against.

The condition section of the screen changes depending on what type of condition
is selected.

When the condition checks for the existence of or selection status of a certain
feature, the following fields are displayed:

  Feature ID
  Condition

 When the condition checks the value of a certain variable, the following
 fields are displayed:

  Feature ID
  Condition
  Setting
  Value

 When the referenced object is found, that object is queried for the value of
 the setting defined in the Setting entry field.  The title of any setting from
 the Information, Variables, Media, Ascii File Updates, Objects, Dependencies,
 or User Exits pages in the object's Properties notebook or any other user or
 internal variable may be specified.

 This value is then compared against the value entered in the Value entry
 field, using the condition specified in the Condition field.

 Any installation object in the current object's hierarchy, or any installed
 software object on the system, can be identified through that object's Feature
 ID. Installed software objects are specified by adding the prefix inv_ to the
 feature tag of the install object that created it. For example, if the feature
 tag of an install object is DatabaseSystem, then its corresponding installed
 software object would have a Feature ID of INV_DatabaseSystem.

 The following table lists the conditions that may be selected from the
 Condition drop-down-list box:

  ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
  ΓöéOption         ΓöéDescription                                  Γöé
  Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
  ΓöéExists         ΓöéChecks for existence or nonexistence of the  Γöé
  ΓöéDoesn't exist  Γöéinstall object or installed software object  Γöé
  Γöé               Γöéspecified by the Feature ID field.           Γöé
  Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
  ΓöéIs selected    ΓöéChecks selection status of the install objectΓöé
  ΓöéIs not selectedΓöéspecified by the Feature ID field.           Γöé
  Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
  Γöé=              ΓöéChecks an install object's variable against aΓöé
  Γöé!=             Γöéconstant value or another variable.  Specify Γöé
  Γöé<              Γöéthe variable's name in the Setting field.    Γöé
  Γöé<=             ΓöéSpecify a constant or another variable's nameΓöé
  Γöé>              Γöéin the Value field.                          Γöé
  Γöé>=             Γöé                                             Γöé
  ΓöéContains       Γöé                                             Γöé
  ΓöéIs part of     Γöé                                             Γöé
  ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Related topics:

The Evaluation Time Section
The Action Section


ΓòÉΓòÉΓòÉ 8. Configuring Install Objects ΓòÉΓòÉΓòÉ

Install objects are configured via the object's Properties notebook.  The
notebook pages may be filled in manually, or they may be filled in using
install helper objects.  Use the Install Helper template in the Feature Install
folder to create new install helper objects.  With an install helper object you
can create a permanent definition of an install object's settings, which may be
used to re-initialize the install object repeatedly during the development
process.

The Properties notebook for install objects contains the following pages in
addition to the standard folder pages:

      Information
      Variables
      Media Sets
      File List
      ASCII File Updates
      Os2Prf .Ini File Updates
      WinOs2 .Ini File Updates
      Objects Creation
      Class Registration
      Dependencies
      User Exits


ΓòÉΓòÉΓòÉ 9. Creating an Install Object Hierarchy ΓòÉΓòÉΓòÉ

An application may have several optional features that the user can choose to
install.  There could also be optional subfeatures within one or more primary
features that the user can choose to install.  This hierarchical structure can
be represented using a tree view of the application.

To create a hierarchy of features and subfeatures, create a separate install
object for each feature and subfeature, then drag each subfeature object onto
its top feature object (in bottom to top order).  There should be one object at
the top of the hierarchy representing the complete install package.  When this
object is opened, the entire hierarchy is displayed using a standard folder
tree view. Only the top object has the Media Sets page in its Properties
notebook.

Note:  Each object within the hierarchy represents a feature and has its own
       Properties notebook that contains instructions for installing the
       feature.  The Dependencies page of the Properties notebook may be used
       to ensure that certain features are always installed together.


ΓòÉΓòÉΓòÉ 10. Creating Media Sets During Packaging ΓòÉΓòÉΓòÉ

You may define zero or one media entries for a media set and have the others
created dynamically during packaging.  If fewer media entries are defined than
are needed to package the files, the Media Definition dialog will be displayed
with the fields set to values of the last defined media entry, if any exist.
You may change the values or accept them.  When OK is selected, the media type
is verified and the files are packaged to the newly created media.  If the type
or capacity of the media path do not match the type and capacity specified, a
dialog box is displayed with the option to automatically change the type and
capacity, to cancel packaging, or to accept the inconsistency.


ΓòÉΓòÉΓòÉ 11. Dependencies Dialog ΓòÉΓòÉΓòÉ

The Dependencies dialog has three sections:

  The Evaluation Time Section, titled When Feature ID is, defines when to
   evaluate the expression.

  The Condition Section, titled If this condition is met, defines a
   conditional expression.

  The Action Section, titled Then perform this action, defines what action to
   perform if the expression is true.

 After the dependency is defined, its name is added to the Defined Dependencies
 list.


ΓòÉΓòÉΓòÉ 12. Dependencies Page ΓòÉΓòÉΓòÉ

Use this page to specify the package's dependencies on other software or
conditions.  When an install object is in user mode, these dependencies will be
checked at specified times, triggering specified actions if a dependency
condition is met.

Add

Create a new dependency by selecting the Add button. This brings up the
Dependencies dialog.

Delete

Delete a dependency from the list by highlighting the dependency to be deleted
and selecting the Delete button.  A message box is displayed requiring
confirmation to delete the dependency.  You may select Delete to delete the
dependency or Cancel to cancel the delete operation.

Update or View

Update or view a dependency definition by highlighting the dependency to be
modified or viewed and selecting the Update button.  This brings up the
Dependencies dialog.

Copy

Copy another dependency entry to the list box by selecting the Copy button.
This will copy the highlighted entry in the list box.


ΓòÉΓòÉΓòÉ 13. Development Mode ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Development mode sets the install object's Properties notebook to update mode.
Installations cannot be initiated when the install object is in development
mode.

The following behaviors are unique to development mode:

      Changes are allowed in the Properties notebook.
      A Package button is provided in the object's open view.
      The object's pop-up menu displays the Package menu item.


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Related topics:

User Mode
Setting the mode


ΓòÉΓòÉΓòÉ 14. Developer Object ΓòÉΓòÉΓòÉ

The Developer object, found in the Feature Install folder, is an Install Helper
object with the setting MODE=DEVELOPMENT entered on the Object Data page.  You
can change an install object to Developer Mode by dragging and dropping the
Developer object onto the install object.


ΓòÉΓòÉΓòÉ 15. Edit Line Dialog ΓòÉΓòÉΓòÉ

This action will substitute a specific string in an existing line with a new
string.  If the line is not found within the file, no action is taken.

If the specified string is found within the line, it may be substituted by the
new string.  If the string is not found, you may specify to insert the new
string in the line at a particular location.

The following controls are displayed with the Edit Line action.

 Edit line
           If Use GREP to search was selected, enter a regular expression to
           compare against the lines in the search; otherwise, enter a literal
           expression.

 Occurrence
           Possible occurrence values are:

                first
                last
                every

 Value section of line is group of delimited substrings, and delimiter is
           Specifies that the line consists of a keyword-value pair, where the
           value consists of a group of substrings (as in a path statement) and
           specifies the delimiter between each keyword-value pair.  For
           example, in the path statement, the delimiter is the semi-colon (;).
           If this box is checked, the entire string within the delimiters will
           be replaced by the new string.

           For example, suppose you specify that in the line "SET PATH=", the
           string "MYPATH" is to be substituted with the string "d:\newpath",
           and the existing path statement is:

                        SET PATH=.;C:\;C:\MYPATH

           If the line is identified as a set of groups, the resulting line
           will be:

                        SET PATH=.;C:\;d:\newpath

           If the check box had not been checked, the line would have
           incorrectly been converted to:

                        SET PATH=.;C:\;C:\d:\newpath

 Delimiter after last entry
           If this box is checked, a delimiter will be placed after the last
           entry.

 Search for string
           Enter the string that you wish to replace.  If Use GREP to search
           was selected, the string is a regular expression.  Otherwise, the
           string is a literal expression.  In the previous example, this would
           be "MYPATH".  You would not want to include "C:\" since each user's
           drive specification may be different.

           If you wish to add a new string without replacing an existing
           string, then enter the new string in both the Search for string and
           New string fields, and set If search string found to "Take no
           action".  This will ensure that the string does not get added twice
           if the user reinstalls the software.

 Occurrence
           Possible occurrence values are:

               first
               last
               every

 New string
           Enter the string you wish to have inserted.  In the above example,
           this would be "d:\newpath".

 If search string found
           This group specifies which action to take if the search string
           matches a string in the line.  The possible actions are:

           Replace with new string
                          Replace the matching string with the new string.

           Take no action
                          Do nothing.

           Use "Take no action" to add a new string to the line only if the
           string does not already exist.  For example, you may wish to simply
           add "d:\newpath" to the path statement, but if "d:\newpath" already
           exists in the path statement then do nothing.

 Otherwise
           This group specifies which action to take if no match for the search
           string is found in the line.  The possible actions are:

               Add new string to beginning of line
               Add new string to end of line
               Add string before or after other strings
               Take no action

 Add new string before or after other strings
           The controls in this group are enabled when the corresponding radio
           button has been selected in the Otherwise  group.

           Add Before
                          Add the new string before all strings matching the
                          string to search for.

           Add After
                          Add the new string after all strings matching the
                          string to search for.

 If matching position is found
           Specifies what to do if the requested position is found.  Possible
           actions are:

               Add string at this position
               Take no action

 Otherwise
           Specifies what to do if the requested position is not found.
           Possible actions are:

               Add new string to beginning of line
               Add new string to end of line
               Take no action


ΓòÉΓòÉΓòÉ 16. EOS/2 Sample Program ΓòÉΓòÉΓòÉ

The EOS/2 Sample demonstrates the basic functionality available to the
application developer when using the HTML inferface to FI as the installation
vehicle for their application.


ΓòÉΓòÉΓòÉ 17. The Evaluation Time Section ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> Dependencies Page ΓòÉΓòÉΓòÉ

The evaluation time section, titled When Feature ID is, determines when the
expression is evaluated (and the associated action performed, if the expression
is true).  Whenever the specified feature reports the occurrence of an event,
the install object loops through the defined dependencies and takes action on
those whose evaluation time entry matches the event.

The following table lists the events that may be selected from the
drop-down-list box for the is selection:

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéOption         ΓöéDescription                                  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöéselected       ΓöéThe evaluation is processed when the         Γöé
Γöé               Γöéspecified install object is selected (when   Γöé
Γöé               Γöéthe selection check box is clicked on).      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöédeselected     ΓöéThe evaluation is processed when the         Γöé
Γöé               Γöéspecified install object is deselected (when Γöé
Γöé               Γöéthe selection check box is clicked off).     Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöéinstalled      ΓöéThe evaluation is processed when the         Γöé
Γöé               Γöéspecified install object performs the        Γöé
Γöé               Γöéinstallation.                                Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöéuninstalled    ΓöéThe evaluation is processed when the         Γöé
Γöé               Γöéspecified install object performs the        Γöé
Γöé               Γöéuninstall function.                          Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Related topics:

The Condition Section
The Action Section


ΓòÉΓòÉΓòÉ 18. Feature ID ΓòÉΓòÉΓòÉ

The feature ID is a string that uniquely identifies an install object. Each
install object has to have a unique feature ID.


ΓòÉΓòÉΓòÉ 19. Feature Install Object ΓòÉΓòÉΓòÉ

The Feature Install Template Object, found in the Feature Install Toolkit
folder, can be used to create a Feature Install Object by dragging it to
another folder.


ΓòÉΓòÉΓòÉ 20. Feature Install Samples ΓòÉΓòÉΓòÉ

The Feature Install Samples folder, found in the Feature Install folder,
provides the following:

     The EOS/2 Sample demonstrates the basic functionality available to the
      application developer when using the HTML inferface to FI as the
      installation vehicle for their application.
     A README file provides details about the two samples.
     The Uninstall Samples folder contains the Uninstall EOS/2 Sample to
      enable you to uninstall the sample programs files.


ΓòÉΓòÉΓòÉ 21. Feature Install TEMPLATE ΓòÉΓòÉΓòÉ

The Feature Install TEMPLATE, found in the Feature Install Toolkit folder,
provides a graphical template to facilitate creation of a consistent Feature
Install user interface.  This template consists of graphics and HTML files to
arrange Feature Install GUI elements.


ΓòÉΓòÉΓòÉ 22. File Dialog ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> File Dialog ΓòÉΓòÉΓòÉ

The File dialog contains four sections:

  Source Information: where named file can be found before packaging:

   Source Path
                  The fully-qualified path (including the drive) where the file
                  can be found when packaging is run.

   Source Filename
                  The file name of the source file.

  Package Information: where & how file will be stored during packaging

   Media Subdirectory
                  An optional subdirectory where the file is to be placed on
                  the media. The base path for all the files in the install
                  object is defined in the Media Path field for each media (see
                  Media Definition Dialog).  The optional subdirectory
                  specified for this file will be created under the media path
                  specified for the media.

   Media Filename
                  The packaged file name to use for this file.  The file will
                  be created on the media with this file name.  By default, the
                  media filename will be the same as the source filename.

   File has media restrictions
                  A media restriction means that the file must be placed on a
                  specific media within a media set.  For example, a file may
                  need to be on the first diskette so that the user's machine
                  can be restarted from the diskette during installation.

                  Select the "File has media restrictions" check box to specify
                  a media restriction for this file.  The Restrict file button
                  will then be enabled.  Select this button to specify which
                  media this file should be placed on.  When the Restrict file
                  button is selected, the Restrict File dialog is displayed.

  Target Information: where & how file will be transferred during installation

   Target Path
                  The fully-qualified path (including the drive) where the file
                  is to be placed on the user's system during installation.
                  This field should contain variables such as {BootDrive} or
                  {TargetPath} that can be specified by the user during
                  installation.  (Variables are declared on the Variables
                  page.)  If the target path does not exist when the file is
                  installed, it will be created, if possible.

   Target Filename
                  The file name of the target file.  The file will be created
                  on the user's system with this file name.  By default, the
                  target filename will be the same as the source filename.
                  After the file is defined, its name is added to the file
                  list.

   Hidden, Read-only, and System check boxes
                  The attributes of the installed files may be specified using
                  the Hidden, Read-only, and System check boxes.  By default,
                  none of these check boxes are selected.

  Source and Target File Information

   No validity checking is performed at file definition time.  When the
   packaging process is initiated, each of the source files will be validated
   and other information obtained, including date and time, file size, EA size,
   and checksum.  This information will be displayed in the packaged object's
   Source and Target File Information area of the File dialog.

 A default Source Path and Target Path is shown when the dialog is displayed.
 These defaults can be cleared by selecting the Clear button in the lower right
 corner of the dialog.


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Related topics:

Packaging
Restrict File Dialog
Variables Page


ΓòÉΓòÉΓòÉ 23. File List Page ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Use this page to specify the files that will be included in the install object.
These files will be placed on the source media during packaging and installed
on the user's system during installation.

Add

Add a file to the file list by selecting the Add button.  This brings up the
File dialog.

For each file, you specify the path and file name of the source file to be used
during packaging, the path and file name of the file on the media, and the
target path and file name to be used during installation.

Delete

Delete a file from the file list by highlighting the file to be deleted and
selecting the Delete button.  A message box is displayed requiring confirmation
to delete the file.  You may select Delete to delete the file or Cancel to
cancel the delete operation.

Update or View

Update or view a file definition by highlighting the file to be modified or
viewed and selecting the Update button.  This brings up the File dialog.


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Related topics:

Packaging


ΓòÉΓòÉΓòÉ 24. Information Page ΓòÉΓòÉΓòÉ

Use the Information page to specify information about the product being
installed and the Feature ID of this install object.

This page includes the following fields:

 Installation Feature ID
           A string that uniquely identifies an object.  Objects must have a
           Feature ID in order to be packaged, installed, uninstalled, saved to
           disk, or read from disk.  Without a Feature ID, an install object
           cannot even save its own instance data to disk.

 Package Title
           Your name for this application or feature object.

 Version Number
           The version number you have designated for this application.

 Version Date
           The day this version was released.

 Company Name
           Your company's name.


ΓòÉΓòÉΓòÉ 25. Installation Summary ΓòÉΓòÉΓòÉ

This confirmation panel lists the features selected for installation on your
computer.

Click on Confirm overwrite of existing files if you want to be prompted by the
installation program before a file on the target drive is overwritten by a file
being installed.

Click on the Install push button to install these features.

Click on the Cancel push button to return to the previous screen and change
your selections.


ΓòÉΓòÉΓòÉ 26. Install Helper Objects ΓòÉΓòÉΓòÉ

Install helper objects provide a way to set an install object's settings
automatically, using a set of pre-defined keywords that correspond to the
settings.  Also, refer to Install Object.

One or more keyword=value lines are entered in the install object. The Install
helper object can then be dropped onto an install object to set the values of
the install object's settings.

The advantages of using Install helper objects are:

     The settings for an install object can be pre-configured and activated at
      a later date.
     Install objects can be initialized repeatedly for testing purposes.
     Frequently made changes can be done with one drag and drop action.

 To use an install helper object:

   1. Drag the install helper template to a folder or to the desktop to create
      a new install helper object.

   2. Double-click on the install helper object and enter the desired
      keyword=value line(s).  Close the file to save the information.

   3. Drag and drop the customized install helper object onto the desired
      install object or vice-versa.


ΓòÉΓòÉΓòÉ 27. Install Helper Template ΓòÉΓòÉΓòÉ

This Install Helper template can be dragged onto the desktop to create a new
install helper object.  The system editor is displayed when the new object is
opened.  The install helper object can then be customized by entering specific
keywords into the editor.  When the edit session is saved, the data is saved in
the install helper object.


ΓòÉΓòÉΓòÉ 28. Install Object ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> Install Object ΓòÉΓòÉΓòÉ

Install objects are used for creating custom installations.  A developer may
use install objects to configure an installation of their application.  The
configured installation object is then shipped with the application to be
installed by the user.  Therefore, an installation object has two modes:
development mode and user mode.

Install objects are derived from WPFolder and so can be thought of as a special
type of folder.  The install object opens in tree view by default, but may also
be opened in icon or details view.  Note that the Properties notebook  contains
several new pages in addition to the standard folder pages.  The settings pages
are filled in by the developer to tell the install object what to do during the
installation process.

Create a new install object from the Feature Install Object template in the
Feature Install folder.


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Related topics:

Creating an Install object hierarchy
Configuring Install objects


ΓòÉΓòÉΓòÉ 29. Internal Variables ΓòÉΓòÉΓòÉ

The following internal variables are created automatically and are available to
any install object.  They may be overridden by a local variable definition.

 BootDrive
           Letter of startup drive with a trailing colon (:)

 TargetFolder
           Fully qualified path name of the Workplace Shell folder into which
           the user has selected to install the application (evaluated at
           install time only).


ΓòÉΓòÉΓòÉ 30. Keywords ΓòÉΓòÉΓòÉ

Select from the following list for a description of available keywords:

General Install Object Information

Dependencies Page
Prerequisites
File List
Information
Media Sets
Objects Creation
Class Registration
Packaging
User Exits
Configure Page 1 (Update Ascii Files)
Configure Page 2 (Update Os2Prf Type .Ini
Files)
Configure Page 3 (Update WinOs2 Type .Ini
Files)
Variables

See also Response File Syntax


ΓòÉΓòÉΓòÉ 31. Keywords for General Install Object Information ΓòÉΓòÉΓòÉ

The following keywords are for general Install Object information:

TopObjectID=
TargetFolder=

Mode= Development
      User

Selection=0  No
          1  Yes

ObjectType= Install
            Inventory


ΓòÉΓòÉΓòÉ 32. Keywords for Class Registration Page ΓòÉΓòÉΓòÉ

The following keywords are for the Class Registration page. Class registrations
are entered into the ClassRegistration[] array, with each index in the array
representing a class registration entry in the Setttings notebook.

ClassRegistration[0].ClassName=
ClassRegistration[0].DLLName=
ClassRegistration[0].ClassReplace=


ΓòÉΓòÉΓòÉ 33. Keywords for Dependencies Page ΓòÉΓòÉΓòÉ

The following keywords are for the Properties notebook Dependencies page.
Dependencies are entered into the Dependency[] array, with each index in the
array representing a dependency entry in the Setttings notebook.

Dependency[0].FeatureID=
Dependency[0].ActionFeatureID=
Dependency[0].WhenFeatureID=
Dependency[0].ResolveTime=0 - selected
                          1 - deselected
                          2 - installed
                          3 - uninstalled
Dependency[0].Condition=0 - exists
                        1 - does not exist
                        2 - selected
                        3 - is not selected
                        4 - equal
                        5 - not equal
                        6 - less
                        7 - less or equal
                        8 - greater
                        9 - greater or equal
                        10 - contains
                        11 - is part of
Dependency[0].Action=0 - select feature
                     1 - deselect feature
                     2 - uninstall feature
                     3 - display warning
                     4 - display error
                     5 - set variable
Dependency[0].ActionText[0]=
Dependency[0].Setting=
Dependency[0].Value=
Dependency[0].ResolveNow=0 - variables resolved at some later point
                         1 - variables resolved before
Dependency[0].CaseSensitive=0 - case insensitive comparison
                            1 - case sensitive comparison


ΓòÉΓòÉΓòÉ 34. Keywords for File List Page ΓòÉΓòÉΓòÉ

The following keywords are for the File List page.  File entries are entered
into the File[] array, with each index in the array representing a File entry.

File[0].EAMediaIndex=
File[0].Source=
File[0].SourcePath=
File[0].SourceFileName=
File[0].SourceChecksum=
File[0].SourceEASize=
File[0].CBFile=
File[0].CBFileAlloc=
File[0].AttrFile=
File[0].TargetPath=
File[0].TargetFileName=
File[0].MediaPath=
File[0].MediaFileName=
File[0].MediaNumber=
File[0].Flags=
File[0].TargetAttrib=0 - regular file
                     1 - read-only file
                     2 - hidden file
                     3 - hidden read-only file
                     4 - system file
                     5 - read-only system file
                     6 - hidden system file
                     7 - hidden read-only system file


ΓòÉΓòÉΓòÉ 35. Keywords for Information Page ΓòÉΓòÉΓòÉ

The following keywords are for the Information page:

ObjectTitle=
Mode=   Development
        User
PackageTitle=
CompanyName=
VersionNumber=
VersionDate=


ΓòÉΓòÉΓòÉ 36. Keywords for Prerequisites Page ΓòÉΓòÉΓòÉ

The following keyword is for the Prerequisites page.

  Prerequisite[0].FeatureID=CharString


ΓòÉΓòÉΓòÉ 37. Keywords for Media Set Page ΓòÉΓòÉΓòÉ

The following keywords are for the Media Set page.  Media Sets are entered into
the MediaSet[] array, with each index in the array representing a Media Set
entry in the Setttings notebook.

  MediaSet[0].Media[0].Type=1 - diskette
                            2 - CD
                            4 - hard drive

  MediaSet[0].Media[0].Capacity=
  MediaSet[0].Media[0].ClusterSize=
  MediaSet[0].Media[0].Description=
  MediaSet[0].Media[0].MediaPath=
  MediaSet[0].Media[0].ReservedSpace=

  MediaSet[0].MediaFinishedExit.ExitType=0 - DLL
                                         1 - EXE
                                         2 - CMD
  MediaSet[0].MediaFinishedExit.FilePath=
  MediaSet[0].MediaFinishedExit.ExitData=
  MediaSet[0].MediaFinishedExit.SessionVisible=0 - minimized
                                               1 - visible to user
  MediaSet[0st].MediaFinishedExit[0].DLLStackSize=40


ΓòÉΓòÉΓòÉ 38. Keywords for Objects Page ΓòÉΓòÉΓòÉ

The following keywords are for the Objects Creation page. Objects are entered
into the ObjectCreation[] array, with each index in the array representing an
object entry in the Setttings notebook.

ObjectCreation[0].ClassName=
ObjectCreation[0].ObjectTitle[0]=
ObjectCreation[0].SetupString=
ObjectCreation[0].Location=
ObjectCreation[0].Flags=0 - CO_FAILIFEXISTS
                        1 - CO_REPLACEIFEXISTS
                        2 - CO_UPDATEIFEXISTS
                        3 - CO_PRESERVEOLD

Note:  You should only use the CO_PRESERVEOLD flag to create Workplace Shell
       objects on OS/2 Warp systems.


ΓòÉΓòÉΓòÉ 39. Keywords for Packaging ΓòÉΓòÉΓòÉ

The following keywords are for Packaging:

MediaSetIndex=
FilesDone=
TotalFiles=
ProductID=
FirstSerialNum=
PackageFlags=
TotalMediaUsed=


ΓòÉΓòÉΓòÉ 40. Keywords for Update ASCII Files ΓòÉΓòÉΓòÉ

The following keywords are for the Properties notebook Configure page 1, Ascii
File Updates. ASCII File entries are entered into the AsciiFile[] array, with
each index in the array representing an ASCII File entry in the Setttings
notebook.

AsciiFile[0].CaseSensitive=0 - case insensitive
                           1 - case sensitive
AsciiFile[0].UseGrep=0 - do not use GREP
                     1 - use GREP
AsciiFile[0].FileName=
AsciiFile[0].EditLine=
AsciiFile[0].SearchLine=
AsciiFile[0].NewLine=
AsciiFile[0].SearchFound=1 - replace with the string defined by
                         2 - take no action
AsciiFile[0].SearchNotFound=1 - add new line to beginning of file
                            2 - add new line to end of file
                            4 - add before or after other lines
                            8 - take no action
AsciiFile[0].AddBeforeLine=
AsciiFile[0].AddAfterLine=
AsciiFile[0].Delimiter=
AsciiFile[0].SubstrChk=0 - value is not a set of delimitered key=value substrings
                       1 - value is a set of delimitered key=value substrings
AsciiFile[0].DelimChk=0 - there is no delimiter after last entry
                      1 - there is a delimiter after last entry
AsciiFile[0].Action=0 - replace a line with another line
                    1 - edit a selected line
AsciiFile[0].EditLineOcc=0 - search for first occurrence
                         1 - search for last occurrence
                         2 - search for every occurrence
AsciiFile[0].SrcLineOcc=0 - search for first occurrence
                        1 - search for last occurrence
                        2 - search for every occurrence
AsciiFile[0].AddBLineOcc=0 - search for first occurrence
                         1 - search for last occurrence
                         2 - search for every occurrence
AsciiFile[0].AddALineOcc=0 - search for first occurrence
                         1 - search for last occurrence
                         2 - search for every occurrence
AsciiFile[0].MatchPosition=1 - replace with the string defined by
                           2 - take no action
AsciiFile[0].NoMatchPosition=1 - add new line to beginning of file
                             2 - add new line to end of file
                             8 - take no action


ΓòÉΓòÉΓòÉ 41. Keywords for Update Os2Prf Type .Ini Files ΓòÉΓòÉΓòÉ

The following keywords are for the Properties notebook Configure page 2 Os2Prf
.Ini File Updates.  OS/2 INI Files are entered into the Os2PrfIni[] array, with
each index in the array representing an OS/2 INI File entry in the Setttings
notebook.

Os2PrfIni[0].FileName=
Os2PrfIni[0].Application=
Os2PrfIni[0].Key=
Os2PrfIni[0].Value=
Os2PrfIni[0].IniType=1


ΓòÉΓòÉΓòÉ 42. Keywords for Update WinOs2 Type .Ini Files ΓòÉΓòÉΓòÉ

The following keywords are for the Properties notebook Configure page 3, WinOs2
.Ini File Updates.  WIN INI Files are entered into the WinOs2Ini[] array, with
each index in the array representing a WIN INI File entry in the Setttings
notebook.

WinOs2Ini[0].FileName=
WinOs2Ini[0].Application=
WinOs2Ini[0].Key=
WinOs2Ini[0].Value=
WinOs2Ini[0].IniType=2


ΓòÉΓòÉΓòÉ 43. Keywords for User Exits Page ΓòÉΓòÉΓòÉ

The following keywords are for the User Exits page.  User Exits are entered
into the UserExits[] array, with each index in the array representing a User
Exit entry in the Setttings notebook.

UserExits[0].ExitType=0 - DLL
                      1 - EXE
                      2 - CMD

UserExits[0].FilePath=
UserExits[0].ExitData=
UserExits[0].SessionVisible=0 - minimized
                            1 - visible to user
UserExits[1].DLLStackSize=200
UserExits[0].CallTime=0 - after awakening
                      1 - before sleeping
                      2 - before install
                      3 - before file transfer
                      4 - after file transfer
                      5 - before configuration updates
                      6 - after configuration updates
                      7 - before object creation
                      8 - after object creation
                      9 - after install
                      10 - before uninstall
                      11 - before file deletion
                      12 - after file deletion
                      13 - before configuration entry removal
                      14 - after configuration entry removal
                      15 - before object deletion
                      16 - after object deletion
                      17 - after uninstall


ΓòÉΓòÉΓòÉ 44. Keywords for Variables Page ΓòÉΓòÉΓòÉ

The following keywords are for the Variables page.  Variables are entered into
the Variable[] array, with each index in the array representing a variable
entry in the Setttings notebook.

Variable[0].Name=
Variable[0].Description=
Variable[0].Value=

        Variable[0].ValidationExit.ExitType=0 - DLL
                                            1 - EXE
                                            2 - CMD
        Variable[0].ValidationExit.FilePath=
        Variable[0].ValidationExit.ExitData=
        Variable[0].ValidationExit.DLLStackSize=200
        Variable[0].ValidationExit.SessionVisible=0 - minimized
                                                  1 - visible to user

        Variable[0].ResolutionExit.ExitType=0 - DLL
                                            1 - EXE
                                            2 - CMD
        Variable[0].ResolutionExit.FilePath=
        Variable[0].ResolutionExit.ExitData=
        Variable[0].ValidationExit.DLLStackSize=200
        Variable[0].ResolutionExit.SessionVisible=0 - minimized
                                                  1 - visible to user


ΓòÉΓòÉΓòÉ 45. Media Definition Dialog ΓòÉΓòÉΓòÉ

The media entry has a media type, a description to be used when prompting for
the media during installation, a media path, and reserved space.

Media Type

The media type is specified using radio buttons.  The available media types are
diskette, CD, and logical disk.  Both CD and logical disk are packaged to a
logical disk.  When CD is specified, the CD directory structure is created on
the logical disk with the extended attributes split into separate files.
Extended attributes are joined with the file during the installation process.

You must then use a CD mastering system to place the created directory
structure onto a CD.  You should specify that the media is a CD so that the
appropriate prompt will be displayed during installation.

Media Capacity

Media capacity is used during the packaging process to calculate if there is
enough space on the CD for the files in the media set.

 Capacity
   Total capacity of a CD (it can vary for different CDs).

 Cluster size
   Used to estimate how much space the files will occupy on a CD.  A single
   file will always round up to a multiple of the cluster size.  For example,
   for a cluster size of 512, a file with a size of 2 bytes will occupy 512
   bytes and a file with a size of 513 bytes will occupy 1024 bytes.

 Description

 The description is used to prompt the user for the media during installation.
 The description may contain variables, including the internal status variable
 {CURRENT_MEDIA}, which resolves to the sequence number of the media currently
 being used to install the package.  CURRENT_MEDIA is useful for homogeneous
 media sets, such as all diskettes, but may cause confusion in heterogeneous
 media sets.  For example, a media set consisting of a diskette and a CD may
 prompt for CD #2 when there is only one CD.

 Media Path

 The media path is the target path to be used during packaging and should be
 the fully-qualified base directory for the packaged files. For diskettes this
 path should be the root of a drive, such as A:\.  For CDs and logical disks it
 may include a subdirectory.

 Note:  You may specify a further breakdown of files into subdirectories on the
        File List page.  These subdirectories will be created under the media
        path directory.

 Reserved Space

 Reserved space may be used to set aside disk space for files that will be
 added after packaging or for temporary space needed during installation.
 Specify the reserved space in bytes.  The value will be rounded up to the
 cluster size of the media during packaging.  Normally, reserved space is not
 necessary.


ΓòÉΓòÉΓòÉ 46. Media Set Definition Dialog ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

A media set consists of a set name and a list of media entries.  Each media
entry describes a physical component of the media set, such as a diskette or a
CD, and includes information such as the media type, capacity, and reserved
space.  Media sets may be homogeneous (consisting of one media type) or
heterogeneous (consisting of multiple media types).

Fill in the Media Set Name field with a unique name to create a new media set.
The media entries may either be created now or during packaging.

To create the media list now, select Add to bring up the Media Definition
dialog.  After the media entry is defined it will be added to the Media
Definitions list. Repeat this process for each media entry.  You may select Add
to add new media entries, Copy to duplicate an existing entry, Delete to delete
an entry, or Update to modify or view an entry.

Use Media Finished User Exit so that, rather than prompting for the next
diskette, the program calls a user exit.

After the media set is defined, its name will be added to the Available Media
Sets list.


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Related topics:

Creating Media Sets During Packaging


ΓòÉΓòÉΓòÉ 47. Media Sets Page ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Use this page to define "media sets."  A media set describes a set of media
that can be used for packaging your product.  For example, you may define media
sets for diskettes, CD-ROM images, and logical disks.  You can then select one
of these media sets when the packaging process is initiated.

Media sets can only be defined in the top-level object in the application
hierarchy.

Add

Add a new media set by selecting the Add button.  This brings up the Media Set
Definition dialog.

Copy

Copy a media set by highlighting the set name and selecting the Copy button.  A
new media set is created with a name of XXX:n, where XXX is the name of the
original media set and n is an integer.  (This integer will be the lowest
possible value to produce a unique media set name, beginning with "1".)  You
may then update the new media set to change its name.

Delete

Delete a media set by highlighting the set name and selecting the Delete
button.  A message box is displayed requiring confirmation to delete the media
set.  You may select Delete to delete the media set or Cancel to cancel the
delete operation.

Update or View

Update or view an existing media set by highlighting the set name and selecting
the Update button.  This brings up the Media Set Definition dialog.


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Related topics:

File List Page
Packaging


ΓòÉΓòÉΓòÉ 48. Objects Dialog ΓòÉΓòÉΓòÉ

Each field in the Objects dialog corresponds to a parameter in the
WinCreateObject() system call.

 Class Name
           Name of the object's class.

 Object Title
           Title as it will appear on the desktop.

 Setup String
           Arguments to initialize the new object, of the format KEYWORD=VALUE,
           with each keyword separated by a semicolon (;)  and comma (,)
           separating multiple values.

 Object Location
           The object-ID or fully-qualified pathname of the folder in which the
           new object will be created.  Some predefined locations are:

                          <WP_DESKTOP>                  the Workplace desktop
                          <WP_START>                    the OS/2 startup
                                                        folder.

 Creation Flag
           Determines how object-creation will proceed if a duplicate name
           exists:

                          CO_REPLACEIFEXISTS            Replace old object.
                          CO_FAILIFEXISTS               Keep old object.
                          CO_UPDATEIFEXISTS             Update old object.
                          CO_PRESERVEOLD                Keep old object; ID of
                                                        existing old object
                                                        assigned to new object.

 After the object is defined, its name is added to the Objects list.


ΓòÉΓòÉΓòÉ 49. Objects Page ΓòÉΓòÉΓòÉ

Use this page to specify the desktop objects to be created during installation.

Add

Define a new object by selecting the Add button.  This brings up the Object
dialog.

Delete

Delete an object from the list by highlighting the object to be deleted and
selecting the Delete button.  A message box is displayed requiring confirmation
to delete the record.  You may select Delete to delete the object definition
record or Cancel to cancel the delete operation.

Update or View

Update or view an object definition by highlighting the object record to be
modified or viewed and selecting the Update button.  This brings up the Object
dialog.

Copy

Copy another object entry to the list box by selecting the Copy button.  This
will copy the highlighted entry in the list box.


ΓòÉΓòÉΓòÉ 50. Configure Page 2 ΓòÉΓòÉΓòÉ

Use the Configure Page 2 (Os2Prf .Ini File Updates) to specify updates to be
made to one of the user's OS/2-type INI files during installation.

Each line in the list box represents an OS/2-type INI file to add or update at
installation time.

Add

Add an INI file entry to the list box by selecting the Add button.  This brings
up the Update Os2Prf Type .Ini File dialog.

Copy

Copy an Os2Prf .Ini File by selecting the name of the file to copy and
selecting the Copy button.  You may then update the new file to change its
name.

Delete

Delete entries from the list box by highlighting the entry to be deleted and
selecting the Delete button.  When the Delete button is selected, a message box
is displayed requiring confirmation to delete the entry.  You may select Delete
to delete the entry or Cancel to cancel the delete operation.

Update or View

Update or view entries by highlighting the entry and selecting the Update
button.  This brings up the same Update Os2Prf Type .INI File dialog as for the
Add button.


ΓòÉΓòÉΓòÉ 51. Packaging ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> Packaging ΓòÉΓòÉΓòÉ

Select the desired media set to use for packaging from the drop down list box.
The list box will contain all media sets that have been defined, and another
entry called Create new media set.  If no media sets have been defined for the
install object, Create new media set  will be the only available entry.  When
this entry is chosen, the Media Set Definition dialog is displayed so you can
define the new media set.  This new name must be unique.

After the media set is selected or created, all of the files in all of the
objects in the hierarchy are validated and file information is obtained,
including date and time, file size, EA size, and checksum. Media entries are
validated to make sure the media path exists and that the specified type and
capacity matches that of the media path.  If a media's type or capacity is
different, you are given the option to have it corrected automatically or to
proceed with discrepancy.  If any of the validations fail, an error message is
displayed and the packaging process is terminated.

After validation, the Media Definition dialog is displayed for the first media.
If the media entry was previously defined in the Properties notebook, this
information will be displayed in the dialog.  If the media entry was not
previously defined, default values are set in the dialog fields.  You may
change the information as needed.  Select OK to accept the information in the
dialog.  The information is then validated.  If the validation fails, a message
is displayed and control is returned to the dialog, where you may make the
necessary corrections.

After the media is validated, space is reserved for the install object
hierarchy and for any additional space specified in the media definition
dialog.  A file is written out to the media that will be used during
installation to validate the media.  This file contains the media set name,
media sequence number, feature ID, and revision of the install object from
which packaging was initiated.

Next, all files for all objects in the hierarchy that are restricted to the
first media for the selected media set are placed.  If these restricted files
do not fit on the media, an error message is displayed and packaging is
terminated.

Unrestricted files in the hierarchy are then placed on the media.

If any files remain to be packaged after the first media is filled, the Media
Definition dialog is displayed for the second media.  If the media entry was
previously defined in the Properties notebook, this information will be
displayed in the dialog.  If the media entry was not previously defined,
default values are set in the dialog fields.  Follow the same procedure as for
the first media to accept the information and proceed with packaging.  If any
files remain to be packaged after the second media is filled, the Media
Definition dialog is displayed for the next media.  This process is repeated
until all files have been packaged.

For the second and subsequent media, the identification data file is written,
space is reserved as specified on the media dialog, and restricted files are
placed.  Incomplete file parts are then placed, followed by unrestricted files.
This is repeated until all files and file parts have been placed.

After all files have been packaged, the first media is prompted for again.
This time, the media information cannot be changed.  With the first media
present, the install object hierarchy is copied and changed to the packaged
state and switched to user mode.  All of the media set information is preserved
and the selected media set is saved in the install object.  This information
will be used for installation.


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Related topics:

Media Definition Dialog
File Dialog


ΓòÉΓòÉΓòÉ 52. Prerequisites Dialog ΓòÉΓòÉΓòÉ

The Prerequisites dialog allows you to specify the Feature ID of the
prerequisite feature.


ΓòÉΓòÉΓòÉ 53. Prerequisites Page ΓòÉΓòÉΓòÉ

The Prerequisites page allows you to specify prerequisite install objects for
the current Feature ID.

Add

Add new prerequisites by selecting the Add button. This brings up the
Prerequisites dialog.

Copy

Copy a prerequisite feature by selecting the Feature ID of the prerequisite
feature to copy and selecting the Copy button. You may then update the new
prerequisite feature to change its name.

Delete

Delete a prerequisite feature by highlighting the Feature ID and selecting the
Delete button.  A message box is displayed requiring confirmation to delete the
prerequisite feature.  You may select Delete to delete the prerequisite or
Cancel to cancel the delete operation.

Update or View

Update or view an existing prerequisite by highlighting the Feature ID and
selecting the Update button.  This brings up the Prerequisites dialog.


ΓòÉΓòÉΓòÉ 54. Processing Response Files ΓòÉΓòÉΓòÉ

The replace response file read user exit call time can be used to provide
non-default parsing.  If a user exit is specified at this call time, the user
exit will be called instead of the normal response file parsing.  The
RESPONSE_FILE status variable can be queried within the user exit to obtain the
fully-qualified response file name.

See also Response File Syntax.

Alternatively, the user exit API InstQueryResponseFile can be used to query
information from the response file after the response file is read and parsed
by the install object.

All references to keyword names within user exits must be fully qualified.  For
example:

   SectionName1 = (
         KeyWord1 = Value11
         KeyWord2 = (
                kw1 = Val1
                kw2 = Val2
                )
                .
                .
         KeyWordn = Value1n
         )

   SectionName2 = (
         KeyWord1 = Value21
         KeyWord2 = Value22
                .
                .
         KeyWordn = Value2n
         )

KeyWord1 by itself is ambiguous.  A fully-qualified name must be used. A
fully-qualified name is formed by prefixing the keyword with the section name,
using the format <section name>/<keyword>. For example, a query for
SectionName1/KeyWord1 would return Value11, a query for
SectionName1/KeyWord2/kw1 would return Val1, and a query for
SectionName1/KeyWord2/kw2 would return:

  (
  kw1 = Val1
  kw2 = Val2
  )

The '/' character will be interpreted as an escape character.  If only one '/'
exists on the string it will be treated as a name qualification separator.  Two
slashes ("//") would be treated as the literal '/'.


ΓòÉΓòÉΓòÉ 55. Read Response File ΓòÉΓòÉΓòÉ

Use Read Response File to specify the drive, directory, and file name of the
file you want to use as the response file.

To read the response file:

   1. Click on the arrow to the right of the Drive list to display all the
      drives on your system.

   2. Click on a drive letter.

   3. Click on a directory name in the Directory list.

   4. Click on the scroll bar to the right of the File field until the name of
      the response file appears.

   5. Click on the name of the file in the File field.

   6. Click on the Read push button to read the file or the Cancel push button
      to return to the previous screen without reading the file.


ΓòÉΓòÉΓòÉ 56. READ.ME ΓòÉΓòÉΓòÉ

The READ.ME file for the Feature Install program provides the latest
information you can use for installing and using the Feature Install sample
programs.  It contains information about using the Feature Install Object
template and the EOS/2 sample program.


ΓòÉΓòÉΓòÉ 57. Replace Line ΓòÉΓòÉΓòÉ

This action will add a new line or substitute an existing line in the ASCII
file with a new line.  The following controls are displayed with the Replace
Line action.

 Search for line
           If Use GREP to search was selected, enter a regular expression to
           compare against the lines in the search.  Otherwise, enter a literal
           expression.

 Occurrence
           Possible occurrence values are:

                first
                last
                every

 New line
           Enter the complete new line.

 If Search line is found
           This group specifies which action to take if the search line matches
           a line in the file.  The possible actions are:

           Replace with New Line
                          Replace the search line with the new line.

           Take no action
                          Do nothing.  Use this option to add a new line only
                          if the line does not already exist.

 Otherwise
           This group specifies which action to take if no match for the search
           line is found in the file.  The possible actions are:

                Add new line to beginning of file
                Add new line to end of file
                Add line before or after other lines
                Take no action

 Add line before or after other lines
           The controls in this group are enabled when the corresponding radio
           button has been selected in the Otherwise group.

           Add Before
                          Add the new line before all lines matching the line
                          to search for.

           Add After
                          Add the new line after all lines matching the line to
                          search for.

 occurrence
           Occurrence allows you to specify the First or Last occurrence of the
           specified line.  Possible occurrence values are:

                First
                Last

 If matching position is found
           Specifies what to do if the requested position is found.  Possible
           actions are:

                Add new line at this position
                Take no action

 Otherwise
           Specifies what to do if the requested position is not found.
           Possible actions are:

                Add line to beginning of file
                Add line to end of file
                Take no action


ΓòÉΓòÉΓòÉ 58. Response File Syntax ΓòÉΓòÉΓòÉ

Response files have the following syntax:

# Text of the comment

TopObjectID=MFID


MFID=(
      SubfeatureID=MFID Child
      ObjectTitle[0]=FI Object
      Mode=Development
      PackageTitle=MPT
      CompanyName=IBM
      VersionNumber=1.45
      VersionDate=03-19-97
      Variable=(
                Name=variable1
                Description=Dsc. of var1
                Value=Default_value
                ValidationExit=(
                                DLL Stack Size
                                ExitType=2
                                FilePath=DLLNAME.DLL
                                ExitData=UserValidate
                                SessionVisible=1
                               )
                ResolutionExit=(
                                DLL Stack Size
                                ExitType=2
                                FilePath=CMDRES.CMD
                                ExitData=-pcmd1 -pcmd2
                                SessionVisible=1
                               )
               )
      Dependency=(
                  FeatureID=ConditionID
                  ActionFeatureID=ResultID
                  WhenFeatureID=CauseID
                  ResolveTime=1
                  Condition=1
                  Action=1
                  ActionText[0]=Text Text Text
                  Setting=SettingKey
                  Value=SettingValue
                  ResolveNow=1
                  CaseSensitive=0
                 )
      UserExits=(
                 ExitType=1
                 FilePath=DLLNAME.DLL
                 ExitData=-pcmd1 -pcmd2
                 SessionVisible=1
                )
      ObjectCreation=(
                      ClassName=WP_CLASS
                      ObjectTitle[0]=Shurum-Burum
                      SetupString=EXENAME=exefile.exe^;PARAMS=param
                      Location=WP_FOLDERNAME
                      Flags=0
                     )
      ClassRegistration=(
                         ClassName=WP_CLASS
                         DLLName=regclass.dll
                         ClassReplace=WP_OLD
                        )
      MediaSet=(
                SetName=MediaSetMike
                Media=(
                       Type=2
                       Capacity=48
                       ClusterSize=34
                       Description=CD
                       MediaPath=D:\
                       ReservedSpace=1000
                      )
      MediaFinishedExit=(
                         DLL Stack Size
                         ExitType=1
                         FilePath=DLLNAME.DLL
                         ExitData=-pcmd1 -pcmd2
                         SessionVisible=1
                        )
     )
AsciiFile=(
           CaseSensitive=1
           UseGrep=0
           FileName=config.sys
           EditLine=Line To Edit
           SearchLine=set path
           NewLine=rem set path
           SearchFound=2
           SearchNotFound=2
           AddBeforeLine=beforeline
           AddAfterLine=afterline
           Delimiter=*
           SubstrChk=1
           DelimChk=1
           Action=1
           EditLineOcc=2
           SrcLineOcc=1
           AddBLineOcc=1
           AddALineOcc=1
           MatchPosition=2
           NoMatchPosition=2
          )
Os2PrfIni=(
           FileName=d:\path\os2.ini
           Application=ApplicationName
           Key=KeyName
           Value=KeyValue
           IniType=1
          )
WinOs2Ini=(
           FileName=d:\winpath\win.ini
           Application=WinAppName
           Key=WinKeyName
           Value=WinKeyValue
           IniType=2
          )
File=(
      EAMediaIndex=0
      Source=S:\srcpath\srcname
      SourcePath=S:\srcpath
      SourceFileName=srcname
      SourceChecksum=0
      SourceEASize=0
      CBFile=0
      CBFileAlloc=0
      AttrFile=0
      TargetPath=T:\targetpath
      TargetFileName=srcname
      MediaPath=mediapath
      MediaFileName=srcname
      MediaNumber=0
      Flags=0
      TargetAttrib=3
     )
)


ΓòÉΓòÉΓòÉ 59. Restrict File Dialog ΓòÉΓòÉΓòÉ

The Restrict File dialog contains a list of current media restrictions for this
file.  You should specify a media restriction for each media set where the
restriction applies.  For example, the restriction may apply to media sets for
diskettes, but not to a CD.

Add

Add a restriction for this file by selecting the Add button.  This brings up
the Restriction dialog.

Delete

Delete entries from the Media Restrictions list by highlighting the entry to be
deleted and selecting the Delete button.  When the Delete button is selected, a
message box is displayed requiring confirmation to delete the restriction.  You
may select Delete to delete the restriction or Cancel to cancel the delete
operation.

Update or View

Update or view entries by highlighting the entry and selecting the Update
button.  This brings up the Restriction dialog.


ΓòÉΓòÉΓòÉ 60. Restriction Dialog ΓòÉΓòÉΓòÉ

On the Restriction dialog you enter the media set name and media number on
which to place this file.

 Media Set Name
           Enter the name of the media set that you are specifying the
           restriction for.  This name should be the same name that was entered
           for this media set on the Media Sets page.

 Media Number
           Enter the sequence number of the media on which this file is to be
           placed.  (Enter 1 for the first media.)

           When the Restriction dialog is filled in and OK is selected, the
           Restrict File dialog is redisplayed with the new restriction added
           to the Current Media Restrictions list.

 After the file restriction is defined, the restriction is added to the Current
 Media Restrictions list.


ΓòÉΓòÉΓòÉ 61. Properties Notebook ΓòÉΓòÉΓòÉ

All objects have a Properties notebook that defines the object's icon, title,
location on disk and window behavior.  Follow these steps to view the
Properties notebook:

   1. Press the right mouse button on the object's icon to display the object's
      pop-up menu.
   2. Select Properties from the pop-up menu.


ΓòÉΓòÉΓòÉ 62. Setting the Mode ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

In the Feature Install Toolkit folder are two Install Helper objects titled
"User" and "Developer".

To set an install object to user mode, drop the User object onto the install
object.  (Alternatively, drop the install object onto the User object.)

To set the install object to development mode, drop the Developer object onto
the install object.  (Alternatively, drop the install object onto the Developer
object.)


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Related topics:

User Mode
Development Mode


ΓòÉΓòÉΓòÉ 63. Save Response File ΓòÉΓòÉΓòÉ

Use Save Response File to specify the drive, directory, and file name you want
to use for the response file.

To save the response file:

   1. Click on the arrow to the right of the Drive list to display all the
      drives on your system.

   2. Click on a drive letter.

   3. Click on a directory name in the Directory list.

   4. Type the name you want to use for the file in the Save as filename field.

   5. Click on the Save push button to save the file or the Cancel push button
      to return to the previous screen without saving the changes.


ΓòÉΓòÉΓòÉ 64. Status Variables ΓòÉΓòÉΓòÉ

User exits need to be able to query the current state of the install object.
To support this, a set of internal variables containing object status
information are defined in the install object class.  Their values will be
updated based on the current state of the install object.

The following variables are only valid during file transfer in packaging:

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéVariable                      ΓöéDescription                   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCURRENT_SOURCE_PATHNAME       ΓöéFully-qualified packaging     Γöé
Γöé                              Γöésource path and filename      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCURRENT_SOURCE_PATH           ΓöéPath portion of               Γöé
Γöé                              ΓöéCURRENT_SOURCE_PATHNAME       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCURRENT_SOURCE_FILENAME       ΓöéFilename portion of           Γöé
Γöé                              ΓöéCURRENT_SOURCE_PATHNAME       Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

The following variables are valid during file transfer in packaging and
installation:

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéVariable                      ΓöéDescription                   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCURRENT_MEDIA_PATHNAME        ΓöéFully-qualified path and      Γöé
Γöé                              Γöéfilename on media             Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCURRENT_MEDIA_PATH            ΓöéPath portion of               Γöé
Γöé                              ΓöéCURRENT_MEDIA_PATHNAME        Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCURRENT_MEDIA_FILENAME        ΓöéFilename portion of           Γöé
Γöé                              ΓöéCURRENT_MEDIA_PATHNAME        Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCURRENT_MEDIA                 ΓöéNumber of current media       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCURRENT_FILE_PART             ΓöéNumber of current file part   Γöé
Γöé                              Γöébeing processed               Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

The following variables are only valid during file transfer in installation:

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéVariable                      ΓöéDescription                   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCURRENT_TARGET_PATHNAME       ΓöéFully-qualified path and      Γöé
Γöé                              Γöéfilename on install target    Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCURRENT_TARGET_PATH           ΓöéPath portion of               Γöé
Γöé                              ΓöéCURRENT_TARGET_PATHNAME       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCURRENT_TARGET_FILENAME       ΓöéFilename portion of           Γöé
Γöé                              ΓöéCURRENT_TARGET_PATHNAME       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéTOTAL_FILE_PARTS              ΓöéNumber of parts in current    Γöé
Γöé                              Γöéfile                          Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

The following variable is only valid after packaging (including installation)
at the top object in the hierarchy:

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéVariable                      ΓöéDescription                   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéTOTAL_MEDIA                   ΓöéNumber of media in current    Γöé
Γöé                              Γöémedia set                     Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

The following variables are always valid:

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéVariable                      ΓöéDescription                   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPACKAGED                      Γöé{"YES", "NO"}                 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSTATE                         Γöé{"INSTALLABLE", "INSTALLED"}  Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

The following variables are only valid when PACKAGED is equal to "NO".

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéVariable                      ΓöéDescription                   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCHILD_OBJECT[<index>]         ΓöéFeature ID of contained objectΓöé
Γöé                              Γöéreferenced by <index>         Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCHILD_OBJECT_COUNT            ΓöéNumber of contained objects   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPARENT_OBJECT                 ΓöéFeature ID of parent object   Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

The following variables are only valid during installation or uninstallation
(and only at the top object):

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéVariable                      ΓöéDescription                   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCURRENT_PROGRESS              ΓöéPercentage complete           Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCURRENT_ACTION                Γöé{"INSTALL", "UNINSTALL"}      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCURRENT_SUBTRACTION           Γöé{"DEPENDENCY",                Γöé
Γöé                              Γöé"FILE_TRANSFER", "CONFIGURE"} Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

The following variable is only valid during execution of user exits.

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéVariable                      ΓöéValid Values                  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCURRENT_USER_EXIT             Γöé"BEFORERESPONSEFILEREAD"      Γöé
Γöé                              Γöé"REPLACERESPONSEFILEREAD"     Γöé
Γöé                              Γöé"AFTERRESPONSEFILEREAD"       Γöé
Γöé                              Γöé"AFTERAWAKENING"              Γöé
Γöé                              Γöé"REPLACEOPTIONS"              Γöé
Γöé                              Γöé"BEFOREINSTALL"               Γöé
Γöé                              Γöé"BEFOREFILETRANSFER"          Γöé
Γöé                              Γöé"AFTERFILETRANSFER"           Γöé
Γöé                              Γöé"BEFORECONFIGURATION"         Γöé
Γöé                              Γöé"AFTERCONFIGURATION"          Γöé
Γöé                              Γöé"BEFOREOBJECTCREATION"        Γöé
Γöé                              Γöé"AFTEROBJECTCREATION"         Γöé
Γöé                              Γöé"AFTERINSTALL"                Γöé
Γöé                              Γöé"BEFOREUNINSTALL"             Γöé
Γöé                              Γöé"BEFOREFILEDELETION"          Γöé
Γöé                              Γöé"AFTERFILEDELETION"           Γöé
Γöé                              Γöé"BEFORECONFIGURATIONREMOVAL"  Γöé
Γöé                              Γöé"AFTERCONFIGURATIONREMOVAL"   Γöé
Γöé                              Γöé"BEFOREOBJECTDELETION"        Γöé
Γöé                              Γöé"AFTEROBJECTDELETION"         Γöé
Γöé                              Γöé"AFTERUNINSTALL"              Γöé
Γöé                              Γöé"RESOLVEVAR"                  Γöé
Γöé                              Γöé"VALIDATEVAR"                 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 65. Syntax for Regular Expressions ΓòÉΓòÉΓòÉ

A GREP pattern (pszPattern) is a null-terminated string containing the pattern
to search pszBuffer for.  This type of pattern is called a "regular
expression", and has the following syntax:

 Character Description

 literal   Any character not otherwise given a special function is treated as a
           literal, meaning it matches only itself.  This includes the letters
           A-Z (both upper and lower case), the numbers 1-9, most punctuation,
           and anything else not specifically listed below.

 \         The backslash may be used to escape characters that would otherwise
           have special meaning.  Any character (except the digits 1-9)
           immediately following a backslash is treated as a literal, including
           ".", "[", "]", "(", ")", "*", "{", "}", and "^".

           See the section on "parenthetical blocks" for information on
           escaping the digits 1 through 9.

 .         A period wildcard (".") matches any single character.

           Example: The pattern "A.C" could match the substrings "ABC", "A!C",
           or "A.C".

 *         An asterisk wildcard ("*") matches any zero or more characters.

           Example: The pattern "A*Z" could match the substrings "AZ", "A-Z",
           or "ABCDEFGHIJKLMNOPQRSTUVWXYZ".

 [ ]       Square brackets define a "character list," including any combination
           of the following:

           [string]       A string enclosed in square brackets matches any
                          single character in the string. The characters "-",
                          "]", "!", and "\" must be escaped with a backslash
                          ("\") to always be treated as literals in this
                          context. All other characters are automatically
                          treated as literals.

           [a-z]          Two characters separated by a dash match any single
                          character between those two characters.

                          If a dash occurs as the first or last character in
                          the character list, the dash is treated as a literal.
                          Otherwise, the character after the dash is treated as
                          a literal, including "-" and "\".

           [!string]      If the first character of a character list is an
                          exclamation point ("!"), the character list will
                          match any single character not listed. Exclamation
                          points after the first position are treated as
                          literals.

                          Example:  "[^abc\-1-9XYZ]" will match any single
                          character except lower case a, b, or c, a dash, the
                          numbers 1 through 9, or upper case X, Y, or Z.

                          Note:  Character lists do not currently support high
                                 ascii (values > 127) or DBCS characters.

 { }       Curly braces ("{ }") define a range of occurrences for the next
           element of the search pattern.

           The next element of the pattern that a range applies to can be a
           literal, a character list, a period wildcard, a parenthetical block,
           or another range.

           The braces can contain either one or two comma separated decimal
           integers ranging from zero to 254.  The first number is the low
           boundary, and the second is the high boundary for the range.  They
           indicate that the pattern element immediately following the range
           must occur at least "low" times in order to match, and can be
           matched as many as "high" times.

           If only one number is specified, it will be used as both the low and
           high boundaries.  "X{3}qY" will only match the substring "XqqqY"
           within the buffer.

           If "low" is left blank, zero is used as the default.  "A{,5}[a-z]B"
           can match "AB", "AzzzB", and "AaeiouB".

           If "high" is left blank, there will be no upper limit on the number
           of times the match can be repeated.  Typically, after "high"
           matches, GREP moves on to evaluate the rest of the pattern, even if
           there are more matches.

           Note:  "{,}." and "*" are not the same.  The construct "{,}." is
                  ineffective because it would match the entire rest of the
                  string, and thus a search string like "A{,}.Z" could never be
                  matched because any "Z" at the end would already have been
                  matched.

 ( )       Parentheses define sub-blocks within the pattern.  By themselves,
           they have no effect: "abc" and "a(b(c))" match the same string:
           "abc".

           Parenthetical blocks are useful in conjunction with curly brace
           ranges.  For example, the search string "{3}(abc.)" could match the
           line "abc1abcXabc.".

 \#        If a backslash is used to escape the digits 1 through 9, the result
           is to repeat the appropriate parenthetical block.  The number of a
           parenthetical block is determined by the count of the opening
           parentheses:

                      Search string   Block 1     Block 2    Block 3

                      "(A(B))(C)"     (A(B))      (B)        (C)

           Example: "ABC( defghi )JKL\1MNO\1" will match exactly the string
           "ABC defghi JKL defghi MNO defghi "

           You cannot repeat a parenthetical block that has not been completed
           yet.  "\1(ABC)" is illegal, as is "(ABC\1)".

 ^         If a caret ("^") is the first character of the search pattern, it
           matches the start of a line.  If it is the last character, it
           matches the end of a line.

           In the middle of a pattern, a caret is treated as a literal.

           Example:  The pattern "^Fred^" matches the line "Fred".  It does not
           match "Say hi to Fred" because of the first caret, and it does not
           match "Fred says hi" because of the second caret.

 Examples:

 Pattern   What it matches

 "*ab*"    Any string containing "ab", such as "ab", "blab", or "babies".

 "ab.c"    Any string that is four characters long, begins with ab, and ends
           with c.

 "[ABC]*\." Any string that begins with A, B, or C, and ends with a period.

 "[a-zA-Z]*!" Any string that begins with an upper or lowercase letter and ends
           with an exclamation point.

 "the{1,5} cat" Any string beginning with "the", ending with "cat", and
           containing one to five spaces in between.

 "{1,}[!.]" Any string that does not contain a period.

 "^{,}[! ]{,} ={,} {,}[! ]^" Any complete line with an equals sign that does
           not contain any spaces except around the equals sign.

 "{3}(No ){,2}{2}\1" Any odd number of consecutive occurrences of the string
           "No " between three and seven (inclusive).

 "[a-zA-Z]{,}[0-9a-zA-Z]" Any string that begins with a letter and is followed
           only by letters or numbers.

 "{0,1}[-+]{1,}[0-9]" Any string that optionally begins with a - or + sign and
           consists of one or more digits.


ΓòÉΓòÉΓòÉ 66. TOOLKIT ΓòÉΓòÉΓòÉ

The Feature Install TOOLKIT, found in the Feature Install folder,  provides a
set of files to be used for the creation of user exits.  User exits are also
included for facilitating interface with Software Installer(tm) installed
packages.


ΓòÉΓòÉΓòÉ 67. Uninstallation Summary ΓòÉΓòÉΓòÉ

This confirmation panel lists the features selected for removal from your
computer.

Select the Uninstall push button to remove these features.

Select the Cancel push button to return to the previous screen and change your
selections.


ΓòÉΓòÉΓòÉ 68. Uninstall EOS/2 Sample ΓòÉΓòÉΓòÉ

Use the Uninstall EOS/2 Sample to remove the files associated with the EOS/2
sample program.


ΓòÉΓòÉΓòÉ 69. Uninstall Feature Install Toolkit ΓòÉΓòÉΓòÉ

The Uninstall Feature Install Toolkit icon, found in the Feature Install
folder,  starts an HTML file interface to allow you to uninstall the Feature
Install Toolkit or the Feature Install Samples.


ΓòÉΓòÉΓòÉ 70. Uninstall Feature Install Toolkit ΓòÉΓòÉΓòÉ

Use Uninstall Feature Install Toolkit to remove the Feature Install product or
any of its features from your computer.  When the Feature Install product is
uninstalled, the icon and all of the files associated with it are deleted.


ΓòÉΓòÉΓòÉ 71. Uninstall Samples Folder ΓòÉΓòÉΓòÉ

The Uninstall Samples folder contains the two HTML interface uninstall programs
for the EOS/2 sample program and the Supermarket sample program.


ΓòÉΓòÉΓòÉ 72. Uninstall Supermarket Sample ΓòÉΓòÉΓòÉ

Use the Uninstall Supermarket Sample to remove the files associated with the
Supermarket sample program.


ΓòÉΓòÉΓòÉ 73. Update ASCII File Dialog ΓòÉΓòÉΓòÉ

The Update ASCII File dialog contains the following fields:

 File      The name of an ASCII file to be updated, such as the CONFIG.SYS
           file. The file specified must be in ASCII format.

 Action    Specifies the editing operation to be performed on the file.  The
           possible actions are:

           Replace Line
                          Replace an existing line in the configuration file
                          with a new line.

           Edit line
                          Edit a string within an existing line of an ASCII
                          file.

 Case sensitive search If this box is checked, the search is case sensitive.
           The default is case insensitive search.

 Use GREP to search When checked, GREP escape sequences are used to search for
           lines to replace or substrings within strings to edit.

           Which controls are displayed in the remaining portion of the Update
           ASCII File dialog depends on which Action you selected.

 When the Update ASCII File dialog is filled in and OK is selected, the ASCII
 File Updates page is redisplayed with the new entry added to the list box.


ΓòÉΓòÉΓòÉ 74. Update .Ini Files ΓòÉΓòÉΓòÉ

The Update .Ini File dialogs for Os2Prf and WinOs2 type .INI files contain the
following fields:

 Filename and Path
           Enter the path and name of the INI file you wish to update.

 Application
           The application in the .INI file.

 Key
           The keyword in the application to add or update in the .INI file.

 Value
           The value to assign to the keyword.

 When the dialog is filled in and OK is selected, the Os2Prf .Ini File Updates
 page or WinOs2 File Updates page is redisplayed with the new entry added to
 the list box.


ΓòÉΓòÉΓòÉ 75. User Exits Dialog ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> User Exits Dialog ΓòÉΓòÉΓòÉ

On the User Exits dialog you specify the Call Time, the Exit Type, and the Exit
Specification.  Call Time is not specified if this is a variable resolution,
variable validation, or media finished user exit.

Call Time

The valid options for Call Time are:

 After Awakening
           Awakening occurs when the install object becomes visible.

 Before Sleeping
           Just before the install object is about to go away (for example,
           when the object is deleted or when system shutdown occurs).

 Before Install
           When the user selects Install, before the installation process
           begins.

 Before file transfer
           Just before transferring files during installation.

 After file transfer
           Just after transferring files during installation.

 Before configuration updates
           Just before updating the ASCII, OS/2 .INI, or WIN-OS/2 .INI files.

 After configuration updates
           Just after updating the ASCII, OS/2 .INI, or WIN-OS/2 .INI files.

 Before object creation
           Just before object creation.

 After object creation
           Just after object creation.

 After Install
           Just after the installation process is completed.

 Before Uninstall
           When the user selects Uninstall, before the uninstall process
           begins.

 Before file deletion
           Just before file deletion.

 After file deletion
           Just after file deletion

 Before configuration entry removal
           Just before updating the ASCII, OS/2 .INI, or WIN-OS/2 .INI files.

 After configuration entry removal
           Just after updating the ASCII, OS/2 .INI, or WIN-OS/2 .INI files.

 Before object deletion
           Just before object deletion.

 After object deletion
           Just after object deletion.

 After Uninstall
           Just after the uninstall process is completed.

 Exit Type

 If a user exit is provided in a DLL, the entry point must take the following
 form:

      BOOL APIENTRY procedure_name(HMODULE hModule, LHANDLE hFeature);

      The hModule and hFeature parameters are passed to the user exit by the
      install object.

      hModule is the module handle of the user exit DLL, loaded by the install
      object;

      hFeature is a handle to the install object, used by the DLL when calling
      User Exit APIs.

 For an .EXE and .CMD type user exit, the developer may choose to have the
 handle to the install object passed as an ASCII decimal string in the command
 line parameter as {FEATURE_HANDLE}.  In order to call User Exit APIs, the
 program must convert the string to an LHANDLE (using the "C" library function
 atol, for instance).

 The user exit returns a BOOL value to indicate whether the operation failed.
 If the user exit indicates that the operation failed (returns TRUE), the
 operation in progress when the exit was called is aborted.

 Exit Specification

 For a DLL exit, the Exit Specification group box contains the following
 controls:

 DLL Name
           The name of the DLL module to be loaded.

 Procedure Name
           The entry point in the DLL to be called.

 Stack Size
           The size of the stack available when the DLL entry point is called.

 For an EXE exit, the Exit Specification group box contains the following
 controls:

 EXE File Path
           The full path of the program file.

 Parameters
           Developer-defined parameters to be passed on the executable's
           command line.

 Session visible to user
           Specifies that the user exit session is visible to or hidden from
           the user.

 For an CMD exit, the Exit Specification group box contains the following
 controls:

 CMD File Path
           The full path of the batch file.

 Parameters
           Developer-defined parameters to be passed on the batch file's
           command line.

 Session visible to user
           Specifies that the user exit session is visible to or hidden from
           the user.

 After the user exit is defined, its name is added to the Defined User Exits
 list.


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Related topics:

Status Variables


ΓòÉΓòÉΓòÉ 76. User Exits Page ΓòÉΓòÉΓòÉ

A User Exit is code provided by the developer.  The code may be in the form of
a DLL, an OS/2 executable, or a CMD batch or REXX batch file.  On this page you
define the user exits for this install object.

Add

Define a new user exit by selecting the Add button. This brings up the User
Exits dialog.

Delete

Delete a user exit from the list by highlighting the user exit to be deleted
and selecting the Delete button.  A message box is displayed requiring
confirmation to delete the user exit.  You may select Delete to delete the user
exit or Cancel to cancel the delete operation.

Update

Update or view a user exit definition by highlighting the user exit to be
modified or viewed and selecting the Update button. This brings up the User
Exits dialog.

Copy

Copy another user exit to the list box by selecting the Copy button.  This will
copy the highlighted entry in the list box.


ΓòÉΓòÉΓòÉ 77. User Mode ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

User mode sets the install object's Properties notebook to read-only mode. The
user may view the notebook, but may not change its settings. Installations can
be initiated only when the install object is in user mode.

The following behaviors are unique to user mode:

      No changes are allowed in the Properties notebook.
      An Install button is provided in the object's open view.
      The object's pop-up menu displays the Install and Options menu items.


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Related topics:

Development Mode
Setting the mode


ΓòÉΓòÉΓòÉ 78. User Object ΓòÉΓòÉΓòÉ

The User object, found in the Feature Install folder, is an Install Helper
object with the setting MODE=USER entered on the Object Data page of its
Settings notebook.  You can change an install object to User Mode by dragging
and dropping the Developer object onto the install object.


ΓòÉΓòÉΓòÉ 79. Using Variables ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> Using Variables ΓòÉΓòÉΓòÉ

A variable can be used in any Feature Install string (except Feature ID) by
enclosing its name in { }, for example, {myVariable}.

For example, the destination directory for the files needed for the
installation of a feature is unknown at the time that you enter the list of
files into the File List page.  You would like the user to be able to specify
the destination directory for these files.  You could declare the following
variable:

 Name                  DriveDest
 Description           Destination Drive
 Value                 C:

 When entering a file \TEST.FIL into the File List page, you would specify the
 target path and file name as:

    {DriveDest}\TEST.FIL

 Any other files that should be copied to this same drive would be entered in
 the same way.

 Notes:

   1. The {} delimiters are not included in the variable's Name field on the
      Variables page when the variable is being defined.

   2. In User mode, the Properties notebook will display substituted values for
      variable references.  If a reference cannot be resolved, its text will
      not be substituted.

   3. Variables are inherited from parent objects in the install hierarchy,
      although a local definition always overrides an inherited one.


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Related topics:

Variable Reference Syntax
Internal Variables
Keyword Variables
Status Variables


ΓòÉΓòÉΓòÉ 80. Variable Definition Dialog ΓòÉΓòÉΓòÉ

The Variable Definition dialog contains three sections:

  The Variable Description section

   Variable Name
                  The name of the variable.

   Description
                  A user-level description of the information contained in the
                  variable.  This information is a comment for development
                  purposes only.

   Default value
                  The default value you assign to the variable.

  The Variable Validation section

   A user exit may be called to validate the value of a variable every time the
   variable value is changed.  Select the type of user exit to be used for
   validating the variable's value.  The same user exit options are available
   as for the Variable Resolution section.

   Two temporary variables are available whenever Variable Validation is
   called:

   {VARIABLE_NAME}
                  Contains the variable name currently being validated.

   {NEW_VALUE}
                  Contains the new value of the variable which can be updated
                  by the user exit.

  The Variable Resolution section

   If the variable resolution user exit is defined, it will be called every
   time the variable is resolved.  Two temporary variables are available
   whenever the variable resolution is called:

   {VARIABLE_NAME}
                  Contains the name of the variable currently being resolved.

   {OLD_VALUE}
                  Contains the current value of the variable, which can be
                  queried without recursively triggering user exits.


ΓòÉΓòÉΓòÉ 81. Variable Reference Syntax ΓòÉΓòÉΓòÉ

Variable references have the following format:

  { [<feature id>:[<varname> <index>.<fieldname> }

 <feature id>
           The feature ID of the install object that contains the variable's
           definition.  The feature tag is defined on the install object's
           Information settings page.

 <varname>
           The name of the variable being referenced.

 <index>
           Array index (for pre-defined lists only, such as FILE[0]).

 <fieldname>
           Struct fieldname (for pre-defined structures only, such as
           FILELIST[0].SRCFILENAME).

 The following list shows some examples of valid variable references:

    {CURRENT_FILE}
    {SELECTION}
    {FILELIST[0].SRCFILENAME}
    {P2P:SELECTION}

 Variables may include embedded variable references.  All embedded variables
 are resolved completely before the outer variable is resolved.

  For example, the variable reference:

    {FILE[{CURRENT_FILE}].SRCFILENAME}

 would first be resolved to the following variable reference (assumes
 CURRENT_FILE is set to 2):

    {FILELIST[2].SRCFILENAME}

 If the second file's SRCFILENAME is C:\OS2\MY.FILE, then this will resolve to:

    C:\OS2\MY.FIL

 Embedding can be used to any level.  In the preceding example, CURRENT_FILE
 could have been defined as {CUR_FIL}.  This would have added an additional
 variable lookup of {CUR_FIL}.

 Note:  Do not use circular references.

 When the Variable Definition dialog is filled in and OK is selected, the
 Variable List page is redisplayed with the new variable added to the list.


ΓòÉΓòÉΓòÉ 82. Variables Page ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Use this page to declare variables that can be used in any of the install
object settings pages.

Add

Declare variables by selecting the Add button on the Variables settings page.
This brings up the Variable Definition dialog.

For each variable you specify the variable name, a user-level description of
information contained in the variable, a default value, the method for
resolving the variable, and the method for validating the variable's value.
The variable can then be used in any setting on any page by enclosing the
variable string with the "{" and "}" symbols.

Delete

Delete a variable from the variable list by highlighting the variable to be
deleted and selecting the Delete button.  A message box is displayed requiring
confirmation to delete the variable. You may select Delete to delete the
variable or Cancel to cancel the delete operation.

Update or View

Update or view a variable definition by highlighting the variable to be
modified or viewed and selecting the Update button. This brings up the same
Variable Definition dialog as for the Add button.

Copy

Copy a variable definition by highlighting the variable name and selecting the
Copy  button.  A new variable is created with a name of XXX:n, where XXX is the
name of the original variable and n is some integer.  (This integer will be the
lowest possible value to produce a unique media set name, beginning with "1".)
You may then update the new variable to change its name.


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Related topics:

Variable Definition Dialog
Using Variables
Variable Reference Syntax


ΓòÉΓòÉΓòÉ 83. Configure Page 3 ΓòÉΓòÉΓòÉ

Use the Configure Page 3 (WinOs2 .Ini File Updates) to specify updates to be
made to one of the user's WinOS/2-type INI files during installation.

Each line in the list box represents a WinOS/2-type INI file to add or update
at installation time.

Add

Add an .INI file entry to the list box by selecting the Add button.  This
brings up the Update WinOs2 Type .Ini File.

Copy

Copy a WinOs2 .Ini File by selecting the name of the file to copy and selecting
the Copy button.  You may then update the new file to change its name.

Delete

Delete entries from the list box by highlighting the entry to be deleted and
selecting the Delete button.  When the Delete button is selected, a message box
is displayed requiring confirmation to delete the entry.  You may select Delete
to delete the entry or Cancel to cancel the delete operation.

Update

Update or view entries by highlighting the entry and selecting the Update
button.  This brings up the same Update WinOs2 Type .Ini File dialog as for the
Add button.


ΓòÉΓòÉΓòÉ 84. Syslevel Page ΓòÉΓòÉΓòÉ

Use the Syslevel page to specify system file information.

Note:  All features delivered using IBM Software Choice are required to include
       a syslevel file.

 Add

 Add a syslevel file to the Syslevel List by selecting the Add button.  This
 brings up the Syslevel dialog.  Only one syslevel file per feature can be
 defined.

 Delete

 Delete a syslevel file entry from the Syslevel List by highlighting the entry
 to be deleted and selecting the Delete button.  When the Delete button is
 selected, a message box is displayed requiring confirmation to delete the
 entry.  You may select Delete to delete the entry or Cancel to cancel the
 delete operation.

 Update

 Update by highlighting the entry and selecting the Update button.  This brings
 up the same Syslevel dialog as for the Add button.

 The Reboot Required check box is selected by default. Removing the check mark
 from the Reboot Required check box specifies that locked file processing
 during installation of a subfeature is not required.

 Removing the check mark from the Reboot Required check box on the top-level
 feature will not always prevent a reboot during installation. A reboot will
 take place if locked file processing is required or if any configuration file
 changes that will not take effect until the next reboot have been made during
 the installation.


ΓòÉΓòÉΓòÉ 85. Syslevel Dialog ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> Syslevel Dialog ΓòÉΓòÉΓòÉ

The Syslevel dialog contains the following field:

 Syslevel file including path:
           The fully-qualified path (including the drive) and file name of the
           syslevel file.  The file must be named syslevel.xxx, where xxx is a
           three-character file extension you assign to the feature.

 For a top-level component of a feature, specify the syslevel file for the
 feature that is being packaged. Feature Install will validate that each
 executable file packaged with the feature contains a valid enhanced version
 string and will update the proper field in the version string with the
 <Version Level>.<SYSLEVEL Suffix> of the top-level feature.

 For a subfeature, an entry in this field indicates that the subfeature is
 being used to package updates to a previously installed system component on
 the target system. Provide the syslevel file for the minimum service level of
 the component to be updated that the feature is dependent on.  During
 packaging, Feature Install will extract the information that it needs from the
 syslevel file in order to locate the system component on the target system.

 Note:  When you specify a syslevel for a subfeature, you must enter the target
        information on the File dialog (for the files packaged with the
        subfeature) as a path relative to the syslevel file.


ΓòÉΓòÉΓòÉ <hidden> Dummy ΓòÉΓòÉΓòÉ

Related topics:

File Dialog
Packaging


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Comments can be placed anywhere in the response file.  If # is the first
character in the line, the rest of the line is treated as a comment.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

(Top) object ID definition

Acceptable Values:  Any unique string with no spaces.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Current object ID; marking the beginning of the object description; this type
of block can appear multiple times.

Acceptable Values:  Any previously defined object ID


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Subfeature ID

Acceptable Values:  Any defined object ID (can appear multiple times if there
is more than one subfeature exists, or can be omitted if there is no
subfeatures).


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Object title [line# -1]

Acceptable Values:  Any ordered set of strings


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

State of the object

Acceptable Values:  Development User


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Package title

Acceptable Values:  Any string


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Company name

Acceptable Values:  Any string


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Version number

Acceptable Values:  Any string


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Version date

Acceptable Values:  Any string


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

No-value keyword; marking the beginning of a variable description; this type of
block can appear multiple times


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Variable name

Acceptable Values:  Any string with no spaces


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Verbal description of the variable

Acceptable Values:  Any string


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Default value for the variable

Acceptable Values:  Any string


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

No-value keyword; marking the beginning of a variable validation user exit
description


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Specifies the size of the stack available when the DLL entry point is called.

Acceptable Values:

      18 - Variable resolution user exit
      19 - Variable validation user exit


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Type of the user exit

Acceptable Values:

      0 - DLL (default, can be omitted);
      1 - EXE
      2 - CMD


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

User exit location

Acceptable Values:  Qualified full path


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Details for the user exit

Acceptable Values:

      For exit type 0, it means name of the procedure in DLL which is being
      called.
      For exit type 1, it means EXE file parameters.
      For exit type 2, it means CMD file parameters.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

If the session visible or minimized (for ExitType=1, 2 only)

Acceptable Values:

      0 - minimized (default, can be omitted)
      1 - visible to user


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

End of the validation user exit description


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

No-value keyword; marking the beginning of a variable validation user exit
description


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Type of the user exit

Acceptable Values:

      0 - DLL (default, can be omitted);
      1 - EXE
      2 - CMD


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

User exit location

Acceptable Values:  Fully qualified path


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Details for the user exit

Acceptable Values:

      For exit type 0, it means name of the procedure in DLL which is being
      called.
      For exit type 1, it means EXE file parameters.
      For exit type 2, it means CMD file parameters


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

If the session visible or minimized (for ExitType=1, 2 only)

Acceptable Values:

      0 - minimized (default, can be omitted)
      1 - visible to user


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

End of the validation user exit description


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

End of the variable description


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

No-value keyword; marking the beginning of a dependency description; this type
of block can appear multiple times


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

ID of the feature which state is examined to perform a dependency action

Acceptable Values:  Any previously defined feature ID


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

ID of the feature on which the action is performed

Acceptable Values:  Any previously defined feature ID


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

ID of the feature which state is examined to evaluate the need to check the
existence of the dependency condition

Acceptable Values:  Any previously defined feature ID


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Determines when the condition of the feature defined by WhenFeatureID is
evaluated

Acceptable Values:

      0 - selected (default, can be omitted)
      1 - deselected
      2 - installed
      3 - uninstalled


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Determines the condition of the feature defined by FeatureID which has to be
met for the dependency action to be performed

Acceptable Values:

      0 - exists (default, can be omitted)
      1 - does not exist
      2 - selected
      3 - is not selected
      4 - equal
      5 - not equal
      6 - less
      7 - less or equal
      8 - greater
      9 - greater or equal
      10 - contains
      11 - is part of


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Determines what dependency action is to be performed if all the conditions are
met

Acceptable Values:

      0 - select feature
      1 - deselect feature
      2 - uninstall feature
      3 - display warning
      4 - display error
      5 - set variable


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Text to be displayed for the warning (Action=3) or for the error (Action=4)
[line# - 1] (for Action=3, 4 only)

Acceptable Values:  Any ordered set of strings


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Key to be compared to the value defined by Value key in the feature defined by
ActionFeatureID (the true condition for comparison is defined by Condition key)
(for Condition=4, 5, 6, 7, 8, 9 only)

Acceptable Values:  Any key valid for this feature


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Value to be compared to the value of the key defined by Setting key in the
feature defined by ActionFeatureID (the true condition for comparison is
defined by Condition key) (for Condition=4, 5, 6, 7, 8, 9 only)

Acceptable Values:  Any value compatible to the Setting key type


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

If a Value key setting contains variables, this key determines if they are
resolved before the Value is assigned to the Setting rather than Setting is
assigned the value with variable references in it (for Action=5 only)

Acceptable Values:

      0 - variables resolved at some later point (default, can be omitted)
      1 - variables resolved before the value is assigned


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Determines if the comparison defined by Condition is case sensitive (for
Condition=4, 5, 6, 7, 8, 9 only)

Acceptable Values:

      0 - case insensitive comparison
      1 - case sensitive comparison (default, can be omitted)


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

End of the dependency description


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

No-value keyword; marking the beginning of a user exit description; this type
of block can appear multiple times


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Type of the user exit

Acceptable Values:

      0 - DLL (default, can be omitted);
      1 - EXE
      2 - CMD


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

User exit location

Acceptable Values:  Qualified full path


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Details for the user exit

Acceptable Values:

      For exit type 0, it means of the procedure in DLL is being called.
      For exit type 1, it means EXE file parameters.
      For exit type 2, it means CMD file parameters.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

If the session visible or minimized (for ExitType=1, 2 only)

Acceptable Values:

      0 - minimized (default, can be omitted)
      1 - visible to user


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

End of the user exit description


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

No-value keyword; marking the beginning of the description of an object to be
created; this type of block can appear multiple times


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Class name for the object

Acceptable Values:  Any registered class name


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Object title [line# - 1]

Acceptable Values:  Any ordered set of strings


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Setup string without spaces consisting of pairs Key=Value, delimitered by ^;

Acceptable Values:  Setup string for the object (caret-semicolon combination).
For the list of valid keys and appropriate values for them, refer for help
WPObject class in the Workplace Shell Guide.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Location of the object on the desktop

Acceptable Values:  Object ID for a folder; if the folder does not exist, the
object is placed on the Desktop (WP_DESKTOP).


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Object creation flags; determines action performed if the object already exists

Acceptable Values:

      0 - CO_FAILIFEXISTS
      1 - CO_REPLACEIFEXISTS (default, can be omitted)
      2 - CO_UPDATEIFEXISTS
      3 - CO_PRESERVEOLD

 For the full description of the flags and the corresponding behaviors, refer
 to the Workplace Shell Guide.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

End of the user exit description


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

No-value keyword; marking the beginning of the description of a class to be
registered; this type of block can appear multiple times


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Class name

Acceptable Values:  Class name defined in the DLL determined by DLLName key.
For the full description of the valid values for this key refer to help on
WinRegisterObjectClass procedure in the Workplace Shell Guide.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Name of the DLL containing the definition of the class

Acceptable Values:  Qualified full path; For the full description of the valid
values for this key refer to help on WinRegisterObjectClass procedure in the
Workplace Shell Guide.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Class to replace with the class determined by ClassName key (can be          omitted
if no class has to be replaced)

Acceptable Values:  Registered class name.  For the full description of the
valid values for this key refer to help on WinRegisterObjectClass procedure in
the Workplace Shell Guide.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

End of the user exit description


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

No-value keyword; marking the beginning of a media set description; this type
of block can appear multiple times


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Media set name

Acceptable Values:  Any string without spaces


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

No-value keyword; marking the beginning of a media description


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Media type

Acceptable Values:

      1 - diskette (default, can be omitted)
      2 - CD
      4 - hard drive


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Media capacity

Acceptable Values:  Any number in MB


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Cluster size (for Type=2 only)

Acceptable Values:  Any number


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Media description

Acceptable Values:  Any string  (can be omitted for Type=1)


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Media path

Acceptable Values:  Qualified path (can be omitted for Type=1)


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Reserved space on the media in bytes

Acceptable Values:  Any string (can be omitted if 0)


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

End of the media description


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

No-value keyword; marking the beginning of the description of a user exit being
run if there is no more space on the media


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Type of the user exit

Acceptable Values:

      0 - DLL (default, can be omitted);
      1 - EXE
      2 - CMD


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

User exit location

Acceptable Values:  Qualified full path


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Details for the user exit

Acceptable Values:

      For exit type 0, it means name of the procedure in DLL which is being
      called.
      For exit type 1, it means EXE file parameters.
      For exit type 2, it means CMD file parameters.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

If the session visible or minimized (for ExitType=1, 2 only)

Acceptable Values:

      0 - minimized (default, can be omitted)
      1 - visible to user


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

End of the media finished user exit description


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

End of the media set description


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

No-value keyword; marking the beginning of an ASCII configuration file change
description; this type of block can appear multiple times


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Determines If search for the entity to be updated is case sensitive

Acceptable Values:

      0 - case insensitive (default, can be omitted)
      1 - case sensitive


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

If GREP is used to search for the entity to be updated

Acceptable Values:

      0 - do not use GREP
      1 - use GREP (default, can be omitted)


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Configuration file name

Acceptable Values:  Qualified name


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Line to edit (for Action=1 only)

Acceptable Values:  Any string


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Line to search for for Action=0 and a substring in searched lines to scan for
for Action=1

Acceptable Values:  Any string


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Line to replace with

Acceptable Values:  Any string


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Determines action to be performed if the string defined by SearchLine is found

Acceptable Values:

      1 - replace with the string defined by NewLine (default; can be omitted)
      2 - take no action


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Determines action to be performed if the string defined by SearchLine is not
found

Acceptable Values:

      1 - add new line to beginning of file
      2 - add new line to end of file
      8 - take no action
      4 - add before or after other lines


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Line before which the line defined by SearchLine is to be inserted (for
SearchNotFound=4 only)

Acceptable Values:  Any string


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Line after which the line defined by SearchLine is to be inserted (for
SearchNotFound=4 only)

Acceptable Values:  Any string


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

If the value is treated as a group of delimited substrings, the delimiter for
these substrings (for Action=1 only)

Acceptable Values:  Any string without spaces


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Determines if the value is treated as a group of delimeted substrings (for
Action=1 only)

Acceptable Values:

      0 - no
      1 - yes


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Determines if there is a delimiter after last entry (for Action=1 only)

Acceptable Values:

      0 - no
      1 - yes


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Configuration file editing action to perform

Acceptable Values:

      0 - replace a line with another line (default, can be omitted)
      1 - edit a selected line


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Determines which occurrence of the string defined by EditLine in the
configuration file is looked for (for Action=1 only)

Acceptable Values:

      0 - first (default, can be omitted)
      1 - last
      2 - every


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Determines which occurrence of the string defined by SearchLine in the
configuration file is looked for

Acceptable Values:

      0 - first (default, can be omitted)
      1 - last
      2 - every


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Determines which occurrence of the string defined by AddBeforeLine in the
configuration file is looked for (for SearchNotFound=4 only)

Acceptable Values:

      0 - first (default, can be omitted)
      1 - last
      2 - every


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Determines which occurrence of the string defined by AddAfterLine in the
configuration file is looked for (for SearchNotFound=4 only)

Acceptable Values:

      0 - first (default, can be omitted)
      1 - last
      2 - every


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Determines action to be performed if the position to insert the string defined
by SearchLine is found (for SearchNotFound=4 only)

Acceptable Values:

      1 - replace with the string defined by NewLine (default; can be omitted)
      2 - take no action


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Determines action to be performed if the position to insert the string defined
by SearchLine is not found (for SearchNotFound=4 only)

Acceptable Values:

      1 - add new line to beginning of file
      2 - add new line to end of file
      8 - take no action


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

End of the ASCII configuration file change description


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

No-value keyword; marking the beginning of an OS/2 *.INI configuration file
change description; this type of block can appear multiple times


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Configuration file name

Acceptable Values:  Qualified name


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Application which section in OS/2 *.INI file is to be changed

Acceptable Values:  Any string


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Name of the key which value is to be changed for the application determined by
Application key

Acceptable Values:  Any string with no spaces


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Value to be set for the key determined by Key key

Acceptable Values:  Any appropriate value


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Set to 1 for the OS/2 *.INI configuration files

Acceptable Values:  1 is the only possible value


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

End of the OS/2 *.INI configuration file change description.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

No-value keyword; marking the beginning of an WinOS/2 *.INI configuration file
change description; this type of block can appear multiple times.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Configuration file name

Acceptable Values:  Qualified name


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Application which section in WinOS/2 *.INI file is to be changed.

Acceptable Values:  Any string


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Name of the key which value is to be changed for the application determined by
Application key.

Acceptable Values:  Any string with no spaces


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Value to be set for the key determined by Key key.

Acceptable Values:  Any appropriate value


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Set to 2 for the WinOS/2 *.INI configuration files

Acceptable Values:  2 is the only possible value


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

End of the WinOS/2 *.INI configuration file change description.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

No-value keyword; marking the beginning of the description of the file to be
transferred during installation; this type of block can appear multiple times


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

File location on the source

Acceptable Values:  Qualified full filename


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

File path on the source

Acceptable Values:  Qualified pathname


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

File name on the source

Acceptable Values:  Qualified filename


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Checksum for the file on the source

Acceptable Values:  Set automatically


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

EA size for the file on the source

Acceptable Values:  Set automatically


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Current number of bytes used for the file on the source

Acceptable Values:  Set automatically


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Current number of bytes allocated for the file on the source

Acceptable Values:  Set automatically


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Not used


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

File path on the target

Acceptable Values:  Qualified pathname


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

File name on the target

Acceptable Values:  Qualified filename


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

File path on the media

Acceptable Values:  Qualified pathname


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

File name on the media

Acceptable Values:  Qualified file name


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Media number in the set

Acceptable Values:  Number between 0 and n - 1 where n is the number of media
defined in the media set


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Not used


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Attributes of the file on the target

Acceptable Values:  0 - 7; in binary representation first digit stands for
System File (0 - off, 1 - on), second digit stands for Hidden File (0 - off, 1-
on); third digit stands for Read-Only File (0 - off, 1 - on).  So the values
are:

      0 - regular file;
      1 - read-only file;
      2 - hidden file;
      3 - hidden read-only file;
      4 - system file;
      5 - read-only system file;
      6 - hidden system file;
      7 - hidden read-only system file.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

End of the description of the file being transferred during installation


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

End of the install object definition