Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: notesfiles - hp 1.2 08/01/83; site hp-pcd.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!hplabs!hp-pcd!courtney
From: courtney@hp-pcd.UUCP (courtney)
Newsgroups: net.micro.pc
Subject: Forking a Large Environment?
Message-ID: <13600005@hpcvla.UUCP>
Date: Tue, 25-Mar-86 15:13:00 EST
Article-I.D.: hpcvla.13600005
Posted: Tue Mar 25 15:13:00 1986
Date-Received: Fri, 28-Mar-86 05:48:37 EST
Organization: Hewlett-Packard - Corvallis, OR
Lines: 19
Nf-ID: #N:hpcvla:13600005:000:768
Nf-From: hpcvla!courtney    Mar 25 12:13:00 1986

Keeping the ENVIRONMENT size discussion alive...


I am trying to do nested batch file processing by forking a COMMAND shell.
The sub-process batch file requires an "enlarged" environment space.  I have
been unable to generate a command shell with the same (enlarged) environment
space as the parent process.  I am running DOS 3.1.

I have tried to achieve this in three ways:

1) In the CONFIG.SYS file, do `SHELL=C:\COMMAND.COM /P C:\ /E:60`.
   Inside the user-invoked batch file, do `COMMAND /C FOO.BAT`.

2) The COMMAND.COM `debug` patch for V3.1 environment size enlargement.
   Then do the fork in a batch file command line `COMMAND /C FOO.BAT`.

3) A guess:  using the syntax `COMMAND /E:60 /C FOO.BAT`.

Has anybody else experienced this problem?  Got a fix?