Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/3/84; site teddy.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!gatech!seismo!harvard!talcott!panda!teddy!jpn
From: jpn@teddy.UUCP
Newsgroups: net.micro.pc
Subject: Re: HELP: How to increase ENV space?
Message-ID: <1685@teddy.UUCP>
Date: Tue, 19-Nov-85 13:32:39 EST
Article-I.D.: teddy.1685
Posted: Tue Nov 19 13:32:39 1985
Date-Received: Thu, 21-Nov-85 07:15:43 EST
References: <215@ur-tut.UUCP> <5100105@uiucdcsb>
Reply-To: jpn@teddy.UUCP (John P. Nelson)
Organization: GenRad, Inc., Concord, Mass.
Lines: 20

>Is it possible that loading device drivers (ansi.sys, vdisk.sys, etc.)
>in your config.sys file could be keeping your environment space from 
>being expanded, even though you aren't using any programs which stay 
>resident

Actually, these are loaded BEFORE command.com, and so, are BELOW command.com
in memory.

The only reason command.com cannot expand the memory space, is because there
is something loaded into memory directly above it.  (The PC can't re-shuffle
tasks in memory).

The REAL problem, is that the environment cannot be expanded when executing
a batch script INCLUDING config.sys.   This is a real lose.  Presumably this
is because the script file is loaded into memory above command.com, but you
would think that microsoft would have implemented batch files so that the
batch file could be moved around in memory when command.com decides it needs
more environment space.

Of course it seems that batch files were an afterthought.  Fairly crude.