Changing Custom Module Properties

The following properties can be configured for each module listed in Pharos Administrator.

General

Property	Description
Name	The Module name uniquely identifies a Custom Module in the Pharos system; it appears only in Pharos Administrator.
Install Order	The Module's position in the order execution of multiple Custom Modules in the same installation. Custom Modules with lower numbers run first. Pharos-supplied modules and Queue modules are run first, then any custom drivers and Custom Modules.
Attributes	This property lists extra attributes that may need to be specified for the module. These attributes apply to all operating systems.

Property

Description

Name

The Module name uniquely identifies a Custom Module in the Pharos system; it appears only in Pharos Administrator.

Install Order

The Module's position in the order execution of multiple Custom Modules in the same installation. Custom Modules with lower numbers run first.

Pharos-supplied modules and Queue modules are run first, then any custom drivers and Custom Modules.

Attributes

This property lists extra attributes that may need to be specified for the module. These attributes apply to all operating systems.

Property	Description
32-Bit Module Filename	The path and file name of the module file/executable that should be run when installing on a 32-bit operating system. To change the module's file name and path, enter a new value into this field, or click the editing button to browse for the file.
32-Bit Module Behavior	A list of options that affect the Custom Module's behavior when installing on a 32-bit operating system. Reboot needed to finish install - If this box is ticked, the user will be prompted to reboot the PC once the entire package is installed. Continue install if module fails - By default, if any module fails to install, the entire install process will be halted. If failure to install this module is not a critical error, tick this box. Module does not write result.txt file - All Pharos-supplied modules produce a file called result.txt, which contains information about the success or failure of the module's install. Custom modules can produce a result.txt file as well - if this module does not produce a file, tick this box. Skip module - Some modules may need to be run by the installer (e.g. executables, batch files), while others may simply need to be copied to the install directory (where a later module may make use of them). Tick this box if the module does not need to be run by the installer.
64-Bit Module Filename	The path and file name of the module file/executable that should be run when installing on a 64-bit operating system.

Property

Description

32-Bit Module Filename

The path and file name of the module file/executable that should be run when installing on a 32-bit operating system.

To change the module's file name and path, enter a new value into this field, or click the editing button to browse for the file.

32-Bit Module Behavior

A list of options that affect the Custom Module's behavior when installing on a 32-bit operating system.

Reboot needed to finish install - If this box is ticked, the user will be prompted to reboot the PC once the entire package is installed.
Continue install if module fails - By default, if any module fails to install, the entire install process will be halted. If failure to install this module is not a critical error, tick this box.
Module does not write result.txt file - All Pharos-supplied modules produce a file called result.txt, which contains information about the success or failure of the module's install. Custom modules can produce a result.txt file as well - if this module does not produce a file, tick this box.
Skip module - Some modules may need to be run by the installer (e.g. executables, batch files), while others may simply need to be copied to the install directory (where a later module may make use of them). Tick this box if the module does not need to be run by the installer.

64-Bit Module Filename

The path and file name of the module file/executable that should be run when installing on a 64-bit operating system.


64-Bit Module Behavior	A list of options that affect the Custom Module's behavior when installing on a 32-bit operating system. See "32-Bit Module Behavior" for a detailed description of the options.