home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
DP Tool Club 15
/
CD_ASCQ_15_070894.iso
/
vrac
/
ticrb101.zip
/
TICTOSS.DOC
< prev
next >
Wrap
Text File
|
1994-05-25
|
11KB
|
331 lines
TicToss for RBBS-PC
Release 1.00
May 25, 1994
(c) Copyright 1994 WER Development, All Rights Reserved.
WER Development
500 Roselawn, Suite 4
Monroe, LA 71201
BBS: (318) 325-6608 (v.32bis/V.FC 28.8)
Fidonet: WerDev@Fidonet#1:136/1.0
Internet: WerDev@Aol.Com
Fax: (318) 387-1085
WHAT IS TICTOSS for RBBS-PC?
TicToss allows RBBS-PC sysops to participate in File Distribution
Networks (commonly referred to as FDNs or simply File Echos).
File Distribution Networks distribute software in archived form
and distribute TIC files with the archive that contains
information about the archive. TicToss processes the TIC files so
the archives are copied to the proper download path for RBBS
callers, and imports descriptions for the archives into your FMS.
TicToss for RBBS-PC Page 1
COPYRIGHT AND LICENSE
TicToss for RBBS-PC is (C) Copyright 1994 WER Development, All
Rights Reserved.
TicToss for RBBS is a fully functional shareware package. After
a reasonable evaluation period to ensure it meets your needs, you
are obligated to register the application with WER Development by
completing the ORDER.FRM and returning it to WER Development with
payment.
WARRANTY
No warranty of any kind is offered on TicToss for RBBS-PC.
Furthermore, you use this program AT YOUR OWN RISK. Under no
circumstances shall the author be liable for damage this software
may inflict upon you or your property -- either by itself or with
your help.
SNAPSHOT of KEY FEATURES OF TICTOSS for RBBS-PC
* Automatically determines the FMS description widths (40-46)
* Automatically determines the FMS order (reverse or forward)
* Elegantly wraps the description text without truncation
* Supports using TICK for Hubbing Files
* Supports Planet Connect Downlinks
* Supports ftp.fidonet.org Downlinks
LIMITATIONS OF TICTOSS for RBBS-PC
* Maximum of 150 different AreaNames/File Echos currently
* Maximum of 10 lines of extended description currently
SOFTWARE REQUIREMENTS
TicToss for RBBS-PC has been tested with RBBS-PC 17.4 and
currently requires the use of the FMS (File Management System).
Additional versions of TicToss are being developed for other BBS
packages. Currently we have versions for Spitfire, TriBBS, and
FeatherNet PRO under development.
TicToss for RBBS-PC is currently a DOS only application. TicToss
has been tested under DESQview 2.4x as well as OS/2 2.1's DOS
support.
ACKNOWLEDGMENTS
Barry Geller, author of the TICK package.
TicToss for RBBS-PC Page 2
TICTOSS.CFG INSTALLATION
TicToss compiles its TICTOSS.CFG before processing new arrived
files and their TICs. TicToss's configuration file works off the
keyword concept currently used by most Fidonet related utilities.
A sample TICTOSS.CFG should be present in our distribution archive
with much of its information duplicated from this section of our
documentation.
First, TicToss needs to know where to expect to find the TICs &
the archived files that arrive from your Fidonet Host. The
"Inbound" keyword should be set to the path where TicToss will
find the arriving TICs and Files. For BinkleyTerm users this will
be the setting you have for "NetFile", "KnownInbound", or
"ProtInbound" depending on your configuration. For FrontDoor
users this will be the FILES directory.
(We STRONGLY suggest the usage of session level passwords with
your mailer to prevent someone trying to send you files which you
do not expect. Session Level Passwords are a feature of your
mailer -- refer to your mailer's security section for help in
setting up.)
TicToss currently supports only ONE "Inbound" directory.
Example: Inbound d:\binkley\inboundp
Next, TicToss needs information about how it should process the
TIC files. The "AreaName" is the name each File Distribution
Network uses for its various File Echos. The AreaName should be
unique for each file echo. TicToss currently supports the
commonly used limitation of 8 CHARACTERS for the AreaName. There
should not be any spaces as part of the AreaName -- underline
characters are substituted. (ie RBBS UTL would be RBBS_UTL)
TicToss currently supports up to 150 AreaNames which translates
into 150 different File Echos.
Example: AreaName UTILNET
The "FilePath" is the full path where TicToss will copy the files
after their TIC information has been verified as valid &
description added to your FMS. (After copying the file, TicToss
deletes the file in your Inbound directory.)
Example: FilePath D:\FileBone\Utility
The "FMSCode" is the Category Code to assign files received in the
current AreaName. Generally most assign a unique Category Code
for each AreaName, but often the AreaNames of a FDN are not
different enough to warrant their own category code so you may
wish to use the same Category Code for an entire FDN.
TicToss for RBBS-PC Page 3
RBBS is limited to three characters for Category Codes, so
likewise you should limit your FMSCode to three characters. Be
sure that the FMSCode used here is the SAME as those used in your
RBBS setup or callers will be faced with mixed up files, and/or
not see some files at all.
Note: You may use the same FMSCodes for multiple FMS files --
this would require Subboards on RBBS's part.
Example: FMSCode UTL
The "FMSFile" is the FMS file where the descriptions will be
written. Most new RBBS sysops use the same FMS for all their
files, but others may choose to use MANY FMS files for various
reasons such as Subboards.
Example: FMSFile D:\Rbbs\Fms\OS2.Dir
The "Host" is the Fidonet address of the system which sends the
files and their associated TIC file. As far as we know the Host's
address is specified in the 3D form of Zone:Network/Node, but
there isn't any manipulation done on TicToss's part to break an
address apart -- TicToss just compares the string of characters
for a proper match when verifing TIC files. If you find yourself
on the receiving end of a different address format, just note the
format and use it instead. We would also appreciate hearing about
this variation to help alert others.
Note: The Host keyword works in conjunction with the Password
keyword.
Example: Host 1:136/2
The "Password" is the password your Host adds to the TIC file
before forwarding the TIC and its file to your system. This
password is generally agreed upon by mutual consent, but if your
Host assigned your password at random, you may have to do a bit of
detective work. Using a text file browser (such as LIST), look at
the very last line of the TIC file. The last line should begin
with "Pw" which is short for Password -- the word that follows
"Pw" is the Password for AreaName. Most sysops receive files from
only one system, but since each Password is associated with an
AreaName you may receive different file echos from different Hosts
if you so desire. Just remember to use a UNIQUE and DIFFERENT
Password for each system sending you Files.
Note: The Password keyword works in conjunction with the Host
keyword.
Example: Password LetMeIn
TicToss for RBBS-PC Page 4
TICTOSS.CFG INSTALLATION (Optional Parameters)
In addition to the above required configuration information for
your TICTOSS.CFG, there are a couple of optional keywords which
may be of use to some TicToss users.
The "Preprocess" keyword is a temporary work around for those who
need support for hubbing of files (which will be included in a
future release). Using "Preprocess" allows for adding file
descriptions to your FMS, but TicToss will NOT copy the file, NOR
will it delete the TIC file. Immediately AFTER running TicToss
you need to run TICK and let it take care of sending to your
downlinks as well as copying the file to the appropriate download
path for your BBS callers. The "Preprocess" keyword is targeted
primarily towards current TICK users who find its "support" of
RBBS lacking.
Example: Preprocess
The "DeleteUnknown" keyword is a option which is intended for
Planet Connect subscribers or those with ftp connectivity. (Note
there are no spaces between "Delete" and "Unknown".) Planet
Connect subscribers and ftp users receive ALL the areas from their
"host" no matter how few they actually process for their BBS.
Using "DeleteUnknown" causes TicToss to delete BOTH the TIC and
the file in the event it cannot find a match in your TICTOSS.CFG.
Normally, TicToss leaves the TIC file as well as the file attached
to the TIC file alone if it cannot find a matching AreaName in the
TICTOSS.CFG -- ie. TicToss assumes you have requested new areas
from your host and have not configured the areas in your
TICTOSS.CFG yet.
Example: DeleteUnknown
MULTINODE CONSIDERATIONS
TicToss does NOT include any type of file locking support at this
time. In order to ensure no loss of data, TicToss should only be
run during maintenance events in which there is both no access to
your BBS and no possibility of TicToss being run while your mailer
is still online receiving files from your host.
WER Development has invested significantly in software and
hardware to attempt to duplicate the environments used by our
clients. While this is expensive, it helps ensure reliability as
well as reducing incompatibilities. Tentative plans call for
utilizing Personal Netware (Novell) to facilitate the
implementation of file locking during the 3rd Quarter of 1994.