Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!wuarchive!psuvax1!ukma!gatech!emcard!wa4mei!nanovx!msa3b!kevin
From: kevin@msa3b.UUCP (Kevin P. Kleinfelter)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Microsoft Mouse meets DOS 4.01
Keywords: Microsoft mouse Northgate MSDOS
Message-ID: <1167@msa3b.UUCP>
Date: 26 Oct 89 13:03:29 GMT
References: <5216@uhccux.uhcc.hawaii.edu>
Organization: Management Science America, Inc., Atlanta, GA
Lines: 30

dillon@uhccux.uhcc.hawaii.edu (Ian Dillon) writes:

>After running "msetup" (the Microsoft Mouse install program), and
>making the appropriate changes to the AUTOEXEC.BAT file, I receive
>the following message after rebooting: 

>   " Microsoft mouse not found"
...
>Microsoft suggested switching to a bus port (no thanks), or wait until
>they send a new driver (which hasn't even been developed yet).  Option
>2 has me thinking of trading in for a Logitech device, or switching to
>DOS 3.3x.
>If you have had similar problems, I would appreciate hearing from you. 

I installed a non-Microsoft serial mouse on a HYUNDAI-286C.  The
driver that came with it found it, and all my mouse software found
it just fine, EXCEPT FLIGHT SIMULATOR 3.0.  Now the funny thing about
FS is that Microsoft sells it.

I installed a Microsoft SERIAL mouse on a PS/2 SERIAL port (not the
mouse port).  The Microsoft driver absolutely refused to find it.

One hypothesis is that serial hardware which does not PERFECTLY match
the XT may cause mouse problems.  Another hypothesis is that Microsoft
is a pain in the a** just for the h*** of it.

My solution was to put a Microsoft Bus mouse on my Hyundai and attach
a Microsoft mouse to the mouse port on my PS/2.  Whatever the reason,
Microsoft software seems to do a better job of finding bus-attached
mice.