Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site watdcsu.UUCP
Path: utzoo!watmath!watnot!watdcsu!rsellens
From: rsellens@watdcsu.UUCP (Rick Sellens - Mech. Eng.)
Newsgroups: net.micro.pc
Subject: Re: HELP: How to increase ENV space?
Message-ID: <1897@watdcsu.UUCP>
Date: Tue, 19-Nov-85 10:58:41 EST
Article-I.D.: watdcsu.1897
Posted: Tue Nov 19 10:58:41 1985
Date-Received: Wed, 20-Nov-85 00:46:46 EST
References: <215@ur-tut.UUCP> <1869@watdcsu.UUCP> <399@uwvax.UUCP>
Reply-To: rsellens@watdcsu.UUCP (Rick Sellens - Mech. Eng.)
Distribution: net
Organization: U of Waterloo, Ontario
Lines: 20
Summary: 

In article <399@uwvax.UUCP> ericf@uwvax.UUCP (Eric Feigenson) writes:
>                                                       .........  I, too,
>suffered from the "Out of environment space" message.  The wierd thing is
>that once I got my prompt I was able to set environment variables until the
>cows came home, with *no* errors reported.  My theory is that the code that
>deals with environment *thinks* something is resident (other than command.com),
>
>				    -Eric Feigenson

I read somewhere that the memory map has the environment immediately above
DOS, with anything running under DOS immediately above that. It was pointed
out that this even includes batch files. Because of this DOS cannot grow
the environment while running a batch file. Ugly!


Rick Sellens
UUCP:     watmath!watdcsu!rsellens
CSNET:    rsellens%watdcsu@waterloo.csnet
ARPA:     rsellens%watdcsu%waterloo.csnet@csnet-relay.arpa
Physical: 372A Churchill Court, Waterloo, Ontario, Canada  N2L 6B4