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

Both a character mode and a GUI debugger are supplied that run in the
Windows environment.  You must choose which of these debuggers you are going
to use.  They both have advantages and disadvantages.  When your application
is suspended, the GUI and character mode debuggers behave differently.  The
GUI debugger allows other applications to continue running.  The character
mode debugger does not.  Although the GUI debugger has a much nicer looking
user interface, you should not use it under some circumstances.  You can
always use the character mode debugger.  You should be aware of the
following restrictions:

 1. If you are trying to debug an applications that uses DDE you should not
    use the GUI debugger.

 2. Do not try to use the GUI debugger to debug system modal dialogs.

 3. If you hit a break-point in a dialog callback procedure or in your
    window procedure when it is receiving certain events (e.g.,
    WM_MENUSELECT), the GUI debugger will lock input to itself.  When this
    happens, you will not be able to switch away from the debugger, and no
    other application will repaint themselves.  When this happens, pop-up
    menus will not draw correctly and you will have to use the Action menu
    instead.  You should not try to quit the debugger when it is in this
    state.

 4. Do not try to use either of the Windows debuggers in a seamless Win-OS/2
    session.

If you find that the Windows debugger starts too slowly, try using the
option "/DIP=WATCOM".  This prevents the debugger from searching each DLL in
the system for debugging information.  It will start up faster, but you will
not be able to see the name of the Windows API calls.

To start the Watcom Debugger, select the program group in which you have
installed the Watcom Debugger.  One of the icons presented is used to start
the debugger.  Double-click on the Watcom Debugger icon.

You can make special versions of the Watcom Debugger icon using Properties
from the File menu of the Windows "Program Manager".  For example, you can
add any options you wish to the "Command Line" field of the "Properties"
window.  When you click on the newly created icon, the options specified in
the "Command Line" field are the defaults.  As long as no executable file
name was specified in the "Command Line" field, the Watcom Debugger will
present its prompt window.  In the prompt window, you can specify an
executable file name and arguments.

If you are debugging the same program over and over again, you might wish to
create an icon that includes the name of the file you wish to debug in the
"Command Line" field.  Each time you click on that icon, the Watcom Debugger
is started and it automatically loads the program you wish to debug.