Xref: news2.mv.net comp.os.msdos.djgpp:4875
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Bug in CWSDPMI?
Date: Tue, 11 Jun 1996 22:55:59 CDT
Organization: Rice University, Houston, Texas
Lines: 6
Message-ID: <31be3fcf.sandmann@clio.rice.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 960609183529 DOT 342r-100000 AT is> <4ph0gv$eeh AT ns DOT felk DOT cvut DOT cz>
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

OK, I can reproduce this bug, and I think I know why it happens, and I think
I know a fix.  What's interesting is that on my box, the bug only happens
if you run a NESTED djgpp app (ie GCC) and not if you just run a normal app.
So, my normal testing didn't find it.  For those interested, it seems the
local_enable count wasn't zero when Windows tries to start.  Why Windows 
pukes in this case is unknown to me.  Hopefully fixed in R2.