Isn't all DosBox file access sshown in the debug ver in the console window? if so then use that and use log= setting in dosbox.conf to redirect console output to a text file.

Like I said, where do I find a debug version? Do I have to compile it under Linux from the original sources? Is there no Win32 binary?

IIRC, only ykhwong's CVS build in the CVS thread includes a debug ver.

I see... Interesting.

There's no documentation for the debugger available, is there? Specifically, how do I interact with the debug window? r/f, up/down, and home/end don't seem to do anything. And can I log any of the various fields to a file?

U need to pause the emulation for r/f etc. to work

That's what I thought... But pressing CTRL+PAUSE in ykhwong's version doesn't seem to do anything. (I assume PAUSE is the key next to the Scroll Lock button?) Pressing CTRL+PAUSE after clicking in the debug window closes the program entirely.

Just Pause, no Ctrl.

No, it should be ctrl-pause, but it seems to be broken on some systems
(windows only??).

I have found no log= command for the config file anywhere. I even looked in the source and didn't see a place for it to be read in. How would this be used?

As long as I know, Ctrl-Pause used to be broken in windows, so the hot key was changed to Alt-pause. By doing "config -writeconf dosbox.conf" on the dos prompt in debugger, you can get [log] section.

Guide to the DOSBox debugger

Sweet! I have been looking for this forever. The actual key is logfile=<filename> for <filename> I use output.txt as a test and it worked.

Saved me a major headache. Thanks again!