There is one thing that is wrong here and may be a source of problems:

At the beginning mac had only keys:
f1-f12

later they added three more f keys above ins,home,pgup
f1-f12
13,14,15
http://upload.wikimedia.org/wikipedia/commons … rd_II_black.jpg

later there was one keyboard model, that was later abandoned, that moved f13 to the block of f1-13 keys, made a block of 14,15,16, and another one above the numpad: 17,18,19,eject
f1-12,f13
14,15,16
17,18,19,eject
en.wikipedia.org/wiki/File:Apple_Pro_Ke ... n_top).jpg

i guess cause of appeared incompatibilities they changed it to the currant layout:
f1-12,eject
13,14,15
16,17,18,19
http://store.apple.com/us/product/MB110LL/A?f … mco=MTA4Mzc4ODA

according to what you say, in dosbox the layout is detected this way (the incompatible way):
f1-12,f13
14,15,16
17,18,19,eject

btw - your keyboard only has 15 F keys (actually it looks the f14 is missing too, but lets leave that for now) so F16(pause in dosbox) cannot work cause you simply don't have it, so if you want to test pause key do it with your gf's keyboard.

If you need to press a key combination already captured by Mac OS X, additionally press the Fn key (bottom left), if available.

For example, the new Hercules different colors, you need to press Alt-F11 to cycle the color. If that doesn' t work, press the Fn key together with.

btw does it help if you change in sdlmain.cpp:
if(event.key.keysym.sym==SDLK_PAUSE) {
into this:
if(event.key.keysym.sym==SDLK_p) {
(does letter p unpauses dosbox after that?)

IIGS_User wrote:

If you need to press a key combination already captured by Mac OS X, additionally press the Fn key (bottom left), if available.

Unfortunately this is not entirely true. Because the (today) standard Apple keyboard has the F-keys mapped twice.
Special functions like decrease/increase brightness (F1/F2), Exposé (F3)... and so on. To get the normal F-keys function you need to press Fn+F-key (or you disable these special functions alltogether in the System Settings -> Keyboard -> keyboard tab -> "Keys F1, F2... use standard functions"). You then use the special functions by pressing Fn+F-key.
BUT if the F-key is mapped to something in the system settings you can't bypass this by pressing Fn+F-key (because like I wrote just now, the Fn-key just switches between special and standard function, if the standard function is mapped you can't bypass this).

btw - your keyboard only has 15 F keys (actually it looks the f14 is missing too, but lets leave that for now) so F16(pause in dosbox) cannot work cause you simply don't have it, so if you want to test pause key do it with your gf's keyboard.

To make clear what I'm talking about, there is the Logitech Keyboard Cordless Wave, closely resembling that one http://www.amazon.de/Logitech-Cordless-Deskto … 57&sr=8-2-fkmr1 (this is not the qwertz layout of the german one, but I couldn't find one right away).
and there is the Apple keyboard with numpad http://store.apple.com/de/product/MB110D/A?fn … mco=MTMzNzcyMDM

The Logitech one is the one where I only have print screen, scroll lock and nothing else. Instead of the F13 key it has the insert key up there (as can be seen on the amazon link), so it got F14, F15 but no F16 and following.

The Apple one is behaving like explained, with the problem that the pause key is not working like expected.
The Apple keyboard became mine now and the Logitech is now my gf's 😀

btw does it help if you change in sdlmain.cpp: if(event.key.keysym.sym==SDLK_PAUSE) { into this: if(event.key.keysym.sym==SDLK_p […]
Show full quote

btw does it help if you change in sdlmain.cpp:
if(event.key.keysym.sym==SDLK_PAUSE) {
into this:
if(event.key.keysym.sym==SDLK_p) {
(does letter p unpauses dosbox after that?)

Yes, letter p does unpasue Dosbox, when compiled with these changes.

Dominus wrote:

The Logitech one is the one where I only have print screen, scroll lock and nothing else. Instead of the F13 key it has the insert key up there (as can be seen on the amazon link), so it got F14, F15 but no F16 and following.

http://www.benchmark.pl/uploads/image/wave.jpg
i see only ins, print screen,pause break, no scoll lock

And keyboards that had only three extra f keys were numbered this way:
print screen (f13), no scoll lock (f14), pause break(f15)
so you have only f13 and f15, while f14 is missing
although i think it would be rather unusual not to have f14 so i guess your keyboard is just "the first standard" with only f1-12 and no more extra mac f keys, i guess these keys are only used in windows.
Unless you say that they indeed were working like f13,14,15 in mac. 😀

On the apple keyboard, f13 is NOT print screen. At least not as SDL and Dosbox mapper recognizes. As I wrote in the first post
F14 is Print Screen
F15 is Scroll lock
F16 is Pause
(and F13 is recognized as F13 in the mapper)

On the Logitech with Logitech drivers the behaviour and layout was
F12 Eject - this made it only sometimes register as F12 in the mapper
Insert
Print Screen
Scroll lock (even though it says Pause on the key lettering).

On the Logitech WITHOUT Logitech drivers:
F12
Insert
F13
Scroll lock

So on the logitech with logitech drivers, both F13 and Pause (F16) are missing.
Without the drivers, both F14 and F16 are missing.

On the Alt key issue, with the logitech drivers you have the choice to keep the layout like on Windows: ctrl-cmd(windows key)-alt-space-alt-fn-ctrl
Or as on the Mac (as opposed to the picture you posted of the wave, my keyboard has dual markings on alt, windows key to easily see the mac layout):
Ctrl-alt(windows key)-cmd-space-cmd-fn-ctrl
You can then further customize the fn key and assign it the function of either alt,cmd,ctrl or shift. Unfortunately when you assign it alt it gets the left-alt-key function 🙁
Without the logitech drivers:
Ctrl-cmd(windows key)-alt-space-alt-NO_KEY-Ctrl
The Alt keys get recognized as left and right, the Fn key is not recognized at all (neither in the mapper, nor in OS X at all, it seems)

Edit: I added the results for the Logitech keyboard WITHOUT the drivers

do these two work too for unpausing?
if(event.key.keysym.sym==SDLK_F12) {
if(event.key.keysym.sym==SDLK_F16) {

F12 does unpause, F16 does not compile.

sdlmain.cpp: In function ‘void PauseDOSBox(bool)’: sdlmain.cpp:267: error: ‘SDLK_F16’ was not declared in this scope sdlmain.cpp […]
Show full quote

sdlmain.cpp: In function ‘void PauseDOSBox(bool)’:
sdlmain.cpp:267: error: ‘SDLK_F16’ was not declared in this scope
sdlmain.cpp: In function ‘void show_warning(const char*)’:
sdlmain.cpp:1533: warning: format not a string literal and no format arguments
make[3]: *** [sdlmain.o] Error 1

Which is probably not surprising since I think SDL doesn't know about F16...

how about F13,14 and 15?

Those work.
SDLK_F16 and upwards are not declared (or whatever the right word word is) in SDL, only up to F15.
However I found that Dolphin (Gamecube emulator) does something to declare it with

1SDLK_F16 = SDL_SCANCODE_TO_KEYCODE(SDL_SCANCODE_F16),

Don't know if anything can be done with this.

what about
SDLK_PRINT
SDLK_SCROLLOCK

Those compile but do not unpause Dosbox.

(I changed the 7th post in here with the results of the logitech keyboard without the logitech drivers, btw)