Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!rochester!uhura.cc.rochester.edu!joss
From: joss@uhura.cc.rochester.edu (Josh Sirota)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Options on command.com
Message-ID: <778@ur-cc.UUCP>
Date: 3 Feb 89 16:44:43 GMT
References: <1608@mace.cc.purdue.edu> <451@dcscg1.UUCP>
Reply-To: joss@uhura.cc.rochester.edu (Josh Sirota)
Organization: Univ. of Rochester, Computing Center
Lines: 35

In article <451@dcscg1.UUCP> drezac@dcscg1.UUCP (Duane L. Rezac) writes:
>From article <1608@mace.cc.purdue.edu>, by du4@mace.cc.purdue.edu (Ted Goldstein):
>>   I recently tried using the /e: switch on command.com to increase
>> the enviroment space on my Zenith 248. This worked fine, but now my
>> autoexec doesn't execute.....
>
>I also had a problem like this. Try setting the shell variable in your 
>config.sys file like this..
>       shell = c:\command.com\ /e:300 /p

Now, I know we're all just spewing out unknown info, but a LONG time ago I
was told to use:
	shell = c:\command.com c:\ /p /e:300

The first thing is where to find the command interpreter.  The first argument
is where to find autoexec.bat (I haven't experimented ...) ... the /p does
something like tell command.com that it is the top-level process so it can
process client exits nicely, and, well, we all now know what the /e is.

A couple of things.  On my machine (which is still running MS-DOS 3.1, sigh)
the environment size argument is in PARAGRAPHS (16 bytes), not bytes.  If I
try anything as big as 300, it doesn't work.  So if this doesn't work for you,
try 32 instead of 300 or so.

On MY machine, I needed the spaces around the /p and /e ... this isn't
consistent with DOS conventions, but it didn't work without them.

Anyway, for the poster who's autoexec doesn't work, I suggest adding that
first argument.

Josh
-- 
Josh Sirota
INTERNET: joss@uhura.cc.rochester.edu        BITNET: joss_ss@uordbv.bitnet
          sirota@cs.rochester.edu            UUCP: ...!rochester!sirota