home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 2 BBS
/
02-BBS.zip
/
vdocs.zip
/
VC12C
< prev
next >
Wrap
Text File
|
1994-01-10
|
23KB
|
491 lines
.TOPIC:
Interfacing with WWIV-type Networks
╔══════════════════════════════════════════════════════════╗
║ CHAPTER 12 ANNEX C INTERFACING WITH WWIV-TYPE NETWORKS ║
╚══════════════════════════════════════════════════════════╝
Requirements
════════════
It should be pointed out that in order to interface VBBS
with WWIVNet and WWIVLink (or other WWIVtype networks), you
should register VBBS as soon as possible. Multinet access in
the demo version is limited to 60 days, after which time
all network interface utilities with the exception of VNet,
become inoperable. By registering, you are guaranteed that
network access will not be interrupted, so please do register
VBBS as soon as possible to avoid any inconvenience.
VWW4.EXE is the interface utility designed especially for
VBBS which carries out the net interface function for every
WWIV-type network, including WWIVNet, WWIVLink, and
ICENet. Before setting up the interface, however, you should be
aware that many subs from these networks are now being gated to
VirtualNET. Thus, it may not even be necessary for you to carry
out this interface at all if that is what you are after.
Now, if you already have VWW4.EXE in hand and want to continue
with the interface installation, be aware that you MUST also
have a WWIVnet or WWIV-type node number in order to net. You
must also set up the appropriate WWIV network files according
to instructions from your AC/GC.
WWIVNet network policy requires registration of the WWIV
network software within 60 days. After this period ,
unregistered sysops are automatically dropped from the WWIV
bbslist. The WWIV network files may be registered separately
for $20, and we urge all sysops that wish to have access to
all WWIV-type subs to register this software. Contact your
local WWIV AC for more information. As for WWIVLink sysops,
no such registration requirement currently exists and separate
network software is available.
VBBS 6.12 Documentation--12-C-2
Installation
════════════
Step 1 - Run option 7, Networks Configuration in VConfig
and choose the appropriate slot to configure.
Here you will see the following:
1. Node Number:
2. Data Directory:
3. Mode:
4. EXE Directory:
5. Dialout Init String:
U. Uninstall this Network
Step 2 - Enter your WWIVnet node number in the first field.
Step 3 - In the next field, enter the full path to the WWIVNet
DATA directory (e.g. c:\wwiv\data).
Step 4 - For Mode, select NET for WWIVNet-type networks, or
LINK for WWIVLink-type networks.
Step 5 - For the entry to the EXE (executeable) directory,
specify the complete path to where the WWIV network
executeable files are located (e.g. c:\wwiv).
Step 6 - For your Dialout Init String, leave this blank for now,
unless you are using a version of WWIV prior to WWIV
4.20. Later on when testing your WWIV connect with the
multinet engine, it may be necessary for you to include
the WWIV modem init string in this space if you fail to
connect properly. This string would be the same one
chosen from the WWIV modems.mdm file. Again, make sure
you connect properly to your WWIV server independently
from VBBS before attempting the interface here.
Step 7 - After Vconfiguring the NETWORK option above, unzip the
VWW4.exe file in your root VBBS directory and read the
technical information given in the VWW4.DOC . It should
be noted that the multinet engine in VBBS 6 is
automatic and requires no batch files, but batch files
may be used for convenience and flexibility depending
upon your setup.
Step 8 - You must now create an ANSWER.NET file based on the
information provided in the MULTINET.DOC file. This
should be placed in your VBBS DATA subdirectory.
For a VBBS that is on WWIVNet, the ANSWER.NET file
would look as follows:
!
?78=2
?32=2
For a VBBS on WWIVNet and WWIVLink, the ANSWER.NET
would contain:
VBBS 6.12 Documentation--12-C-3
!
?78=2
?32=2
?76=3
Please refer to other parts of the documentation for
more details. Just as an explanation, the ?78 above
refers to the N N N sign that WWIVNet sends as an
incoming identifier. The ?76 is an L L L that WWIVLink
uses. These are ascii characters 78 and 76,
respectively.
Step 9 - Copy NETWORKS.LST from the zip package to the VBBS NET
subdirectory.
Step 10 - If you are interfacing with both WWIVnet and WWIVLink,
you MUST maintain separate directories for NET and
LINK as mentioned previously. The same holds true for
any other WWIV-type networks you subscribe to. In each
directory make sure that all of the WWIV network files
are in their proper places. Make sure you have run
Vconfig's Network option and set the path correctly
to where the respective networkx.exe files are
located.
NOTE :
You will also have to maintain the DATA subdirectories in each
of these to create the necessary NNxxxx.net and Nxxxx.net
or NNALL.NET files needed later to subscribe and to host subs
on WWIVNet. If you are converting totally over to VBBS from WWIV
and would like to delete unnecessary/unwanted WWIV files, a list
of the required WWIV files is available from support sites. Erasure
of unwanted files, however, should be the very last step you
take in the conversion process after verifying successful
net connections. As an alternative to deletion, we suggest that
you simply zip up the unnecessary files and keep them in a safe
place in the event you need them to reconfigure something in
WWIV itself later.
Step 11- Run VConfig again and choose the Databases (option 3).
Choose Sort Databases to allow the program to set up.
Now choose the Compile Networks option. It is important
to note than whenever ANY changes are made in the
Network option or in Database entries, this must be
followed by the Sorting and Compiling options above
for the changes to take effect.
This complete the network installation procedure.
VBBS 6.12 Documentation--12-C-4
Installing Message Bases
════════════════════════
Assuming you have placed VWW4.exe in your main VBBS
directory and vconfigured the networks properly,
then installing a message base is a fairly simple process.
Follow the instructions given in the main documentation
regarding adding databases.
In the database entry for a sub, note that option G is for
Networks Configuration. Choosing this will bring up
a screen which allows you to A)dd D)elete E)dit a
network.
Pressing A) to add a network brings up a screen where you
can choose the appropriate network. For a sub carried on
WWIVNet, you would choose entry 2, for example.
Doing so will bring up another prompt as follows:
WWIVNet Network Conference Identifier:_
Simply enter the subtype number of the message base you
want, and press enter.
Exit out of the database to the main database menu and
once again, choose Sort Databases and Compile Networks.
Please note that if a message base is being gated to
VirtualNET from any other network, you have the option
of subscribing to it as a VirtualNET sub or as a sub
from another network, but NOT both. Doing so will result
in duplicate posts.
NOTE:
If you are subscribing to a Net or Link sub for the first
time, you must follow the normal procedure of requesting
the sub from the host and setting up the appropriate
NNxxx.NET files or NNALL.NET file in the proper data directory.
In addition this version of VBBS also supports WWIV's auto
request sub feature (req.exe) using the VREQ utility available.
It also accepts type 20 messages (subs.pub) using the VWWIV
utility.
Hosting a WWIV Sub
══════════════════
If you are currently hosting a WWIV message base, be assured
that the same procedure above works for hosts. Again, simply
enter the appropriate subtype when asked for the Network
Conference Identifier. Don't forget that you must maintain your
distribution list through you Nxxxx.NET file as usual. Subs
flagged for validation may be validated from the SysOp SubMenu.
VBBS 6.12 Documentation--12-C-5
Gating Subs to Other Networks
═════════════════════════════
If you are currently hosting a sub on WWIVNet or another
network, you probably will be interested in 'gating' your sub
into VirtualNET or other networks to expand your subscriber
base. This is easily accomplished by adding additional networks
to your database entry. Entering more than one network and
respective Network Conference Identifier (subtype, sub number,
echo,area,etc.) effectively 'gates' that database.
NOTE:
If you are running VBBS as a chain, we do not recommend that you
attempt gating due to the mechanics of the multinet engine. If
you wish to gate to multiple networks, we strongly recommend
that you run VBBS as your main bbs software for simplicity's
sake.
Please refer to the network portion of the documentation for
how to set up a hosted VirtualNET sub, sub numbers,etc.
Forcing a Callout
═════════════════
Please note that the VWW4 software is fully automatic, and will
callout and receive calls from your server depending upon your
main settings for Threshold and Polling in Vconfig. However, you
most likely will wish to force callouts to your server from
the WFC screen from time to time. To do so, you should Type 'N'
from the Control Panel. First, this will bring up all the
Networks you currently belong to. Select the appropriate network
followed by the appropriate system (server). This will force
the system to call a particular node.
NOTE:
WWIVNet and WWIV-type callouts are completely automated if you
are running VBBS as your main program. Be sure to set your
Threshold level and Polling frequency in Vconfig. Note that the
settings of these levels apply generically to all networks,
(e.g. the same threshold and polling configurations apply to
VirtualNET, WWIVNet, and WWIVLink packets). Setting the
threshold level to 0 effectively tells the software never to
dial out automatically, so be sure to change this. For different
calling schedules, appropriate utilities such as POLLUTIL.ZIP
and VWW4-CHK.ZIP are available to customize your setup.
VWW4 Activity Log
═════════════════
All net connections made by VWW4 are also listed in the VWW4.LOG
file which can be found in your main WWIV directory. We suggest
setting up a function key to be able to view this from the VBBS
WFC screen using the Control Panel option in Vconfig. For
example, a bat file called VWW4LOG.BAT could be created and
placed in your VBBS directory with the following command line:
CD\WWIV
VLIST VWW4.LOG
CD\VBBS
VBBS 6.12 Documentation--12-C-6
If you are interfacing with both WWIVNet and WWIVLink, then a
second batch file similar to the above would need to be created
pointing to your Link directory, and a second function key set
up in the Control Panel.
Viewing WWIV's net logs may be done in the same fashion using
the Control Panel. Simple script mods are also available to view
all pending lists from the internal Sysop Menu in VBBS.
Analyzing the BBSList
═════════════════════
VBBS creates a listing of systems belonging to various networks
that is used for routing mail. You will need to compile this
information for WWIV the first time you set up so that it may be
viewed from inside of the board. Subsequent updates are made
automatically. Note that when WWIV calls in with new bbslists,
these will be compiled normally and no special maintenance is
necessary.
To make a new indexed list of WWIV boards for use by VBBS,
please delete the existing BBSDATA.IDX file from your WWIV data
subdirectory first. Then, from the WWIV main directory type:
NETWORK3 /Y . This will produce new a new idx file.
Now, generate a new bbslist index for VBBS. Change to the root
VBBS directory where VWW4 is located and type:
VWW4 B NETWORKID=2 for the WWIVNet list, or
VWW4 B NETWORKID=3 for the WWIVLink index
You should now have succesfully created the new bbslist index
file that VBBS uses. This is located in your VBBS Data
subdirectory.
The procedure is similar for generating bbs listings for other
WWIV-type networks. Be aware of the importance of specifying the
correct Network Identifer Number in the above command line
NETWORKID= . Refer to the list of networks available in
VConfig's Network options if you need to refresh your memory on
what network the appropriate network number is.
VWW4 Command Line Switches
══════════════════════════
The Virtual MultiNet Engine (VME) handles WWIVtype networks
seamlessly. However, VWW4 functions may be called up from batch
files also, thus providing a flexible means for you to customize
your setup.
VME will run the VWW4 as needed automatically, providing the
proper NETWORKID= and PORT= parameters. Running from a command
line, however, you must specify the following three command
line parameters:
VBBS 6.12 Documentation--12-C-7
VWW4 <command letter> NETWORKID=<net #> PORT=<COM port #>
The command letter tells VWW4 what to do:
Command Letters are:
B Bundle mail for WWIV (Update WWIV packets and bbslists)
U Unbundle mail from WWIV and store in VBBS databases
D#### Dial WWIV System #, do transfer, and unbundle if
successful
A Answer WWIVnet call, do transfer, and unbundle if
successful.
The NETWORKID= parameter tells VWW4 which network to process.
WWIVnet is net #2, WWIVLink is net #3, ICEnet is net #6, and if
new WWIVnet based nets appear, they will have net numbers
assigned to them as well. Check NETWORKS.LST for the current
network list.
The PORT= parameter must be included when using VWW4 to answer,
or dial a network call. This specifies a COM port number.
An example of forcing bundling from the command line would
look like this:
VWW4 B NETWORKID=2 PORT=2
This would bundle the mail for WWIVNet for processing on comport
2.
VBBS 6.12 Documentation--12-C-8
Below, we put this altogether in a specific example:
Installation Example
════════════════════
For this example, we will be using a WWIV type network called
WeasNet. Be sure to change the directory and network names with
the directory and network names that you use.
-= Step A: WWIV Setup =-
NOTE: You will need to install one copy of WWIV for EACH WWIV
type network you will be running. The following steps can
be used for each WWIV network.
1) Make a directory under your VBBS directory called WEASNET.
i.e. C:\VBBS\WEASNET
2) Copy an uninstalled version of WWIV and the WWIV network
software (like NET33) into the WEASNET directory.
3) Run INIT to perform the initial installation. Be sure to
set up your modem type and COM port, since the WWIV network
software will use this to dial out.
4) Once finished, exit INIT and run NETWORK3. It should give
you an error that you do not have a WWIVNet node number set
up.
5) Go back into INIT. Go into 'N' for network info. Change the
name to WeasNet and change the node number to the node number
assigned to you.
Example: Network name : WeasNet
Node number : 10
Data Directory : DATA\
6) Exit INIT. Copy your WeasNet network files (BBSLIST.1,
CONNECT.0, etc) into your WeasNet DATA directory.
i.e. C:\VBBS\WEASNET\DATA
7) From the VBBS\WEASNET directory, run NETWORK3. It should
say 'net33: Analyzing WeasNet connections...'
VBBS 6.12 Documentation--12-C-9
-= Step B: VBBS Setup =-
NOTE: You will need VWW4 6.11 or later, the VBBS<->WWIV
interface, available from the VBBS Support Boards.
1) Install VWW4 in your VBBS directory.
2) Edit your NETWORKS.LST file in your VBBS\DATA directory.
Either add or change an entry to read WeasNet, and the type
(the second number) should be 2. i.e. 4,2,WeasNet
3) Run Vconfig. Go into 7. Network Configuration. Add a
network and choose WeasNet. Type in your node number. The
DATA directory will be C:\VBBS\WEASNET\DATA and the EXE
directory will be C:\VBBS\WEASNET.
Leave the dialout string blank.
4) Go into 3. Database Configuration and Compile Network Info.
5) Try running VBBS. WeasNet should now show up in your
Network Listing.
That should be it for the basic setup. There will be a few more
things to take into consideration, and we'll cover those now.
When WWIV calls WWIV for a network connect, it sends a series
of N's and spaces (i.e. 'N N N N N'), and WWIV will look for
these to tell that it's the network. VBBS will do this, but not
automatically. You need to make a file called ANSWER.NET in your
DATA directory to tell VBBS what to look for, and when it sees
it, what net to go to.
It's recommended that your WWIV network connects use a macro
that will send a unique network identifier when it calls. Let's
say that your WeasNet connect uses a macro that sends a 'W' when
it calls. You will need to make an ANSWER.NET file that looks
something like this:
>NN:
!
?87=4
The '>NN:' will tell VBBS to send a NN: at the Network Detection
Phase. The '?87' will tell VBBS that when it sees a 'W' when it's
doing the Network Detection, go and run the software for network
4 in the Network Configuration.
Make sure that the WWIV board you connect to is aware of this.
They will have to make a macro to send the 'W' to access
WeasNet, and also modify their CALLOUT.NET file to have the macro
enabled.
VBBS 6.12 Documentation--12-C-10
The macro should look something like this (M1.NET):
DEBUG ""
DIAL "%2"
WAITFOR "NN:"
SEND "W"
When the WWIV network software sees a 'NN:' it will send a 'W'
to access WeasNet.
Also, in their CALLOUT.NET file, they will need to add a %1
between their WeasNet connect and the & sign. Example:
@1 %1 & ; "KHOGKEJHKLJDHF"
The %1 tells WWIV to run the macro M1.NET. A %2 would tell it
to run M2.NET, %3 is M3.NET, etc.
Ok, now with a little luck and if everything is set up
correctly, here is what is supposed to happen: WWIV starts a
net callout and runs the macro. Once connected, it starts
looking for 'NN:'. Meanwhile, VBBS is answering the phone
and doing its Network Detection. A few seconds after VBBS sends
the '°°', it will send an 'NN:'. WWIV sees this and then sends
a 'W'. VBBS sees this and, according to the ANSWER.NET file,
goes and runs network 4.