Mouse drivers: mouse.com mouse.sys mouse.drv
Joe M. Abbate
but I was never able to find any discussion as to why would someone use
one vs. the other. With Windows 3.1, there's mouse.drv and mouse.com
(version 8.20). If I assume correctly, the .drv is used by Windows
and .com is for DOS use. Can someone confirm this and/or point me to
anywhere in the documentation where the differences are explained?
Joe
----------------------------------------------------------------------
Joe M. Abbate
Ingres - Latin America
jab...@ingres.com
Blake Coverett
>one vs. the other. With Windows 3.1, there's mouse.drv and mouse.com
>(version 8.20). If I assume correctly, the .drv is used by Windows
>and .com is for DOS use. Can someone confirm this and/or point me to
>anywhere in the documentation where the differences are explained?
This is correct. mouse.com is the driver for DOS and mouse.drv is the Windows
driver.
I answered this mostly because it gives a perfect example of Windows
virtualization. Both of these mouse drivers are designed to talk directly
to the mouse hardware. In fact they both do, mouse.com talks directly
to the hardware if Windows isn't running or if a DOS app is active in
standard mode, mouse.drv talks directly to the hardware if a Win app
is active in standard mode.
In enhanced mode both drivers continue to think they are talking to the
hardware but in fact they are being virtualized by *vmd (the virtual mouse
driver built into win386.exe)
-Blake (Apologizes for the sermon, Tomer I hope you are reading this)
Now was that a sneaky followup to the thread that won't die or what?
--
#include <std/disclaimer.h> bla...@microsoft.com
Mail Flames, Post Apologies. ...!uunet!microsoft!blakeco
DAVID SCOTT PASCHAL
In article <1992Sep02.0...@microsoft.com>, bla...@microsoft.com (Blake Coverett) writes:
|> Newsgroups: comp.os.ms-windows.misc
|> Path: taco!rock!stanford.edu!ames!haven.umd.edu!uunet!microsoft!hexnut!blakeco
|> From: bla...@microsoft.com (Blake Coverett)
|> Subject: Re: Mouse drivers: mouse.com mouse.sys mouse.drv
|> Message-ID: <1992Sep02.0...@microsoft.com>
|> Date: Tue, 1 Sep 92 22:06:52 GMT+5:00
|> Organization: Microsoft Canada Inc.
|> References: <1992Sep1.1...@pony.Ingres.COM>
|> Keywords: mouse drivers
|> Lines: 25
Hi. So what is MOUSE.SYS for?
Also, while we're on the subject of mice, why is it that the INT 33h call to
reset the mouse (function 0) takes so long? Certain programs (like old
versions of Turbo Debugger and some programs that were written with True
BASIC) like to call this function constantly, and it really slows things down.
I wrote a program on my computer to selectively disable the mouse driver, but
still I wonder why it's so time-consuming in the first place to reset the
mouse...
Tschuess,
David Paschal
stephen_gibson
Maybe it has to deal with all of the resources used to gain mouse access
in DOS windows.
Steve Gibson
gibs...@sonoma.edu
M. Guyott
mouse.com - used in autoexec.bat
mouse.drv - used by Windows.
Marc
----
Two of the worst things we teach our children are that a knowledge of science
is nice but not necessary, and a knowledge of sex is necessary but not nice.
Marc Guyott Constellation Software, Inc. (508) 620-2800
Framingham, Mass. 01701 USA Ext. 3135
mgu...@primerd.prime.com ...!{uunet, decwrl}!primerd.prime.com!mguyott
mgu...@eriador.prime.com ...!{uunet, decwrl}!eriador.prime.com!mguyott
Arnold R Cowan
Abbate) writes:
> >one vs. the other. With Windows 3.1, there's mouse.drv and mouse.com
> >(version 8.20). If I assume correctly, the .drv is used by Windows
>
> In enhanced mode both drivers continue to think they are talking to the
> hardware but in fact they are being virtualized by *vmd (the virtual mouse
> driver built into win386.exe)
>
mouse and Windows 3.1? When I try to run a DOS app I get a dialog box that says
I have to pick whether to have Windows or the DOS app use COM2 (the port to
which the mouse is attached). If I pick the app, the mouse works fine in that
app, but dies when I return to Windows.
Where *vmd comes in is that Gateway tech support once had me comment out the
*vmd line in ?.INI. I started having the mouse problem well after that, when I
installed a Telepath internal modem (using previously unassigned COM1). The
modem gives me no trouble and the mouse gives me no trouble as long as I stay in
Windows apps or don't run Windows. There are no IRQ conflicts.
Any information or advice would be appreciated.