Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version nyu B notes v1.5 12/10/84; site acf4.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!whuxl!whuxlm!akgua!sdcsvax!dcdwest!ittvax!decvax!mcnc!philabs!cmcl2!acf4!tsc2597
From: tsc2597@acf4.UUCP (Sam Chin)
Newsgroups: net.micro.pc
Subject: Solution to COMSPEC/COMMAND.COM problem
Message-ID: <1050016@acf4.UUCP>
Date: Mon, 25-Mar-85 10:48:00 EST
Article-I.D.: acf4.1050016
Posted: Mon Mar 25 10:48:00 1985
Date-Received: Fri, 29-Mar-85 01:19:48 EST
Organization: New York University
Lines: 18

<<<>>>

Thanks to all who responded to my query about the COMSPEC/COMMAND.COM
problem. The solution it turns out is to use the poorly documented SHELL
command within the CONFIG.SYS file. For example to cause MS-DOS to go to
drive A: each time to look for COMMAND.COM when it has been overlayed, use
the following sequence (add this line to your CONFIG.SYS)

SHELL = A:\COMMAND.COM A:\ /P

You can similiarly to this for drive C: etc. It is rather curious that many
people have tried various solutions to this. On dec-marlboro for instance,
there is a file called COMSPEC.ASM which searches memory for the actual
COMSPEC parameter used by MS-DOS and patches it to a new value.

                                             Sam Chin
                                             allegra!cmcl2!acf4!tsc2597
                                             tsc2597.acf4@nyu