Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!nic.csu.net!beach.csulb.edu!csus.edu!wuarchive!zaphod.mps.ohio-state.edu!caen!hellgate.utah.edu!fcom.cc.utah.edu!npd.novell.com!newsun!tporczyk
From: tporczyk@na.excelan.com (Tony Porczyk)
Newsgroups: comp.os.msdos.misc
Subject: Re: cloning COMSPEC?
Keywords: look elsewhere for command.com
Message-ID: <1991Mar1.030744.22045@novell.com>
Date: 6 Mar 91 02:18:28 GMT
Sender: news@novell.com (
Lines: 18

The News Manager)
Nntp-Posting-Host: na
Reply-To: tporczyk@na.excelan.com (Tony Porczyk)
Organization: Standard Disclaimer
References: <Feb.19.20.13.10.1991.10914@remus.rutgers.edu> <valley.667524975@gsbsun> <27155@uflorida.cis.ufl.EDU>
Distribution: na
Date: Fri, 1 Mar 1991 03:07:44 GMT

In article <27155@uflorida.cis.ufl.EDU> (Brian K. W. Hook) writes:
>|>cousens@remus.rutgers.edu (Scott Cousens) writes:
>|>>I am trying to create a startup disk for use on a network with a
>|>>I have set COMSPEC=L:\COMMAND.COM but this does not always work.
>SHELL=L:\COMMAND.COM

Add /e:<size of the environment> /p
The first is useful if you want your environment to have any reasonable
size, and since you're on the network, you probably will want that. The
second makes the command.com shell permanent.

Tony