Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site omen.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!tektronix!reed!omen!caf
From: caf@omen.UUCP (Chuck Forsberg WA7KGX)
Newsgroups: net.micro.pc
Subject: Re: msc 3.0
Message-ID: <314@omen.UUCP>
Date: Mon, 24-Mar-86 06:47:05 EST
Article-I.D.: omen.314
Posted: Mon Mar 24 06:47:05 1986
Date-Received: Wed, 26-Mar-86 03:34:55 EST
References: <670@wjvax.wjvax.UUCP>
Reply-To: caf@omen.UUCP (Chuck Forsberg WA7KGX)
Organization: Omen Technology, Portland
Lines: 21

In article <670@wjvax.wjvax.UUCP> curl@wjvax.UUCP (Jim Curl) writes:
>I recently implemented a patch to command.com in DOS 3.1 to enlarge the
>environment space (the shell command method didn't work??).  I really needed
>to do this because the paths in my environment variables had to be limited
>and the drive specifications left out because the environment was full.
>
>Upon implementing the change, I happily added paths to the INCLUDE environment
>variable for MSC 3.00 only to discover that it caused the error
>
>          Command line error: argument list for `p0.exe' too big
>
>Apparently the INCLUDE variable is included in the total 128 characters allowed
>as part of the command line.  I wasn't able to account for all 128, though.
>
>Has anyone else encountered this problem?  Is there an easy way around it?

MSC 3.0 copies the environment into the program's data space at startup to
allow getenv() to operate as it does on Unix.  A large environment will
reduce the space available for the stack and heap.  The solution is to use
an 80386 ("what the 286 SHOULD have been -Bill Gates) in 32 bit address mode,
but that requires hardware and software changes.