Date:	Thu, 27 May 1999 10:34:44 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	djgpp AT delorie DOT com
Subject:	Re: intrrupt handler.
In-Reply-To:	<374B647E.1A9D48EA@geocities.com>
Message-ID:	<Pine.SUN.3.91.990527103426.9561H-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, 25 May 1999, Derek wrote:

> whoops..sorry..a couple mistakes...I corrected them but it stiil doesn't
> work....

Define ``doesn't work''.  Otherwise, how can you expect us to help
you?

I also think this is a very inefficient way of hooking the mouse.  You
are intercepting the COM1 communications port (presumably connected to
a serial mouse).  This means you will have to handle all the
communications with the mouse yourself, instead of letting the mouse
driver handle it.  Even the mouse cursor won't appear and won't move
unless your program creates it, puts it on the screen, and then moves
it whenever the mouse reports movement.  In effect, you will be
writing your own mouse driver.

And then, of course, some (many?) modern PCs use a mouse that plugs
directly into the system bus, in which case you won't see anything
useful coming your way through COM1.

Hooking the mouse through function 0Ch of Int 33h is much, much, MUCH
easier.

- Raw text -