Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!henry.jpl.nasa.gov!elroy.jpl.nasa.gov!peregrine!ccicpg!cci632!rit!ritcv!pga-grd
From: pga-grd%ritcv@cs.rit.edu (pga-grd%ritcv@cs.rit.edu)
Newsgroups: comp.sys.ibm.pc
Subject: Logitech Mouse Driver and Turbo Debugger don't mix!!
Summary: getting caught in the mouse hardware interrupt handler
Keywords: Logitech, Turbo Debugger
Message-ID: <1444@cs.rit.edu>
Date: 15 Dec 89 16:37:34 GMT
Sender: news@cs.rit.edu
Reply-To: pga-grd%ritcv@cs.rit.edu  (Jack D. Unrue)
Distribution: usa
Organization: Rochester Institute of Technology, Rochester, NY
Lines: 19


	Greetings!

	I have an interesting problem involving my Logitech Bus Mouse (the
driver is version 3.4) and Turbo Debugger.  Whenever I am stepping through code
using the CPU window, TD invariably places me at the beginning of what appears
to be the hardware interrupt handler of the mouse driver.  This doesn't
happen with every instruction; in fact, I usually am able to get a fair
distance before it happens.  However, it ALWAYS happens at least once and
is very annoying.

	I have an idea of what is causing this, but I am interested in hearing
other opinions.  I would also like to know if subsequent revisions of the 
driver took care of this?  Has anyone else experienced this??

	Thanks a bunch!


		- Jack D. Unrue