Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!super.upenn.edu!dsl.cis.upenn.edu!catone
From: catone@dsl.cis.upenn.edu.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: IBM new 'standard'
Message-ID: <1017@super.upenn.edu.upenn.edu>
Date: Tue, 7-Apr-87 18:09:20 EST
Article-I.D.: super.1017
Posted: Tue Apr  7 18:09:20 1987
Date-Received: Fri, 10-Apr-87 06:09:09 EST
References: <1010@rpics.RPI.EDU> <3320008@hpsrlc.HP.COM> <659@mind.UUCP>
Sender: root@super.upenn.edu.upenn.edu
Reply-To: catone@dsl.cis.upenn.edu.UUCP (Tony Catone)
Organization: University of Pennsylvania
Lines: 21
Keywords: Command.com, replacement shells, Console Command Processors

In article <659@mind.UUCP> romero@mind.UUCP (Antonio Romero) writes:
>In article <3320008@hpsrlc.HP.COM>, darrylo@hpsrlc.HP.COM (Darryl Okahata) writes:
>
>One of the nice things about Unix is that you get to put any shell you
>can come up with on it... if you so hate the features you're given,
>write a new one yourself... :-)
>(although wouldn't changing command.com on your PC's do same thing?)
>-Antonio Romero   princeton!mind!romero
>Disclaimer: Blame only me.

Indeed changing Command.com would do the same thing.  Unfortunately,
a great many of the "replacement" shells for DOS are merely extensions
that sit on top of Command.com and let it do all the really grungy
work.  My objection to these is that they leave you saddled with
all the Command.com internal defects, i.e. lots of things don't
work quite the way they should because Command.com won't let it
work this way.  Be wary when shopping for other shells.

					- Tony
					  catone@dsl.cis.upenn.edu
					  catone@wharton.upenn.edu