X-Sent:	15 Jul 2001 19:53:35 GMT
Message-ID:	<001701c10d68$074978e0$e33e1d18@nycap.rr.com>
From:	"Matthew Conte" <matt AT conte DOT com>
To:	<djgpp AT delorie DOT com>
Cc:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
References:	<001d01c10d33$d7e6b9c0$e33e1d18 AT nycap DOT rr DOT com> <3405-Sun15Jul2001183438+0300-eliz AT is DOT elta DOT co DOT il> <000a01c10d47$14145340$e33e1d18 AT nycap DOT rr DOT com> <9003-Sun15Jul2001213443+0300-eliz AT is DOT elta DOT co DOT il>
Subject:	Re: '9x and raise in interrupt service routines
Date:	Sun, 15 Jul 2001 15:54:57 -0400
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2479.0006
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2479.0006
Reply-To:	djgpp AT delorie DOT com

From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>

> You have all the cards: just chain to the default handler only when
> Ctrl-C or Ctrl-BREAK was pressed.  You can detect that using the
same
> code as the default handler does (see the file
src/libc/go32/exceptn.S
> in the djlsr203.zip archive).  In a nutshell, it looks at the
keyscan
> code and the shift byte in the BIOS area.

perhaps i'm being thick here, but i haven't seen a mechanism to
selectively chain to a previous interrupt handler anywhere, the FAQ or
otherwise.  i've always either set up the interrupt handler via
_go32_dpmi_[set/chain]_protected_mode_interrupt_vector, and that's
all.

how does one chain to the previous handler from C code, especially in
the middle of an already-executing interrupt handler?  should i be
accessing ___djgpp_hwint_flags?

thanks in advance,
matthew.

- Raw text -