Path: utzoo!dciem!nrcaer!scs!spl1!laidbak!att!pacbell!ames!oliveb!pyramid!prls!philabs!linus!mbunix!jcmorris
From: jcmorris@mitre-bedford.ARPA (Joseph C. Morris)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Shell command question
Message-ID: <33415@linus.UUCP>
Date: 2 Jun 88 13:31:38 GMT
Article-I.D.: linus.33415
References: <1102@cod.NOSC.MIL>
Sender: news@linus.UUCP
Reply-To: jcmorris@mbunix (Morris)
Organization: The MITRE Corporation, McLean, VA.
Lines: 14

In article <1102@cod.NOSC.MIL> desmond@cod.NOSC.MIL (J. Desmond) writes:
>I've noticed that using the shell= command in the config.sys file
>inhibits execution of the autoexec file on my Zenith 248.  Is this
>true of other clones?  Is there a way to inhibit the inhibition?
>Even shell=command.com does it.

If you are using COMMAND.COM, add the /p parameter to the SHELL line.  It's
documented in the DOS manual that /p causes the shell to be permanently
resident AND to execute AUTOEXEC.BAT at startup time.  Without /p it won't
run AUTOEXEC.

Since AUTOEXEC.BAT is processed by the command processor, if you use a
program other than COMMAND.COM you have to know how to make it run the
AUTOEXEC.BAT file.