Newsgroups: comp.os.msdos.programmer
Path: utzoo!utgpu!watserv1!maytag!watstat.waterloo.edu!dmurdoch
From: dmurdoch@watstat.waterloo.edu (Duncan Murdoch)
Subject: TD 2.01 versus Desqview
Message-ID: <1991Feb4.195510.8883@maytag.waterloo.edu>
Sender: daemon@maytag.waterloo.edu (Admin)
Organization: University of Waterloo
Date: Mon, 4 Feb 91 19:55:10 GMT
Lines: 26


Here's a little irritant I've found running either TD or TD286 under
Desqview 2.25.  Something about the way the debugger disconnects itself
from the mouse doesn't get through to Desqview, so if you 

 - run TD in a DOS window
 - exit TD
 - switch to a different window
 - switch back to the DOS window

Desqview will reinstall the TD mouse driver for you.  Of course, since
TD isn't there any more, it's not long until you crash if you move the
mouse.

It appears that a little program that just does a mouse initialization
call (i.e. INT 33h with AH=0) run after TD will convince Desqview
that the mouse driver isn't there any more, and things will be fine.

A nicer alternative would be a way to tell Desqview that it should handle
the mouse again.  As it is, once a window takes over the mouse, there
appears to be no way to give it back to DV.  Does anyone know of one?
(I've tried simply saving the mouse state and restoring it later,
but it doesn't seem to work.)

Duncan Murdoch
dmurdoch@watstat.waterloo.edu