Xref: news2.mv.net comp.os.msdos.djgpp:4160
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: What does _go32_dpmi_chain_protected_mode_interrupt() really do?
Date: Tue, 21 May 1996 09:29:05 CDT
Organization: Rice University, Houston, Texas
Lines: 8
Message-ID: <31a1d331.sandmann@clio.rice.edu>
References: <4nrmku$2sm AT news1 DOT goodnet DOT com>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> I'm going on the assumption that upon interrupt entry, eflags, cs, and eip
> have been pushed onto the stack, and everything else is unchanged.  

You need to get a copy of the DPMI 0.9 specification and read on hardware
interrupts.  Your assumptions are wrong, and what you are trying to do won't
work at all.  Notifying the "main line code" that a HW interrupt has happened
is difficult - it's what the signal() library in V2 does for you.  You might
be able to use those routines to time slice, but it won't be trivial.