DOSBox don't have, don't need, and don't support an C:\AUTOEXEC.BAT file. Anything you want to do when DOSBox starts is configured inside the dosbox.conf file.

Reading the excellent README-file that came with DOSBox is known to help people figuring out such things.

Well, I did, but I guess I misread it then. My apologies, no need to snap, dude...

Oh noes - you haven't seen me snap just a tiny bit. If I had snapped at you, you would be crying your eyes out in your psychotherapists office.

dude, you need to relax 😀

No he doesn't, because he is relaxed. His first reply was on the point.

Unfortunately, this is a problem I cannot solve either. See, the following is DOSBOX keymapper:

The keymapper only gives you lowercase characters (for example, 'a' instead of 'A', semicolon instead of colon). When you want to get key_a event, for example, you click on the virtual keyboard and get the key_a event.

Question is: what are you supposed to do when you want to get key_A event instead of key_a? I have read the 'Mapper' section in DOSBOX README, as well as DOSBOX wiki, yet I still couldn't figure how to get uppercase event. I have experimented with things like mod3 and hold, but nope.

On the other hand, messing around with keymapper is not something I need to do very often.

Keymapper is for remapping physical keys. So it is NOT possible to discern
between A and a, and this would make no sense as they are the same key.

I'm in this poor man's boat too, and I have read through the ReadMe to no avail. I need to add an even (key_colon i would guess) but it seems one can only add binds and mods.

I managed a workaround by putting in the commands under the 'autoexec' part of the .cfg file as suggested in another thread. But I would still like an answer to this colon issue.

Works for me.

I figured it out. dosbox only gives you caps if you use the left shift key unless you set it otherwise. This is odd because it wasn't always this way, and through me off. Whatever.