UUE
*** UUE ***
uue filename
uue -n filename
uue filename -
If given no args, uue will tells you what version is this, and the usage.
The filename arg will be uuencoded.
the -n option will yield several files, each n lines long.
uue -500 niceprog.ttp will give:
niceprog.uaa niceprog.uab ... niceprog.uaz (!!! that would be a lot),
each (except the last) will be 500 lines long.
If given, the final - character (not valid if -n is present) will send
the output to stdout rather than a disk file.
The filenames synthetized by uue will be at most 8 chars + .uue (or .uxx)
to be in the accepted pattern for GEMDOS, MS/DOS, UN*X and TOPS20.
================================================================================
This is the v3.3 19-Apr-88 version of uud.ttp (and v3.1 of uue.ttp too)
It is named uud instead of uudecode, to avoid confusion between different
implementations of the uudecoding functionnality.
Idem for uue.
These versions have the following capabilities:
1- Missing trailing blanks are still OK. (I am on EARN/BITNET ...)
Absolutely no need for any procedure to restore 61 chars a line...
2- **Some** common internetwork transpositions are OK (e.g.
tilde instead of circonflex...but not coma instead of circonflex!)
(I am still on EARN/BITNET)
No need to edit the file to change chars...
Note: I have been told that the substitution of blanks by grave
accent is not a gateway/network bug, but a feature of some recent
UN*X uuencode, to avoid the blank compression by some protocols.
Note: It is *NOT* BITNET/EARN that damage the files, we transfert non
encoded binaries on this network, but put the blame on some brain damaged
gateways. (One of them, between Usenet and Bitnet, is really ruining
files... Totally wrong ASCII -> EBCDIC table)
3- Multi-file decoding is OK, by the 'include xxx' and 'begin part n' lines.
To allow for identififation of the original file in the parts, the file
name is now provided in the 'begin part n' line.
4- If the included files do not exist, uud.ttp will attempt to go on with the
same file, in case the multiple files have just been concatenated upon
reception.
5- There is a line sequence checking possible, allowing the detection of
missing, duplicate, corrupted lines or files. (I have sloppy fingers when
editing ...)
This feature is enabled if the first line of the 1st uuencoded file
is postfixed with a 'z', this is done automatically by the uue.ttp
companion program.
Note: a bug of the previous version is fixed.
6- A complete check of the uudecoding process is possible, by use of the
-d flag. This will tell you about all whats going on in there, plus
this is enabling a complete character by character check of the file
while decoding. This should make some subtle file corruptions pop up,
as all the uudecode do not check whats in a line before doing their job.
If this option detect an error, then the file produced will not be
correct (uud stops at the first error detected, and close the file).
7- If there is a character table present before each file, it will be used,
this table is produced by the companion uue.
The use of this table allows for some incredible recovery of files that
went through some really brain damage gateway. No sweat.
8- You can decode a single file contaning several uuencoded files, at once;
You give a complete month of INFO-ATARI16 digest, and voila all the
nice PD .prg's, no editing, no sweat. (To be true, it's been a long time
without *.prg in the digests..., but you should try it.)
9- The files are completely compatible with true UN*X uudecode/uuencode.
As long as you do not use the multiple part option of uue.ttp.
10- Compile on the ST, using MWC, on UN*X System V and on TOPS20 using cc.
En resume: get the mail file containing what you want to decode, on the
Atari ST, and apply uud.ttp on it, without any editing of any sort, including
removing mail header. (except for multiple parts, where the file names must be
correct, but no need to edit individual files).
uud v3.3 is the result of:
1. fixing a bug (nobody, but me, complained about it)
2. Having a source that compile and run successfully on
Atari ST, MS-DOS and UNIX. (Nobody got an Amiga around here)
I did the coding/compiling/testing for all 3 systems;
For UNIX, it is done using cc on a real/certified SystemVr2
For Atari, it is done using MWC 2.x.
For the PC, it is done with MSC 4.0. (An attempt with
Turbo C did not give me any thing that run correctly)
(I discovered a slight bug in MSC 4.0 too, but no big deal.)
3. Adding some requested features:
A. The -t option to allow for a full disk/directory target
specification, on which the uuencoded filename is appended.
The resulting pathname is where the result of the decoding
will be written.
B. The -s option: idem -t, but for the source file.
C. the -n option to disable the line sequence checking, in case
of uue'ed files, for any good/bad reason.
The maximum command line can thus be like:
uud -d -n -t c:^binaries^ -s d:^encoded^ file.uue
-d : enable the verbose/debugging option, telling you what
uud is doing, and sometimes even why...
-n : suppress the line sequence checking. (Totally useless option)
(The line checking is turned off automagically for files
that where not uuencoded by uue, even now for the files with
lines terminated by the 'z' char... no more fuzz about them...)
-t directory : where the output file(s) will be written, in this case
must be terminated by the directory separator character;
-s directory : where uud is going to find the file(s) to
decode.
4. This uud can decode line with 80 uuencoded char, instead of the
usual 60, the next generation of uue will take advantage of that.
5. If the file name on the command line,
is replaced by the character '-' then
standard input will be read, instead of a named file.
(For the heavy UNIX news reader...)
6. typing uud alone on a line, or invoking it without arguments
from the desktop, will give you the usage with a reminder
about the options.
Big news for Atari/PC users with only restricted disks,
you can decode now much larger files, as the uud.ttp, source
and destination files can all be on separate disks.
If given no args, uud will tells you what version is this, and the usage.
With the -d option, a whole lot of checking is done, and it is telling
you all that it is doing.
In all case if there is anything else that a perfect decoding, you will
have some message and you'll need to press any key to exit. (I anybody
tell me how to tell if we are working from the desktop, or from a shell,
I will make the pause valid only if run from the desktop. Some kind soul
with an exemple ? I suppose I have to look into the base page...)
In case of any error, the produced file is not valid.
==============================================================================
Back to Packer/Depacker