Category : BBS Programs+Doors
Archive   : TBNET40.ZIP
Filename : TRINET.DOC

TriNet 4.0
A QWK Networking Program for the TriBBS Bulletin Board System
Copyright (c) 1991-1992 By Mark D. Goodwin


TriNet is a QWK networking program that allows your TriBBS board
to participate in one of the many QWK-based mail networks.
Essentially, you download QWK packets from your host's QWK mail
door. You then import these messages into your TriBBS message
base using TriNet. In return, you export messages out of your
TriBBS message base by having TriNet create a REP file. You then
upload these messages to the net through your host's QWK mail
door.


THE TRINET DIRECTORY
---------------------

The first step during the TriNet installation process is to
create a directory for the networking program and copy the files
TRINET.EXE and RESET.EXE into the newly created directory.


THE CONFIGURATION FILE
----------------------

Next, you must create a configuration file in your TriNet
directory. The configuration file is the key to successfully
operating TriNet. You must create a configuration file for each
network host you do transfers with. Let's suppose your host
produces QWK packets with the QWK mail door id of LOBSTER. You
would have to name your configuration file LOBSTER.CFG. The
following is a sample configuration file:

tribbs=c:\tribbs
hsysop=Mark Goodwin
htag=Test Network: The Lobster Buoy * 207-941-0805
lsysop=Denise Goodwin
ltag=Test Network: The Lobster Buoy (Test Board) * 207-555-5555
hsysop1=Mark Goodwin
htag1=TTN: The Lobster Buoy * 207-941-0805
lsysop1=Denise Goodwin
ltag1=TTN: The Lobster Buoy (Test Board) * 207-555-5555
bulletin=c:\tribbs\display\bullet1.bbs
noappend
conf=5,7
conf=4,13,1

You should note that the order of the configuration file
statements isn't significant. The following explanations provide
more detail about each of the TriNet configuration file's
statements:
















TRIBBS=directory

This is a required configuration file statement and simply tells
TriNet where your main TriBBS directory is located.


HSYSOP[n]=host sysop's name

This is a required configuration file statement and simply tells
TriNet the host sysop's name. This statement is necessary so
TriNet can translate any incoming messages from "Sysop" to the
host sysop's name. An optional network number from 0 to 9 can be
specified by "n". You should note that HSYSOP and HSYSOP0 are
synonymous.


HTAG[n]=host tag line

This is a required configuration file statement and simply tells
TriNet the host's tag line. Whenever TriNet doesn't find an
origin tag line in an incoming message, it will insert a tag line
using the host's tag line. An optional network number from 0 to
9 can be specified by "n". You should note that HTAG and HTAG0
are synonymous.


LSYSOP[n]=local sysop's name

This is a required configuration file statement and simply tells
TriNet the name of the local sysop's name. In other words, your
name. This option is necessary so TriNet can translate any
outgoing messages from "Sysop" to your name. An optional network
number from 0 to 9 can be specified by "n". You should note that
LSYSOP and LSYSOP0 are synonymous.


LTAG[n]=local tag line

This is a required configuration file statement and simply tells
TriNet the tag line for your board. Whenever TriNet doesn't find
an origin tag line in an outgoing message, it will insert a tag
line using your board's tag line. An optional network number
from 0 to 9 can be specified by "n". You should note that LTAG
and LTAG0 are synonymous.


BULLETIN=filename

This is an optional configuration file statement. If it is
specified in the configuration file, TriNet will create a
monochrome bulletin each time it imports messages.


NOAPPEND














This is an optional configuration file statement. Normally,
TriNet will append any new outgoing messages to an existing REP
packet. The NOAPPEND option instructs TriNet to delete an
existing REP packet before processing any new outgoing messages.


STRIPNULLS

This is an optional configuration file statement. Some QWK mail
doors (most notably Qmail) incorrectly puts null characters (00H)
into message blocks. Unfortunately, others (most notably
MarkMail) put garbage message blocks into QWK packets and can be
corrected for by ignoring blocks that have null characters. So
to provide for greater compatibility with QMail, you may want to
specify STRIPNULLS in your configuration file if your hub is
using QMail. This will instruct TriNet to simply strip away any
null characters it encounters in a message block.


CONF=local conference,host conference[,network]

You must specify at least one CONF statement per TriNet
configuration file. This statement tells TriNet what conference
numbers are being used on both your board and your host's board.
When you participate in a QWK network, it is more than likely
that the conference numbers on your board will differ from the
conference numbers on your host's board. Accordingly, you must
include a CONF statement for each conference you are
participating in. Let's suppose you are carrying a C programming
conference on your board as conference number 3, but the
conference is number 11 in your host's QWK packets. You would
have to include a statement like CONF=3,11 in your configuration
file for TriNet to properly handle the conference.

You may also specify a network number (0 to 9) to the conference.
If you do not specify a network number, TriNet assumes network 0.
Let's suppose in the above example, that you get two networks
from the same host and that the above conference is for network
1. Accordingly, you would use a statement like CONF=3,11,1 to
specify the proper conference and network numbers.


IMPORTING MESSAGES WITH TRINET
------------------------------

Messages can be imported with TriNet by using the following DOS
command line:

TRINET IMPORT host

Where "host" is the host's QWK mail door id. If your host's id
was LOBSTER you could import your messages with the following
statement:















TRINET IMPORT LOBSTER

NOTE: All QWK packets must be in the TriNet directory for TriNet
to properly process them.


EXPORTING MESSAGES WITH TRINET
------------------------------

Messages can be exported with TriNet by using the following DOS
command line:

TRINET EXPORT host

Where "host" is the host's QWK mail door id. If your host's id
is LOBSTER, you could export your messages with the following
statement:

TRINET EXPORT LOBSTER

NOTE: TriNet will place the REP packet in the TriNet directory.


HIGH MESSAGE POINTERS
---------------------

To be able to keep track of what messages have or haven't been
exported from your message base, TriNet maintains a file of high
message pointers. This file has a filename of host.HGH. Where
"host" is your host's QWK mail door id. Normally, TriNet
maintains this high message pointer file automatically. However,
there are times when you may need to manually intervene.

For example, you may reconfigure your message conferences. This
is no big deal; but if the changes you make move your networked
conferences around, the high message pointer file will be
incorrect. The solution to preventing such a problem is to
export all networked messages before changing your configuration
and then running RESET.EXE after you change your configuration.
RESET is run with the following command line:

RESET host

Where "host" is your host's QWK mail door id. By taking this
action, all unexported messages will be exported and all high
message pointers will be correct.

A similar situation may occur if you renumber one or more of your
networked conferences with TRIPACK. (Remember, you should only
renumber your message base conferences if they are in danger of
rolling over 999,999.) Simply export any messages, run RESET,
and then run TRIPACK.
















SUPPORT
-------

If you have any problems installing and using TriNet, you can
obtain support by calling either The Lobster Buoy, 207-941-0805,
or any other TriBBS support board.