[comp.binaries.ibm.pc.d] zoo 2.01 part 1/3 - received corrupted

wfp@dasys1.UUCP (William Phillips) (09/24/88)

It appears we received a corrupted copy of zoo201.exe - it contains a
line (near the end) of 83 characters.  Can someone mail a valid copy?
(I hope parts 2 and 3 are ok; I haven't noticed any problems, but...)

Thanks.

-- 
William Phillips                 {allegra,philabs,cmcl2}!phri\
Big Electric Cat Public Unix           {bellcore,cmcl2}!cucard!dasys1!wfp
New York, NY, USA                !!! JUST SAY "NO" TO OS/2 !!!

ked@garnet.berkeley.edu (Earl H. Kinmonth) (09/25/88)

In article <6618@dasys1.UUCP> wfp@dasys1.UUCP (William Phillips) writes:
>
>It appears we received a corrupted copy of zoo201.exe - it contains a

People continue to use old versions of uuencode that produce
spaces at the ends of lines or even blocks of largely blank
lines.  Using a sed script such as

sed -e 's/ /z/g'

to code the file (z is not in the uuencode character set) and

sed -e s/z/ /g'

to clean it up would prevent much of this sort of thing.  (Of
course, a better version of uuencode would be an even happier
solution.)