Dosbox: decent keyboard mapper file?


hmc

Active Member
Joined
Dec 19, 2011
Messages
787
Location
Bavaria, Germany
Hi guys,


I'm having problems with the keyboard inside dosbox 0.74 (from the PND).


E.g.:


- The colon (":") doesn't work


- The arrow keys (Dpad) don't work


Does anyone have a good mapper file, that solves those problems?


I already tried crosspoint's mapper.txt file, but that one for me has the problems described above.


I'm running the HP Connectivity Pack under dosbox.


Thanks!
 
Last edited by a moderator:
The colon is shift-semicolon. shift-fn-< (don't get those the wrong way or it will be completely wrong)


I've never had problems with the arrow keys though. I suppose a better map file would be the best solution, I just got used to the standard mapping. :(
 
Last edited by a moderator:
make sure you have use scancodes off

Thanks! That did the trick.

The colon is shift-semicolon. shift-fn-< (don't get those the wrong way or it will be completely wrong)


I've never had problems with the arrow keys though. I suppose a better map file would be the best solution, I just got used to the standard mapping. :(

I confirm that in standard mapping this works, However, it doesn't work with the mapper file I used.


I guess I'll have to look deeper into this mapping stuff and try to develop a good mapper file for the Pandora.


This was such a mess on the Zaurus back then, that I am now afraid of doing this. ;-)


Thanks guys.
 
Last edited by a moderator:
I once did a rather useful mapper file and some explanations. See this post:


http://boards.openpa...nf/#entry178850


I also realized a "perfect" keyboard mapping, but since the Pandora keyboard is non-standard this requires an additional keyboard driver for DOS. In case the mapper file in above post isn't sufficient for your needs, I can try to explain the config path to that.
 
Last edited by a moderator:
Great, thanks bukkit!


Since I plan to use Dosbox for advanced keyboard-based working on a DOS setup replacing a complete HP 200LX, it would be good to have "perfect" mapping.


Or: Can you shortly explain, what's *not* covered with your mapper file? So if that's relevant, I'd be grateful for a rough explanation of your perfect mapping setup.


I also think, that such a mapping solution (either the perfect one or your mapper file only) and good graphics configuration (without black borders, I have finally found the necessary hints here) should find their way into Pickle's Dosbox PND some day! Pickle, are you listening?
 
Last edited by a moderator:
Got an idea.


As far as I understand the mapping scheme, we are mapping KEYS here. Entire keys. That's the reason, why the colon cannot be mapped correctly, because it's the shifted semi-colon on a US keyboard (?) and on the Pandora it's two seperate keys.


However, the dosbox.conf value for toggleing usage of scancodes seems to suggest, that we could also map on a lower level, not entire keys, but each of the several "meanings" of a key separately, which would enable correct mapping independent on the "contents" of one key in the key mapping driver of DOS inside DOSBox.


Is this assumption correct? Should we look into scancode-based mapping rather than key-based mapping?
 
Or: Can you shortly explain, what's *not* covered with your mapper file?

I answered that in the mentioned post. Just a short example: Both Fn-comma and Fn-dot map to the same DOS key: Semicolon. (You'd expect that for Fn-comma, less for Fn-dot.) You get the colon by typing Shift-Fn-dot (and Shift-Fn-comma, of course). Most keys are easy to find that way (The Rule: try adding shift if it doesn't work like you expect), but not all. Some more details, like said, in my post about that, in the spoiler section.

As far as I understand the mapping scheme, we are mapping KEYS here. Entire keys. That's the reason, why the colon cannot be mapped correctly, because it's the shifted semi-colon on a US keyboard (?) and on the Pandora it's two seperate keys.

That's right. The DOSbox is unable to receive sth like a shifted value. Insead it receives a "1" and a "Shift" and infers a "!" from the keyboard layout determined by the driver. And as far as I know there is no standard keyboard layout using the same combinations of Key/Shifted Key the Pandora seems to entertain.

However, the dosbox.conf value for toggleing usage of scancodes seems to suggest, that we could also map on a lower level, not entire keys, but each of the several "meanings" of a key separately, which would enable correct mapping independent on the "contents" of one key in the key mapping driver of DOS inside DOSBox.


Is this assumption correct? Should we look into scancode-based mapping rather than key-based mapping?

Also true. And I walked that way, but enabling scancodes resulted in several characters not arriving in DOSbox in any form, therefore not being mappable. (To be entirely correct, having bits stripped and arriving at the same key marked "unknown".)


Then I thought there could be a way of generating DOSbox-compatible scancodes via .pndXmodmap and then map those. But that would not help at all with mapping shifted values to unshifted values, which the Pandora keyboard layout demands. So, that's also a cul-de-sac unless I miss something.


So I used the xkeyb driver from http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/xkeyb/xkeyb/ ( http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/xkeyb/xkeyb/xkb1_15x.zip to be precise, they have a handful).


That required some awkward back-and-forth-mapping which made the reslulting DOSbox mapper file a tad unpleasant for normal use, but, in combination with the configured xkeyb driver, resulted in a keyboard where every single key was where it belonged (and some room for Umlaute and stuff).


You seem to be very understanding and willing to experiment, so should I leave those configuration files as an exercise for you? :)


(For the time being I have to; I don't have them at hand.)
 
Last edited by a moderator:
thanks, bukkit!


Yes, I'd like to experiment with those files. It would be great, if you could send them to me.
 
Back
Top