X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: jbs30000 AT aol DOT com (Joel) Newsgroups: comp.os.msdos.djgpp Subject: Re: Interrupt handler question Date: 11 Apr 2004 18:48:25 -0700 Organization: http://groups.google.com Lines: 20 Message-ID: <84e4e2a9.0404111748.71d5221f@posting.google.com> References: <84e4e2a9 DOT 0404102155 DOT 6533748 AT posting DOT google DOT com> NNTP-Posting-Host: 172.140.242.173 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1081734505 12445 127.0.0.1 (12 Apr 2004 01:48:25 GMT) X-Complaints-To: groups-abuse AT google DOT com NNTP-Posting-Date: Mon, 12 Apr 2004 01:48:25 +0000 (UTC) To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hans-Bernhard Broeker wrote in message news:... > Joel wrote: > > Anyway, is it possible to call the old routine stored with > > _go32_dpmi_get_real_mode_interrupt_vector while in the middle of the > > new routine? > > I doubt it. The problem being that the end of an interrupt handler is > signalled by a IRET instruction. The old routine will be ending in > such an IRET. So at the minimum, you'ld have to use the DPMI simulate > interrupt call method to call it, and I'm not sure that's allowed from > inside an interrupt handler. OK, how about this then, I saw an example somewhere on line of a program (which I can't find now) that hooks int 21h and screws with the delete file function, but for any other function called, it just chains to the original handler. So how would I do that? See why an interrupt is being called, then decide whether or not to handle it myself, or let the original handler deal with it?