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

This link communicates over the parallel port.  Three different cable types
may be used.  They are called the LapLink, Flying Dutchman, and WATCOM
cables.  Although the WATCOM cable will communicate considerably faster than
the other two, we have found it to be unreliable on some printer cards.  See
Wiring For Remote Debugging.

The parameter to this link is a number from 1 to 3 or the letter "p"
followed by a hexadecimal printer I/O port address.  This tells the software
which parallel port the cable is connected to (LPT1, LPT2, LPT3).  The
default is 1.  The parameter used on each side of the link depends on which
printer port the cable is plugged into on that machine.  It need not be the
same on both sides.  The following example shows how to debug across a
parallel cable plugged into printer port 3 on one machine and port 2 on the
other.


     A>parserv 3
     B>wd /tr=par;2 app

As an alternative, you can specify a port address to use.  It is less
convenient than specifying a port number but will work on systems like OS/2
where the actual I/O port address cannot be obtained from the system.  The
following example shows how to debug across a parallel cable plugged into
I/O port 0x378 on one machine and port 2 on the other.


     A>parserv p378
     B>wd /tr=par;2 app

If you are going to debug a DOS extender application, then you must also
specify a trap file to the server program.  The trap file must be specified
before the port number.  The following example shows how to debug a 32-bit
DOS/4GW application across a parallel cable plugged into printer port 2 on
one machine and port 3 on the other.


     A>parserv /tr=rsi 2
     B>wd /tr=par;3 app

The "RSI" trap file is specified for DOS/4G(W) applications.  You can
specify other trap files for the other DOS extenders (e.g., "PLS" for Phar
Lap).  Do not forget to include other required files in the path.

RSI
    Both "DOS4GW.EXE" and the loader help file "RSIHELP.EXP" must also be
    located in one of the directories listed in the DOS PATH environment
    variable.  See the section entitled
    Debugging DOS/4G(W) 32-bit DOS Extender Applications for more
    information on debugging applications that use the DOS/4GW DOS extender.

PLS
    One or more of "RUN386.EXE" (or "TNT.EXE"), "DBGLIB.REX", "PLSHELP.EXP",
    and "PEDHELP.EXP" must be located in one of the directories listed in
    the DOS PATH environment variable.  See the section entitled
    Debugging Phar Lap 32-bit DOS Extender Applications for more information
    on debugging applications that use the Phar Lap DOS extender.

ADS
    See the section entitled Debugging AutoCAD Applications for more
    information on debugging AutoCAD applications.