home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Datafile PD-CD 4
/
DATAFILE_PDCD4.iso
/
utilities
/
utilst
/
unpost
/
!Unpost
/
!Help
< prev
next >
Wrap
Text File
|
1995-10-17
|
4KB
|
132 lines
UnPost 2.1.2 RISC OS version 0.01
=================================
This is a port of John Stevens' excellent unpost for RISCOS as published in
comp.sources.
UNPOST is a "smart" uudecoder that is designed to extract binaries from
multi-part USENET or email uuencoded binaries.
See !UnPost.Docs directory for the original documentation and more info.
This is a Beta test version, with a minimal desktop front end provided by
the DDE FrontEnd module (probably only available with Acorn DeskTop C, but
I'm not sure).
I'm your first line of support if it doesn't work!
Nick Craig-Wood
ncw@axis.demon.co.uk
Desktop
-------
Double click on !UnPost. Provided you have the DDEFrontEnd module available
this will put an icon on the icon bar where you can drag files to be
uu-decoded.
Command line
------------
Use with
UnPost <file> <file2>...
Make sure the application has been Filer_Boot-ed so the UnPost alias is set
up.
Using with NewsBase
-------------------
If you are feeling cunning you can make UnPost debatch news automatically if
you use NewsBase.
1) Make sure !UnPost has been seen by the filer before debatching news
2) Look at !NewsBase.Transports.XXXX.params (where XXXX is the name of your
transport, eg KA9Q). If there is no line starting prefetch... then add one
prefetch 64 prefetch %f
3) If the file !NewsBase.Transports.XXXX.prefetch does not exist, create it
as an Obey file.
4) Add the line
UnPost -log %*0
To the start
5) Cross your fingers :-)
The interface isn't perfect and I am sure many improvements will ocurr to
you!
(I'd like to hear comments from Beta testers as to how easy they found this
process.)
Changes to original code
------------------------
Fixed up some slight Non-ANSI-isms (eg <memory.h>. This code is very
portable however.
Fixed corruption of name on issue of warning
Made uudecode check line for only the decoded length number of characters,
not the whole line (this enable it to decode SparkFS binaried with the part
number on the end. Some other uu-decoders put an incrementing character
here also)
Made it auto-try file names if the output file exists already.
Made RISCOS filename output mode
Created KA9Q configuration file
Made it notice binaries of the form Subject:*Part xx
Made it recognise +--BEGIN etc lines
Fixed tabs in config files. This is an artifact of its posting of
comp.sources I think.
If a segment has not beed identified by Subject: line or by a line in the
body left by a uu-encoder, then it will only mark the segment as having uu
data if it contains a valid begin line. This is a change from the old
method where only 1 UU line was required which happened a lot in normal text
messages.
-o <path> option added. This specifies the path for the output files. If
you don't specify a path, the output files will go into the current
directory.
To Do
-----
Loads of things probably!
Got a duplicate binary ID when decoding 2 binaries under very nearly the
same subject. Failed to decode the second one.
Doesn't deal with more than one uu file in the same message
I'm a little bit unhappy with the segment decection. The one for e-mail
messages is not very good because in could easily occurr in a news message.
Also it doesn't work with PoP mail.
Notes
-----
In my news feed I get about 1% of the feed put into the incompletes file
erroneously.
Tested with all the news I received in September 95 (35 Mbytes), decoded all
24 binaries in it and left me with 312k of inclompletes.