Keymap.ini
The keymap.ini file contains the mappings between the keys and the ASCII codes that correspond to those keys. Do not change the keymap.ini file since the file is specific to the platform your application server is running on.
For Linux, most of the Meta RF key values are the same as on Windows with some exceptions. These items are not supported no not matter what value you configure for them:
|
Linux |
Windows |
|---|---|
|
#CTRL_C=3 |
CTRL_C=3 |
|
#CTRL_V=22 |
CTRL_V=22 |
|
#HOME=262 |
HOME=262 |
|
#END=358 |
END=358 |
|
#CTRL_TAB=482 |
CTRL_TAB=482 |
|
#CTRL_DELETE=527 |
CTRL_DELETE=527 |
|
PAD_ENTER=343 |
PAD_ENTER=459 |
|
SHIFT_TAB=353 |
SHIFT_TAB=351 |
|
BACKSPACE=263 |
BACKSPACE=8 |
|
ESC=27 |
ESC=27 |
|
ENTER=10 |
ENTER=10 |
|
TAB=9 |
TAB=9 |
|
INSERT=331 |
INSERT=331 |
|
PAGEDOWN=338 |
PAGEDOWN=338 |
|
PAGEUP=339 |
PAGEUP=339 |
|
DELETE=330 |
DELETE=330 |
|
DOWN_ARROW=258 |
DOWN_ARROW=258 |
|
UP_ARROW=259 |
UP_ARROW=259 |
|
LEFT_ARROW=260 |
LEFT_ARROW=260 |
|
RIGHT_ARROW=261 |
RIGHT_ARROW=261 |
|
F1=265 |
F1=265 |
|
F2=266 |
F2=266 |
|
F3=267 |
F3=267 |
|
F4=268 |
F4=268 |
|
F5=265 |
F5=265 |
|
F5=269 |
F5=269 |
|
F6=270 |
F6=270 |
|
F7=271 |
F7=271 |
|
F8=272 |
F8=272 |
|
F9=273 |
F9=273 |
|
F10=274 |
F10=274 |
|
F11=275 |
F11=275 |
|
F12=276 |
F12=276 |
If you are having problems with one or more function keys, or the or keys are not working as expected, these causes are the most common during troubleshooting:
- Check the rfuser Linux login
.bashrcfile for stty commands that explicitly change the raw characters used by and . Some telnet clients, such as PuTTY, provide a configuration for these keys. You may need to change these keys in your telnet client configuration, or in.bashrc. - Your
keymap.inimay have an incorrect integer value. Use Key Finder on the (exit) menu in Meta RF to discover what integer is expected, then compare that to the integer for the corresponding key inkeymap.ini. Editkeymap.inito match what Meta RF expects. - If some of the RF screens show labels twice, or are adding extra whitespace inappropriately, this issue could be caused by an incorrect TERM configuration. For example, your RF equipment or the UNIX startup file,
.bashrc, might need to be changed from xterm to vt300. - Session configuration within the telnet client software installed on the RF equipment is missing configuration for one or more function keys.
- In this case, RF administrators can discover what value is expected at the terminal. The RF administrators can use a Windows workstation and the PuTTY telnet client to exit from the Meta RF application to the command prompt using a required password required. At the command prompt, press -, then press the function key that does not work on your keyboard. This step should print the characters needed by your RF equipment’s function key configuration. For example: A typical value for is: ^[[15~.