🚀 go-pugleaf

Ok, here's my setup:

I am developing a DOS device driver using two systems, a 486
work-station and a 386 target.  I am running Turbo Debugger (td.exe) on
the 486 and TDREMOTE on the target.  The machines are connected with a
standard serial cable.  Both machines are running MS-DOS 5.0, QEMM
and the Windows SMARTDRV disk cache.  The work-station is running
Windows 3.1.

Now, here's the scenerio:

I compile a new version of the driver on the work-station.

I load this driver onto the target system.

I reboot the target system to load the driver.

I run TDREMOTE on the target.

I run TD /R /SM10 on the work-station to run the debugger in remote mode
and to resere 10K for symbol table.

I load the symbol table for the driver and use the "table relocate"
function to set its address.

I then set my breakpoints and select "go resident" to make TDREMOTE on
the target machine to run in the background.

With TDREMOTE running in the backgroun, I then run a test program that
uses my driver and causes the breakpoints to trigger.

Now, all this works fine if I'm NOT running TD under Windows on the
work-station.  If I try to run TD in a DOS-session under WIndows, it
will work for a while, but will eventually crash the work-station as I'm
tracing through the code.

Can anyone help me with this one?  I guess I could set up a third
machine as a debugging console, but that would be a major hassle because
I would have to not only copy the code to the target machine, but alos
to the debugging console every time I wanted to try a new version.

-- 
oooooo ooo o o  o            Keath Milligan            o  o  ooooo oooo oooooo
oooo oo ooo  o   o   Prometheus Light and Sound, Inc.   o   o  o ooooooooooooo
oooooooo o oo  o         Real/Time Communications        o    o o ooo oooooooo
oooooo oooo ooo  o  internet: reaper@wixer.cactus.org  o   o  o ooo oo ooooooo