Did you set scaler=none, then specify fullresolution & windowresolution?
Try gulikoza's build that includes direct3d, too.

I'm suprised that you noticed a difference between speed in D3D/OGL....I haven't noticed a diff between the two speedwise since the video optimizations.

Try running dosbox with -noconsole parameter and see if some error is reported in stdout.txt.

Nothing reported in either with the option (also got a glimpse of the status window without it, before it closed, nothing changes in it either). Scaler's always none.

fullresolution=original
windowresolution=original
changing the fullres doesn't actually change the res, must hang before that. (Taskbar's still same resolution.) Or maybe it's just a laptop ati thing, since opengl doesn't change it either (it just resizes it to a window of the size, after a lot of flickering). Specifying it (1280x800 or 1280x1024) works fine in opengl. I'll try it again on the external monitor when I get home, that one actually switched resolutions.

But yeah, in opengl a/v skips like crazy in both modes, whereas in d3d it's great, no slowdowns in windowed mode. I guess if I have to I could play it at fullres in windowed mode.

I just tried gulikoza's, same deal. (Except dynamic core crashes, but that must be an already-fixed cvs thing.)

stdout.txt has to contain some text, at least the usual

CONFIG:Loading settings from config file dosbox.conf
MIDI:Opened device:win32

or something like it. What happens if you start with fullscreen enabled?

If I exit dosbox normally, it does contain the usual text; I guess the write buffers don't get flushed when it hangs. I could try to force-flush them with a tool, once I get back to the second screen, but I doubt it would illuminate anything since nothing showed on the status window before it closed (when open).

Fullscreen startup just hangs right at start.