Introduction
──────────────────────────────────────────────────────────────────────────────

To include MrDebug in your application instead of CLD, all you have to do
is compile at least one of your .PRGs with the /b switch and link MrDebug
into your application by adding one of the following lines

@MrDMid // for Blinker (real mode)
@MrdRtl // for RTLink (real mode)
FILE MrDebug.LIB // for protected mode linkers
// i.e. Blinker 3, Exospace
// and Causeway

to your link script before CLIPPER.LIB or any references to CLIPPER.LIB.

That will get you up and running. Once you link your application you should
be able to run your program and use MrDebug - as long as you have compiled
at least one .PRG with the /b switch.

If you have set your video mode to one of the higher text modes such as
132x60 or 132x50 or 132x43 you should find that when your program runs the
application will appear in its own window of 80x25 leaving you the rest of
the screen to display and use for the debugging tools.

After you have had time to use MrDebug you may want to read the section on
modifying your error system, which tells you how to take advantage of error
windows and how to make sure that output from your error system goes to the
application window.

There is no manual supplied with MrDebug. We feel that it is unfair of us to
supply you a manual that is out of date and superceded by a READ.ME file on
the disk. Instead we have decided to supply you with a guides file that is
uptodate and complete.