Runtime Environment


The following CARIS-defined environment variables are required:

If uslxafm is not defined, no text can be displayed on a map.  Maps that are profiled to display text on opening will generate error messages, but still open. If any other variables are undefined, no maps can be opened. Attempts to do so, generate various error messages.

The following SICOM-defined environment variables are optional:

If SICOM_PROFILE is undefined, the SDM generates a default profile (and warns that it is doing so).  The remaining environment variables, if set, point to files that are used to customize the SDM Main menu.

* profile.text files are generated by SDM Profiler Version 3.2.  The binary form of the SDM profile generated by the Version 2.5 profiler are still usable by SDM Version 3.2.

There are two ways to establish these environment variables:

The global approach uses the standard operating system mechanisms, i.e. the autoexec.bat or the registry. Global variables are full paths to the various support files.  When using global variables, the support files can be anywhere on the file system, and can have any names, so long as each variable corresponds to a file of the proper type.  However, it is recommended that all support files be kept in a single directory, and that the above naming conventions be used. 

The local approach uses a single directory which must be named "Support", and must contain support files with the above naming conventions.  Upon startup, the SDM looks for this directory parallel to the current directory (See How the Current Directory is Set.)  If such a directory is found, paths to the files therein will be used to set the corresponding environment variables.  In addition, the CARIS Color Index File found in the support directory is applied to all maps opened by the SDM. (Normally, each map would use its own, local color index file if there is one.)