From: "Alexei A. Frounze" <alex DOT fru AT mtu-net DOT ru>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: custom IRQ1 ISR
Date: Sat, 25 Mar 2000 18:58:58 +0300
Organization: MTU-Intel ISP
Lines: 19
Message-ID: <38DCE242.A9610A46@mtu-net.ru>
References: <38DB970F DOT DC2EDA3B AT mtu-net DOT ru> <200003250152 DOT GAA00961 AT midpec DOT com>
NNTP-Posting-Host: ppp99-22.dialup.mtu-net.ru
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: gavrilo.mtu.ru 954146158 95701 212.188.99.22 (27 Mar 2000 08:35:58 GMT)
X-Complaints-To: usenet-abuse AT mtu DOT ru
NNTP-Posting-Date: 27 Mar 2000 08:35:58 GMT
X-Mailer: Mozilla 4.61 [en] (Win95; I)
X-Accept-Language: en,ru
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

I got it working. Thanks.

Alexei A. Frounze


Prashant TR wrote:
> 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).