VOGONS


First post, by DinoNerd

User metadata
Rank Newbie
Rank
Newbie

I'm running dosbox 0.74-3 on Kubuntu 25.10

My desktop environment/window manager is greedily eating keys certain DOS games want to use, and not passing them through to the game.

So I'd like to get dosbox to remap something else to the keys my games want to see.

------
When I run any variant of dosbox -startmapper the result is a tiny window I can barely read, that's basically unusable for anything complex.

This is in spite of having a default dosbox.conf that successfully gets my games displayed at a reasonable size on a monitor with far more resolution than DOS ever dreamed of.

At a guess, this is the result of an extremely common issue. Lots of software seems to react very badly to displays configured with a scaling factor as well as a basic resolution, particularly on linux, and using wayland.

While I'd love to find a fix for this, or a workaround not involving removing the scaling factor, I'm not expecting this.

----
Given the headache-inducing behaviour of the dosbox mapper GUI on this system, I'd like to create an appropriate mapping file using a text editor, and bypass the GUI entirely.

I was able to get a sample mapper file by clicking the save button in the mapper GUI without having changed anything.

That has a possibly complete list of keys, and the names dosbox knows them by. But it doesn't come with a glossary. I cannot, for example, figure out what it calls the "windows" key - notorious for being referred to differently in windows, MacOS and linux documentation.

And the things the keys are mapped _to_ have unhelpful names like "key 97" (probably a lower case a)

Where can I find documentation for the language used here?

---
Also, is it possible to map key combinations? I.e. either map e.g. "x" to <alt><f1> or vice versa? Or map <shift><f2> to <alt><f1> and similar?

Or if for example my desktop manager eats <alt><f1>, would I have to remap individual keys to produce <alt> and/or <f1>wherever they are used?

I think it's the 3rd case - need to remap <alt> everywhere, even it only affects a small number of key combos. But this is pure guesswork.

--
Thanks in advance for any enlightenment.