Message-ID:	<3A03B1C5.199BCA0A@home.com>
From:	Andy Chamard <achamard AT home DOT com>
Organization:	@Home Network
X-Mailer:	Mozilla 4.5 [en]C-AtHome0405 (Win98; U)
X-Accept-Language:	en
MIME-Version:	1.0
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Installing a custom PS/2 Mouse ISR
References:	<3A039ACD DOT D198A637 AT home DOT com> <7458-Sat04Nov2000083520+0200-eliz AT is DOT elta DOT co DOT il>
Lines:	12
Date:	Sat, 04 Nov 2000 06:52:47 GMT
NNTP-Posting-Host:	24.64.24.6
X-Complaints-To:	abuse AT home DOT net
X-Trace:	news1.rdc1.ab.home.com 973320767 24.64.24.6 (Fri, 03 Nov 2000 22:52:47 PST)
NNTP-Posting-Date:	Fri, 03 Nov 2000 22:52:47 PST
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Thanks for the reply...
	A little bit more info... I am basically making my own ISR and
hooking that up to INT74h -- the ps2 mouse interrupt channel. In the ISR
itself, every byte of data that comes from the port ( using inportb())is
stuffed into a circular queque.. the only problem is that there is no
address (not that i have been able to find anyways) that corresponds to
IRQ 12 (that is mapped to INT74h). If so, then one can't really get the
byte data using inportb() can they? Off to sift through my Indispensable
PC Hardware book...
				JAC

- Raw text -