Date: Mon, 25 Nov 1996 18:30:54 +0000
From: Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>
Subject: Re: Install bash as DOS 6.22 shell
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: Weiqi Gao <weiqigao AT crl DOT com>, djgpp AT delorie DOT com
Reply-to: billc AT blackmagic DOT tait DOT co DOT nz
Message-id: <3299E5DE.78B4@blackmagic.tait.co.nz>
Organization: Tait Electronics NZ
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
References: <Pine DOT SUN DOT 3 DOT 91 DOT 961125070939 DOT 844E-100000 AT is>

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

Doh! forgot about that :)'

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

One reason for bothering is so you NEVER unintentionally run a dos
command.

As for overcoming the various problems, what about a custom stub?  It
could
accept parameters for the locations of the dpmi server and any initial 
environment variables that should be set BEFORE the coff image is
executed.

Yes, this is still nontrivial, but for those that realy want to get rid
of 
command.com, it could be worth it.

Bill
-- 
Leave others their otherness.