Config
Previous  Top  Next

The [Config] section defines the configuration files that are loaded when the system is started.


EntryAssignment  
BlkFilesThe BlkFiles entry specifies the block definition files to be loaded. If you don't specify a file here the block file with the project name is loaded. You usually want to include the system block definitions from system\system.blk. In addition you want to provide your specific block definitions in one or multiple additional files. Multiple file names are separated by spaces.  
LoadThis entry specifies the configuration files to be loaded when the system comes up. The file names specified in this enty must be separated by spaces. The path names can be absolute or relative to the working directory the system starts in. It is important that the files specified have well known extensions. The recognized extensions are:  
*.cpd:   Command definition file  
*.cpb:   Command batch file  
*.cm:   Command menu file  
*.dt:   Desktop  
*.scr:   Screen file  
*.log:   Log file  
*.py?:   Python module  
 
It is possible to specify more than one configuration files for all types except the desktop. If no desktop file is specfied the desktop configuration that was active when the last session was closed is loaded (autodskN.dt). When a desktop file is specified this desktop is loaded on every start of the system. This enables the same appearance of the system with every start. Loading the desktop file, if specified, is always deferred to the end of the load sequence.  

Example
The following example installs a desktop, two command files, one monitor condition file and one monitor check file.


[Config]
BlkFiles =system\system.blk  MyProject.blk demo\mon1\mon1.blk
Load     = general.dt mimi.cm startup.cpb