home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 2 BBS
/
02-BBS.zip
/
mag7demo.zip
/
PIPES.ZIP
/
MAGPIPE.DOC
next >
Wrap
Text File
|
1993-08-25
|
13KB
|
283 lines
Magnum Pipe Module v1.00C
(C)Copyright 1991, Gilmore Systems - All Rights Reserved
NOTICE:
------
This document covers the use of both the OS/2 pipe module (MAGPIPE2.EXE)
and the DOS pipe module (MAGPIPE.EXE) although each is a separate product
sold separately.
============
Introduction
============
Until the intdroduction of our Pipe Modules, the following methods were
available to actually "log on" to a Magnum BBS system:
- Modem
- Keyboard/Console (at the machine the BBS is running on)
- Dumb Terminal (via null modem cable)
Up until now, users of Magnum running on a LAN had the option of logging
on via "local logon modules" (LOCALBBS.EXE). However, the "local logon
modules" were merely an 'interface' to Magnum's databases. The user of
a "local logon module" was virtually running their own copy of Magnum in
order to log onto the databases, so to speak.
Although there's advantages and disadvantages to the "local logon
modules", clearly the one major disadvantage was enough to sway many
LAN environments away from "local logon modules". This disadvantage was
the fact that the "local logon module" required the workstation to have
READ/WRITE access to EVERY directory used by Magnum on the server.
Although this was not a problem for everyone, it was nonetheless a
security risk. To others, the advantage of this method was tremendous...
unlimited numbers of users could be "logged on to the 'databases'"
concurrently.
The solution to this problem has arrived with version 5.xx of Magnum: the
ability to support what's known as "Named Pipes". Most LAN software
such as IBM's Lan Server and Microsoft's Lan Manager support "Named
Pipes". This allows those with Magnum's "Pipe Module" to log onto Magnum
BBS itself - just as though they were calling in with a modem. As with a
modem, users logged on via "named pipe" have no direct access to anything
on the BBS machine (server) other than what the BBS lets them have access
to. The BBS (not the user or workstation) has access to the files and
directories, which, by many corporate standards, is the way it should be.
Up until now, there was no possible way for the user of a DOS workstation
to be able to log onto Magnum (the "localbbs.exe" program was OS/2 only).
With the advent of "named pipe" support for DOS 5 workstations, now users
on DOS workstations can also log onto Magnum!
With the advent of our "pipe modules", the old "localbbs.exe" method was
discontinued at the close of Magnum v4.00.
NOTICE: Magnum BBS (MBBS.EXE) must be running on a SERVER (or PEER SERVER)
in order for your pipe module(s) to access the BBS.
There are two pipe modules (sold separately):
MAGPIPE.EXE - For DOS Workstations on a LAN
MAGPIPE2.EXE - For OS/2 Workstations on a LAN
Each module is sold as a one-time license fee for use on your LAN. You
may make as many copies of your Pipe Module as you wish and distribute
them to as many workstations on your LAN as you wish. Each Pipe Module
has been serialized to match the serial number of your BBS. If you're
running more than one copy of Magnum on your LAN, you'll need to purchase
additional copies of the Pipe Module(s). Each Pipe Module will only work
with the Serial Number of the Magnum BBS it is encoded for.
The operation of both programs are identical. However, because of the
way DOS is designed, the following restrictions are imposed by Magnum
to the user logged on via MAGPIPE.EXE from a DOS Workstation:
- Cannot Stop Displays with <Ctrl-X> or Spacebar.
- Cannot use 'Chat' functions (not even between Sysop and User).
- Cannot execute any interactive Child (door) programs. Programs
which are non-interactive are fine, and RJE programs are fine.
There are NO restrictions for users of MAGPIPE2.EXE (for OS/2
workstations). Anything a caller via modem can do, so can a user of
the OS/2 pipe module. With the exception of the above limitations, the
same can be said of a DOS workstation user.
===========================
Installing the Pipe Modules
===========================
Once you've installed Magnum version 5.02 or higher and have it "up and
running" successfully, you will be ready to set up your BBS for use with
the pipe modules.
Currently there are 10 configurations for Magnum:
DEMO ( 1 dialup + console)
2-node ( 1 dialup + console)
3-node ( 2 dialup + console)
4-node ( 3 dialup + console)
5-node ( 4 dialup + console)
9-node ( 8 dialup + console)
13-node (12 dialup + console)
17-node (16 dialup + console)
25-node (24 dialup + console)
33-node (32 dialup + console)
ANY of your "dialup" nodes can be configured for "modem use" (as has
always been the case until now), or "pipe use". Thus, if you're using the
4-node version (3 dialup) with 3 modems, you'll have to give up one of
your modems to convert that node to "pipe" use.
To set up ANY dialup node(s) for pipe use, perform the following steps:
1) Shut down the BBS (or deactivate the node you'll be working with
with the 'x inactive' command).
2) Remake the STARTUP.x file for that node:
MAKEMBBS -x >STARTUP.x
where 'x' is the node number.
3) Bring the STARTUP.x file into your text editor and change the
DEVICENAME: parameter to:
DEVICENAME: \PIPE\MAGNODEx
where 'x' is the node number. NOTE: This is an example only, you
can give the DEVICENAME any name you wish as long as the following
is observed:
- The name MUST start with: \PIPE\
(it MUST be preceded and succeeded with the \ character).
- The part after \PIPE\ must conform to the naming conventions
of an OS/2 filename (or DOS if you want DOS workstations to
be able to log onto this node). Note that DOS observes the
8.3 naming conventions, so if you're using the 17-node node
version of Magnum, a pipe name such as \PIPE\MAGNODE12 will
not be accessible to DOS workstations because the MAGNODE12
part of the name is 9 characters in length as opposed to the
limitation of 8 under DOS.
- There must be NO imbedded spaces or blanks.
- Magnum will accept up to 30 characters for the name,
including the \PIPE\ part.
For most LAN systems, the priority class and levels should also
be changed. We've had the best experience with priority class 2,
priority level 5.
4) Save your changes and "re-compile" with:
MAKEMBBS x
where 'x' is the node number.
5) Repeat the above steps for each node you wish to convert to
a "pipe", giving each node a unique pipe name for the DEVICENAME
parameter.
6) ReStart your BBS (or ACTIVATE the nodes you deactivated).
Note that the MBBS.EXE display screen will read ACTIVE PORT for modem
nodes or ACTIVE PIPE for pipe nodes.
==============================
Logging on Via the Pipe Module
==============================
Logging on from an OS/2 workstation or a DOS workstation is identical
except for the name of the program (MAGPIPE2.EXE for OS/2 or MAGPIPE.EXE
for DOS). We'll assume OS/2 workstations in the remainder of this
document.
To log on via the pipe module, the user at the remote workstation needs
to know two things:
1) The name of the Server that Magnum is running on.
2) The name of the Pipe for the node s/he wants to log on to.
This can be paralleled to a modem user - they have to know 2 things as
well: AreaCode and Telephone Number.
Once these two things are known, the remote workstation is ready for
logon. Assuming the Sever Name is MAGSRVR and the Pipe Name is
\PIPE\MAGNODE3, the user would log on as follows:
MAGPIPE2 \\MAGSRVR\PIPE\MAGNODE3
Note the syntax of the pipe name. It's identical to that of the pipe
name specified in the DEVICENAME statement for that node, except that
it's ALWAYS preceded with two backslashes (\\) and the server name.
Just for informational purposes, you can log on to your BBS via pipe
module from the same physical machine that the BBS is running on
(no network) by eliminating the \\SERVERNAME part of the name:
(ie: MAGPIPE2 \PIPE\MAGNODE3).
In a moment, you'll see the exact same thing you'd see as though you'd
dialed up via modem. Everything from this point on is self-explanatory.
=========
File Xfer
=========
The file transfers work differently for pipes than they do for modems.
Although the interface is the same [choose a protocol, name your file(s),
and start your download/upload], the actual file transfer protocol is
a proprietary error-correcting "pipe xfer protocol" that both Magnum and
the Pipe Module understand. You'll notice that downloads also prompt for
the target filename for your workstation, and uploads prompt for the
source filename for your workstation. So even though you've chosen one
of the 6 modem protocols (xmodem, xmodem-crc, xmodem-1k, ymodem, ymodem-g
or zmodem), that's as far as it goes - those protocols are never
activated, but internally replaced with the pipe xfer protocol). You can
still choose a batch protocol such as Ymodem to download with, but you'll
be prompted for a target filename for your workstation prior to each file
sent.
======
Ctrl-C
======
Note that <Ctrl-C> is NOT trapped in these versions of the Pipe Modules.
You can accidentally (or intentionally) press <Ctrl-C> and the program
will terminate (Magnum will treat this the same way it treats a dropped
carrier and will reset the node). Be careful not to accidentally hit
<Ctrl-C> when using the ANSI message editor.
=====================================================
Simulating a "Rotary" or "Hunt Group" with Pipe Nodes
=====================================================
Many multi-node dial-up BBS's have one main telephone (modem) number
which, if busy when called, is automatically routed to the first
available free line (if available). This is known as a "Rotary" or
"Hunt Group" and is performed at the telephone company.
You can simulate this with .CMD files for OS/2 or .BAT files for DOS.
MAGPIPE2 and MAGPIPE were designed with this in mind. If a connection
is made to a node, then when the program ends (regardless of the reason
for termination), it will end with the errorlevel of 0. However, if a
connection is not made, it will end with the errorlevel of 1.
To demonstrate this via example, lets suppose you're using the 9-node
version of Magnum with Nodes 1, 2, and 3 set up as modem lines. Nodes
4 thru 8 are Pipe nodes with names of \pipe\magnode4 thru \pipe\magnode8.
Assume Magnum is running on a server known as \\magsrvr. The following
.CMD file would connect you to the first available node:
magpipe2 \\magsrvr\pipe\magnode4
if errorlevel 1 goto try5
goto done
:try5
magpipe2 \\magsrvr\pipe\magnode5
if errorlevel 1 goto try6
goto done
:try6
magpipe2 \\magsrvr\pipe\magnode6
if errorlevel 1 goto try7
goto done
:try7
magpipe2 \\magsrvr\pipe\magnode7
if errorlevel 1 goto try8
goto done
:try8
magpipe2 \\magsrvr\pipe\magnode8
if errorlevel 1 goto allbusy
goto done
:allbusy
echo All Nodes Busy or BBS is Down. Try again later...
:done
If you were to name the above .CMD file MP.CMD, then all the user would
have to do to log onto the first available node would be to run MP.
Note that the equivalent DOS .BAT file would be identical except that
the program name would be magpipe instead of magpipe2.
End.