Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 exptools; site whuts.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!mhuxn!mhuxr!mhuxt!houxm!whuxl!whuts!2212msr
From: 2212msr@whuts.UUCP (ROBIN)
Newsgroups: net.micro.pc
Subject: Re: HELP: How to increase ENV space?
Message-ID: <377@whuts.UUCP>
Date: Thu, 14-Nov-85 10:09:08 EST
Article-I.D.: whuts.377
Posted: Thu Nov 14 10:09:08 1985
Date-Received: Sat, 16-Nov-85 01:19:55 EST
References: <215@ur-tut.UUCP> <1869@watdcsu.UUCP>
Distribution: net
Organization: AT&T Bell Laboratories
Lines: 28

> In article <215@ur-tut.UUCP> dewa@ur-tut.UUCP (Rajiv Dewan) writes:
> If you look in the DOS 3.00 manual under the SET command, it says
> "If you have *not* loaded a program that remains resident... DOS expands
> the environment string area to hold additional strings."  Otherwise it
> only has the default 127 bytes.
> 
> There are two approaches: either do a SET in your autoexec *before* any
> resident utilities (SideKick, keyboard typeahead expanders, ramdisks, etc)
> are loaded.  This SET (or series of SETs) should increase the space to some
> high limit.  You can always get rid of these placeholders variables after
> you've loaded other stuff above them.
> 
> The other approach is to patch COMMAND.COM; there was a patch posted to
> the net a while back (sorry, I don't have it around any more) to do is,
> but it tends to be highly version-dependent.
> 

I've tried to use the SET command in DOS 3.0, from my autoexec file and it
does not appear to increase environment space.  Could you post an
example of your SET command that does work in DOS 3.0 please.  This is part
of the reason I've been using the memory patch in command.com (see sep. 
posting).

Max S. Robin  email:whuxg!2212msr
AT&T Bell Laboratories
201-386-6865

*** REPLACE THIS LINE WITH YOUR MESSAGE ***