Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!bbn!bbn.com!tgoodman
From: tgoodman@bbn.com (Todd Goodman)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: SHAR files
Keywords: MKS Toolkit Korn sh shar
Message-ID: <36509@bbn.COM>
Date: 27 Feb 89 21:32:23 GMT
References: <5827@bsu-cs.UUCP> <1131@marlin.NOSC.MIL> <430@ontenv.UUCP> <6000@sdcsvax.UCSD.Edu>
Sender: news@bbn.COM
Reply-To: Todd@ccv.bbn.com. (Todd Goodman)
Distribution: na
Organization: Bolt Beranek and Newman Inc., Cambdridge MA
Lines: 36

In article <6000@sdcsvax.UCSD.Edu> hartung@amos.ling.ucsd.edu (Jeff Hartung) writes:
>In article <430@ontenv.UUCP> soley@ontenv.UUCP (Norman S. Soley) writes:
>> [Lotsa stuff deleted]
>>DOS of course doesn't have the bourne shell (unless you have the MKS
>>toolkit or something like it) [...]
>
>Has anyone actually used the MKS Toolkit's Korn "sh" to unpack shar files?
>
> --Jeff Hartung--  	
> Disclaimer: My opinions only, etc., etc., BLAH! BLAH! BLAH!...
> Internet - hartung@amos.ling.ucsd.edu          
> UUCP - ucsd!amos.ucsd.edu!hartung

I use the MKS shell to unpack shar files.  The only difficulties (I can't even
call them problems) I've encountered are:

	1.)  Any "PATH" lines need to be removed since the shell doesn't grok
		':'s in it (due to DOSs use of ':' with drive designators).

	2.)  Some shars wrap some 'if' statements with options that the MKS
		shell doesn't grok.  This isn't a problem since it continues
		to unshar anyway (although you could write over any existing
		files with the same name, since that's where the 'if's usually
		are).

I strongly recommend the MKS Toolkit to anyone interested in gaining the
functionality of UNIX in a DOS environment.  It works great.

My only peeve is the size of the shell.  Any plans to use EMS MKS?

				Todd Goodman
				tgoodman@bbn.com

Disclaimer: I don't work for MKS, nor have I ever worked for MKS.  I'm just a
	satisfied customer who thinks that MKS supplies a great product for a
	great price.