Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ihnp4!inuxc!pur-ee!j.cc.purdue.edu!tim
From: tim@j.cc.purdue.edu (Timothy Lange)
Newsgroups: net.micro.pc
Subject: Re: trouble with MS mouse (bus version) & MS windows
Message-ID: <2017@j.cc.purdue.edu>
Date: Wed, 10-Sep-86 17:44:51 EDT
Article-I.D.: j.2017
Posted: Wed Sep 10 17:44:51 1986
Date-Received: Thu, 11-Sep-86 10:57:39 EDT
References: <2ffc0121.1d22@apollo.uucp>
Reply-To: tim@j.cc.purdue.edu.UUCP (Timothy Lange)
Organization: PUCC, Purdue University
Lines: 17


To: decvax!wanginst!apollo!wyant	(We use domain names here, mail
gives fits when I try to reply to an address similar to above.)

This may interest others that just purchased MS Mouse and have Windows.

I had the same trouble too, found out that with the newer mice (boards
marked with Rev. G), you have to copy the file MOUSE.DRV from the mouse
disks to one of the Windows disks.  This replaces an older copy of the
driver for Windows.  There is a loose page in your Mouse book describing
this change.  I had to call MicroSoft to find out about the loose page
IN THE BACK of my manual.  After I copied the new driver and reinstalled
Windows, all was well.

Tim Lange
Purdue University Computing Center
West Lafayette, IN