Date: Wed, 12 Apr 2000 10:07:58 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Alexei A. Frounze" <alex DOT fru AT mtu-net DOT ru>
cc: djgpp AT delorie DOT com
Subject: Re: Processor Exceptions
In-Reply-To: <38F384D2.59DCB6FF@mtu-net.ru>
Message-ID: <Pine.SUN.3.91.1000412100526.16084H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 12 Apr 2000, Alexei A. Frounze wrote:

> I believe I could get that working under DPMI as well. It can't be impossible at
> all.

It's not impossible, just prohibited by the DPMI spec.

You can, of course, work around that, but the solution will have to be a 
different one for every DPMI server out there.  And you will need a lot 
of knowledge about how each DPMI server processes hardware interrupts.

While this seems like a wonderful way of learning about DPMI, it is 
hardly an efficient way to write a multithreading program.  For the 
latter, I recommend to stick with setitimer.