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

This link communicates over the serial port.  See the appendix entitled
Wiring For Remote Debugging for wiring details.  The debugger and server
will automatically synchronize on a communications speed.  They may
communicate at rates as high as 115kB.  The DOS and OS/2 "mode" command or
the QNX "stty" commands need not be used.

The parameter to this link takes the form


     port_number.baud_rate

port_number is a number from 1 to 3 indicating which serial port the cable
is connected to.  The default is 1.

baud_rate is the maximum BAUD rate at which to communicate.  If you already
know the maximum BAUD rate at which the two machines will communicate, this
parameter will speed up the connection time by eliminating some of the
synchronization protocol.

baud_rate may be any of 115200, 57600, 38400, 19200, 9600, 4800, 2400, or
1200.  It may be shortened to the first 2 digits.

A special BAUD rate of 0 is also allowed.  This should be used if the serial
port has been pre-assigned using the "mode" or "stty" commands.  The
pre-assigned BAUD rate is used and the BAUD rate negotiation is avoided.
 This will allow you to debug over a modem.

The following example shows how to debug across a serial cable using default
settings:


     A>serserv
     B>wd /tr=ser app

The following example shows how to debug across a serial cable using serial
port 2 on each machine setting the maximum BAUD rate to 9600:


     A>serserv 2.9600
     B>wd /tr=ser;2.9600 app

QNX Note:
    Under QNX, a node id may be specified followed by a comma if the serial
    port is not located on the current node.  The command "serserv 3,1.9600"
    would use the device //3/dev/ser1 at a BAUD rate of 9600.
     Alternatively, you can specify a device such as /dev/foobar.  To
    specify the maximum line speed, you can specify something like
    /dev/foobar.56.  Of course, you can also include a node id such as
    //5/dev/foobar.


         A>serserv //3/dev/ser2.9600
         B>wd /tr=ser;//5/dev/ser2.9600 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 and BAUD rate.  The following example shows how to
debug a 32-bit DOS/4GW application across a serial cable using serial port 1
on one machine and serial port 2 on the other machine setting the maximum
BAUD rate to 9600 for each:


     A>serserv /tr=rsi 1.9600
     B>wd /tr=ser;2.9600 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.