First post, by r_wolfcastle
I hope this is the right place to report bugs; I searched and searched for a bug report form but couldn't find one.
First of all, kudos for 0.72!! I am able to run my much-beloved and missed larn, and the CPU tuning and such are fantastic!
Running Leopard (10.5.1) on a new Macbook Pro (Intel).
Problem #1) I am attempting to set the following in the config file [sdl] section:
priority=higher,pause
When I run DOSBox, it comes up paused even though it is obviously the app with focus. Since there is no documented keystroke on Mac OS X to un-pause it (see the second bug below), it is stuck there.
HOWEVER, if I remove focus by switching to another app or minimizing DOSBox and then return focus to DOSBox, and do that *twice*, then it magically becomes un-paused, and from then on it correctly pauses and unpauses on de-focus/focus exactly as advertised. This is 100% repeatable, and I backed out all my other changes to verify that this change to the conf file, and this change alone, causes the problem.
Another clue: If I start with the default conf file and make this change, then the first time I de-focus and re-focus on DOSBox, it appears visually that nothing at all has happened. But if I also include this change to the conf file:
windowresolution=1024x640
then DOSBox initially comes up paused and original size. After I de-focus and re-focus once, DOSBox resizes to 1024x640, but then becomes PAUSED again without showing the welcome text, BLASTER setting, etc. It is only after the second time that I de-focus and re-focus that it fully comes up, and also executes any extra commands I may have added at the end of the conf file.
Problem #2) INTRO documents the key to pause the game (and presumably it is a toggle to un-pause it as well) as ALT-PAUSE. There is no such key on the Mac; I assume this is a reference to the PC's pause/break key. I decided I'd try to set it to something else, but...
Problem #3) CTRL-F1 does not appear to start the keymapper as advertised. Perhaps this functionality has not yet been ported to OS X.
I have an obvious workaround for problem #1, and #2 and #3 are really of no consequence to me, but I thought I'd report them for completeness.[/img]