Date: Mon, 25 Nov 1996 13:03:21 +0000
From: Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>
Subject: Re: Install bash as DOS 6.22 shell
To: Weiqi Gao <weiqigao AT crl DOT com>
Cc: djgpp AT delorie DOT com
Reply-to: billc AT blackmagic DOT tait DOT co DOT nz
Message-id: <32999919.6ABD@blackmagic.tait.co.nz>
Organization: Tait Electronics NZ
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
References: <574ef8$5dk AT nexp DOT crl DOT com> <01bbd8e8$2f3c16a0$010200c0 AT weiqigao>
 <3296BC7E DOT 6B9A AT stud DOT warande DOT ruu DOT nl> <01bbda1f$b76aed20$010200c0 AT weiqigao>

Weiqi Gao wrote:
> 
> Apparently, DOS was unable to open SOMETHING while trying to run bash.exe .
>  Since I have no problem running bash.exe from the COMMAND.COM command
> line, this leads me to thinking that maybe, bash.exe is dependent on
> COMMAND.COM after all.  And the whole idea of using bash as the DOS shell
> isn't feasible?  (And Windows wouldn't start from within bash.)
> 
> Still, bash looks most impressive even when invoked as a secondary shell.

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

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

I don't realy know about the above as I haven't realy used bash yet.

Bill
-- 
Leave others their otherness.