New to DOSBox - and I have this same problem, some of my "dead-keys" can be mapped to unrecognized keys in the keymapper -
and they (mostly) work fine in that session of DOSBox - but it saves as > key_[function] "key 0" < in the mapper file...
... so I have to map again on the next session!
I will also mention that the picture in the mapper does NOT match the physical layout of my keyboard!
Mapper picture shows a row of keys starting with the tab and ending with "]", over a row starting with Caps Lock and ending with "\" - both rows to the left of a tall enter-key;
but my keyboard has a short enter-key entirely on this second row, with a slightly longer "\" key at the end of the tab-key row!
(and when I bind key_grave to the appropriate key on my keyboard - appears that using that key leaves the key stuck in the down position?)
In my mind - it would seem that if the mapper depiction were to match my physical key-layout - then these keys would be properly recognized ...
(these keys might still need to be mapped - but they would map to a recognized key!)
(As I have found 3 common physical layouts shown on the MSDN site?)
--- See Microsoft Keyboard Layout Creator - View (menu) - Options (choice) : for three Keyboard Layout Types I have referred to ---
--- (would be nice if the keymapper included something like this - if various keyboardlayout settings don't already imply it!) ---
... Sooo ... in DOSBox - how does one change the depiction of the keyboard layout in the Keymapper?
.
.
.
OR - is this a to be hoped for feature of a future version of DOSBox?
----------------------------------------------------------------------------------------------------------
As stated above - I'm new to DOSBox - my apologies if I have this in the wrong place...
If this has not yet been resolved - additional information - someone may have to dig for even more!
This problem seems to be caused by improper calls to the MS-Windows keyboard-layout/mapping support routines ...
... somehow DOSBox appears to be getting a few translations -the unknown and/or misplaced keys- supposedly from
a Multimedia Infra Red Remote receiver confused with translations coming from the actual keyboard?
(Windows Vista - FOR CERTAIN and later Windows seems to incorporate these Infra Red Remote drivers into the WIN-standard-drivers package;
apparently whenever the receiver is present - it is presumed that the Infra Red Remote, or maybe an IR Keyboard, will also be in use!)
THERE has got to be a call that will allow you to get the keyboard-key values before the Infra Red drivers alter them!
I currently lack the appropriate tools to dig out just how this is happening?
The articles that I was reading on MSDN on Keyboard Layout/Mapping - if I remember correctly - have the affected keys assigned to virtual labels
such as key_oem(1), key_oem(2) etc. I could relocate said articles and provide proper refereneces - if this would help anyone?
