UUDO v1.1  (c) 1993, Ryan Kim.  -  Multi-file/Multi-part uudecoder


DESCRIPTION:

- UUDO is an uudecoder for DOS for generating binary files from
  uuencoded files that may be split into many parts.
- The only requirement is that, for multi-part files, each uuencoded part must
  be in its own file and has a "Subject: ..." line indicating the part number.
  (Assuming the uuencoded files are coming from the Usenet:
  This can be done easily by issuing "s" command without filename inside rn.
  Make sure to start rn with -N and -/ options.)
- UUDO supports the subject line with part numbers in the format of "##/##" or
  "## of ##", where ## is the part number, and the second ## is
  the total part number.
  If none of these is found, it is assumed that the file contains the entire
  uuencoded text for a binary.
- If any error is found in generating a binary file, UUDO will copy all the
  uuencoded part files for that binary to the error directory which must be
  specified in the command line.
- A report is generated describing which uuencoded texts were decoded into
  which binary files.


DISCLAIMER:

- This is a FREEWARE.  Although the program is copyrighted by me, Ryan Kim,
  you're allowed to use, copy, and distribute this program for FREE
  as long as nothing is modified in any way, this document is
  always present with the program, and you're not gaining any profit
  with this program.
- There is no warranty whatsoever.  Use it at your own risk!

- Please read the section marked "FINAL NOTES" at the end of this document
  for a small (non-obligatory) favour I ask for the users of UUDO program.


HOW TO:

Typing UUDO by itself gives the following help screen:

UUDO v1.1  (c) 1993, Ryan Kim.  -  Multi-file/Multi-part uudecoder

Usage:  UUDO [/n] [/k] [/r1] [/r2] input_files error_directory
             where /n:   No report file "UUDO.REP" generated
                   /k:   Keep incomplete binary files
                   /r1:  Relaxed format-checking level 1
                   /r2:  Relaxed format-checking level 2 (See Doc)

1. If you're getting the uuencoded files from the Usenet:
   In 'rn', save each article in different files by doing, say, "1650-1759 s".
   This will save different articles in files 1650, 1651, 1652, ..., 1759,
   provided that you turned on -N and -/ switches in 'rn' command line.
2. Move these files to a DOS machine.  This may be either in text or
   binary mode file transfer.
3. Assuming you have a path to UUDO.EXE, or UUDO is available somewhere,
   and all the above files are in the current directory:
   Create a subdirectory called ERROR, from the current directory.
4. Type "UUDO *.* error"

Now, UUDO will extract all the binary files to the current directory.
Any files that cannot be decoded properly will be copied to
the "error" directory, you just created.
UUDO will also create a file called "UUDO.REP" in the current directory
and report which files are decoded to which.  This is very handy way of
checking where the binaries came from and how UUDO read the subject line.

UUDO has a few options to accomodate some uuencoded files that may contain
errors or may not use the standard uuencode format:

/k option:   By default, UUDO deletes any binary files that were not decoded
             properly to the end.  If this option is specified, UUDO will keep
             all the binary files with error, even though they're incomplete.
/r1 option:  With this option, UUDO will not do most of the uuencode format
             checking.  This is useful when the uuencoded file uses some
             non-standard uuencode format and UUDO stops at certain line.
             NOTE:  /r1 and /r2 options may generate incorrect binary file
                    because many format checkings are not done.  Use these
                    options only on files that UUDO has trouble decoding.
/r2 option:  This option may be used when /r1 option generates the correct
             binary file except the last few bytes.  Use this after you tried
             /r1 option.  You may have to put all the parts together manually.
If all these do not work, the uuencoded file probably contains
some unrecoverable errors.  If you are _really_ desperate, you may try
to concatenate all uuencoded parts together in a file (deleting all
non-uuencoded texts) and use /r2 option, although, it may still not work.

UUDO uses two file names (which may be different) to indicate the name of
the binary file.  The first is the name UUDO found in the subject line
and the second is the name UUDO found in "begin xxx zzzz" line of
the uuencoded text.  UUDO will use the first name until the real name
(the second name) is found.

You can press ESC key at any time to stop UUDO.  There will be slight delay
while UUDO finishes off its current operation.
 

HISTORY:

v1.0     Initial Release to a few testers for some first-impressions.
v1.1     The first general public release of UUDO!
         Minor changes in command-line options and the document.


FINAL NOTES:

I wrote this program for my personal use (to save my precious time from
looking through files, trying to fit pieces together, and decoding),
and I hope you will find it useful also.

I'd like very much to know if you're using this program since this is,
I believe, my first program that could be used widely around the world.
I would appreciate it very much if you could drop me a line and tell me
where you're from, and where you got this program (i.e. Usenet group name,
FTP site name, BBS name, etc).  This is for some statistics for my personal
use.  Don't worry, I won't sell your names to the junk-mail companies
and NO SALESPERSON WILL CALL YOU.    :-)
Thanks!

I can be reached by e-mail at rkim@eecg.toronto.edu


                                                       Ryan
                                          from Scarborough, Ontario, CANADA