Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!cs.utexas.edu!samsung!xylogics!merk!alliant!linus!mwunix.mitre.org!jcmorris
From: jcmorris@mwunix.mitre.org (Joe Morris)
Newsgroups: comp.sys.ibm.pc
Subject: Re: 386MAX
Keywords: Compatibility, Bus Mouse
Message-ID: <108728@linus.UUCP>
Date: 9 May 90 12:39:00 GMT
References: <307@tlvx.UUCP> <221@demott.COM>
Sender: news@linus.UUCP
Reply-To: jcmorris@mwunix.mitre.org (Joe Morris)
Distribution: na
Organization: The Mitre Corporation
Lines: 20

In article <221@demott.COM> kdq@demott.COM (Kevin D. Quitt) writes:
>
>    386Max has a problem with the Miscorsoft BUS mouse; according to
>Qualitas, it manifests itself differently on each machine.  On my
>system, the mouse motions are very jerky in CodeView, making the mouse
>almost useless.

On my PS/2-70-121 (the 20 MHz version) with 386^max the only mouse 
problem I've seen is a "wild mouse" on Microsoft Word, both versions
4 and 5.  The system also locks down the bit switch showing that
the left mouse button has been pressed, which makes Word do interesting
things.

Interestingly, I found that by (a) clicking the left mouse button, (b)
invoking UNDO to get rid of the unwanted copied text, and (c) invoking
*ANY* command under LIBRARY RUN (the VER command works fine) I can recover
from the situation without having to exit WORD.  I can't make the problem
occur on demand, which is curious since I don't have any time-dependent
TSR's on my machine and see failures (sometimes) when I haven't touched
any comm ports...