![]() I tried the working links, and I got the EXE but with no installer. For some reason, they do not keep a build of this on the main DosBox website. It would help if there was a simple way to have the internal debugger breakpoint on the first instruction in a new program, started from the shell, so I don't have to debug the shell nor keyboard input, before the process starts. The DosBox debug version has developer tools for viewing memory, stepping through code one line at a time, etc. Dosbox-x does not seem to have a way to start a program in the internal debugger I believe previous posts mentioned using the debug command in the DOS window for this, but that doesn't work in dosbox-x. One notable problem is if I use the run command, and there are no breakpoints nor anything to make it stop, there's no way to get the prompt back, and I have to restart dosobox-x for it. And I've encountered some issues with it. Still, I want to know - if possible - how to use the dosbox debugger for this. ![]() So far I'm browsing the CW code that's part of Open Watcom Ive tried OllyDbg, it looks really great, but it cant 16 bit. I guess its time for me to learn how to decompile stuff, since it seems the only way to restore file format. There are no docs, no source, and no information about the author. Emulation-wise, it runs Dune, Dune 2, and not much else right now. I have some crucial data written decades ago by an ancient 16bit DOS application. I'm part of a team who works on this project, in order to reverse-enginneer real-mode programs (which offers also a GDB server) : ĬauseWay extender MIGHT run with it. I am member of group dialout and everybody (777) has access to /dev/ttyS0.The source code of CauseWay extender is here: Normally','this shortcut is set to Alt+Pause.','','In Windows, DOSBox-X can create a console and show the debugger interface','on it.','','On other systems including Linux and Mac OS X, DOSBox-X must be started','from a terminal in order to enable the debugger.','','The debugger interface should scale and respond to resizing of the','terminal wi. I redirected the serial port to /dev/ttyS0 and the DOSBox terminal says" Serial1: Opening ttyS0" so that seems ok too. I tested with a serial mouse and the correct com port is working and its ttyS0. The only difference is the Ubuntu machine. Also the nullmodem cable is tested in this windowsDOS test setup so all that is working ok. So the DOS end of this setup is tested and works and it also confirms that Norton Commander works fine in a DOSBox, at least if its running on Windows 10 Pro. ![]() I tested with a third machine that has DOSBox 0.74-2 on Windows 10 Pro and that works great (I set Windows COM1 to 38400.). To do that I use a serial nullmodem cable. I cannot get a connection using the Link feature in NC. ![]() I am actually still using this 30+ years old laptop almost daily to communicate with satellites in earth orbit via the COM port>TNC>transceiver.) that has no USB, ISA or PCI and only one COM port communicate with another Norton Commander 5.5 that is in a DOSBox 0.74 on an Ubuntu 18.04.2LTS machine. Contribute to bytefall/debugbox development by creating an account on GitHub. I am trying to make Norton Commander 5.5 on an OLD 80286 DOS 6.22 box (Tulip LT286. Contribute to bytefall/debugbox development by creating an account on GitHub.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |