(Continued from previous message)
 
TIC SETUP TUTORIAL
------------------
 
This is a "Quick start" guide for using the new TIC subsystem, and this is
written for those of you upgrading from 3.64 or prior. Newcomers installing
for the first time have plenty of help available via F1 at any time.
 
In this example, your uplink for fileechoes is my system (1:229/426) and
you want to handle the weekly Fidonet NODEDIFF updates to the nodelist. You
want D'Bridge to automatically "toss" and compile the nodediff on receipt.
 
Since the NodeDIFF is usually an ".ARC" file, I would go to the XMAIL
CONFIGURATION screen and make sure that the ARC program is properly set up.
 
ARC comes with D'Bridge so you don't need to download or install it. The
redesigned/revised installation in 3.7 takes care of the work setting those
programs up - so ARC should already be good to go.
 
In order to use the new TIC system, you must first configure some new paths
in the DIRECTORY PATHS screen.
 
 BAD TICS: If D'Bridge encounters a problem processing a TIC, it will move
           that along with the corrosponding file into this directory. If
           this path is not specified, TIC processing is disabled. (default)
           Suggested path is C:\DB\BADTICS and that is the default for
           new installations. (Replace "C" drive with whatever drive DB is
           installed on)
 
NEW AREAS: Specify this path where new fileecho areas will be created, if
           you choose to store received files in their own directories.
 
Define your uplinks/downlinks in the FILEECHO/TIC SETTINGS screen. Pay
attention to passwords and security access. When the TIC subsystem is used
and there are "problems", D'Bridge will log them and also create a log
file in the BAD TICS directory; explaining in detail which TIC and/or which
file caused the problem... such as invalid password, etc.
 
If your Echomail AREAFIX configuration is very simple, as in, you are
not "Hubbing" any mail so you just have one system defined, you can select
"Use FILEFIX info from AREAFIX" so it will copy the same security settings
there into this screen. Obviously you are able to change all of this later.
 
Create the area NODEDIFF in the FILEECHO/TIC AREAS editor. For the directory
for files, you may leave this set to None... we will use them but not keep a
directory of them. Be sure the area is setup good; paying attention to
things like alias-addressing (if Fidonet is not your primary network), and
security.
 
When specifying the FORWARD-TO lines, you may optionally specify READ,
WRITE or BOTH read/write access, for example:
 
                    Forward-to: 1:229/426,NW 619,NR 723,NR
 
Means 1:229/426 has Normal priority and Write/Hatch access only (any other
links should have READ access only to prevent accepting NODEDIFF's from
anyone but 426)
 
Next, we will go to the ACTIONS/MAGIC NAMES. We will use an "Action" to
automatically copy received Nodediff files to our DB directory. Select
"CopyFile". Then type in the fileecho we're copying from
("NODEDIFF") and
then the DOS path where we are copying to ("C:\DB" for example)
 
Finally, the D'Bridge scheduler controls which events are allowed to
process TIC's, just like it controls if XMAIL/Echomail is allowed. Go in
to the SCHEDULER screen, and change the settings for the UN-EVENT along
with any other mail-events you want TIC processing enabled for. Save your
changes and you're done!
 
Hopefully this will make sense for everyone and remember that you may press
F1 at any question or screen for help on configuring the settings.
 
Moving on, lets look at the screens in detail:
 
 
FILEECHO/TIC AREAS:
-------------------
 
This screen is where you specify the individual TIC "areas", very simular
to the screen that controls the Echomail areas:
 
Codeword: NODEDIFF
 
The CODEWORD is a word from 1 to 16 characters which you designate as a
mnemonic reference to an area. It could be a word like NODEDIFF for node
"diff" files or GRAPHICS for image files. CODEWORDs must be unique - the
words "NETMAIL" and "BADECHO" are predefined by the
system and may not be
used here.
 
Alert flag: D
 
If you wish to be notified (on the status line) about new files in this
area, specify a one character "flag" here. When files are received, the
mailer will show it by listing the defined "flag" character on the right
side of the bottom status line.
 
Security level: 500
 
The SECURITY LEVEL is used by the FILEFIX subsystem to allow other
systems to automatically add or delete themselves from Fileecho links.
Security levels range from 0 to 9999; if a system has a security
level of 50, it has access to all areas with a SECURITY LEVEL of 50
or less. If you don't want anyone to have access to an area, define
its level to be 9999.
 
Group/Sort: A1
 
GROUP/SORT is a two-byte field; the first character is the FILEFIX access
group; the second is the sort code for use with DBUTIL SORT TICS.
In FILEFIX, each area is assigned a GROUP code. Each system with a FILEFIX
password also has one or more group codes associated with it. Only those
systems with matching GROUP codes have access to a given area.
 
Description: Weekly Fidonet NodeDIFF files
 
This description field will be used throughout the system to describe the
conference.
 
Storage method: Directory  (Or N for None/Passthru)
 
This question is where you specify if the files will reside on your system.
If NONE is specified, the area is regarded as an area "passing through"
your system. The files are stored temporarily until the last system has
been sent the files during mail-tossing. The files are then erased later.
 
Directory path: C:\MYFILES\NODEDIFF
 
The DIRECTORY PATH is any DOS directory where D'Bridge should store the
received files for this conference. It may be a local drive and path or
a drive and path that is "mapped" from another computer on a network.
 
Conference name: NODEDIFF
 
Each fileecho area must have a unique CONFERENCE NAME. This may be the
same as or different from the CODEWORD specified above, but must reflect
the actual fileecho name or conference tag specified in the corrosponding
TIC files that arrive with the files.
 
The CONFERENCE NAME may be up to 54 characters and must not contain any
spaces; when creating a new fileecho conference, it is suggested your
CONFERENCE TAG should not exceed 16 characters if at all possible to
maintain compatibility with other systems.
 
NOTE: D'Bridge does not allow "NETMAIL" or "BADECHO" to
be used as
      conference names. Those two names are reserved by the internal mail
      processor. Any received TIC's with those names are immediately flagged
      as "bad" and will not be processed further.
 
Alias address: 1:1/130
 
If you are a member of more than one network, it might be necessary to
use an "alias" address on a fileecho area. This means that the address
put on the Address field of the outgoing TIC files will be different than
your primary address. Most systems would leave this blank.
 
NOTE: Be sure that ALIAS ADDRESSING is properly defined in BASIC CONFIG when
      using another address other than the Primary.
 
Default priority: Normal (Immediate/Crash/Normal/Hold)
 
For each conference, you specify a DEFAULT PRIORITY for forwarding of
fileecho files and TIC's. Choose either IMMEDIATE, CRASH, NORMAL or
HOLD; This default may be overridden for any specific system.
 
Forward to: 1:229/426
 
The FORWARD TO fields allow you to specify a list of systems to whom you
wish to forward files received in this conference. You may specify as many
systems as will fit on the lines available.
 
(Continued in next message)

--- D'Bridge 3.7