Differences from Borland's TD32

RTD32 behaves just like Borland's TD32 for Win32 would for local debugging, with the following exceptions:

Pressing Ctrl-C or Ctrl-Break while the program under test is running will suspend execution immediately. This can be useful to get out of endless loops. Ctrl-C/Ctrl-Break only works if interrupts are not disabled on the target. If the target no longer responds, pressing Ctrl-C/Ctrl-Break more than three times will abort the debug session.
A non maskable interrupt (NMI) is treated like a breakpoint, interrupting program execution. This feature can be useful to regain control when the program has entered a dead loop with interrupts disabled. Of course, it must be possible to trigger an NMI manually on the target to use this feature.
Resetting the debugger will restore all interrupt vectors to their original values.
Program output of displayless targets is displayed in a separate window on the host and written to file Rttarget.log. Rttarget.log is overwritten each time RTD32 is started. The log file name can be specified in Rttarget.ini.
Menu options View | Global Descriptors and View | Interrupt Descriptors have been added.
In the CPU window, local menu option I/O for reading from or writing to I/O ports has been added.