home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.misc
- Path: sparky!uunet!microsoft!hexnut!blakeco
- From: blakeco@microsoft.com (Blake Coverett)
- Subject: Re: Mouse drivers: mouse.com mouse.sys mouse.drv
- Message-ID: <1992Sep02.020652.14983@microsoft.com>
- Date: 02 Sep 92 02:06:52 GMT
- Organization: Microsoft Canada Inc.
- References: <1992Sep1.175930.9276@pony.Ingres.COM>
- Keywords: mouse drivers
- Lines: 25
-
- In article <1992Sep1.175930.9276@pony.Ingres.COM> jabbate@Ingres.COM (Joe M. 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
- >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> blakeco@microsoft.com
- Mail Flames, Post Apologies. ...!uunet!microsoft!blakeco
-