View Full Version : Using uudecode
mscheurer
02-22-2002, 04:45 PM
Hi all,
anyone know the trick to using this one.
Stuff downloaded with MT Newswatcher won't decode, it reports a no "begin" line error. I've checked the files with pico, they all have the begin line.
Alternatively, is there an alternative to YA-Decoder in X?
StuffIt Expander isn't up tp the job...
michael
stetner
02-22-2002, 05:15 PM
There is a command line version:
% which uudecode
/usr/bin/uudecode
thatch
02-22-2002, 05:16 PM
Although I haven't used the feature in a long while, Stuffit Deluxe will decode uuencoded files and it appears to be in the X version as well.
mscheurer
02-22-2002, 05:23 PM
Originally posted by stetner
There is a command line version:
% which uudecode
/usr/bin/uudecode
That's what I was using...
mscheurer
02-22-2002, 05:24 PM
Originally posted by thatch
Although I haven't used the feature in a long while, Stuffit Deluxe will decode uuencoded files and it appears to be in the X version as well.
Expander fails to about 50% of the files...
thatch
02-22-2002, 05:49 PM
See this thread in an Aladdin Systems forum about this for some more possible info:
http://www.macfixitforums.com/php/showflat.php?Cat=&Board=Forum13&Number=287630&page=&view=&sb=&o=&vc=1
mscheurer
02-22-2002, 05:59 PM
Originally posted by thatch
See this thread in an Aladdin Systems forum about this for some more possible info:
http://www.macfixitforums.com/php/showflat.php?Cat=&Board=Forum13&Number=287630&page=&view=&sb=&o=&vc=1
Thanks for the reply, this forum being "Unix - Newcomers" I really would prefer to use the command line. I just don't know why it's giving this error.
mick
stetner
02-22-2002, 06:21 PM
Ahh, I didn't realize that is what you were doing to start with.
Could it be a mac vs unix line ending issue?
stevetech
02-22-2002, 06:47 PM
I didn't realize that Stuff-it could handle uuencoded files.. I've been using an old "classic" piece of software to decode, thank!
-Steve
mscheurer
02-22-2002, 08:05 PM
Originally posted by stetner
Ahh, I didn't realize that is what you were doing to start with.
Could it be a mac vs unix line ending issue?
Line feeds, hmmmm.
Didn't think of that.
back to the drawing board.
mick
thatch
02-22-2002, 08:17 PM
Stuffit Deluxe, not Expander, has a translate menu that has the decode for a number of different formats including uuencode/uudecode.
Also, the link I directed you to on the Aladdin Systems forum contained information about spaces in file names that caused a uudecode problem as well as a gzip poblem with uuencoded files, two possible solutions for you.
None of those suggestions are unix ways to fix your problems as you have now indicated you'd prefer but your thread started with both unix and GUI solutions and so I gave you what I found with a bit of footwork of my own for you.
mscheurer
02-22-2002, 08:23 PM
Originally posted by thatch
Stuffit Deluxe, not Expander, has a translate menu that has the decode for a number of different formats including uuencode/uudecode.
Also, the link I directed you to on the Aladdin Systems forum contained information about spaces in file names that caused a uudecode problem as well as a gzip poblem with uuencoded files, two possible solutions for you.
None of those suggestions are unix ways to fix your problems as you have now indicated you'd prefer but your thread started with both unix and GUI solutions and so I gave you what I found with a bit of footwork of my own for you.
I actually resaved using pico, making sure there wasn't any spaces, still get the same error using uudecode.
The problem with Expander is that it pops up in front when decoding, as well as that it quits and relaunches in between each decode. It also can't handle multiple files coming in, using MT Newswatcher.
thanks for you trouble though...
michael
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.