Category : BBS Programs+Doors
Archive   : TTUFLT20.ZIP
Filename : TTUFLT.DOC

 
Output of file : TTUFLT.DOC contained in archive : TTUFLT20.ZIP
TriTel Upload Filter v. 2.0
For Tritel v2.0 or above.
written in Turbo Pascal 5.5

-by-

E.L. Morrow
Work of Art BBS (SysOp) (707)465-3193
Voice Phone (707)465-6765 9:00am-9:00pm
BBS Node 2 9:00pm-9:00am
(For Validated Members only!)

I hereby give this program to the Public Domain (yup, it's more Freeware).
Please don't do anything strange with it. I don't need the trouble.


DISCLAIMER:
It's not my fault if anything happens that you don't want to
happen when you use this program. If you use it correctly and
the Powers that Be don't decide to cultivate a random seed in
your system when you're running this util, nothing will go wrong.

Okay, now that that's taken care of, let's get down to business. The
first thing you need to know, is what exactly this utility does. Well,
simply put, it allows you to filter out files that are older than some
arbitrary date that you set, and to be able to exclude files by their
names and by general masks (i.e. you can use wildcards).

This utility, in order to work, must be placed in your UPLOAD.BAT file
before anything else. Then, you need to place a few extra statements in
the batch file. For example, this is the batch that I run for uploads:

UPLOAD.BAT
TTUFLT TTUFLT1.CFG %1

TTUFLT will return a DOS ErrorLevel of 1 if the file did not make the
cut. It also places an entry in the CALLERS.LOG telling you *why*,
and deletes the file from the hard drive. If a file makes it through
this utility (which is VERY fast) it must still pass through any other
testing you have set up through the BBS. This makes for a very secure
system that will not be receiving 'junky old files' that aren't worth
much. If you're wondering about the quotes, the reason I wrote this
util is because a friend of mine complained about his users sending
him files that were worse than useless. (Smile Verne!)

THE COMMAND LINE:

The program requires a couple of parameters. One is supplied by you,
in the form of a configuration file, the other is supplied by TriTel
at run-time when it calls UPLOAD.BAT. The configuration file takes
this form:

C:\TRITEL <--Path to TriTel Node 1 Main directory
COM2 <--Communications Port for this node
01-01-1981 <--Oldest date an upload can be
*.arc <--Lines #3-#500 are filenames
#1*.* <--(wildcards ok!) that you want
(up to 475 other masks!)
to exclude from your system.

The config file should be a simple text file. You know, the same type
of thing that everybody else makes you put together and use up space on
your directory listing. This IS required though, so just make up your
config file and stop grumbling about it!

If you're running a multi-node system, you need to have an UPLOAD.BAT
in each main directory. For instance, I call my second node C:\TRITEL2
and have two different config files. One is in C:\TRITEL (my main node
directory) and the other in the node's directory. For convenience I call
them TTUFLT1.CFG and TTUFLT2.CFG.

It is important that the parameters be placed in the order they were
shown in the example above. Put the name of the config file first (or the
entire path if the file isn't in the current directory) then the %1.
Without that %1 at the end, nothing will happen, so be sure to include
it.

Umm, let's see. You can call the config file anything you want, just
as long as you pass the name to the program when it's being run. I think
that's about it.



IMPORTANT!!!!!
This will only work with TriTel BBS v2.0 or greater!
Do *not* try to use it with older versions. If you
want to have an upload filter and are running TriTel
1.x then look for my older version of this util
called TTUFLT10.ZIP.



  3 Responses to “Category : BBS Programs+Doors
Archive   : TTUFLT20.ZIP
Filename : TTUFLT.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/