Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!comcon!roy
From: roy@comcon.UUCP (Roy M. Silvernail)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Trouble With Arced Simtel20 Files via LISTSERV
Summary: This one works for vm1.nodak.edu
Message-ID: <146@comcon.UUCP>
Date: 9 Dec 89 13:37:17 GMT
References: <5439@ncrcae.Columbia.NCR.COM> <6297@cbnewsh.ATT.COM>
Organization: Computer Connection
Lines: 34

In article <6297@cbnewsh.ATT.COM>, mbb@cbnewsh.ATT.COM (martin.b.brilliant) writes:
> 
> I wrote a shell script to remove the "cut here" lines from uuencoded
> pieces from the binaries newsgroup. It also verifies (before I
> uudecode) that I have all the pieces, and creates a text file
> containing the header of the first piece.  I used the same script on
> the pieces from the LISTSERV server, and got errors in the archive.
> 

The parts of a SIMTEL20 archive that I get from the vm1.nodak listserv
have headers similar to the c.p.i.b postings, but not exactly the same.

I wrote the following little script which seems to do a pretty good job
for me.

Cut here--cut here--cut here

cat $* | sed '/--- End /,/--- Part/d' | uudecode 2>err

cut again--cut again--cut again

stderr is redirected to err because of the particular flavor of uuencode
that the listserv uses. When I decode at my site, I get checksum errors
on every line, but the file is intact. (the files have M at the
beginning *and* end of each line) It's easier to tail err for any bad
conclusion messages than to watch 5000 lines of errors at 2400 bps, at
least for me ;-)

(Next project... patch uudecode to handle these files correctly, I
guess...)
-- 
_R_o_y _M_. _S_i_l_v_e_r_n_a_i_l  | UUCP: uunet!comcon!roy  |  "No, I don't live in an igloo!"
[ah, but it's my account... of course I opine!]           -Sourdough's riposte
SnailMail: P.O. Box 210856, Anchorage, Alaska, 99521-0856, U.S.A., Earth, etc.