X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
X-Authentication-Warning:	new-smtp2.ihug.com.au: Host p519-apx1.syd.ihug.com.au [203.173.142.11] claimed to be acceleron
Message-ID:	<001301c17f92$7a602a80$0102a8c0@acceleron>
From:	"Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
To:	"Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
Cc:	<djgpp-workers AT delorie DOT com>
References:	<10112080159 DOT AA19682 AT clio DOT rice DOT edu>
Subject:	Re: DJGPP 2.03 update
Date:	Sat, 8 Dec 2001 13:45:31 +1100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
Reply-To:	djgpp-workers AT delorie DOT com

> > I spotted change that was missed, but it was also forgotten in the
original
> > 2.03. The stub.asm file ws not updated when DJGPP 2.03 was released. The
> > stub.asm on the CVS trunk is as is the version in the updated 2.03
source
> > zip:
> > stubinfo_magic:                         ; char [16]
> >         .db     "go32stub, v 2.02"      ; version may change, [0..7]
won't
>
> Someone may be looking at this for a structure change - and I don't
> want to potentially break anything without a good reason.  I want to
> just leave it alone.
>
> I'm really time constrained, and unless something is something more broken
> than 2.03 in the current distribution, I'd like to just send the refresh
> out when it gets enough testing and then put a push in for the 2.04
> release.  There are about 20 bugs fixed in the refresh.  If we looked
> hard enough we could find some more (like the ident string in all the
> stubs has year 101 in it...)
I agree that the 2.03 update should ship once it gets anough testing. I have
been working on this for the past 3 hours getting all the files from the
original 2.03 that I had on an old CD (that took about 1 hour to find as my
current CD has some Win 2K files!!!) installed on W98 box and configured
correctly and have built LIBC, make, bash 204, shell utiles, file utils, bin
utils and as I wrote this got a fail on the GCC 2.9.5.3 install phase, once
GCC is built I will do a complete re-build as then I shouldn't get any
selector leaks when doing a complete build.

> > The reason I am bringing this up is that I need a way of checking that I
> > have installed the updated exe files and don't have any of the "old"
2.03
> > files when I try the files on my XP box.
>
> No easy way.  You could look for images built with the V2.03.1 ident
> string (nov 25?) with 2.8.1.
Should I assume that any exe downloaded from Simtel that does not have a
date of "Sun Nov 25 22:31:37 2001" in the stub is does not support Win 2K or
XP?

Andrew

- Raw text -