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

The following switches are applicable to all operating systems.

/TRap=trap_file[;trap_parm]
    specifies an executable helper program that the debugger uses to control
    the application being debugged, or to communicate across a remote link.
    It is called a "trap file" since the interrupts used for debugging are
    sometimes called "traps".  The trap option selects the appropriate trap
    file to use.  This option must be specified when remote debugging,
    debugging DOS extender applications, debugging OS/2 exception handlers,
    or debugging an AutoCAD ADS application.

    The remote trap files themselves have startup parameters.  This is
    specified following the semi-colon.  See Remote Debugging.  Normally you
    do not have to specify a trap file.  If you do not specify the trap
    option, the default trap file that supports local debugging is loaded.
     There are several exceptions.

     1. To debug a Tenberry Software 32-bit DOS/4G(W) application, you must
        use /TRAP=RSI.

     2. To debug a Phar Lap 32-bit application, you must use /TRAP=PLS.

     3. To debug an OS/2 exception handler, you must use /TRAP=STD 2 which
        tells the debugger to catch exceptions only on the second chance
        (normally it would be the debugger that traps the exception).

     4. To debug an AutoCAD add on, you must use /TRAP=ADS.

     5. To debug an OS/2 16-bit application under Phar Lap's RUN286 DOS
        extender, you must use /TRAP=STD16.

/LInes=n
    controls the number of lines used by a character mode debugger.  The
    number of lines available depends on the operating system and your video
    card.  The values 25, 43 and 50 are often supported.

/COlumns=n
    controls the number of columns used by a character mode debugger.  The
    number of columns available depends on the operating system and your
    video card.  If your system does not support the requested number of
    columns, this option is ignored

/Invoke=file
    may be used to specify an alternate name for the debugger configuration
    file which is to be used at start-up time.  The default file name is
    "WD.DBG".  Debugger configuration files are found in the current
    directory or one of the directories in your PATH .

/NOInvoke
    specifies that the default debugger configuration file is not to be
    invoked.

/NOMouse
    requests that the debugger ignore any attached mouse.   This may be
    necessary if you are trying to debug mouse events received by your
    application.  This option ensures that the debugger will not interfere
    with the mouse.

/DYnamic=number
    specifies the amount of dynamic storage that the debugger is to set
    aside for its own use on startup.  The default amount that is set aside
    is 500K bytes.  The larger the amount, the less memory will be available
    for the application to be debugged.  You only need to use this option if
    the debugger runs out of memory, or is causing your application to run
    out of memory.  If you are using the remote debugging feature, the
    debugger will use as much available memory as available.

/NOExports
    specifies that no exports (system symbols) should be loaded.  It helps
    to speed up load time when debugging remotely and marginally so when
    debugging locally.

/LOcalinfo=local_file
    is used primarily in conjunction with the remote debugging capabilities
    of the debugger.  It causes the debugger to use one or more local files
    as sources of debugging information if the right conditions are met.
     When the debugger observes that an executable file or Dynamic Link
    Library (DLL) is being loaded with the same name (i.e., the path and
    extension have been stripped) as one of the /localinfo files, then the
    named local file is used as a source of debugging information.  The
    named file can be an executable file, a DLL file (.dll), a symbolic
    information file (.sym), or any other file with debugging information
    attached.

    Example:

         wd /local=c:\dlls\mydll.sym /local=c:\exes\myexe.exe /tr=par myexe

    In the above example, the debugger would obtain debugging information
    for any executable or DLL called myexe or mydll from C:\EXES\MYEXE.EXE
    or C:\DLLS\MYDLL.SYM respectively.  Note that no path searching is done
    for local files.  The debugger tries to open the file exactly as
    specified in the localinfo option.

    See the section entitled Remote Debugging for an explanation of remote
    debugging.

/DOwnload
    specifies that executable file to be debugged is to be downloaded to the
    task machine from the debugger machine.  The debugger searches for the
    executable file in the local path, and downloads it to the debug
    server's current working directory on the remote machine before starting
    to debug.  Debugging information is not downloaded, but is obtained
    locally, as in the localinfo option.  Note:  Only the executable is
    downloaded; any required DLLs must be present on the remote machine.
     Downloading is relatively fast if you are using one of the TCP/IP (TCP)
    or Netware (NOV) remote links.  Be sure to specify the file extension if
    it is not ".exe".

    Example:

         wd /tr=nov;john /download sample.exe
         wd /tr=nov;john /download sample.nlm

    The debugger does not erase the file when the debugging session ends.
     So if you debug the application again, it will check the timestamp, and
    if the file is up-to-date, it doesn't bother re-downloading it.

    See the section entitled Remote Debugging for an explanation of remote
    debugging.

/REMotefiles
    is used in conjunction with the remote debugging capabilities of the
    debugger.  It causes the debugger to look for all source files and
    debugger files on the remote machine.  When remotefiles is specified,
    all debugger files (except "trap" files) and application source files
    are opened on the task machine rather than the debugger machine.  The
    trap file must be located on the debugger machine.

    The PATH environment variable on the task machine is always used in
    locating executable image files.  When remotefiles is specified, the
    debugger also uses the task machine's PATH environment variable to
    locate debugger command files.  See the section entitled
    Remote Debugging for an explanation of remote debugging.  See the
    section entitled Specifying Files on Remote and Local Machines for an
    explanation of remote and local file names.

/NOFpu
    requests that the debugger ignore the presence of a math coprocessor.

/NOSymbols
    requests that the debugger omit all debugging information when loading
    an executable image.  This option is useful if the debugger detects and
    tries to load debugging information which is not valid.

/DIp=dipname
    used to load a non-default Debug Information Processor (DIP).  This
    option is generally not needed since the debugger loads all DIPs that it
    finds by default.  See The Images Window.