Path: utzoo!dciem!nrcaer!scs!spl1!laidbak!att!osu-cis!tut.cis.ohio-state.edu!rutgers!iuvax!bobmon From: bobmon@iuvax.cs.indiana.edu (RAMontante) Newsgroups: comp.sys.ibm.pc Subject: Re: Shell command question Message-ID: <9301@iuvax.cs.indiana.edu> Date: 2 Jun 88 00:35:17 GMT Article-I.D.: iuvax.9301 References: <1102@cod.NOSC.MIL> Reply-To: bobmon@iuvax.UUCP (RAMontante) Organization: Computer Science Dept., Indiana University Lines: 22 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. >-J M Desmond >desmond@nosc.mil I ran into this behavior in the process of upgrading (well, let's call it "converting") to v3.21 on my Z-158. Coincidentally, I added another line to my config.sys file, _after_ the 'shell=' line. I rearranged things to keep 'shell=' the very last line of the file, terminated by a CR/LF pair and with a ctrl-Z marking the file end. (The last wasn't deliberate, it's just what Sidekick does with files.) That restored the use of AUTOEXEC.BAT for me. Sheesh. Does this make sense to anyone, or is it black magic? Unix has gurus, but I'm a little leery of shamans... -Bob Montante, bobmon@iuvax.cs.indiana.edu "In this position, the skier is flying in a complete stall..."