Date:	Mon, 5 Apr 1999 17:06:25 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	"Mark E." <snowball3 AT usa DOT net>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Bash 2.03 updated March 22nd
In-Reply-To:	<199904051436.OAA79226@out2.ibm.net>
Message-ID:	<Pine.SUN.3.91.990405170300.29531A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 5 Apr 1999, Mark E. wrote:

> > Wasn't that time frame about the same as when you switched from Bash 2.02 
> > to 2.03?  If so, could it be that the problem appeared in 2.03?
> 
> My changelog says Feb. 19th.

I don't think I had the 19th build.  So it's quite possible that the 
problem only appeared with v2.03.

> BTW, does the problem start at the same check every time?

For the same Bash binary, yes.  I tried the new binary from April the 1st 
yesterday, and the problem began to appear in a slightly different place 
(like one or two tests later).

> And if you 
> can, let me know if the problem still happens under a Win9x DOS box.

No, in the DOS box it doesn't happen.  But these are two different 
machines; I will try tomorrow to run in plain DOS on the system where I 
usually boot Windows 95 (cannot afford to reboot just any time ;-).

- Raw text -