Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!decwrl!mcnc!gatech!bloom-beacon!eru!hagbard!sunic!mcsun!hp4nl!sci.kun.nl!wn3.sci.kun.nl!ge
From: ge@wn3.sci.kun.nl (Ge' Weijers)
Newsgroups: comp.sys.ibm.pc.hardware
Subject: Re: Mice
Keywords: mouse protocols
Message-ID: <2431@wn1.sci.kun.nl>
Date: 12 Nov 90 10:39:44 GMT
References: <2410@wn1.sci.kun.nl> <2361@moscom.UUCP> <2445@cod.NOSC.MIL>
Sender: root@sci.kun.nl
Distribution: comp
Lines: 17

bmarsh@cod.NOSC.MIL (William C. Marsh) writes:

>First, check to make sure the interrupt vector used by the 'int 33h' is not
>all zeros!  Older versions of DOS did not initialize all the interrupt vectors
>to point to an iret, so simply calling the interrupt would result in a crash.

>This is important for looking for an EMS driver too.

This is all pointless to me. The mouse is not connected to a system with an
Intel processor, or MS-DOS.

Ge'
--
Ge' Weijers                                    Internet/UUCP: ge@cs.kun.nl
Faculty of Mathematics and Computer Science,   (uunet.uu.net!cs.kun.nl!ge)
University of Nijmegen, Toernooiveld 1         
6525 ED Nijmegen, the Netherlands              tel. +3180652483 (UTC-2)