Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!mit-eddie!uw-beaver!zephyr.ens.tek.com!tektronix!reed!minar
From: minar@reed.bitnet (Nelson Minar,L08,x640,7776519)
Newsgroups: comp.os.msdos.programmer
Subject: Turbo Debugger 2.0 and 4DOS 3.01a do not get along well
Message-ID: <15339@reed.UUCP>
Date: 15 Aug 90 19:32:11 GMT
Sender: news@reed.UUCP
Reply-To: minar@reed.bitnet (Nelson Minar)
Organization: Reed College, Portland, OR
Lines: 19

(posted here because I am tired of reading 30+ messages a day on comp.sys.ibm.
 pc.misc which don't belong there)

I've run into a few problems when using Turbo Debugger 2.0 running from 4DOS.
Specifically, when one exits TD 2.0 in one of its TSR modes.

If one shells to OS, 4DOS has a few problems with the keyboard: namely, the
command line editing is broken.  You can't hit the home key to get to the
beginning of your prompt line, etc. Its a small problem, but its annoying.
Perhaps TD 2.0 doesn't give up its hook into the readline routine? Furthermore,
returning back to TD 2.0 via exit tends to crash by 286 irrevocably - time to
hit the reset switch..

Similar problems exist when one asks TD to 'Go resident' - IE: return to DOS
but still catch breakpoints. When TD is reentered, it breaks the machine.

The fix for this is simple: switch back to command.com. Unfortunately, having
used 4DOS for 2 weeks now I am already addicted to it, so I find myself
switching back and forth fairly frequently..