home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.msdos.programmer
- Path: sparky!uunet!news.centerline.com!noc.near.net!news.Brown.EDU!qt.cs.utexas.edu!yale.edu!spool.mu.edu!wupost!cs.utexas.edu!hellgate.utah.edu!peruvian.utah.edu!msmith
- From: msmith%peruvian.utah.edu@cs.utah.edu (Matthew Smith)
- Subject: Re: Capturing Mouse Interrupts
- Date: 16 Nov 92 08:59:29 MST
- Message-ID: <1992Nov16.085929.14092@hellgate.utah.edu>
- Keywords: mouse capture interrupt IRQ
- Reply-To: msmith%peruvian.utah.edu@cs.utah.edu
- Organization: University of Utah, CS Dept., Salt Lake City
- References: <ua#@byu.edu>
- Lines: 25
-
- In article <ua#@byu.edu>, $dougn@sasb.byu.edu (Douglas R. Nebeker - MIS_SAS) writes:
- |> Help!
- |>
- |> I am trying to hook the mouse interrupts so that each time the mouse is
- |> moved, my routine can be notified. I've tried hooking Int 33h, but found
- |> that didn't work since Int 33h is only called to initialize the mouse and/or
- |> driver. Int 33h, AX=24h returns the IRQ number and tells me that my mouse
- |> is using IRQ 4 (I have comfirmed this with other utilities).
-
- Try looking at interrupt 33h, function 12h. This call allows you to force the
- mouse to call a function of yours whenever an interrupt occurs. I believe you
- need to pass in the address of your function in DS:BX, and the mask of "interrupt
- types" (such as every time the mouse moves, a button is pressed, a button is
- released, etc) that determines which mouse functions causes your handler to be
- called in CX. You can find that information in any lowlevel reference such as Ralf
- Brown's interrupt listings.
-
- |> Douglas R. Nebeker Internet: $dougn@sasb.byu.edu
-
- --
- Matt Smith
- msmith@peruvian.utah.edu
- Student - University of Utah Department of Computer Science
-
- "Dead minds stink alike" - me.
-