home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Media Share 9
/
MEDIASHARE_09.ISO
/
bbs
/
bpq407a.zip
/
BPQ407A.EXE
/
CLUSTER.DOC
< prev
next >
Wrap
Text File
|
1992-02-09
|
6KB
|
167 lines
G8BPQ Switch to PacketCluster Interface.
Version 4.05
A facility has being developed to allow a PacketCluster to run above
my switch code. This works by emulating the DRSI support routine TNCTSR,
which provides a WA7DED Host Mode interface. It is provided as a TSR
(DEDHOST) which must be run after BPQCODE. If running with Desqview,
DEDHOST should be run in the PacketCluster window. Version 4.01 (or higher)
of BPQCODE is required. Note that my code emulates a single DSRI port -
multiple comms links may be connected to the switch, but as far as the
Cluster software is concerned, there is a single (virtual) link to the
switch, capable of supporting up to 32 sessions.
BPQCFG.TXT Parameters.
You dont need any TNCPORTs.
MAXCIRCUITS needs to be at least twice the expected number of users.
The code supports 32 streams - if you want to use them all you should have
MAXCIRCUITS=64. (Or more if you are also operating as a switch for other
users).
APPLICATIONS
Normally I would expect you to want to use the BBSCALL and ALIAS to
access the Cluster, so it should be application 1. You may wish to
use a more sensible name than BBS - APPLICATIONS=CLUSTER,,*SYS would
be reasonable. I suggest you run the Remote SYSOP facility, to allow
you to reconfigure the node without reloading. A BPQ Host version of
SYSOP (SYSOPH) is included with this release.
It is possible to run a conventional BBS on the same machine as the
PacketCluster - but only one can have the Level 4 Callsign/Alias.
DEDHOST
This program requires 5 parameters, all are decimal numbers. A 6th is
optional - if present it is a single letter:
Number of Streams.
This should match the number in the TNC definition of SYSOP.DAT
The maximum is 32.
Start Stream.
The first stream number to use. The switch supports 64 streams. Unless
you are running more than one copy of the PacketCluster, or are also
running a BBS which uses the BPQ HostMode interface, I suggest you start
at port 1.
Application.
The number allocated to the Cluster in the APPLICATIONS param of BPQCFG.TXT.
Will normally be 1.
Buffer Space.
The space to be allocated for buffering messages. You can specify up to 60
(Kilobytes). The program will allocate a minimum of 8k even if you specify
less. The space needed will depend on your traffic. I suggest you allocate as
much as you can spare. You can display the current and minimum buffer counts
using the @B and @M commands (ATTACH a stream, then enter (ESC)@B, or (ESC)@M).
Interrupt Number.
The Interrupt used to by the Cluster to communicate with DEDHOST. Will be
255, unless you need to use that for some other software.
Autotimer Flag.
Optional parameter - if set to N, suppresses AUTOTIMER messages (see below)
A typical command line would be DEDHOST 32 1 1 60 255 Y
Please note that DEDHOST reads BPQCFG.BIN to find what interrupt to use
to talk to the switch. BPQCFG.BIN must therefore be in the current directory
when DEDHOST is loaded.
Connect Scripts.
All connects must start with C SWITCH. You can then connect to the
required station as normal.
Recovery.
I've put SWITCH in the NORECOVER list - I'm not sure if it is essential,
but it wont do any harm.
AUTO-TIMERS.
As users often want to remain connected to the cluster for long periods,
it is neccessary to defeat the idle session timeout (usually 15 mins) of
the switch, and any intermediate nodes. It is possible to disable the
timeout on the switch, but this doesnt help users connecting via other nodes.
Some SYSOPS use the timer driven REPEAT.CMD to send a message to each
connected user every 10 minutes. This works, but causes extra network traffic,
and, as the message contains the BELL char, it can be rather irritating.
I have therefore added code to send a message to each connected user after
11 mins without other traffic. The message consists of two nulls, which seems
to be pretty harmless to most terminal programs. If this is not required,
it may be supressed by adding a 6th paramter of N to the DEDHOST command line.
Monitoring.
The TNC monitor facility can be controlled by the @S command. This takes
two parameters, the first sets MMASK, and the second MCOM. MMASK controls
which radio ports are monitored. This works in the same way as the TNC2
mode MMASK command. Each bit corresponds to a radio port, (bit 0 = port 1),
so to monitor say ports 1 and 3 you should set a value of 101 binary, or
5 decimal. MCOM controls whether supervisory frames are displayed, in
addition to information frames.
The @S command is entered by ATTACHing a stream, then entering:
(ESC)@SM N ((ESC) represents the ESC key)
where M is the required MMASK value, and N the MCOM setting. MCOM should
be set to 0 or 1 The MMASK value may be specified in decimal, or, if
preceeded by a $, in hex. The default setting is 65535 or $FFFF, which
monitors all ports.
To access the node from the cluster, attach a stream, then enter
(ESC)CSWITCH You can then enter node commands, use SYSOP, or
connect to other stations.
Sample startup file.
BPQCODE
SYSOPH 63 RESIDENT
DEDHOST 32 1 1 60 255
PACKCLUS
If running with Desqview, BPQCODE and SYSOPH should be run before DV.
DEDHOST should be run in the PacketCluster window.
Sample SYSOP.DAT (only the relevant bit)
SET/TNC1 DRSI 32
Remember that however many radio ports you have, the cluster only sees
one TNC port. You cant define TNC2, or use port 2 of TNC1.
John Wiseman, G8BPQ
1/1/92