All geek questions in one place

Best Approach for Debugging a Win 16-Bit Application?

I have to flip the legacy application (16-bit, NE exec) that is managing the old DAQ, with which I have to somehow interact with the upgraded hardware. I was able to parse exec using W32Dasm (and WindowsCodeBack, as well as only two of the many that I tried to work on), but as a result, the asm file contains too many lines. I would like to use a debugger and set some breakpoints to limit the work. Could you advise what is the right approach to debug a Win16 application in 32-bit times? For example, a VM running Windows98? Which Win16 debugger can I use?

Many thanks

+4
source share
1 answer

The IDA can disassemble Win16 programs (although not the free version), and this is much more convenient than a simple dead list.

As for the debuggers, I would try to find the Win16 Turbo Debugger (TDW.EXE). There is also OpenWatcom , which even supports remote debugging (so you can run the program in a virtual machine and the debugger user interface on your desktop).

+1
source

Source: https://habr.com/ru/post/1393867/

More articles:


All Articles