> Ok, here's another blast from the past. I was playing around with my WFWG
> installation, and I also had the SDK and DDK installed. I remember from years
> ago debugging software using the debugging kernel and the wdeb386 remote
> debugger. So, I thought I'd give this a try in a virtual environment. I don't
> have it working yet, so before I knock myself senseless, I thought I'd ping
> the group to see if it had been done yet.
>
> I have two identical DOS 6.22 virtual machines and as a test, I configured
> both to map COM1 to the same named pipe. I installed PROCOMM (another of my
> favorite programs -- I still use it for my vintage computing projects) and
> was able to send characters between the virtual machines. So far, so good.
>
> I left PROCOMM running on one VM (and still connected to COM1) and started
> wdeb386 on the other. I made sure I switched to the debugging kernel (using
> the n2d batch file) and fired up the debugger with "wdeb386 /c:1 /v win.com".
>
> All I get is a big fat nothing. I haven't yet tried connecting to the
> virtual machine over a real serial port but since I have PROCOMM
> communicating I figure that it's not the link.
>
> Has anyone tried to do this? Right now, it's part intellectual exercise more
> than a specific need but I do have some old software I wrote long ago that
> I'd like to poke around with again.
>
> Any input appreciated. Thanks!
>