Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 exptools; site whuxlm.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!whuxlm!jph
From: jph@whuxlm.UUCP (Holtman Jim)
Newsgroups: net.micro.pc
Subject: Re: HELP: How to increase ENV space?
Message-ID: <877@whuxlm.UUCP>
Date: Wed, 20-Nov-85 08:40:49 EST
Article-I.D.: whuxlm.877
Posted: Wed Nov 20 08:40:49 1985
Date-Received: Thu, 21-Nov-85 07:21:01 EST
References: <215@ur-tut.UUCP> <1869@watdcsu.UUCP> <399@uwvax.UUCP> <1897@watdcsu.UUCP>
Distribution: net
Organization: AT&T Bell Laboratories, Whippany
Lines: 36

> 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

The way to increase the environment space is to patch COMMAND.COM
to allocate more space. In the DOS 2.0 that I have on my COMPAQ,
the following code sequence is at F66;
	MOV BX,0A
	MOV AH,48
	INT 21

This allocates 10 paragraphs (160 bytes) to the environment
space, which is too small for most of the stuff I do. WHat I did
was change the instruction to:
	MOV BX,40

which gives me 64x16 (1024 bytes) of envrionment. For other
versions of COMMAND.COM, search for a similar code sequence and
patch a 'backup' copy of COMMAND.COM and try it.