Brandt Everett wrote in a message to Mike Bilow:

 BE> I was wondering if there was a way to get the Watcom Debugging 
 BE> to work in a VDM.

 BE> I have a small DOS program that I want to debug (running the 
 BE> OS/2 IDE), and keep dieing when I try to de-bug.  Im at a lose.

 BE> Using Warp Connect, Watcom 10.0, on a 486DX4-120 with 16Megs. 

I can't speak specifically to Watcom 10.0 because I replaced it with the
later versions, but there is a documented facility for this.  Look in the
Debugger Help document (WD.INF), under "Remote Debugging."

The Watcom debugger supports linking to the target under test using the
parallel and serial ports, a LAN (SPX, NetBIOS, or TCP/IP), a VDM link, or
a named pipe link.

To use the named pipe link, you have to have NMPBIND.EXE running on the
system.  The Watcom installation puts a line in CONFIG.SYS that starts
NMPBIND.EXE as a detached process.  Assuming you are using the named pipe
link with both ends on a single machine, just start NMPSERV (or NMPSERVW
under Windows) running in one window and then start WD with the
"/tr=nmp" switch.  If NMPBIND.EXE is running on a remote machine,
you have to specify its name when starting NMPSERV and WD, which can
themselves be anywhere on the network.

To use the VDM link, which only works on a single machine, you do not need
a detached process.  Start VDMSERV in one window, and then start WD with
the "/tr=vdm" switch.  The VDM link system is less flexible than
the named pipe link, but is simpler to configure.

Or am I completely misunderstanding your question?
 
-- Mike


---