USQB015@LIVERPOOL.AC.UK (Mark Powell) (06/13/89)
Several people on the net have had problems decoding software especially
the recently posted BIGSCRN.PRG. I too have seen these problems occurring.
The "short file" error seems only to occur when using a UNIX uudecode.
It's best to stick with an ST uudecoder. The one I use is called UUD.TTP and
is obtainable from most PD servers. It is very forgiving and will even
decode files that have a bad checksum, if you wish (just in case some network
protocol has messed with it.) It has a nice debug feature (qualifier -d) that
informs you of what it's doing (very useful.)
Anyway, the moral of the story is...
KEEP AWAY FROM UNIX UUDECODERS (IT'LL ALL END IN TEARS!)
USE A HOME GROWN ST DECODER INSTEAD
Mark Powell
ARPAnet : usqb015%ibm.liv.ac.uk@{ucl-cs.arpa,cs.ucl.ac.uk}
JANET : usqb015@uk.ac.liv.ibm
USENET : mcvax!ukc!ibm.liv.ac.uk!usqb015silvert@cs.dal.ca (Bill Silvert) (06/13/89)
In article <8906121914.AA15703@ucbvax.Berkeley.EDU> USQB015@LIVERPOOL.AC.UK (Mark Powell) writes: >Anyway, the moral of the story is... >KEEP AWAY FROM UNIX UUDECODERS (IT'LL ALL END IN TEARS!) >USE A HOME GROWN ST DECODER INSTEAD Although UUD was developed for the ST, it compiles and runs fine on Unix systems. I do all my decoding on Unix so that I only have the shorter binary files to download. The only change needed is to use printf instead of the Dumas call to a TOS-specific output routine. Easily done with ifdef's -- Bill Silvert, Habitat Ecology Division. Bedford Institute of Oceanography, Dartmouth, NS, Canada B2Y 4A2 UUCP: ...!{uunet,watmath}!dalcs!biomel!bill Internet: biomel@cs.dal.CA BITNET: bs%dalcs@dalac.BITNET
obryan@gumby.cc.wmich.edu (Mark O'Bryan) (06/13/89)
In article <8906121914.AA15703@ucbvax.Berkeley.EDU>, USQB015@LIVERPOOL.AC.UK (Mark Powell) writes: > Several people on the net have had problems decoding software especially > the recently posted BIGSCRN.PRG. I too have seen these problems occurring. > The "short file" error seems only to occur when using a UNIX uudecode. > It's best to stick with an ST uudecoder. The one I use is called UUD.TTP and Of course, in the case of BIGSCRN, you'll have to upload it back to your Unix box after uudecoding, unless you have "uncompress" on your ST already (it's in the Terminator archives at UM). -- Mark T. O'Bryan Internet: obryan@gumby.cc.wmich.edu Western Michigan University Kalamazoo, MI 49008
ljdickey@water.waterloo.edu (Lee Dickey) (06/17/89)
In article <3297@cs.dal.ca> bill@biomel.UUCP (Bill Silvert) writes: >Although UUD was developed for the ST, it compiles and runs fine on Unix >systems. I do all my decoding on Unix so that I only have the shorter >binary files to download. ... > UUCP: ...!{uunet,watmath}!dalcs!biomel!bill > Internet: biomel@cs.dal.CA BITNET: bs%dalcs@dalac.BITNET I have used Bill's port of UUD and UUE on our UNIX system in Waterloo, and much prefer it to the usual uuencode and uudecode. For one thing, I like the naming conventions and easier syntax. I also like tables that appears before the "begin" line. I suppose that someday, EBCDIC machines will get thier act together, and adopt a universal mapping to the ASCII character set. In the meantime, UUD and UUE help. -- L. J. Dickey, Faculty of Mathematics, University of Waterloo. ljdickey@water.UWaterloo.ca ljdickey@water.BITNET ljdickey@water.UUCP ..!uunet!watmath!water!ljdickey ljdickey@water.waterloo.edu