Configuration strings

Native Oberon uses configuration strings for setting low-level configuration options. These strings are (name, value) ASCII string pairs which are stored in a table on the boot device (diskette or hard disk). Permanent values for these strings are normally set during installation using the Install or FDInstall programs in Oberon-0. The strings are read by low-level modules in the system using the Kernel.GetConfig procedure. Higher-level modules should use the more flexible Oberon.Text and the Oberon.OpenScanner procedure for configuration information.

Sometimes it is necessary to temporarily override the setting of some configuration strings. The OBL bootstrap loader provides a facility for doing this:

When booting the system, before the message "Oberon Bootstrap Loader" appears, activate ScrollLock, or hold down any shift key. The "OBL>" prompt should appear and the current values of the configuration strings are displayed. There are some options at this prompt:

The DOS-based boot loader, noboot.exe, uses a DOS file for the configuration information. The latest version of the boot loader also supports the ScrollLock or shift key method of changing the configuration strings. Instead of a built-in editor, it invokes any DOS editor, using the command line specified by the EDITOR environment variable (default "edit"). When invoking the editor, noboot.exe appends the name of the configuration file to the command line.

Configuration string definitions

The following are the configuration strings currently defined (note the version numbers displayed below; some strings are only defined for some versions of the system).

Display drivers

Input drivers

File system and disk driver

Memory management

Compatibility

Customization

Tracing

Obsolete

26 Aug 2001 - Copyright © 2001 ETH Zürich. All rights reserved.
E-Mail: oberon-web at inf.ethz.ch
Homepage: http://www.ethoberon.ethz.ch/native/