Click above to get retro games delivered to your door ever month!

 Borland Turbo Debugger
------------------------------------------------------------------------------
 The Borland Turbo Debugger may be used to debug DOS real mode and Windows
 programs created with Blinker, displaying module source code with line
 numbers, public data symbols and non-overlaid public code symbols. Turbo
 Debugger does not support symbolic debugging of code overlaid by Blinker in
 a real mode program, although you can still debug it at the assembly level.
 Turbo Debugger CANNOT be used to debug DOS extended programs, to do so
 requires a protected mode debugger such as NuMega SoftICE/W.

 Extra symbolic debugging information for DOS real mode and Windows programs
 can be obtained through the use of the TDCONVRT utility, which was supplied
 by Borland with some of their earlier compilers. This utility converts a
 CodeView format .EXE file to Turbo Debugger format. For further information
 on this utility, please refer to the appropriate Borland documentation.

 If a program contains C or ASM overlays then the -c option must be used to
 create an external .TDS file, otherwise a Blinker 1203 error will occur at
 run time. This is because TDCONVRT places the debugging information directly
 after the root of the .EXE file. It also creates unusually large .TDS files
 with overlaid programs due to some internal confusion, but they appear to
 function correctly for the root part of the program.

 Overlaid programs will otherwise run correctly, but breakpoints on overlaid
 code will be ignored and display meaningless code at the symbol addresses.
 Turbo Debugger does not currently recognise the _main symbol as output from
 Blinker and TDCONVRT, so when running a program under the debugger select
 GOTO (Ctl G) and enter "main" to locate the start of the program.