The root element of any pInstaller XML File Set this to true to force a reboot at the completion of the installation. This is the product name used for user interface elements in the installation, including the uninstaller entry. Setting this to true runs the installation without presenting a user interface (this is ideal for controlled environments, such as automated enterprise deployments) This group of attributes allows you to force particular dialogs to show during an otherwise silent installation. Shows the PreInstallation Message with an ok button Shows the user selection dialog with an ok button Shows the post installation dialog with an ok button Show a final thank you for installing <productName> message Generates a logfile of the installation Details requried to show a rich text message prior to installation (such as a license agreement) The title to display The caption to display The name of a text or rtf file to display Shows "I accept the license agreement"/ "I do not accept the license agreement" radio buttons on the form and will cancel if the user does not select the "I accept the license agreement" radio button. Defaults to select one of the radio buttons. Details required to show a rich text message after the installation (such as a readme) The title to display The caption to display The name of a text or rtf file to display Details for implementing registry changes. Defines the Root Key of the registry to write to. Setting this to HKEY_USERS will set pInstaller to attempt to write the setting to each users registry hive, and is not recommended The path tree for the registry change (e.g. \Software\abcCo\myConduit) The name of the value to be created The type of value to be created. Must be "stringValue" or "integerValue" Ignored if valueType is set to "integerValue". This is the value to be written. Ignored if valueType is set to "stringValue". This is the value to be written. A registy file to be processedr The name of the file to be processed This setting should only be used if you are using INSTALL_KEY variable substitution inside of your registry file. Specify an executable to run after the installation is complete here. Any command line parameters to be applied to the executable should be specified here. Setting this to true will run the executable from the installation directory without installing the file If you select doNotInstall, setting this value to true will display the file as a user selectable choice. The file will only be executed if the user selects it. By default, pInstaller will wait for the completion of the installer before completing the installation. If you want to change this behavior, set this value to true The default path for installing PC Files. Can be a hard coded path or use one of the following variables: (1)$HOTSYNCDIR (installs to the users HotSync directory) (2)$PALMUSERDIR (installs to the user path for any users selected for installation (3)$WINDIR (installs to the windows directory (4)$SYSDIR (installs to the Windows\System32 directory or equivalent) (5)$PROGFILESDIR (Installs to C:\Program Files or the language appropriate equivalent) The information used to register the conduit. The name of the dll to register (destination variables will be parsed). Note that if this is a Java conduit, the value must be jSync13.dll and if it is a COM Conduit, the value must be COMConduit.dll, otherwise, this should be the name of your conduit Each application on the handheld has a unique creator ID associated with it. This ID is used to link the Conduit and the Palm application. To register a Creator ID for your application with Palm, visit http://www.palmos.com/dev/tech/palmos/creatorid/ This value determines when your Conduit executes in relation to other conduits. It must be a value between 0 and 4 (lower numbers execute first). In general, the default value of 2 is fine. Conduit’s directory name. This is a subdirectory in the user’s directory on the desktop computer. Within each user’s directory, each conduit can have a directory for file storage. For example, it could hold support files, such as record ID mapping files, needed to accurately perform a record-level synchronization with a third-party database. Name of the desktop file that your conduit synchronizes with the handheld database. Your conduit can synchronize with more than one file, however. Note that this configuration entry can be either a full path and file name, or only a file name. If the value is only a file name, the file can be found in the directory specified by the Directory entry. Name of the database on the handheld. The conduit uses this name to create the database on the handheld if the database did not exist before synchronization. The name is case-sensitive. Name of the user for whom this conduit has been installed. Note: this entry is not currently used. Anything you want to say about your conduit. For example, if an installer discovers a conduit with the same creator ID already installed, it could display this string and ask the user which conduit should be used. However, the Palm Desktop software does not currently uses this entry. Additional nformation used to register Java Conduits. Directory that contains all the classes used by the selected Java-based conduit. This is the value of CLASSPATH required to find all the classes invoked by the Java-based conduit. The CLASSPATH setting in the Windows environment variable (NT) or autoexec.bat files is ignored by the Java-based conduit at runtime. The ClassPath13 entry is used only for Java-based conduits; other conduits ignore it. (Conduits written for an older version of the JSync module based on JRE 1.1.3 use the ClassPath entry instead. All conduits written for JSync based on JRE 1.3 must use the ClassPath13). Full name of the Java-based conduit class (including package). This entry is used only for Java-based conduits; other conduits ignore it. Additional nformation used to register COM Conduits. If your conduit is a standard executable (.exe), then this value is the full path and file name of your client conduit — for example, C:\Program Files\Microsoft Visual Studio\VB98\VB6.exe. If your conduit is an ActiveX server, this value is the notification object’s PROGID (also called the Programmatic ID) — for example, SimpleDb.CNotify. This entry is used only for COM conduits; other conduits ignore it. Names for different installation types such as minimal, default, etc.) A description of the file group which is presented to the end user A unique numerical ID for this file group If "true" then this file group is installed by default. The information required to install a file The name of the file to be installed can be a hard coded path (not recommended in most cases) or one of the following variables: (1) $PALM_DEVICE (installs to the users palmos device) (2)$HOTSYNCDIR (installs to the users HotSync directory) (3)$PALMUSERDIR (installs to the user path for any users selected for installation. For obvious reasons, it is not valid to make this the destination for a conduit. (4)$WINDIR (installs to the windows directory (5)$SYSDIR (installs to the Windows\System32 directory or equivalent) (6)$USERINSTALLDIR (installs to the directory selected by the user as the installation path) If set to 0, this file will always be installed. If set to another number, that number must match a filegroup. A description of the file to be installed. A boolean value that controls the default behavior for this file when it's file group is selected for installation. Set to "true" if your Palm application supports reading this file from an expansion card. Set to "true" to only allow the users to install this file to an expansion card. If this is a COM dll that needs to be registered with Windows, set this value to "true" If this is a Palm notifier Dll, set this value to "true" This structure allows you to specify the settings to create a shortcut for this file. The description for the shortcut. Any parameters to be appended to the executable for the shortcut The startup directory for the shortcut (destination variables will be parsed) The Character to be used as a shortcut key for the icon The default window state for the shortuct The icon path for the shortcut. The icon index for the shortcut Setting this to true will add a copy of the icon to your desktop Allows users to pick and choose individual files for installation (n.b.- all installationFiles assigned to filegroup 0 are ALWAYS installed. Generally speaking, your palm app and conduit should always have a groupID of 0). If you are installing PC files, this allows you to create Start Menu Shortcuts If you set this to true, the user is prompted to select their own Start Menu Path for the icons. This is the default path for the Start Menu Icons. Start..\Programs (or the language appropriate equivalent) is assumed, do not include it. If you set "allowUserShortcutPathPrompt" to false, any defined shortcuts will be installed here. Setting this to true allows the user to select the path for installation (only applies if PC files are included in the installation) The name of the COM Conduit Installer executable (included with the CDK) If true, the COM Conduit Installer is run in the background The name of the JSync Installer executatble (included with the CDK) If true, the JSync Installer is run in the background