Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!tikal!amc!ipmoea!ericr
From: ericr@ipmoea.UUCP (Eric Roskos)
Newsgroups: comp.os.minix
Subject: Mouse Problems
Message-ID: <41@ipmoea.UUCP>
Date: Thu, 22-Oct-87 01:44:54 EST
Article-I.D.: ipmoea.41
Posted: Thu Oct 22 01:44:54 1987
Date-Received: Sun, 25-Oct-87 10:05:51 EST
Reply-To: ericr@ipmoea.UUCP (Eric Roskos)
Organization: Redmond, WA
Lines: 16
Summary: I forgot to mention, this is a BUS mouse

Bing H. Bang at Lanier writes:

> i had this problem with my mouse before i made my com port drivers.
> the problem is very simple; the mouse being connected to a serial port,
> gives off com port interrupts 11 or 12 and since minix does not have a
> handler for these interrupts, they produce the generic error about
> unknown interrupts. several solutions:

I forgot to mention in my posting, this is a "Bus" mouse that is causing
the problem (i.e., it has its own interface card, & you can set the
interrupt to use with a jumper).  I don't *think* the mouse interrupts
if you don't move it (does it? Unfortunately it doesn't come with any
hardware documentation).  It looks like this is a more subtle bug than
that; I had thought maybe the mouse driver enabled something in the
mouse card which was causing periodic interrupts, but so far I haven't
found any evidence to support or refute that idea.