Red Hat NETSCAPE MANAGEMENT SYSTEM 6.01 - CUSTOMIZATION Especificações descarregar pdf (Página 98)

If Player does not recognize the remote server as an XFree86 server, add the

xkeymap.usekeycodeMapIfXFree86 property and set it to TRUE.

This property tells Player to use key code mapping if you are using an XFree86 server, even if it is

remote.

For example: usekeycodeMapIfXFree86 = "TRUE"

Understanding X-Key Codes and Keysyms

Pressing a key on a PC keyboard generates a PC scan code based roughly on the position of the key. For

example, the Z key on a German keyboard generates the same code as the Y key on an English keyboard

because they are in the same position on the keyboard. Most keys have one-byte scan codes, but some keys

have two-byte scan codes with prefix 0xe0.

Internally, Player uses a simplified version of the PC scan code that is a single nine-bit numeric value, called

a v-scan code. A v-scan code is written as a three-digit hexadecimal number. The first digit is 0 or 1. For

example, the Ctrl key on the left side of the keyboard has a one-byte scan code (0x1d) and its v-scan code is

0x01d. The Ctrl key scan code on the right side of the keyboard is two bytes (0xe0, 0x1d) and its v-scan code

is 0x11d.

An XFree86 server on a PC has a one-to-one mapping from X key codes to PC scan codes, or v-scan codes,

which is what Player uses. When Player is hosted on an XFree86 server and runs a local virtual machine, it

uses the built-in mapping from X key codes to v-scan codes. This mapping is keyboard independent and

should be correct for most languages. In other cases (not an XFree86 server or not a local server), Player

must map keysyms to v-scan codes by using a set of keyboard-specific tables.

An X server uses a two-level encoding of keys, which includes the X key code and the keysym. An X key

code is a one-byte value. The assignment of key codes to keys depends on the X server implementation and

the physical keyboard. As a result, an X application normally cannot use key codes directly. Instead, the key

codes are mapped into keysyms that have names like space, escape, x and 2. You can use an X application to

control the mapping by using the function XChangeKeyboardMapping() or by the program xmodmap. To

explore keyboard mappings, you can use the xev command, which shows the key codes and keysyms for

keys typed into its window.

A key code corresponds roughly to a physical key, while a keysym corresponds to the symbol on the key

top. For example, with an XFree86 server running on a PC, the Z key on the German keyboard has the same

key code as the Y key on an English keyboard. The German Z keysym, however, is the same as the English Z

keysym, and different from the English Y keysym.

Change How a Specific Key Is Mapped

If some keys on the keyboard do not work correctly in a virtual machine, you can set a property that makes

a modification to the map. To change how a specific key is mapped, you add the appropriate property to the

virtual machine configuration (.vmx) file or to ~/.vmware/config.

Prerequisites

Verify that the X server is an XFree86 server running on a PC. If the X server is remote, configure it to

use key code mapping. See “Configure Keyboard Mapping for a Remote X Server,” on page 97.

Determine the X key code and the corresponding v-scan code for the key. To find the X key code for a

key, run xev or xmodmap -pk. See “V-Scan Code Table,” on page 100 for most v-scan codes.

Power off the virtual machine and exit Player.

Procedure

1 Open .vmx or ~/.vmware/config in a text editor.

Getting Started with VMware Player

98 VMware, Inc.

1 2 ... 93 94 95 96 97 98 99 100 101 102 103 ... 115 116

Comentários a estes Manuais

Sem comentários

Red Hat NETSCAPE MANAGEMENT SYSTEM 6.01 - CUSTOMIZATION Especificações Página 98

Comentários a estes Manuais