Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version nyu B notes v1.5 12/10/84; site csd2.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!mcnc!philabs!cmcl2!csd2!hummel
From: hummel@csd2.UUCP (Robert Hummel)
Newsgroups: net.micro.pc
Subject: Re: Solution to COMSPEC/COMMAND.COM problem
Message-ID: <3340001@csd2.UUCP>
Date: Tue, 26-Mar-85 11:37:00 EST
Article-I.D.: csd2.3340001
Posted: Tue Mar 26 11:37:00 1985
Date-Received: Sun, 31-Mar-85 04:13:56 EST
References: <1050016@acf4.UUCP>
Organization: New York University
Lines: 18

The solution given to the COMSPEC problem works fine EXCEPT for the
case in which you want your shell to come from RAMdisk (which saves a
lot of time if you frequently use programs that overlay COMMAND.COM).
In this case the SHELL command in CONFIG.SYS will fail because the
desired COMMAND.COM has not yet been copied into the RAMdisk when
CONFIG.SYS is executed. For this purpose, the public-domain COMSPEC
program is useful (and works, in my experience, under all versions of
PC or MSDOS >= 2.0). Also, if you (as I do) use the public-domain
"BOOT" pseudo-shell to create more environment space for DOS, you do
not have the option of using SHELL for COMMAND.COM.

Tony Movshon

uucp:	{seismo|allegra|ihnp4}!cmcl2!hipl!tony
arpa:	hipl!tony@nyu
usps:	dept of psychology / nyu / nyc 10003

(using a friend's account ... )