From: "A. Sinan Unur" Newsgroups: comp.os.msdos.djgpp Subject: Re: Install bash as DOS 6.22 shell Date: Wed, 27 Nov 1996 08:54:33 -0800 Organization: Cornell University Lines: 27 Sender: asu1 AT cornell DOT edu (Verified) Message-ID: <329C7249.6F04@cornell.edu> References: NNTP-Posting-Host: 128 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: grendel AT ananke DOT amu DOT edu DOT pl DJ-Gateway: from newsgroup comp.os.msdos.djgpp Mark Habersack wrote: > On 24 Nov 1996, Weiqi Gao wrote: > >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: > DOS 6.2x has the INSTALLHIGH command, only it's undocummented. install or installhigh do not help with installing bash as primary dos shell because (as you can clearly see if you step through config.sys), install and installhigh commands are executed after shell=whatever. > >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." > That's probably because bash does not comply with the shell > specifications for DOS. But there's nothing wrong in loading it as a > normal app. It will remove the transient part of command.com from the > memory anyway. And since bash won't ever return - you'll have no memory > loss. what do you mean by your last comment??? sinan.