X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10112092150.AA14739@clio.rice.edu>
Subject: Re: DJGPP 2.03 update
To: acottrel AT ihug DOT com DOT au (Andrew Cottrell)
Date: Sun, 9 Dec 2001 15:50:51 -0600 (CST)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <Pine.SUN.3.91.1011209113607.13320I-100000@is> from "Eli Zaretskii" at Dec 09, 2001 11:36:32 AM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

I found out the cause of my recent win2K ntvdm crashes ...
I was running gcc 2.95.3 (20010315) unpatched.  I always assumed this
didn't nest more than 2 deep.  But I found out that collect2 spawns 
something (?) - when I binary patched collect2.exe to set the psp
no more problems under Win2K (so far, but I also did gcc.exe too).

Yes, I have a binary patch utility which can add 'set psp' code to a 
v2.03 binary.  It only patches images which contain the spawn code.  
It removes the "test" of _8087 in __exit and replaces it with an 8
byte 'get psp/set psp' which shouldn't hurt any system.  The thought
was any system which supports Win2K/XP must have a comprocessor...
I'll eventually make it available on clio.  I wanted to be able 
to run old binaries which nest (like gcc 2.8.1) under Win2K
(or XP where I can't patch NTVDM...) without having to rebuild 
everything.