Date: Sat, 25 Mar 2000 06:52:40 +0500
Message-Id: <200003250152.GAA00961@midpec.com>
From: tr AT midpec DOT com (Prashant TR)
To: djgpp AT delorie DOT com
In-reply-to: <38DB970F.DC2EDA3B@mtu-net.ru> (alex.fru@mtu-net.ru)
Subject: Re: custom IRQ1 ISR
References:  <38DB970F DOT DC2EDA3B AT mtu-net DOT ru>
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

"Alexei A. Frounze" <alex DOT fru AT mtu-net DOT ru> proclaimed:

> AFAIK, there is no such reserved word as "interrupt" like in Borland
> C/C++ or Watcom C/C++.
> So how to set up kbd ISR just using standard library functions (DPMI /
> Go32 I think)?

Use _go32_dpmi_chain_protected_mode_interrupt_vector if you
want the original handler to be called.

If you don't wish to chain to the original handler, use
_go32_dpmi_allocate_iret_wrapper first and then use
_go32_dpmi_set_protected_mode_interrupt_vector to setup the
handler. And since you're talking of IRQ1, don't forget to
send an EOI signal if you use the second method.

And I think this is already there in the DJGPP FAQ (info faq).