Path: utzoo!attcan!uunet!ginosko!uakari.primate.wisc.edu!ames!apple!oliveb!tymix!cirrusl!sun505!dhesi From: dhesi@sun505.UUCP (Rahul Dhesi) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: c.b.i.p troubles? Message-ID: <906@cirrusl.UUCP> Date: 27 Sep 89 19:20:24 GMT References: <3458@cbnewsc.ATT.COM> <6001@tekgvs.LABS.TEK.COM> Sender: news@cirrusl.UUCP Reply-To: dhesi%cirrusl@oliveb.ATC.olivetti.com (Rahul Dhesi) Organization: Cirrus Logic Inc. Lines: 22 In article <6001@tekgvs.LABS.TEK.COM> keithe@tekgvs.LABS.TEK.COM (Keith Ericson) writes: >The uuencoded portion included lowercase alphabet characters, in >descending order, tacked onto the end of each line. I guess a >"correct" uudecode would simply determine the proper number of >characters to include in the uudecoding and ignore the rest...? > >kEITHe Yes, this observation is correct. The uuencode that I was using adds a sequence number to the end of each line, presumably for consistency checking at the other end. I did not realize it was doing this. When I tested with the standard uudecode here under SunOS, it worked fine, so I didn't suspect there might be a problem. Please use a suitable shell script as Keith did, or an editor command, to delete the last character on each uuencoded line, and then extract. I'm fixing my uuencode so it won't do this again. Rahul DhesiUUCP: oliveb!cirrusl!dhesi