msc@cbnewsc.ATT.COM (michael.s.cross) (09/26/89)
Did anyone else have troubles uudecoding Rahul's latest postings? They seem to check out OK with brik(1), but I get an 'Illegal Character' message out of my PC based uudecode (Richard Mark's latest ... or was that Robert). My UNIX(R) uudecode doesn't complain about it? Am I the only one? Mike -- Michael S. Cross (msc@ihc.att.com) (312)-982-2018 AT&T Bell Laboratories, 5555 Touhy Ave., Skokie, IL 60077 ________________________To Live is to risk Dying______________________________
mlord@bmers58.UUCP (Mark Lord) (09/26/89)
In article <3458@cbnewsc.ATT.COM> msc@cbnewsc.ATT.COM (michael.s.cross) writes: >Did anyone else have troubles uudecoding Rahul's latest postings? They Yep. I had to uudecode and then re-uuencode them on UNIX before downloading to MS-DOS, after which my MS-DOS uu stuff could handle them. -Mark
keithe@tekgvs.LABS.TEK.COM (Keith Ericson) (09/27/89)
In article <3458@cbnewsc.ATT.COM> msc@cbnewsc.ATT.COM (michael.s.cross) writes: >Did anyone else have troubles uudecoding Rahul's latest postings? They >seem to check out OK with brik(1), but I get an 'Illegal Character' message >out of my PC based uudecode (Richard Mark's latest ... or was that Robert). >My UNIX(R) uudecode doesn't complain about it? Am I the only one? > My UNIX uudecode DID complain; I essentially sent the article through the following pipeline to extract the stuff: cat article | sed '/^[!-`]./s/[a-z]$//' | sed '/^END-/,/^BEGIN-/d'| uudecode And if you're wondering why the multiple "sed's" it's because the "sed ... | uudecode" already exists as an alias (and so does the first part, now). (Don't send mail about more efficient pipelines or sending it directly from rn, either, OK?) 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
dhesi@sun505.UUCP (Rahul Dhesi) (09/27/89)
In article <3458@cbnewsc.ATT.COM> msc@cbnewsc.ATT.COM (michael.s.cross) writes: >Did anyone else have troubles uudecoding Rahul's latest postings? They >seem to check out OK with brik(1), but I get an 'Illegal Character' message >out of my PC based uudecode (Richard Mark's latest ... or was that Robert). >My UNIX(R) uudecode doesn't complain about it? Am I the only one? Sorry, these are moving pains. I'm about to fix this. The uuencoded stuff that went out had extra characters at the end of each line. Rahul Dhesi <dhesi%cirrusl@oliveb.ATC.olivetti.com> UUCP: oliveb!cirrusl!dhesi
fredex@cg-atla.UUCP (Fred Smith) (09/27/89)
In article <6001@tekgvs.LABS.TEK.COM> keithe@tekgvs.LABS.TEK.COM (Keith Ericson) writes: > >In article <3458@cbnewsc.ATT.COM> msc@cbnewsc.ATT.COM (michael.s.cross) writes: >>Did anyone else have troubles uudecoding Rahul's latest postings? What postings are these?? We haven't received any recent postings here! Is there trouble somewhere on the net????? Fred
davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr) (09/27/89)
In article <6001@tekgvs.LABS.TEK.COM>, keithe@tekgvs.LABS.TEK.COM (Keith Ericson) writes: | My UNIX uudecode DID complain; I essentially sent the article through the | following pipeline to extract the stuff: | | cat article | sed '/^[!-`]./s/[a-z]$//' | sed '/^END-/,/^BEGIN-/d'| uudecode Do I have a special "good" version of uudecode? The one I have ignores everything before the beginning of the data and after the end, and I can just: sed '/^END-/,/^BEGIN-/d'| uudecode without problems. I thought I had a garden variety. -- bill davidsen (davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen) "The world is filled with fools. They blindly follow their so-called 'reason' in the face of the church and common sense. Any fool can see that the world is flat!" - anon
dhesi@sun505.UUCP (Rahul Dhesi) (09/28/89)
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 Dhesi <dhesi%cirrusl@oliveb.ATC.olivetti.com> UUCP: oliveb!cirrusl!dhesi