
|
84782 packages online
|
|
 |
|
|
|
No screenshot available
|
|
UUDecode Bud v1.0
- By Carmen Rizzolo
Alright.. I'll keep these docs short. Because UUDecodeBud is
*REALLY* simple to use.
-=* Installation:
Put the UUDecodeBud.rexx file in your Rexx: directory, or
wherever you like to keep your *.rexx scripts.
You will need the rexxsupport.library in your LIBS: directory.
You will need the program UUDecode in your C: directory.
(Not inlcuded)
-=* How to use it:
Copy your fragmented UUencoded files into your RAM: disk.
These files would be named something like MyImage.01 , MyImage.02 ,
MyImage.03 , etc...
In a shell window, type the following:
RX UUDecodeBud.rexx
This is assuming your "Rexx:" assignment is correctly "pathed" in
your startup sequence. If you have any trouble, type
"RX Rexx:UUDecodeBud.rexx" instead (without the quotes, silly!).
-=* What it does:
UUDecodeBud looks in your RAM: disk for any files that end
with a ".01"... This is how fragmented uudecoded files are usually
named when grabbed from Usenet.
Once it finds the *.01 file, it will shave off any text before
and after the actual UUencoded data. This information is stored in a
*.UUE file (* being the same name as the * in your *.01 file).
Then UUDecodeBud will then look for a *.02 with the same root
name, shave and add to the *.UUE file. The process will continue until
no more consecutive *.?? files are found.
Then it will slap an "end" line to the *.UUE file and delete the
*.01, *.02, etc. files.
Next UUDecodeBud will use the 'ol UUDecode program in your C:
directory to decode the *.UUE file. The *.UUE file is then deleted.
If UUDecodeBud finds any other *.01 files (Where the * would be
an entirely different name) it will repeat the entire process over
again until all UUencoded files in your RAM: disk are processed.
Folks, it just doesn't get any simpler than this. Enjoy!
-=* CUSTOMIZING THE SCRIPT!
This should only be done by someone who knows what they are
doing.
Lines 6 and 7 can be modified to suit your system's needs.
The pathname for where UUDecodeBud looks for your *.01 files
and the pathname to your UUDecode utility can be modified here.
Use a text editor to make the changes.
WARNINGS! The value you put inside the quotes MUST end with
a : or / character. This of course specifies a pathname, so it's
logical, captain. Another warning is to remember that ANY files
that end with a ".01" will be processed and deleted in the drawer
you specify for UUPathName. I strongly reccommend you keep this
as RAM: and just throw your UUencoded files into RAM whenever you
need to decode in bulk. And if you *REALLY* know what you are doing
you can disable the delete functions in the script. Proceed with
caution, tho!
I will not be held responsible for any damage caused to data,
hard drives, computers or animals within 100 yards when using this
script.
|
Contents of util/arc/UUDBud.lha
PERMSSN UID GID PACKED SIZE RATIO CRC STAMP NAME
---------- ----------- ------- ------- ------ ---------- ------------ -------------
[generic] 1416 2981 47.5% -lh5- b046 Sep 21 1994 UUDecodeBud.ReadMe
[generic] 919 2565 35.8% -lh5- 32bf Sep 19 1994 UUDecodeBud.rexx
---------- ----------- ------- ------- ------ ---------- ------------ -------------
Total 2 files 2335 5546 42.1% Sep 22 1994
|
|
|
 |
Page generated in 0.02 seconds |
Aminet © 1992-2024 Urban
Müller and the Aminet team.
Aminet contact address: <aminet aminet net> |