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

The named pipes link allows you to communicate between any two sessions on
an OS/2 machine.  You can also debug remotely between DOS, Windows 3.x and
OS/2 machines if you have installed remote named pipe support on these
machines.  See your network documentation for details on remote named pipes.

In order to use named pipes, you must first run the NMPBIND program.  This
may run any OS/2 machine on the network.  It can be run detached, by putting
the following line into your OS/2 CONFIG.SYS.


     RUN=C:\WATCOM\BINP\NMPBIND.EXE

If you run NMPSERVW under Win-OS/2, it must be run as a seamless Windows
session.  This is due to the fact that full screen Win-OS/2 sessions may not
get any processor time when they are not in the foreground.

The parameter to this link can take the following forms:


     name
     name@machine

name is an arbitrary name to be used for the connection.  This allows you to
have multiple remote debug sessions active simultaneously.  The default name
is NMPLink.

machine is the name of the machine on which the NMPBIND program is running.
This allows you to use remote named pipes.

The following example shows you how to use the named pipe link between two
sessions on the same OS/2 machine.


     A>nmpserv
     B>wd /tr=nmp app

The following example assumes that there is a machine named HAL with a
remote named pipe server on the network which is running NMPBIND.


     A>nmpserv mylink@hal
     B>wd /tr=nmp;mylink@hal app