Date: Mon, 8 Dec 1997 16:43:42 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Joshua James Turpen <44699 AT ef DOT gc DOT maricopa DOT edu>
cc: djgpp AT delorie DOT com
Subject: Re: Win95 and ___djgpp_hw_exception...
In-Reply-To: <9712080710.AA25722@gcef.gc.maricopa.edu>
Message-ID: <Pine.SUN.3.91.971208163913.4200o-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Mon, 8 Dec 1997, Joshua James Turpen wrote:

> There seems to be a problem with the ___djgpp_hw_exception trick and
> windows 95 (of course).  The below program crashes my DOS box everytime. 
> Sometimes it takes a while, but it's very consistent.  As far as I can
> tell, I'm doing everything by the book.  I hook the PIT timer, I don't
> re-program it, I chain to the old handler, yada yada yada... 

One thing you did NOT do is to lock your interrupt handler and every data
it touches in memory.  This is a sure course to a disaster.  For more
details, see section 18.9 of the DJGPP FAQ list (available as
v2/faq210b.zip from the same place you get DJGPP). 

> Is there a reliable way to raise signals this way under win95?  I've
> written code to hook the interrupt gates directly, but I'm saving that as
> a last resort.  

Why don't you use the SIGALRM signal?  It is already set up for you so it 
works; why reinvent the wheel?