Qbix wrote: ah you mean the main window, not the debug window. Indeed, that one needs vga events to trigger. You could if your code allows it, fire a timerirq. There is a debug command for that. Yes, sorry for the confusion and I'll give timerirq that a try, thanks.

I was using auto, however a quick test with core=normal exhibits the same behavior. Specifically, the the dosbox window won't change after single-stepping over a "printf" call and in fact the only way to get an update seems to be to set a breakpoint past some code which takes a bit more time to run …

I've found the heavy debugger to be incredibly useful for interrogating old assembly code of mine. I've noticed however that when single-stepping through a program, the dosbox display doesn't seem to update regularly. This can be frustrating when dealing with more complicated c-code because, for …