Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!hp4nl!phigate!ehviea!sun4dts!derek
From: derek@sun4dts.dts.ine.philips.nl (derek)
Newsgroups: comp.os.msdos.programmer
Subject: Re: TD 2.01 versus Desqview
Message-ID: <656@sun4dts.dts.ine.philips.nl>
Date: 5 Feb 91 14:39:35 GMT
References: <1991Feb4.195510.8883@maytag.waterloo.edu>
Lines: 19

dmurdoch@watstat.waterloo.edu (Duncan Murdoch) writes:


	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 
[stuff deleted]
	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.)

Doesn't [R]econfigure [T]une performance F1 (restore mouse) work? If so, 
create a script to run after TD (or even a script to run TD?).

Best Regards, Derek Carr
DEREK@DTS.INE.PHILIPS.NL           Philips I&E TQV-5 Eindhoven, The Netherlands 
Standard Disclaimers apply.