Article View: comp.os.msdos.programmer
Article #4892Re: Turbo debugger mouse problem!
From: Mike Castle {Nexus}
Date: Tue, 26 Feb 1991 17:30
Date: Tue, 26 Feb 1991 17:30
45 lines
2648 bytes
2648 bytes
In article <1991Feb26.100353.3527@ugle.unit.no> rmich@Lise.Unit.NO (Rolf Michelsen) writes:
>
>Hi!
>
>I'm having some trouble with using a mouse with Turbo Debugger 2.0 and Turbo
>Profiler 1.0. I am using an Artec Mouse with driver version 6.6.
Can you upgrade to a newer version of a mouse driver?
Having seen this discussed in a number of newsgroups, I think this should be
placed in a FAQ somewhere.
It seems that all the new Borland products that use mouse-based interfaces are
having problems with older mouse drivers. Evidently many mouse drivers don't
have some function that (I *think*) temporarily disables the mouse driver, or
at least puts it back into the state it was before running the program currently
using the mouse. This way you can shell to DOS, and start up another program
that uses the mouse, without having any problems. Similarly, you can compile
and run a program that uses a mouse.
I was having problems with my 6.x mouse driver, but when I upgraded to the 7.04
driver that came with win3, my problems went away (though the mouse does seem
a bit more jerky now.... but that may just be halucinations :-)
< disclaimer >
I've not done any mouse programming, so I'm not sure what all commands this
entails, so some of this information may be incorrect and/or misleading.
< end disclaimer >
A question about mouse driver version numbers:
Rolf states that his mouse driver is version 6.6. Does this mean that it's
equivalent to MS mouse drivers v6.6, or is it just version 6.6 of their own
drivers?
That is, if someone came onto the market with a new mouse and mouse drivers,
would their drivers be listed as v1.0 (and hopefully being MS 7.0 compatible)
or would they list it as being a v7.0 mouse driver?
Btw, does anyone know what the latest version is of MS Mouse drivers??
--
Mike Castle (Nexus) S087891@UMRVMA.UMR.EDU (preferred) | XEDIT: Emacs
mcastle@mcs213k.cs.umr.edu (unix mail-YEACH!)| on a REAL
Life is like a clock: You can work constantly, and be right | operating
all the time, or not work at all, and be right twice a day. | system. :->
Technical Details
Message-ID:
<2273@umriscc.isc.umr.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!umriscc!mcs213f.cs.umr.edu!mcastleReferences:
<1991Feb26.100353.3527@ugle.unit.no>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!umriscc!mcs213f.cs.umr.edu!mcastle
From: mcastle@mcs213f.cs.umr.edu (Mike Castle {Nexus})
Newsgroups: comp.os.msdos.programmer
Subject: Re: Turbo debugger mouse problem!
Message-ID: <2273@umriscc.isc.umr.edu>
Date: 26 Feb 91 17:30:37 GMT
References: <1991Feb26.100353.3527@ugle.unit.no>
Sender: news@umriscc.isc.umr.edu
Organization: University of Missouri - Rolla
Lines: 45