Message-ID: <38E8B9C6.B2B48772@corel.com>
Date: Mon, 03 Apr 2000 11:33:26 -0400
From: Jonathan Meunier <jonathanm AT corel DOT com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: keyboard interrupt
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000403104511 DOT 26246A-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 120.150.3.42
X-Trace: 3 Apr 2000 11:33:49 -0500, 120.150.3.42
Lines: 29
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii wrote:
> 
> On Sun, 2 Apr 2000, Trancelucid wrote:
> 
> > Err, not DJGPP itself, but rather handlers written in C.. DJGPP function
> > _go32_dpmi_chain_protected_mode_interrupt_vector chains the original
> > handler automatically. Is there a way to call the original handler only
> > when I want it to?
> 
> Yes, you could call the original handler (saved during initialization)
> instead of chaining.

I know the original handler's address has been saved in
_go32_dpmi_seginfo var, but how can I actually call the original
handler? I know how to it in Watcom (make a pointer to function, assign
it the return value of _dos_getvect(interrupt_number), and then you
could call it directly), but I don't know how to do it in DJGPP.

> You can always ask questions here, if something in the sources is
> unclear.  That's what's great with DJGPP: you can talk to the
> developers whenever you need to.

I looked at the sources, and it is very similar to what Alexei A.
Frounze posted, except for a few things (eg: call count variable, 32k
stack as you mentionned before, etc).

Thanks,
	.(Trancelucid).
	  .  Jaune  .