Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mailrus!csd4.milw.wisc.edu!astieber
From: astieber@csd4.milw.wisc.edu (Anthony J Stieber)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: More silence in comp.binaries.ibm.pc
Message-ID: <3665@csd4.milw.wisc.edu>
Date: 3 Aug 89 03:41:16 GMT
References: <8472@bsu-cs.bsu.edu> <2487@astroatc.UUCP> <8478@bsu-cs.bsu.edu> <2501@astroatc.UUCP>
Sender: news@csd4.milw.wisc.edu
Reply-To: astieber@csd4.milw.wisc.edu (Anthony J Stieber)
Organization: University of Wisconsin-Milwaukee
Lines: 45


I really feel stupid.  For some time now I have had many problems with
c.b.i.p, often more than half of the files I got were corrupted.  It seems
these combine scripts are used by everyone, so I thought I try it out.
The "corrupted" files I still had around, now are fine!  When I first
started doing this I just used uudecode on the file, it didn't
complain about the headers and footers at all.

Oh well, here are some scripts that I use to make things easier.
(these things work under BSD 4.3-tahoe, your mileage may vary)

#! /bin/sh
# comp.binaries.ibm.pc combine script, I use this now.
cat $* | sed '/^END/,/^BEGIN/d' | uudecode


#! /bin/csh
#uudo
combine $1		<-- just added this now
uuh $1
zoo -test `basename $1 .uue`.zoo
ls  `basename $1 .uue`.*
rm -i $1

#! /bin/csh
#uuh, get the uucode header
sed /\^begin/q < $1 > `basename $1 .uue`.hdr


These scripts enable the user to just type: uudo filename.uue

The file will be decoded, a header file will be created, then the zoo
archive is tested, the relevant files are listed, then the user is
asked if the uucode file should be deleted.

The header files (*.hdr) are everything in a uucode file right up to
the "begin xxx filename.zoo" line.  I keep this around so that I know
what "hg64g78.zoo" is in six months.  The mini-reviews that Rahul
makes are very useful (Thanks Rahul!).
--
Tony Stieber	 astieber@csd4.milw.wisc.edu	 att!uwmcsd1!uwmcsd4!astieber
"The hardware business is not like the software business. In software,
you get immediate feedback. In hardware, there is a fairly long,
unkind period when you have no idea if this pile of junk is going to
work!" -- Chuck Thacker, Alto developer.