Xref: utzoo comp.windows.ms:3679 comp.sys.ibm.pc.misc:202
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!compuram!pgd
From: pgd@bbt.se (P.Garbha)
Newsgroups: comp.windows.ms,comp.sys.ibm.pc.misc
Subject: Re: Win3 and Serial vs Bus Mice
Keywords: Win3, Mouse, Serial
Message-ID: <1990Jul24.065813.1278@bbt.se>
Date: 24 Jul 90 06:58:13 GMT
References: <639@dg.dg.com>
Organization: /etc/organization
Lines: 14

In article <639@dg.dg.com> jorge@dg.dg.com (Jorge Lach) writes:

>As it turns out, that port is for a "bus mouse". The problem seems to be
>that when the Win3 mouse drives sees that port, it thinks that is where the
>mouse is. Of course, since there is no mouse in there, the cursor does not
>move. Microsoft tech support does not know of any way of telling the mouse
>driver not to look there (or telling it to look specifically at one of
>the COM ports). Right now, I'm ready to put Win3 back in its box and ship
>it to Microsoft, and stick to Win286 (at least it's usable).

We have a screen card with a microsoft bus-mouse-port on, but no mouse
that fits the port.  On win286 we had exactly the problem you are
speaking about. Our solution was to use a non-microsoft serial mouse.
(Are microsoft trying to decrease their own sales of mice, or what?)