Xref:	news-dnh.mv.net comp.os.msdos.djgpp:2099
Path:	news-dnh.mv.net!mv!news.sprintlink.net!in1.uu.net!newstf01.news.aol.com!newsbf02.news.aol.com!not-for-mail
From:	hardgeus AT aol DOT com (Hardgeus)
Newsgroups:	comp.os.msdos.djgpp
Subject:	int86() in V2
Date:	19 Sep 1995 11:28:11 -0400
Organization:	America Online, Inc. (1-800-827-6364)
Lines:	20
Sender:	root AT newsbf02 DOT news DOT aol DOT com
Reply-To:	hardgeus AT aol DOT com (Hardgeus)
Nntp-Posting-Host:	newsbf02.mail.aol.com
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

    I have some mouse handler functions that use in86() calls.  In V1.x
they
work fine.  Then when I compile them in V2, either button presses get lost
or the xy coordinates get scrambled.  All of the code is pretty
straightforward.
Is there some change in the way int86() behaves that I should know about?

    Also, I use interrupt handlers a lot in my current project (keyboard,
serial,
timer) and I am following the guidelines of the faq...but they still seem
very 
unstable even in V2.  Recently I have seen people talking about locking
memory
for interrupts to prevent page faults.  Now this is something I have not
heard of
at all.  What is it exactly, how do I do it, and why?

John R. McCawley III
Cap'n Hardgeus

- Raw text -