Newsgroups: comp.os.msdos.djgpp
From: Peter Berdeklis <peter AT atmosp DOT physics DOT utoronto DOT ca>
Subject: Re: Interrupt handlers & GPF's in RMCBs 
Message-ID: <Pine.SGI.3.91.970122105717.28633C-100000@chinook.physics.utoronto.ca>
Nntp-Posting-Host: chinook.physics.utoronto.ca
Sender: news AT info DOT physics DOT utoronto DOT ca (System Administrator)
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Organization: University of Toronto - Dept. of Physics
In-Reply-To: <Pine.GSO.3.95.970120080408.4793A-100000@goodguy> 
Date: Wed, 22 Jan 1997 15:59:01 GMT
References: <Pine DOT GSO DOT 3 DOT 95 DOT 970120080408 DOT 4793A-100000 AT goodguy> 
Lines: 17
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

On Mon, 20 Jan 1997, Josh Turpen wrote:
> I've tried it with and without the sti, as some people told me I don't
> need it while the DPMI spec says I do.  Either way it still blows up
> about 1 out of 10 times.  This interrupt handler is installed with
> the __dpmi_set_protected_mode_interrupt_vector, and it works great
> except for the occasional hang.

You do need to explicitly call the sti under protected mode, because 
popping the flags isn't guarenteed to reset the interrupt flag.

Have you locked the code in your interrupt handler so that it doesn't get 
swapped to disk?

---------------
Peter Berdeklis
Dept. of Physics, Univ. of Toronto