So it seems it's useless on Windows not on every other OS 😉 (mostly because it deletes stderr/out on Windows)

It's working for me (stdout.txt is left behind) in vanilla SVN, so try it there.

All right, I tried the EmuCR build. However, it doesn't seem to use stdout/stderr in the same way as ykhwong's build. When I launch it from a command prompt window – even without any switches – the title of the command prompt window changes to "DOSBox Status Window" and all the DOSBox status messages are displayed in that window. When I launch ykhwong's build from the command prompt, a new, separate DOSBox Status Window opens, and the command prompt window remains free. Does that make sense?

I think the way the EmuCR build handles things is probably much more useful, though I haven't the slightest idea what the difference is.

The way emucr does it is the "correct" way, as it happens on Linux and OS X (after a fashion). But on Windows it is more useful to redirect the output to text files for the users to find afterwards.

Yes – but not so useful if the text files keep getting obliterated right away.

if it's done correctly the files should be left behind (but get overwritten on next start of dosbox)