MEGMS logo - go to the home page
  1. Home

    1. MEGS_Log

      1. MEGS_Log Downloads

      2. MEGS_Log Documentation

        1. MEGS_Log version 3.3 Help

          1. Copyright notice and licence agreement

          2. How to contact MEGS_Log support

          3. What's new in MEGS_Log 3.3

          4. Concepts in MEGS_Log

          5. How to carry out common tasks within MEGS_Log

          6. Menus and commands

          7. Window elements and dialogs

          8. List of appendices

            1. MEGS_Log error messages

            2. Registry key reference

            3. Frequently asked questions

            4. List of short-cut keys

            5. Command line options

          9. MEGS_Log version 3.3 Help Index

    2. CoalLog tools

    3. Fortran Tools

    4. Contact Us

  2. Site map

"Let's model me a mine"


Mining & Exploration Geological Modelling Services

Previous topic Parent topic Home topic Next topic

Registry key reference

This following information is intended for system administrators rather than end users. End users should change MEGS_Log settings using the various dialog boxes (particularly the Options dialog box) that are documented elsewhere.

Note that an incorrect change to the registry could render your computer inoperable. It is recommended that you back-up the registry before you attempt to make any changes. Consult your system documentation for further information.

Note that many aspects of MEGS_Log configuration, such as the hatches available for display, the mapping from hatches to rocktypes, the lists of seams and plies available for correlation and the default settings for display of each geophysical trace are dealt with through the configuration file.

The presence and data of the HKEY_LOCAL_MACHINE\Software\MEGMS\MEGS_Log 3.0\ClientMode value is checked during application startup. If it contains 1 (as a REG_DWORD) then MEGS_Log is run in Client mode. In client mode, the configuration file is loaded only from the directory that contains the MEGS_Log application executable, and editing of MEGS_log configuration is prevented.

(MEGS_Log 3.3 is a 32 bit application and hence uses the 32 bit view of the registry on 64 bit versions of Windows. On 64 bit Windows the name of the above registry key is HKEY_LOCAL_MACHINE\Software\Wow6432Node\MEGMS\MEGS_Log 3.0\ClientMode.)

Other MEGS_Log v3.3 settings are currently only saved under the HKEY_CURRENT_USER\Software\MEGMS\MEGS_Log 3.0 registry key. These other registry settings are therefore user specific.

MEGS_Log 3.3 generall uses the same registry keys as MEGS_Log 3.0, 3.1 and 3.2. However, the "root" MEGS_Log registry location and the various sub-keys and values may change from MEGS_Log version to version and even from build to build within a version.

Default registry key settings are created during application installation. Similar defaults are hard-coded within the application code in the event that the registry key cannot be read on application start-up.


Options around importing and exporting CSV files, generally corresponding to the settings available through the CSV options tab of the Options Dialog Box.


Options around importing and exporting Prolog version 2.1 and 3.0 files, generally corresponding to the settings available through the Prolog options tab of the Options Dialog Box.


Options around importing and exporting Prolog 4.x files, generally corresponding to the settings available through the Prolog 4 options tab of the Options Dialog Box.


General MEGS_Log options.


Internal dialog box and application state settings.


Settings relating to the MEGS_Log display, many of which correspond to settings available through the View tab or the Fonts tab of the Options dialog box.


Settings from the Page Setup dialog box.

Licence related settings

Licence settings, including those from the Licence Information dialog box. These settings are kept under the HKEY_CURRENT_USER\Software\MEGMS\Licences key, common to all versions of MEGS_Log.