Message-Id: <200004051630.LAA22208@darwin.sfbr.org>
Date: Wed, 5 Apr 2000 11:30:24 -0500 (CDT)
From: Jeff Williams <jeffw AT darwin DOT sfbr DOT org>
Subject: Re: Question about DJGPP for DOS
To: djgpp AT delorie DOT com
Cc: d_yerrick AT hotmail DOT com, pad2369 AT iperbole DOT bologna DOT it
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: qEKfr/b7gMNLMto6t7s2kg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.4 SunOS 5.7 sun4u sparc 
Reply-To: djgpp AT delorie DOT com

-: > So you're saying it would be all right to do this:
-: >   SHELL=C:\DJGPP\bin\bash.exe

-: IIRC, one year ago someone posted all the instructions
-: to have bash.exe as a replace for command.com.

I believe it was Martin S, but he did this under DOS 6.x.

-: I tried it on my old 386 with dos 5.0 and it worked, 
-: I will look if I find those instructions and then I can 
-: send them to you if you wish.

IIRC, it's no problem with DOS 6.x, because there you can use the SET
command in config.sys.  Therefore you can SET a non-null path so that
cwsdpmi can be found when the `SHELL' command to load bash.exe is
encountered.  If there is anything in your autoexec.bat file that you
want to keep, move it to config.sys, because your autoexec.bat file
won't be processed after SHELL loads bash.exe.

Under DOS 5.0, config.sys exits with a null path (and I mean *null*;
it's not even PATH=.), so when you use SHELL to load bash.exe, the
system cannot find cwsdpmi.

I'd be *very* interested to know how you did this under DOS 5.0.