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

VDM is actually a limited version of named pipes that does not require the
NMPBIND program to be running.  It has several restrictions however.

 1. It does not support network debugging.

 2. Under OS/2, the debugger (user interface) must run in an OS/2 (not a
    DOS) session.  The debugger may also be started under Windows NT but not
    Windows 95 since it does not support named pipes.

 3. Under OS/2, the remote debug server must run in a seamless Win-OS/2 or a
    DOS session.

 4. Under Windows NT, the remote debug server will be run in a Windows NT
    Virtual DOS Machine.

 5. Under Windows 95, the remote debug server can be started but since
    Windows 95 does not support named pipes it will not work properly.  See
    the section entitled WIN (Windows 3.x/95 Virtual DOS Machine) for an
    alternative.

 6. If you are running VDMSERVW 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 is an arbitrary name to be used for the
connection.  This allows you to have multiple VDM debug sessions active
simultaneously.  The default name is VDMLink.  The following example shows
how to use the VDM link:


     A>vdmserv
     B>wd /tr=vdm app

The following example shows how to use the VDM link specifying "brian" as
the link name.


     A>vdmserv brian
     B>wd /tr=vdm;brian app