I need some speed.
 Making MrDebug Faster
──────────────────────────────────────────────────────────────────────────────

 As with any excellent product, there are always ways to improve the
 performance, at the cost of memory.

 To get the fastest possible usage out of MrDebug, you may want to exclude
 MrDebug's link script and simply link in MrDebug.LIB as an object module.

 To link MrDebug.LIB as an object module:

 with a protected mode linker, include MrDebug as:

        FILE MrDebug.LIB

 Whatever happens....PLEASE make sure that you are using EMS memory as
 Clipper likes to have some EMS memory around so that it can take advantage
 of this extra memory for it's virtual memory, unless you are using ClipXMS.

 To take full advantage of MrDebug we recommend that you use a linker, such
 as Blinker 3, that allows you to run your application in protected mode.

 Other options that may help include:

      - Turning off all of the color syntax highlighting options from the
        Source appearance sub-menu held in the options menu. This will save
        time when MrDebug refreshes the source code window.

      - Using as few watch points and trace points as possible, for optimum
        Performance don't set any watch points or trace points.

      - Turning off the .PPO window. This will save MrDebug from having to
        find which line it should be on when you change lines in the source
        code window.

      - Turn the profiler off. The Profiler adds to the MrDebug overhead and
        can result in some very slow performance penalties - especially in
        real mode.

      - Highlight changes. This can really slow down MrDebug if you have All
        Levels Changes set on. This is noticeable when you have a lot of
        variables at all levels of the program.

      - Turn off the Step Timer from the Options menu.

 The Fast Run command may be used to run MrDebug - this has the advantage of
 speed when using MrDebug in slow situations.

 Running Fast Run Mode, turns off MrDebug's checking of Trace Points, Watch
 Points, Pass Points, Tracked variables, Stop Points i.e. stop on next
 return, run out of codeblock, run to codeblock.

 However checks still occur for the key press of <Alt><D> and any ALTD()
 functions within your code. If you have disabled any ALTD() functions that
 are embedded in your code, the disabled is ignored,