home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
OFFLINE
/
QWKNET12.ZIP
/
QWKNET.DOC
< prev
next >
Wrap
Text File
|
1993-03-23
|
10KB
|
225 lines
==============================================================================
QWKNET v1.2 (03-22-93)
Copyright (c) 1993 by Keith Yox
The Matrix BBS, Indianapolis IN, (317) 297-8270
==============================================================================
QWKNET is a program that allows BBS systems with QWK mail capabilities to swap
public messages with one another without the hassle of complex network
configuration. It takes QWK mail packets and converts them to reply packets.
Thus the process of trading mail between two BBSs would be:
1) Package new messages on one BBS into a QWK packet.
2) Run QWKNET to convert the packet.
3) Log onto the other BBS and upload the packet to the QWK mail door.
4) Download a QWK packet from the BBS.
5) Run QWKNET to convert the packet.
6) Locally upload the reply packet to your system's mail door.
NOTE: Trading messages can be done completely by one sysop, the other
need not do anything, or even have the QWKNET program. However,
sysops may elect to alternate days or week.
The term "link" shall be used to describe the trading of messages
between two BBSs. "Linked" shall describe message bases that will
contain messages from both systems.
The previous process, of course, relies on a few preliminary tasks, but before
explaining how to set up and use QWKNET, the following background information
may prove to be helpful.
[ QWK and REP packet structure ]
The QWK file downloaded from a BBS is, as one may well know, an archive of
several files. There is a file for the actual messages, called MESSAGES.DAT,
a file with information about the BBS conferences/message areas (CONTROL.DAT),
message index files, and perhaps a couple files containing news and screens
from the BBS the mail packet was downloaded from.
QWKNET uses two of the files found in a QWK packet: the MESSAGES.DAT file and
the CONTROL.DAT file.
Inside the CONTROL.DAT file, QWKNET gets the name of the BBS the QWK file is
from, and uses an eight-character (or less) identifier that distinguishes the
BBS from others in the area- in other words, it is an eight-letter (or less)
name for the BBS.
This identifier, called the BBSID, is usually set by the BBS sysop somewhere
during configuration of the BBS' QWK mail door.
The BBSID for both BBS' in a QWKNET link must be known before setting up and
running QWKNET, and must be looked up manually- QWKNET has no facility for
finding the information. Here is how to find the BBSID:
1. Unarchive the QWK packet. If it is ZIPped, unzip it. If it is ARJed,
unarj it. Only the CONTROL.DAT file need be extracted.
2. Load the CONTROL.DAT file in a plain text (ASCII) file viewer or editor.
The BBSID is the second field (the name after the comma) of the 5th line.
In order for QWKNET to run properly, the BBSID for BOTH systems in a link must
be known.
I'm going to drop to first person here for a minute just to make things
easier. Your system's BBSID must known...and the BBSID of the system you will
be trading mail with must be known- the other system's BBSID will be known as
the "remote BBSID".
One can look further into the structure of the QWK format, but the above is
all that is necessary or helpful in the use of QWKNET.
[ The QWKNET.DAT file ]
QWKNET gets information on linking from plain text data files. One such file
is called QWKNET.DAT and must be located in the directory from which the
program is executed.
QWKNET.DAT is a standard text ASCII file. It can be created and modified by
any test file editor. The first line in the file is the registration code.
It will normally be simply three zeroes for the unregistered version, and
should be replaced by the code upon registration. The second line is the
name of (dropping to first person) *your* BBS' QWK packet name. Do not
include the extension (.QWK). The third line of this file contains your BBS'
BBSID.
[ Other QWKNET data files ]
In the same way that the QWKNET.DAT file stores information about your BBS,
there are other files that store info about the systems you will be linked
with. These files are named in the following way:
<remote QWK packet name>.DAT
The name of the QWK file that you download from the other system is called
the remote QWK packet name. For instance, if you download EMPIRE.QWK from the
BBS you will be trading messages with, the remote QWK packet name is EMPIRE.
Thus the name of the data file will be EMPIRE.DAT.
This file will also be a straight text file. It will have three different
sections: a conversion section, a remote BBSID section, and a tagline section.
Section 1: Conversion
Every BBS that has the capability of bundling messages in the QWK format
assigns a number to each conference or message base. This number we will call
the QWK conference number.
To make things more convenient for both SysOps, QWKNET can convert messages
from a conference on your BBS, to a differently numbered conference on the
other BBS. For example, on your BBS conference number 1 is called "Religion".
The other SysOp has assigned "Religion" to conference number 8. QWKNET can
be told to take messages from conference number 1 on your system and put them
in conference number 8 on the other.
The conversion section of the .DAT file tells QWKNET what conferences numbers
to convert messages to.
The first line of the conversion section (also the first line of the .DAT file)
is a single number stating how many conferences will be involved in the link.
If five conferences are being linked, this line will contain the number 5.
NOTE: If you do not wish for any conversion to take place- that is, the
conference numbers on both BBSs refer to the same subject- type a
zero (0) on this line. Then go directly to the remote BBSID section.
For every conference involved in the link, there will be a set of two numbers.
Each set of two numbers will occupy a line in the file. The first number will
be the number of a conference on your BBS, the second will be the number of
the same conference on the other system. Using the previous example with the
religion conference, the first number will be one and the second number will
be an eight, separated by a space. Again, do this for every conference that
will be linked.
Section 2: The Remote BBSID
The second section of the .DAT file consists of entering only piece of inform-
ation: the remote BBSID. On a separate line of the file, type the BBSID of the
other system.
Section 3: The Tagline
The third section will be the last line of the .DAT file. This line can be a
tagline of your choice, to be added to all *outgoing* messages. It should be
a maximum of 45 characters in the unregistered version, and 65 characters once
registered.
*** SAMPLES
The following is a few sample .DAT file.
SAMPLE #1
---------
1 <- Only one conference is being linked
2 12 <- Conference 2 will be converted to 12
dreamnet <- The remote BBSID is "dreamnet"
Testing: DreamNET <=> The Matrix <- This is the *outbound* tagline
SAMPLE #2
---------
0 <- No conversion will take place
sample <- The remote BBSID is "sample"
The Sample .DAT file <- This is the *outbound* tagline
SAMPLE #3
---------
3 <- Three conferences are being linked
2 12 <- Conference 2 will be converted to 12
5 8 <- Conference 5 will be converted to 8
10 13 <- Conference 10 will be converted to 13
skyrocket <- The remote BBSID is "skyrocket"
Blasting off to the Skyrocket <- This is the *outbound* tagline
[ USING QWKNET: COMMANDLINE PARAMETERS ]
The syntax for QWKNET is:
QWKNET 1|2 3|4 <r_qwk> [<DATdirectory>\]
Switch one: If it is "1", QWKNET will prepare outgoing messages for
upload to the other BBS. If it is "2" QWKNET will convert another
BBSs QWK to a reply packet understandable by your BBS.
Switch two: If it is "3", QWKNET will use PKZIP.EXE/PKUNZIP.EXE to
compress and decompress packets. If it is "4", QWKNET will use
ARJ.EXE to do this. Whichever is used must be located somewhere in the
PATH environment variable.
The third parameter is the remote QWK packet name (discussed
previously). Do NOT include the extension (.QWK).
The fourth parameter is optional. It allows the .DAT files (not
QWKNET.DAT) to be stored in a separate directory. Simply type the
full pathname (include the final backslash) on the commandline.
** QWKNET.DAT must be located in the directory from which the program
is executed.
WRAPPING THINGS UP....
That's about it (I think). <grin> Anyway, I hope this program helps those
sysops out there wishing to link with a small group of BBSs without having to
go through the work of creating nodelists and so forth. I'd like to hear
everyone's comments as to whether this documentation file is too terse or if
it is adequate.
This program is copyrighted and distributed freely under the shareware concept.
If this program is used for a period of time in excess of 30 days, you are
legally obligated to purchase it. The registration fee is only a meager $5
(use the form contained in REGISTER.TXT)...it lets me know that there is a
following for the program as well as for future development.
QWKNET is distributed without warranty. In no event will Keith Yox be
liable to you for damages, including any loss of profits, lost savings,
or other incidental or consequential damages arising out of your use of
or inability to use the program.
Please see REGISTER.TXT for further details.