From:	mauch AT uni-duisburg DOT de (Michael Mauch)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Some things don't run under bash--(Resolution)
Date:	Wed, 02 Jul 1997 13:48:02 +0200
Organization:	Home, sweet home (via Gesamthochschule Duisburg)
Lines:	31
Message-ID:	<5pdf4r$bmj$2@news-hrz.uni-duisburg.de>
References:	<5orulb$lln AT hacgate2 DOT hac DOT com> <5pbqm4$atc AT hacgate2 DOT hac DOT com>
NNTP-Posting-Host:	ppp51.uni-duisburg.de
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

On 1 Jul 1997 20:52:20 GMT, velman AT alumni DOT caltech DOT edu (John Velman)
wrote:

> Thus, even if you set /E:2048 in your config.sys, and you use only - say - 256 
> bytes of environment, then when you invoke a new command.com with no E switch 
> it gets only 256 bytes of environment.

Yes, and to make it worse, you can't set
"COMSPEC=c:\command.com /e:2048" because most programs won't like it.

I used to patch my command.com to set a larger default environment size
(hmm, wondering why I didn't do it with Win95 - did they eventually fix
it?).

> So, when running programs that need a lot of envirnment, use a new command.com 
> with an appropriately large E:/nnnn. 
> 
> 
> Unfortunately, I haven't figured out how to get a windows PIF  to start bash 
> directly with a large environment space.
> 
> By the way, I'm running windows 3.11, dos 6.22.

You can put a line with "CommandEnvSize=2048" in the [NonWindowsApp]
section of system.ini, I think that should do the trick.

Regards...
		Michael
-- 
PGP key (0x013CB889) available at public key servers. PGP mail welcome.
PGP fingerprint: 83 D1 C4 76 0A F5 35 C6  C6 C4 C8 73 1B 45 E9 D5

- Raw text -