Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cuae2!ihnp4!inuxc!pur-ee!j.cc.purdue.edu!tim
From: tim@j.cc.purdue.edu.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: DOS enviroment size
Message-ID: <3298@j.cc.purdue.edu>
Date: Wed, 18-Feb-87 15:17:41 EST
Article-I.D.: j.3298
Posted: Wed Feb 18 15:17:41 1987
Date-Received: Fri, 20-Feb-87 01:57:44 EST
References: <2091@ncoast.UUCP>
Reply-To: tim@j.cc.purdue.edu.UUCP (Timothy Lange)
Distribution: na
Organization: PC Learning Resource Center, Purdue University
Lines: 23
Keywords: various dos vers

Here is some info about setting DOS environment variables what to do
about more environment space.  First, how do you change the amount of
space?  If you have DOS prior to 3.xx then you must modify COMMAND.COM
to change the space allocation, if you have DOS 3.[01] then you can use
the SHELL variable in your CONFIG.SYS and set the space in units of
PARAGRAPHS (16 bytes).  If you have DOS 3.2 then the units are in bytes.

I don't remember how much is set initially, but you can enter variables
and definitions for them as long as you do not run any programs,
including BAT files.  If you do, then the environment space is fixed at
127 more bytes than what you are currently using.  That is why an
AUTOEXEC.BAT file setting en vars will run out of space, but if you do
it from the keyboard you will not.  This is somewhat described in the
DOS manual.  By the way, as far as I can tell, the 127 extra bytes
talked about in the previous sentences is not true if you expand the
space using the SHELL variable in the CONFIG.SYS.
-- 
Timothy Lange
PC Learning Resource Center
Purdue University Computing Center
West Lafayette, IN  47907
317-494-1787
tim@j.cc.purdue.edu