The Registry
Description of the entry's in the registry used by
the kernel.
The ConSys System kernel uses the registry for loading key parameters at boot time. The information in the registry is accessed through the class CConSysEnviroment. When this class is constructed it enters the registry and load's the information available.
The registry consists of two parts:
- A common part that every machine running the kernel has. This part has machine specific entry's, and a lint to a 'server'.
- The registry on the server machine contains the common information for all machines on the system. Typically will the 'server' be the same machine that contains the data base. The system is unable to start up if the server is not running.
Below is a schematic view of the registry for a normal computer
HKEY_LOCAL_MACHINE/SOFTWARE + ConSys System + server : REG_SZ : \\Server_name + Devices + Device0 This entry is passed on to the device + Device class : REG_DWORD : Class Id for dynamic construction + Device library : REG_SZ : name of dll where the class is located. + Additional information specific for the device . . + DeviceN
There is no limit to the number of devices that can be loaded into the kernel. The first device (Device0) is the kernel (se Device Layer), and can not be substituted for another device.
For the server the registry will have the structure:
HKEY_LOCAL_MACHINE/SOFTWARE + ConSys System + server : REG_SZ : \\Server_name (this machine) + database name : REG_SZ : Name of the data base. Used for loading the database. + timeout : REG_DWORD : timeout time for a client/server communication + Devices + User priorities + Priority0 + user group : REG_SZ : The name of the user group. + read priority : REG_DWORD : The reading thread priority. + write priority : REG_DWORD : The writing thread priority. . . + PriorityN + Transport This entry is passed on to transport initialization + transport class : REG_DWORD : The class id for the transport class + transport library : REG_SZ : The library in which the class is located. + Additional information for the transport layer
The server also has a list of devices. The first device in the list is, as on all machines, the kernel itself. This structure ensures that the system may run as a stand alone system.
For managing different priorities for the users the ' User priorities'
is listed. the system can manage any number of priority levels.
The levels must be listed in accenting order ( 'Priority0' has
higets priority). This scheme is implemented for two reasons:
The system administrators must be able to force a reading or writing.
Also this priority scheme may be used to give alarm monitors a
'real time' priority superseding all other communication.
Last Modified 11 January 2019