Maybe the "5" key refers to the one on the numeric keypad. In any case, you can probably map the key to something else that will work with the mapper. The DOSBox manual (readme) has information about using the mapper.

Hmmm - Thanks. I saw the mapper mentioned before I posted but could not get it running. F1 (or FN-Ctrl-F1 on my Mac) didn't do anything. Any other tips to get the mapper going? I'm pretty tech savvy so I could probably figure things out if I can get to the mapper. But I'm a relatively "newer" Mac users so still trying to figure out Mac handles certain things.

The README has so extraordinarily useful hints on how to start the mapper.

on a mac you need fn-ctrl-cmd-f1. All other f-keys don't need cmd, only f1. (at least last time I tried it)

Hmm - tried CTRL-F1, tried various different combos, tried to make the Mac keyboard have the F1 keys act like regular function keys. I'm trying to figure out how to enable boxer manually from the Terminal (haven't figured that out yet). Read the Read-Me file but didn't get me too far....any help appreciated.

First of all did you try cmd-ctrl-f1 or cmd-ctrl-fn-f1?
Also you might have to disable stuff in OSX' keyboard preferences since some systemwide f-keys bindings might wreak havoc with other dosbox keycombinations.

@qbix, a selectable keyboard layout for Apple's short bluetooth keyboard might be useful, since those are more and more common these days for mac users.

This forum is for plain DOSBox, not boxer. Who knows what the author did to the keyboard handling.

dominus. Not sure how to detect those.

@op, yes, if you have problems with boxer, contact the boxer author. He hooks into dosbox extensively so, qbix wrote, it could very well be an issue with boxer.

@qbix, maybe not automatically but through some keyb command. Or someone needs to do a sensible mapperfile 😉