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: <10112080159.AA19682@clio.rice.edu>
Subject: Re: DJGPP 2.03 update
To: acottrel AT ihug DOT com DOT au (Andrew Cottrell)
Date: Fri, 7 Dec 2001 19:59:17 -0600 (CST)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <000901c17f83$9fc51060$0102a8c0@acceleron> from "Andrew Cottrell" at Dec 08, 2001 11:59:11 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 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...)

> 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.