Xref: news2.mv.net comp.os.msdos.djgpp:6314 From: alaric AT abwillms DOT demon DOT co DOT uk (Alaric B. Williams) Newsgroups: comp.os.msdos.djgpp Subject: Re: Hardware Interrup Handlers & DJGPP Date: Tue, 23 Jul 1996 11:13:36 GMT Lines: 37 Message-ID: <838120315.10346.3@abwillms.demon.co.uk> References: <837175084 DOT 12151 DOT 0 AT abwillms DOT demon DOT co DOT uk> <4sva4h$suo AT leporello DOT cs DOT unibo DOT it> NNTP-Posting-Host: abwillms.demon.co.uk To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp gaggi AT cs DOT unibo DOT it (Nicola Gaggi) wrote: >Alaric B. Williams (alaric AT abwillms DOT demon DOT co DOT uk) wrote: >: I'm writing a tutorial on DJGPP hardware interrupts! I'll post the >: first draft in a couple of days. It'll be a little delayed; I'm busy :-( >I am interested in hardware interrupt programming too. >Well, I have a problem: I need to call the original interrupt code before >call my interrupt handler, how can I do this? I have used the function >go32_dpmi_chain_etc... but this routine chains the orignal interrupt code >*after* the user interrupt handler. Watcha need to do is keep the original real mode handler address, and use a function called something like "_go32_simulate_fcall_iret" (look in info) to chain the original handler. Put this at the start of thy handler. I haven't tried this lately, so there may be something I've forgotten! >Is there in your tutorial a solution for this? There will be... >Could you mail-me a copy of your tutorial? >Thank you. Sure! ABW -- I have become... Comfortably numb... Alaric B. Williams Internet : alaric AT abwillms DOT demon DOT co DOT uk http://www.hardcafe.co.uk/Alaric/