rOverBoard BBS Software - Version 1.9o (beta)
Copyright (C) 1987 - 1990 FreeLance Programming
All rights reserved
FreeLance Programming / PO Box 726 / Washington DC 20044-0726
The Wizard's Workshop / 301-322-8678 / 300/1200/2400 - 24 hours
Table of Contents Page #
----------------- ---------
About rOverBoard i
Reporting Problems/Making Suggestions i
Hardware and software requirements 1
Partial feature summary 1
Command-line switches 2
rOverBoard .SCReen files 5
rOverBoard .ANSi (screen) files 7
Other rOverBoard related/created files 8
"Questionnaire" screens (REGISTER.SCR, SURVEY.SCR) 10
The Bulletin Menu 11
File listings (BBSFILES.DAT) 12
rOver's Main Menu screen 13
Operating the DOS box 14
Multitasking the DOS box 15
Editing users 16
Configuring message areas 18
Configuring file areas 20
User access control ("Access Masks") 22
Using events 25
Upgrading new users 26
The miscellaneous maintenance screen 28
The modem setup screen 30
Modem requirements & initialization 32
The Active Settings screen 34
Installation and setup 35
rOver's keyboard 37
ANSI & ASCII support 38
rOver's credit system; what it is and how it works 39
Function keys while "spying" on users 40
rOver's doorway system 43
rOver's door interface record 45
EMS memory utilizatoin 47
Outgoing calls explained 48*
Miscellaneous notes 49
* - Not yet documented.
rOverBoard BBS Software
Version 1.9
i
rOverBoard is a user-supported software product from FreeLance Programming.
It is currently in a late beta-test phase; mostly due to a few uncompleted
features (like the docs). There are no known bugs outstanding at the time
of this release. Of course, this in no way means there aren't any. rOver's
earlier beta versions have been running since November, '87, and the code is
fairly solid. I am not requesting donations for this version; however, if
you wish to send $$$ to encourage me to continue, you will receive a) more
rapid help on questions, and b) a discount on the first production version.
Suggestions for improvements are ALWAYS welcome. I can be contacted (as
sysop) on:
The Wizard's Workshop
(301)-322-8678 (free; new users ok)
(301)-322-2115 ($$$; no new users; MNP!)
3/12/24 24hrs
Or by mail at:
FreeLance Programming
P O Box 726
Washington DC 20044-0726
If you find any bugs, or have suggestions, please contact me either on-line
or by mail. Your comments CAN make a difference. The latest version of
rOverBoard will, of course, always be available on The Wizard's Workshop.
rOverBoard BBS Software
Version 1.9
- 1 -
rOverBoard requires an IBM PC/compatible with 384k minimum (640k recommended),
running DOS 3.1 or higher (3.2x not recommended). The CONFIG.SYS file used to
boot the machine should specify a minimum of "FILES=20", and at least 3 more
for each modem (after the 1st) you intend to use. Programs run in the DOS
box may require additional FILES= to be reserved for their use, as well.
Although the software will run on a two-floppy machine, a hard disk is
strongly recommended. Modem support is currently limited to Hayes
compatibles. Some of rOver's features include:
- Support for 4 modems (up to 38.4k baud) plus a "local" BBS window
where the sysop can be logged on simultaneously with callers - on
ONE machine, with no external multitasking software required.
- Complete maintenance capabilities while the board is running, including
shell to DOS, change setup/users/events/etc., upgrade new users.
- The ability to support remote drop-to-DOS and door programs.
- Will run invisibly in the background; all DOS access is multitasked
(this feature requires a higher degree of hardware compatibility).
- A space conservative design that uses fewer files and less disk space.
- Speed! rOver uses in-memory hash tables for superior response times.
- Positive verification security; easy to change privileges at the user
or at the group level. Almost 300 individual access control switches,
with 10 easily assignable pre-defined "masks" to ease global changes.
- Multi-layered menus adjustable to the users' experience level.
- Many file transfer protocols, including Ascii, X, Y, and Zmodem.
- Transparent 'command stacking'; responses to several prompts may be
stacked (D;Z;ROVER, MA0RY, etc.). The on-line help has syntax details.
- The ability to re-edit previously saved messages.
- Automatic msg & user deletions based on configurable time period(s).
- "Notify" messages (to ALL or given user) auto-displayed at log-on time.
- Intelligent welcome/bulletin screens that are displayed at logon only
if they have changed since the user last logged on.
- The ability to invisibly prevent unwanted files from being uploaded.
- Full path support; files need not be in their 'default' directory.
In addition, authorized users can access ANY file on the machine.
- Much, much, more...
rOverBoard BBS Software
Version 1.9
- 2 -
Usage:
ROVER.EXE /1[p] /2[p] /3[p] /4[p] /B# /D# /U#
/A /E /F /H /S /L /M[+/-] /N /P /V /X /Z
All command line switches are optional, as is anything in []'s.
/1[p] - /4[p] : Activate Nodes 1 - 4 (respectively)
'p' is of the form: [#] [!] [+ | - | *], where:
# = Modem init speed (1=300 [default], 2=1200, 3=2400, ..., 7=38400)
- = Prevents 300 (300/1200, if '!' used) baud downloads (on that line)
+ = Prevents 300 (300/1200, if '!' used) baud callers (on that line)
* = Indicates a hard-wired (null- or no- modem) connection. This option
disables baud-rate checking and prevents DTR from cycling when a user
logs off. The specified init speed will be used as the baud rate.
/A : Allow Doors
This switch causes rOver to be started in so-called "single-image" mode.
See the section on the doorway for more information about board modes
and doorway use.
/B# - /U# - /D# : Line Control
Where # specifies a node # (1 - 4). To apply the condition to multiple
ports, specify the switch once for each node (ie. /U1 /U3 etc.).
/U - Callers must have "Can Use Line #" = Y to logon (to that node)
/D - Callers must have "Can Use Line #" = Y to d/l (while on that node)
/B - Similar to /U, except that when callers attempt to log onto a node
to which they do not have "Can Use Line #" privileges, they are
allowed to log on thru the BULLETin menu, which will be displayed
regardless of the date(s) involved or the # of BULLETxx.SCR files.
The slightly-modified BULLETin menu allows use of the G)oodbye
command, but disables Q)uit-this-Menu and M)ain-Menu. Thus, the
user must logoff after reading the bulletins (NO MAIL CHECKING!).
/F, /S : Flicker Control
rOver uses direct screen writes, which can cause "snow" on CGA monitors.
These two switches eliminate such snow. Use of either switch will cause
screen output to take longer. The switches function as follows:
/F - Eradicates snow on _most_ writes. Screen swaps may still snow.
/S - Eradicates ALL snow. You need not use /F if using this switch.
rOverBoard BBS Software
Version 1.9
- 3 -
/I : "All IBM" Mode
This switch eliminates the display of the "Is '¦' the number one" and
"Do you want color" prompts when the user logs on. "Color" is always
set to "Y", while ASCII (the 1st prompt) is set to "Y" for callers
connected at 8/N/1, and to "N" for callers at 7/E/1.
/K : Disable Ansi Color Displays
This switch prevents ANSI colors from being displayed on the local
monitor, while still allowing the remote user to see them.
/L : Log File Control
By default, rOver creates/appends BBSLOG.DAT, a file which contains
a configurable set of information about system and user activity. Use
of the /L switch suppresses this feature.
/M[+/-] : Mail Checking
By default, rOver gives callers the opportunity to check for their new
mail when they log on. This switch functions as follows:
/M : Same as the default; the user is prompted for a y/n response
/M- : The prompt is not displayed, and the mail check is NEVER done
/M+ : The prompt is not displayed, and the mail check is ALWAYS done
(When using this option, ^k/^c/^x will NOT interrupt the search.)
/N : Upload Log File Control
By default, rOver also creates/appends UPLOADS.DAT, a file containing
whodunit info for uploaded files. The /N switch suppresses this feature.
/P : Private Board
When this switch is used, new users are not allowed to log-on. Instead,
they are shown the registration questionnaire (REGISTER.SCR), if any, and
are then immediately logged off. Be aware that if the user calls back,
he/she will no longer be considered new, and WILL be allowed to log on.
Be sure that you have set up your access masks as appropriate! To make
the board totally private, use /U1 - /U4 (as appropriate).
/V : Visual Indicator
While in DOS when using the /Z switch, this switch will provide visual
confirmation that rOver is still getting time in the background (while
in text modes only).
rOverBoard BBS Software
Version 1.9
- 4 -
/E : Extended ASCII in .ANS files
Users who request ANSI color/graphics are normally shown the .ANS
screens (where present), rather than the .SCR versions. This switch
forces users who connect at 7/E/1, or who indicate the inability to
display extended ASCII characters to see the .SCR files, even if they
have requested ANSI support. Use this switch when your .ANS screens
contain a lot of extended ASCII characters, to avoid having them
mangled by the extended ASCII translate table.
/X : Autoexec the DOS box
This switch will cause rOver to shell to DOS and execute AUTO-DOS.BAT
immediately after the board starts. This command, (which is mutually
exclusive with, and will override, the /A switch), will not be executed
if there is < 32k of free memory. AUTO-DOS.BAT must exist in the rOver
startup directory. This command should NOT be used unless /Z is also
specified, though this requirement is not enforced in code.
/Z : Multitasking
When this switch is used, rOver will continue to run in the background
while DOS is being accessed (F1: Dos Cmds). See the section on multi-
tasking for more information on this feature.
/H : EMS
Using this switch will cause rOver to make use of EMS memory for some
of its run-time memory requirements. If no EMS memory is found, use of
this switch will generate a warning message. If insufficient EMS memory
is found, the available EMS memory will be utilized, and subsequent
memory allocation requests will be filled from conventional memory.
See the sections on EMS and multitasking for more information and
potential conflicts.
Note that many switches may alternately be controlled via system events or
the "active settings" screen (F10 from the Main Menu). Also, note that the
"active settings" are re-computed each time the program starts (from the
cmd line switches + any events that were scheduled), NOT saved across each
execution. During this re-computation, scheduled events will override any
comparable command line switches. This re-computation, which calculates what
the board should look like if it had been running continuously for at least
a week, is also performed each time the events are modified via F6:Events.
The use of a .BAT file to start rOver is _strongly_ recommended, both to avoid
having to remember all these switches as well as to trap various return codes.
The RUN.BAT file included in ROVER.ZIP is provided as an example of such.
rOverBoard BBS Software
Version 1.9
- 5 -
rOver can display a variety of screens when a user logs on. Each screen is a
separate text file, with optional embedded ANSI commands (see the section on
ANSI support for more info). ^C, ^X, and ^K are disabled while displaying
"required" screens when the user logs on, but function normally should the
user re-display a screen. In general, and with the exception of WELCOME1,
rOver will not show screens to any user who has already seen them, unless
requested via the MAIN Menu. This can be changed by setting the file date of
the .SCR file to a far future date, in which case rOver will think it is
always new for each user.
WELCOME1.SCR - This is the opening banner; displayed just after the ASCII and
ANSI support prompts. It, like all .SCR files, is optional.
WELCOME2.SCR - This is the 'welcome screen', displayed after the "last called"
message, or when selected from the MAIN Menu via the W)elcome
command. If this screen is not present at system start-up, the
W)elcome command will be disabled.
BULLETIN.SCR - This screen functions either as a single bulletin (ala the
welcome screen) or as a menu of available bulletins. It is
displayed after the W)elcome screen, or when selected via the
B)ulletin command (also disabled if no BULLETIN.SCR at startup
time). See the section on the BULLETIN Menu for more info.
BULLET??.SCR - Where ?? can be 1 - 99. When BULLETIN.SCR is used as a menu of
available bulletins, these files make up the individual bullets.
See the section on the BULLETIN Menu for more information.
HINTS.SCR - This screen is only displayed in response to the H)ints command
on the MAIN Menu. If it is not present at system start-up, the
H)ints command will be disabled.
NEWUSER.SCR - This special screen is only displayed for new callers. It is
displayed immediately after the initial user setup prompts, and
just prior to REGISTER.SCR (if applicable).
LOGOFF.SCR - This optional screen is sent immediately prior to the "Logging
xxxxx OFF" message that precedes disconnect.
REGISTER.SCR - This is a 'questionnaire' screen which may contain prompts for
user input. See the section on questionnaires for information
on the contents of this screen. The presence or absence of this
screen controls new-user access, as follows: If this screen is
is not present, or the user successfully completes it, the user
is assigned default access mask #1. If it is present, and the
users does NOT complete it, he/she is assigned default access
mask #10.
rOverBoard BBS Software
Version 1.9
- 6 -
(rOverBoard's .SCR files, continued)
SURVEY.SCR - This is also a 'questionnaire' screen, using the same commands
as the above screen. It is displayed only in response to the
A)nswer-Survey command on the MAIN Menu, and omission of the
screen will disable that command.
NOUSEx.SCR - These screens work in combination with the /Ux switch(es). If
a new or unauthorized user attempts to log onto a restricted
node, the appropriate NOUSEx.SCR will be displayed, and the
user will then be logged off. Use NOUSE1.SCR for Node 1,
NOUSE2.SCR for Node 2 (etc.), as desired. Note that if the
line is not restricted, these screens are not displayed.
DOORWAY.SCR - This screen serves to list all the doors that are available
(if any). It is displayed in response to the L)ist-Doors
command of the DOORs menu.
MSGxx.SCR - Each msg area can have a MSGxx.SCR associated with it (where
xx is the # of the msg area, 0 - 63). This screen will be
displayed the first time a caller enters that msg area. If
the caller uses the A;? or A;?? command to get a list of the
available areas, this screen will also be displayed for the
next area entered (if one exists for that area), regardless of
whether or not the user has already seen it during this call.
FILExx.SCR - Each file area can have a FILExx.SCR associated with it, just
as with the message areas. This screen will be displayed each
time the A)rea-Info command is used to get information on a
given file area.