From: "Weiqi Gao" <weiqigao AT crl DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Install bash as DOS 6.22 shell
Date: 24 Nov 1996 15:55:51 GMT
Organization: CRL Dialup Internet Access
Lines: 52
Message-ID: <01bbda1f$b76aed20$010200c0@weiqigao>
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>
NNTP-Posting-Host: crl9.crl.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Elliott Oti <e DOT oti AT stud DOT warande DOT ruu DOT nl> wrote in article
<3296BC7E DOT 6B9A AT stud DOT warande DOT ruu DOT nl>...
> Weiqi Gao wrote:
> > Well, I did experiment and came out with the following problems:
> > 1.  If I specify SHELL=D:\PATH\BASH.EXE in CONFIG.SYS,  DOS 6.22 will
> > complain about "No DPMI" and then "Your command processor is no good". 
It
> > falls back to COMMAND.COM .
> > 2.  If I fire up bash from the DOS command line, it will eat up a big
> > chunck of my DOS memory (409K -> 312K).  But everything else works
fine.
> > 3.  I don't have any DPMI server that I can (or know how to) load
before
> > the SHELL= command in CONFIG.SYS .
> > 
> 
> I don't use bash but offhand I would say it's because cwspdpmi is not
> in your path before you start bash ( config.sys is  processed before
> autoexec.bat, where the PATH variable is specified).
> Maybe copying cwsdpmi to the directory where bash resides? Or C:\ root?
> 
> If that doesn't work and you really need a dpmi host, try pmodetsr.exe,
> a TSR dpmi host based on Tran's pmode extender and ported to djgpp.
> It doesn't support virtual memory paging, so you might want to make
> sure that enough RAM is available. Load it in your config.sys before
> you start bash. Available from
ftp://x2ftp.oulu.fi/pub/msdos/programming/djgpp2.
> 
> Or else fork out some $$ and buy QEMM (with QDPMI) which does support
virtual
> memory.

I received a tip e-mail suggesting using the INSTALL command in CONFIG.SYS
to install CWSDPMI.EXE as a resident program.  It worked.  (MEM /M:CWSDPMI
shows it took up 47K of DOS memory,  I didn't see an INSTALLHIGH command,
at least not in DOS 6.2).  My problem now seems to be:
1.  bash.exe still has problem starting up as a DOS shell.  Whereas my
error yesterday was "No DPMI" and then "Your command processor is no good",
today, the message is ": cannot open." followed by "Your command processor
is no good."

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.

-- 
Weiqi Gao
weiqigao AT crl DOT com