Writing Interrupts (ISRs) That Call Mouse Functions

 Last reviewed: September 16, 1996
Article ID: Q46462
The information in this article applies to:
  • Microsoft Mouse Driver for MS-DOS, versions 1.x, 2.x, 3.x, 4.x, 5.x, 6.x, 7.x, 8.x, and 9.0

SUMMARY

The mouse driver protects itself from reentrancy from other mouse function calls but not from interrupt service routines (ISRs) with higher priority.

It is recommended that you do not write an ISR with a higher priority than the mouse hardware interrupt (for example, for the timer interrupt) that calls mouse functions. The result may be undesirable and erroneous. If your ISR is performing a mouse function call, your interrupt may occur during the execution of the mouse function call and start running your ISR again, that is, the original mouse function call may never be finished.

The appropriate routine is to use the mouse function 12/20 to set the mouse user-defined subroutine.

KBCategory: kbhw
KBSubcategory:
Additional reference words: 7.00 7.04 7.05 8.00 8.10 1.00 8.20 9.00

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 16, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.