User Guide


Quick Start
Testing MOL
HFS Volumes
Starting MOL
Newworld ROM

Basic Networking
Advanced Networking
Oldworld Booting
Molrc Summary
External References




Sometimes, the keyboard mapping needs to be tweaked a bit, in particular if an international keyboard is used. Fortunately there exists a tool for this (as of 0.9.63). It is invoked like this:

bash$ startmol --keyconfig

The rest of this helptext is historical.

Internally, mol uses ADB keycodes. However, when MOL sees a key-press,
it is typically described by either a linux keycode or an X-keycod (the later if mol runs in a window). Thus, a conversion table is used. Depending on the linux distribution, the native language (and other things), it might be necessary to hand tune this conversion.

If a key is wrongly mapped. Add the line

show_key_trans: true

to /etc/molrc. Start mol and press the key. In the logfile, the keycode of the key will be printed, as well as the ADB code it is bound to. E.g.

Keycode 106 (0x6a) -> ADB code 60 (0x3c)

Consult this picture to find out which ADB code the key really should have (e.g. 38). Add a line

remap_key: 0x6a 0x38

to the molrc file. Note: If you are running in window-based mode rather than in full-screen mode, then you should instead add a line

remap_xkey: 0x6a 0x38

(the mappings for full-screen mode and X-mode are completely independent).

The keyboard mapping can also be put into a separate file:

kbd_file: filename
xkbd_file: filename

Each line should look like this:

keycode: ADB-code

In X-mode, MOL normally tries to autoconfigure the keyboard (by examining the X-symbols). Sometimes it is better to turn of this feature:

disable_xkey_remap: yes

It is also possible to specify wether linux keycodes or ADB keycodes are used by the linux kernel. Normally this is auto-probed, but it is possible to override this by adding the following line:

use_linux_keycodes: yes/no