Workstation User’s Manual
346 VMware, Inc.
WorkstationdetermineswhichtabletousebyexaminingthecurrentXkeymap.
However,itsdecision‐makingprocesscansometimesfail.Inaddition,eachmappingis
fixedandmightnotbecompletelycorrectforanygivenkeyboardandXkey
code‐to‐keysymmapping.Forexample,ausermighthaveswappedCtrlandCaps
Loc
kusin
gxmodmap.Thismeansthekeysareswappedinthevirtualmachinewhen
usingaremoteserver(keysymmapping)butareunswappedwhenusingalocalserver
(keycodemapping).Tocorrectthissituation,useconfigurationsettings.
To configure how keysyms are mapped
1PoweroffthevirtualmachineandclosetheWorkstationwindow.
2O
nthemach
inethathoststhevirtualmachine,addoneormoreofthefollowing
linestothevirtualmachineconfiguration(.vmx)fileorto~/.vmware/config:
TodisableXkeycodemappingtomapkeysymsratherthankeycodesto
v‐scancodes,setthefollowingproperty:
xkeymap.nokeycodeMap = "TRUE"
Formoreinformation,see“XKeyCodesComparedtoKeysyms”onpage 344.
IfWorkstationhasatableinthexkeymapdirectoryforyourkeyboardbut
cannotdetectit,setthefollowingproperty:
xkeymap.language = "<keyboard_type>"
Thevalue<keyboard_type>mustspecifyoneofthetablesinthexkeymap
directory.However,thefailuretodetectthekeyboardprobablymeansthe
tableisnotcompletelycorrectforyou.Youmightneedtocreateamodified
tableandusethexkeymap.fileNameproperty,describednext.
Touseadifferentkeysymmappingtablethatisnotinthexkeymapdirectory,
setthefollowingproperty,where<file_path>isthepathtothetable:
xkeymap.fileName = "<file_path>"
Thetablemustlistakeysymforeachkeybyusingthefollowingform:
<sym> = "<v-scan_code>"
The <sym>valueisanXkeysymname,and<v-scan_code>isaC‐syntax
hexadecimalnumber(forexample,0x001).Useanewlineforeachkeysym.
Compilingacompletekeysymmappingisdifficult.VMwarerecommends
editinganexistingtableandmakingsmallchanges.
Comentarios a estos manuales