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

The TCP/IP link allows you to communicate between any two sessions using
TCP/IP if you have installed TCP/IP support.  You can also debug remotely
between OS/2 and Windows NT/95 machines if you have installed TCP/IP support
on these machines.  See your network documentation for details on installing
TCP/IP support.

In order to use TCP/IP to remotely debug a program, you must start the
TCPSERV server program first.

Example:

     A>tcpserv
     Socket port number: 3563
     WATCOM TCP/IP Debug Server
     Version 11.0
     Copyright by WATCOM International ...
     Press 'q' to exit

The server program displays an available socket port number on the screen.

You may specify a TCP/IP "service" as an argument on the command line.
 TCPSERV will check the TCP/IP services list to find a matching service.  If
no argument is specified on the command line, TCPSERV uses "tcplink" as the
service name.  If no matching service name is found, TCPSERV attempts to
convert the argument to a numeric port number and use that.  If the argument
can not be converted to a number, port number 3563 is used.

The TCP/IP services list is stored in different places depending on the
operating system.

OS/2
     d:\TCPIP\ETC\SERVICES depending on the drive where TCP/IP is installed

QNX
     /etc/services

Windows 95
     d:\windows\SERVICES depending on the drive and directory where Windows
    95 is installed

Windows NT
     d:\WINNT35\SYSTEM32\DRIVERS\ETC\SERVICES depending on the drive where
    Windows NT is installed

You will also need to know the Internet Protocol (IP) address of the machine
running the TCPSERV program.  This can be in alphanumeric or numeric form
(e.g., jdoe.watcom.on.ca or 172.31.0.99).  With the alphanumeric form, it is
not necessary to specify the domain name portion if the two machines are in
the same domain.

To use the remote TCP/IP server, you must specify the TCP/IP trap file name
to the debugger along with an argument consisting of your IP address,
optionally followed by a ":" and the service name or socket port number used
by TCPSERV.  You must also include the name of the application you wish to
run and debug on the remote machine.

Example1:

     A>tcpserv
     B>wd /tr=tcp;jdoe app
             or
     B>wd /tr=tcp;172.31.0.99 app

Example2:

     A>tcpserv 1024
     B>wd /tr=tcp;jdoe:1024 app
             or
     B>wd /tr=tcp;jdoe.watcom.on.ca:1024 app
             or
     B>wd /tr=tcp;172.31.0.99:1024 app

Example3:

     A>tcpserv dbgservice
     B>wd /tr=tcp;jdoe:dbgservice app
             or
     B>wd /tr=tcp;jdoe.watcom.on.ca:dbgservice app
             or
     B>wd /tr=tcp;172.31.0.99:dbgservice app

The TCP/IP remote debug service permits debugging of applications anywhere
on the Internet.  However, response will vary with the distances involved.