home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
BBS_UTIL
/
BFE3100P.ZIP
/
BFE3100P.EXE
/
DOCS
/
INSTALL.DOC
< prev
next >
Wrap
Text File
|
1994-03-11
|
9KB
|
217 lines
─────────────────────────────────────────────────────────────────────────────
▄▄▄ ▄▄▄ ▄ ▄ ▄ ▄▄ ▄▄▄ ▄▄▄ ▄ ▄▄▄ ▄▄▄ ▄ ▄▄▄ ▄
█ ▄ █▄█ ▀█▀ ▀█▀ █ █▀█ █ ▄ █▄▄ ▀█▀ ▄▄█ █ ▀ ▀█▀ █▄█ ▄▄█
█▄█ █▄▄ █▄ █▄ █ █ █ █▄█ ▄▄█ █▄ █▄█ █ █▄ █▄▄ █▄█
─────────────────────────────────────────────────────────────────────────────
System Requirements
BFE was designed for use with IBM compatible personal computer systems, with
640K minimum RAM, however, it will run in much less. It will run under most
popular BBS packages, to include RemoteAccess, Maximus, SuperBBS, QuickBBS,
GAP, PCBoard, WildCat!, WWIV, RoboBoard and others. Facilities are also in
place to provide complete dropfile customization, which provides maximum
compatibility with nearly all DOS-based BBS software packages.
BFE also requires the use of a fossil driver, such as Ray Gwinn's X00, or
David Nugent's BNU. These programs can be found on most BBS systems, since
they are necessary in running most BBS packages and doors to begin with. If
your BBS does not utilize a fossil driver, you can always enable it for BFE,
and then disable it after BFE exits.
If you would like to allow users to download certain files from BFE, free of
BBS ratios, then you will also need copies of whatever external protocols you
wish to run (i.e. DSZ, MPT, J-Modem, etc).
UPGRADING FROM 2.00.2P
If you are upgrading from the 2.00.2p release of BFE, simply run the
CONVCTL.EXE program (located in the \UTILS) directory. This program will
convert all .CTL files located in the current directory.
INSTALLATION
Create a directory to hold the BFE system. We recommend using something like
C:\BFE or C:\FD\BFE, etc. Next, copy the BFExxxx.ZIP file into the directory
and unzip it in this directory. Simply run the INSTALL.BAT file!
** Note: Your source for obtaining the BFE archive may have changed the
format of the archive to one suitable for use on their system (i.e. ZIP, LZH,
ARJ, etc). Consult your compression package documentation for more
information on using it.
Congratulations! You have now installed the world's *premier* BBS front end
system on your computer. Imagine what the neighbors must think by now!
Although the installation procedure is very straightforward, configuring BFE
can be a bit more challenging, but certainly very rewarding in the end.
─────────────────────────────────────────────────────────────────────────────
▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄ ▄ ▄▄▄ ▄▄
▄▄█ █ █ █ █ █ ▀ █ █ █▄█ █▄█ █ ▀ ▄▄█ ▀█▀ █ █ █ █▀█
█▄█ █▄█ █▄█ █ █▄█ █ █▄▄ █ █▄█ █▄ █ █▄█ █ █
─────────────────────────────────────────────────────────────────────────────
BFE COMMAND LINE ARGUMENTS
BFE accepts the following command line parameters (in any order):
-p(Port)
0,1,2,3,or 4 (COM1, COM2, etc)
-s(Serial speed)
Self explanatory! (0, 300, 1200, 19200, etc)
-c(Control File Path)
Path/filename of your main .CTL file!
-d(Dropfile override path)
-a(Auto Script)
Path/filename of a script to be used as an "auto" script.
-g(Global Configuration Options file, default is GLOBALS.CFG)
Path/filename of your Global Configuration file. This is created by
BFE/Setup and contains all global system settings.
-t(Time to next event)
The time until the next mailer event
-n(node number)
The node number of the BBS
-f
Forces ANSI in local mode
-l
Locks port with value passed in -s & -p
-r
Run BFE in "re-entry" mode. Note that when this feature is used, you do not
need to use the -c switch to specify the .CTL file (see the BFEREF.DOC file
for the section on networking with BFE).
-x
Enable's BFE's "debug" logging mode
-z
Performs a limited "sanity check" on your setup!
You can run BFE in local mode by passing "-p0 -s0" as the port and speed. Of
course, if you are using a dropfile, these values are meaningless once again,
therefore your dropfile must be configured for local use (Or blank out the
Dropfile Path option in the Global Options in BFE/Setup!).
SYSOP KEYS
There are several options available to the Sysop while the user is in the BFE
Door. These options and hotkeys differ from BBS "personality" to
"personality". BFE currently supports 3 BBS personalities (RemoteAccess
2.0x, WildCat!, and the default style). For more information on the RA and
WildCat! hotkeys, consult the documentation which accompanied the BBS software.
DEFAULT SYSOP HOTKEYS
[UP/DOWN]
Use the arrow keys to increase or decrease the amount of time which the user
has left in the door.
[Alt]-[C]
Allows the sysop to break into chat with the user at any time. [Alt]-[C]
again, or [ESC] will end chat mode. (Notice that the Want-Chat indicator will
also be turned off, if it was flashing. If you are running under Apex,
RemoteAccess or QuickBBS, paging from within the door will even cause the
Want-Chat indicator to stay lit when the user returns to the BBS)
[Alt]-[J]
Allows the sysop to shell to DOS, if enough memory is available. Simply type
EXIT to return to the door again.
[Alt]-[H]
Hang up on the user. Plain and simple!
[Alt]-[L]
This key locks the user out of the BBS. It first hangs up on the user, and
then sets their security level to 0, to prevent them from ever logging on
again. This feature may require use of the EXITINFO.BBS file, depending on
what system BFE is running under.
[Alt]-[K]
The "User Keyboard-Off" key allows the sysop to temporarily prevent the user
from typing anything on their keyboard. This has no effect on the local
keyboard, but causes BFE to ignore any keystrokes from remote.
[Alt]-[N]
The "Sysop Next" key, this function reserves the system for use by the sysop
after the user logs off, if BFE is running under an Apex or RA 1.00 or later
system.
[Alt]-[D]
"Drop to BBS" key. This function allows the sysop to exit BFE and return the
user to the BBS, without hanging up.
[F1]
Display basic user information (default)
[F9]
Display help information for sysop
[F10] Turn off the status line
MULTINODE/MULTIUSER OPERATION
BFE is quite capable of running on multinode systems, and in fact, does it
quite adeptly. Special care has been given to ensure 100% multinode
compatibility. If you happen to experience problems running BFE on a
multinode machine, please contact us if you are unable to resolve the
problem.
For smoother operations on multinode setups, ensure that the DOS SHARE.EXE
program is running!
A brief description on how BFE handles node numbers is in order. By default,
BFE will use the value of the NODE field in BFE/Setup. This value can be
overridden on the command line via the "-n" switch.
If a dropfile path has been specified in BFE/Setup, the node number has an
effect on the number of the DORINFO?.DEF file used to run BFE. (i.e. Node 1
is DORINFO1.DEF, and Node Z is DORINFOZ.DEF).
If no node number is specified in either BFE/Setup or on the BFE command
line, Node #1 will be used for compatibility, primarily on single line
systems.
DIGIBOARD COMPATIBILITY
BFE will run on systems which utilize DigiBoard communication cards. To do
so, however, you will need to pick up the latest version of the DigiBoard
Fossil Driver. As of this release, the latest version of DigiFos is v1.3,
and is available as DIGFOS13.LZH on our support BBS (FREQ's welcome).
RESERVED ERRORLEVELS
The following is a list of the reserved errorlevels used by BFE and a brief
description of each:
Errorlevel # Description
0 Critical error has occurred
1 Carrier lost, user off-line!
2 Sysop terminated the call, user off-line! :-)
3 User time used up, user STILL ON-LINE!
4 Keyboard inactivity timeout, user off-line
5 "Twit" user has logged on, user off-line
6 User botched the logon procedure, user off-line
7 User failed through Private Entry System
8 Automatic scripting feature exited normally
255 User exiting door via GOODBYE menu type