Date: Mon, 25 Nov 1996 07:14:04 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>
Cc: Weiqi Gao <weiqigao AT crl DOT com>, djgpp AT delorie DOT com
Subject: Re: Install bash as DOS 6.22 shell
In-Reply-To: <32999919.6ABD@blackmagic.tait.co.nz>
Message-Id: <Pine.SUN.3.91.961125070939.844E-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 25 Nov 1996, Bill Currie wrote:

> Sounds like the 'empty path' bug of djgpp 2.00.  Try rebuilding bash
> with 2.01 and see what happens.

No need to rebuild.  The bug was in the stub, so just `exe2coff' followed 
by `stubify' will do.

However, I don't think this is that bug, because Daysuke Aoyama (who 
ported bash) worked with the latest versions of v2.01 when he produced 
the final release.

> The only problem I can think of is how bash is going to find djgpp.env
> and know to load it. This may require a special environment file loader
> (I think Charles Sandman's tsr sample shows how to specifiy your own).

Why bother?  COMMAND.COM can be loaded HIGH with any decent memory 
manager, so you don't lose a single byte to it below 640K.  It's no 
simple feat to be able to load as a primary shell (as you have 
discovered), but on MSDOS you don't gain much by being one, so I submit 
it isn't worth the hassle.  Just load bash from COMMAND.COM and move on.