Thomas Kjørnes

This would be a very nice feature indeed. Simple toggle-button.

Ancient bug report, but personally I do not want this. So I "vote" for the connection screen option :)

Yes. I tried to run the program through a debugger to see where it goes off the rails, but with no luck. When the hang occurs (when the jump into weird code happens), it is in the middle of doing graphics stuff with I/O ports and stuff related to video. Also the debugger I tried did not have the ability to "record" where it came from (stack trace).

The real bug has little to do with int 16/ax=55xx. That particular service is for a TSR related to Word for DOS according to Ralf Brown's interrupt list. The value "MS" is supposed to be returned in AX if that particular TSR is installed, otherwise AX remains umodified. There has to be another bug, because when you break into the hung black screen, you look at an "arpl ds:[bx+si], ax" instruction (bytes 63 00). Which sits in the middle of otherwise normal code. Looks like a botched jump or return...

Why does Bochs need mouse capture?

Topic says it all. It seems there are nobody active in here. Or is there another place you can go to find information and active discussions about Bochs? T

I decided I could not wait for this, so I downloaded the source code and made the changes myself in VS 2019. With the changes below (or using another key than F4) you can "Run-To-Cursor" which is very handy. File: /gui/enh_dbg.cc: // 1) added variable for auto(remove) breakpoint int AutoBreak = -1; // 2) inside the OnBreak() method, added check for AutoBreak if (AutoBreak >= 0) { bx_dbg_del_lbreak(AutoBreak); } // 3) made a copy of method SetBreak() and changed it to this: void SetAutoBreak() { if...

Debugger: Make cursor/address colors stand out more