Date: Tue, 28 May 2002 21:04:30 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: Lars Erdmann <lars DOT erdmann AT arcor DOT de>
Message-Id: <1659-Tue28May2002210430+0300-eliz@is.elta.co.il>
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
CC: djgpp AT delorie DOT com
In-reply-to: <3CF4EF43.BC5325C9@arcor.de> (message from Lars Erdmann on Wed,
	29 May 2002 17:09:55 +0200)
Subject: Re: Hooking protected mode interrupts
References:  <3CF4EF43 DOT BC5325C9 AT arcor DOT de>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: Lars Erdmann <lars DOT erdmann AT arcor DOT de>
> Newsgroups: comp.os.msdos.djgpp
> Date: Wed, 29 May 2002 17:09:55 +0200
> 
> I have successfully hooked a protected mode interrupt.
> Now I have read in some note, that the protected mode wrapper that is
> obtained via _go32_dpmi_alloc_iret_wrapper (or so) or via
> _go32_chain_protected_mode_interrupt_vector (or so) is not locked by
> djgpp.

No, that's not true: the wrapper code is locked, but the code and the
data of your handler are not.  In particular, locking the stack is
difficult, as is locking code of a C function.

See section 18.9 of the DJGPP FAQ list for more details.