home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
DP Tool Club 8
/
CDASC08.ISO
/
VRAC
/
THUB20.ZIP
/
USERS.DOC
< prev
Wrap
Text File
|
1993-09-16
|
4KB
|
133 lines
TriHub 1.0 User's Manual
Copyright (c) 1993 By Mark D. Goodwin
This manual is intended to provide information about the TriHub door
that users may find helpful; therefore, you are free to redistribute
this in a separate archive if you see fit.
The TriHub Door's Basic Operation
=================================
Because TriHub is designed to eliminate as much online time as
possible during a QWK network transfer, the door is very lean and
mean. When you enter the TriHub door, it will immediately prompt you
to perform a HS/Link transfer of the QWK and REP packets. If you have
a REP packet to be uploaded, simply start a HS/Link upload with the
*.REP file as the file to be uploaded. If you do not have a REP
packet to be uploaded, simply start a HS/Link download.
If the bidirectional file transfer was successful, the TriHub door
will immediately drop carrier and begin processing any incoming
message if a REP packet was uploaded.
If the bidirectional file transfer was not successful, the TriHub door
will present you with the following prompt:
Unsuccessful Transfer....Try Again (Y/n)?
If you try again, the TriHub door will once again prompt you to
perform a bidirectional transfer of the QWK and REP packets. If you
decide not to try again, the TriHub door will save your QWK packet
until the next time you attempt to download it and drop carrier.
What Happens If QWK Packets Are Being Generated?
================================================
Because the TriHub system may be busy generating QWK packets for all
TriHub accounts on another node, the TriHub door will display the
messages "TriHub is busy making QWK packets on another node!" and
"Please call back later!" and log you off. This is necessary in order
for the TriHub door to properly synchronize with the other programs
that make up the TriHub system.
Special Configuration Messages
==============================
You can send messages to the TriHub door by addressing them to TriMail
(yes, I decided to use TriMail to make it conform with TriMail) and
use one of the following commands as the subject:
=================================================================
Command Action
-----------------------------------------------------------------
ADD Adds the conference the message is in to the
user's conference queue.
ADD n Adds the conference the message is in to the
user's conference queue and sets the conference's
last message read pointer to the value specified
by "n".
DROP Drops the conference the message is in from the
user's conference queue.
RESET n Resets the last message read pointer for the
conference the message is in to the value
specified by "n".
=================================================================
The Last Message Read Pointers File
===================================
In addition to putting the user's messages in a QWK packet, TriHub
also includes a file in each QWK packet with the user's last message
read pointers. The file will have a name of QWKid.PTR, where "QWKid"
is the QWK id used by the board. For example, if the board's QWK id
is LOBSTER, the file would be called LOBSTER.PTR.
You can reset the last message read pointers for all conferences by
uploading this file through the TriHub door as a REP packet. This is
useful if for some reason your last message read pointer have become
corrupted on your hub's system.