home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
INTERNET
/
UUCODE.ZIP
/
UUCODE.DOC
< prev
next >
Wrap
Text File
|
1993-12-17
|
3KB
|
78 lines
This archive contains UUENCODE and UUDECODE for OS/2 v2.x
with long filename and wildcard support. You probably need
HPFS to run UUENCODE because target name is source name plus
string ".UUE" which is most probably invalid filename on
FAT system (also on removable media which does not support
HPFS).
These programs are free in the sense that you can use and
re-distribute them if done without any commercial fee. You
can charge the media cost, however. I don't take any
responsibility on any damage caused by usage of these programs.
Bug reports and suggestions may be sent to tke@utu.fi
See below for information of specific behaviour of this
implementation.
Common notes:
1) To see the command line syntax enter the program's
name without parameters.
2) Neiher program support file mode information. UUENCODE
saves mode as 0644 and UUDECODE discards the mode
information.
3) Currently neither program support XX encode method.
UUDECODE:
1) Normally UUDECODEr interprets everything between "begin"
and "end" line as "the UUENCODEd stuff". This UUDECODE.EXE
includes a "semi intelligent line search" algorithm to find
out which source lines are garbage and which are UUENCODEd
stuff. Therefore it is not necessary to pre-process files
extracted from, for example, news to make them suitable for
UUDECODE. The garbage in source file is sent to stdout so
it can be redirected to a file to be examined whether it
contains some intresting information.
The UUENCODEd blocks (for example news articles) must be
stored in one file and the blocks must be in correct
sequence.
2) Some UUENCODE programs add checksum in the end of each
UUENCODEd line. This UUDECODE does not use such checksums
to validate each source line.
3) Sometimes the "semi intelligent line search" algorithm fails,
for example, to think that a certain news header line is
part of the UUENCODEd stuff. In such a case you need to
manually remove the garbage (i.e. news headers between
"begin" and "end" lines) and to disable the "semi intelligent
line search" algorithm by giving switch -d.
Another method is to replace the first character of the line
which is interpreted as UUENCODEd stuff with blank.
UUENCODE:
1) Target filename is created by adding string .UUE in the end
of the source filename which means that this UUENCODE.EXE is
not generally usable for FAT systems.
Thus, FILENAME.EXT becomes FILENAME.EXT.UUE
2) Be careful when using wildcards. If you enter UUENCODE *
the UUENCODE.EXE will enter into an endless loop because
the new files produced by UUENCODE will be UUENCODEd and
the loop continues until disk is full.
/Timo Eronen, tke@utu.fi