Output of file : ROVER.DOC contained in archive :
RVR20C-2.ZIP
rOverBoard BBS Software - Version 2.0a
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 - 9600 / 24 hours
Table of Contents Page #
----------------- ---------
Warranty and registration information i
About rOverBoard 1
Command-line switches 2
rOverBoard .SCReen files (.SCR / .$CR) 6
rOverBoard .ANSi (screen) files (.ANS / .AN$) 8
Other rOverBoard related/created files 9
"Questionnaire" screens (REGISTER.SCR, SURVEY.SCR) 11
The Bulletin Menu 12
File listings (BBSFILES.DAT) 13
rOver's Main Menu screen 14
The DOS box 15
Multitasking the DOS box 16
Editing users 17
Configuring message areas 19
Configuring file areas 21
User access control ("Access Masks") 23
Events 26
New user upgrades 27
The miscellaneous maintenance screen 29
The modem setup screen 31
Modem requirements & initialization 33
The Active Settings screen 35
Installation and setup 37
rOver's keyboard 39
ANSI & ASCII support 40
rOver's credit system; what it is and how it works 41
Function keys while "spying" on users 42
rOver's doorway system 45
rOver's door interface record 48
EMS memory utilization 50
Outgoing calls explained 51
Miscellaneous notes 52
rOverBoard BBS Software
Version 2.0
i
WARRANTY: This program is provided "as is" without warranty of any kind,
expressed or implied. The entire risk as to the results and performance of
the program is assumed by you. Furthermore, FreeLance Programming does not
warrant, guarantee, or make any representations regarding the use of, or
the results of the program, and you rely on the program and results soley
at your own risk. FreeLance Programming cannot accept responsibility for
any system damage, loss of profit, or any other incidental or consequential
damages resulting from the use or inability to use this product.
You are granted a limited license to copy and distribute unregistered
versions of this software. You may examine and use this software for a
period not to exceed 30 days. At the end of that time, you must either
register the software, or cease using it. Upon registering, you agree to
use reasonable efforts to prevent your registered version from being
distributed. You have the right to make unlimited backup copies of both
unregistered and registered versions; however, only ONE (1) copy of the
registered version may be in use at any given time. All rights not
specifically granted in this license are reserved by FreeLance Programming.
rOverBoard and its associated programs are a copyrighted product, being
distributed as user-supported software. User-supported software is similar
to shareware, however, IT IS NOT SHAREWARE. If you use this product for
more than 30 days, you MUST register it. This is a fully functional
release; no features have been omitted or crippled in any way. You are
encouraged to copy the unregistered version of this software and to
distribute it by whatever means. If a fee is charged for its distribution,
it must be made perfectly clear that the fee is ONLY for the distribution,
and in no way obviates the registration requirement. Support for this
product is available to all users (registered or otherwise) on my BBS (see
below). Users who require additional support, or who desire custom program
changes should contact FreeLance Programming, either on the BBS, or by
mail at the address shown below.
The Wizard's Workshop
(301)-322-8678
300 - 9600 24hrs
FreeLance Programming
P O Box 726
Washington DC 20044-0726
I welcome comments and suggestions about this product; please contact me
either on-line or by mail. Your comments CAN make a difference. The
latest version of rOverBoard (guaranteed virus-free) will, of course,
always be available for download from The Wizard's Workshop.
rOverBoard BBS Software
Version 2.0
- 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 _MUST_ 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. Use
of a hard disk is strongly recommended. Modem support is fairly flexible -
certainly any modem that supports the AT command set should work without any
problem. 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 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 2.0
- 2 -
Command line switches:
ROVER.EXE /1[p] /2[p] /3[p] /4[p] /B# /D# /U# /0 /@ /A /B /D /E /F
/G /H /I /K /L /M[+/-] /N /P /Q /S /T /U /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 node)
+ = Prevents 300 (300/1200, if '!' used) baud callers (on that node)
* = Indicates a hard-wired (no or null-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.
@ = Prevents caller input from being echoed. This can greatly reduce
packet counts for callers on X.25 lines. Callers on such nodes need
their comm program to provide local echo as well as to generate both
a CR and a LF when they press the ENTER key.
Note that characters typed on the rOver keyboard WILL be echoed to
the remote caller. The echo will occur as soon as the key is
pressed, instead of being smoothly inserted into the data stream as
is usually done.
/0 : Disable Node 0
Use of this switch will cause rOver to be started without the local
node (Node 0) being present. This configuration will result in as much
as 25k additional memory being available for the DOS box and doorway
programs. However, the board must be re-started without this switch in
order to allow local logons.
/@ : Two-word aliases
Using this switch will require users to have at least two words in
their user name. Boards that require real names to be used instead of
aliases should use this switch. While it does not guarantee that the
user enter their real name (what does?), it does help eliminate the more
obvious abuses. Note that the single-word alias "Sysop" is explicitly
excluded from this check.
/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.
rOverBoard BBS Software
Version 2.0
- 3 -
Command line switches (continued):
/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!).
/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.
/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.
/G : Glass-TTYs
When this switch is used, rOver assumes that all new users have screens
that are 80x24. New users are not prompted to enter their terminal
length and width when they first log on. These values may still be
altered from the CHANGE menu.
/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.
rOverBoard BBS Software
Version 2.0
- 4 -
Command line switches (continued):
/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).
/Q : Quick Logons
This switch will cause rOver to skip asking users to verify their names
when they first log on ("Sysop? [Y,n] >"), if the name they entered is
already known to the system. Execution proceeds as if the user had
entered a "Y" at the missing prompt. Has no affect on new users.
rOverBoard BBS Software
Version 2.0
- 5 -
Command line switches (continued):
/T : Date Tracking
Normally, when a user logs on, if the current date + the # of keep days
for their user record is greater than the explicit keep-til-date for
that user record, the keep-til-date is updated to be the current date
plus the # of keep days. When the /T switch is used, no such update
is done. Thus, sysops who maintain user subscriptions can set the
keep-til-date when the user subscribes, and use the keep-til-date to
keep track of when their subscription expires. (And to delete their
account [via BBSMAINT] if they have not resubscribed by that time.)
Note that when assigning access masks, the keep-til-date is still
explicitly set as the date the user last logged on plus the number of
keep days shown for the access mask being assigned.
/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).
/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.
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 2.0
- 6 -
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.
HELLOx.SCR - These are node-specific opening banners that may be used in
conjunction with, or in place of, WELCOME1.SCR. "x" is the
number of the node the screen applies to (0 - 4). If present,
the appropriate screen (based on the node the user is calling
on) is displayed immediately prior to the "Enter your name"
prompt.
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.
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.
rOverBoard BBS Software
Version 2.0
- 7 -
rOverBoard .SCR files (continued):
REGISTER.SCR - This is a 'questionnaire' screen which may contain prompts for
user input. See the section on questionnaires for more info.
If present, this screen affects new users' access, as follows:
Users who successfully complete the screen are assigned default
access mask #1. If they do not complete it, they are assigned
default access mask #10.
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.
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.
Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!
This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.
But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/