











                            REMOTE BULLETIN BOARD SYSTEM

                                      for the

                                 Personal Computer
                                   Version 17.5
                                   Sept 17, 1994

                               New Features since 17.4

                                      RBBS-PC

                                Copyright 1983-1994
                                         by

                                D. Thomas Mack
                                39 Cranbury Drive
                                Trumbull, Connecticut 06611





Enhancements to RBBS-PC

The new features found in this release are the result of efforts
and ideas of a lot of RBBS-PC users, sysops and programmers.
We would like to thank all of you for your contributions, suggestions,
and patience.

What you won't find in this beta...

For several reasons, support for the following has been removed.

MultiLink
AutoDownload

Internode chat is in the code but still under construction.
Current Message base size is 99 lines and 999 messages max.
Work is in process to increase these dimensions.

This document is not intended to provide an extensive reference
manual or a step-by-step procedure.  Please refer to UPDT175.TXT
for instructions on getting started with RBBS-175.


TURNING ON NEW FEATURES

Some of the new features are enabled or "turned on" by the existence of
a new file.  If the file exists, then it is used and the feature is enabled.
RBBS will not complain if the file is not present and the default will be
for the feature to be disabled.

Some of the new features are configurable by using the new CONFIG.EXE



   *********************** NEW CONFIG PARAMETERS *********************

         RBBS-PC Version 17.5 Configuration Page 18 of 18       RBBS99.DEF

341. Path\Filename used to store MENU0 info. ------ D:MNEW.DEF
342. EXTENSION of new style menu files ------------ SMN
343. Drive and path for new style menu files ------ D:
344. Path\Filename of external color definitions -- D:COLOR.DEF
345. Max new files RBBS will search for ----------- 99
346. Path\Filename of RIP menu when listing files - D:FILESCAN.RIP
347. Path\Filename containing wildcard xfer specs - D:FIDX.CFG
348. Get description from uploader before upload? - NO
349. Should RBBS show 'CTRL-X = Abort' prompts? --- YES
350. Will RBBS add 'Uploaded by...' in description? YES
351. Path\Filename used for exporting messages ---- D:NODE.TXT
352. Path\Filename shown when SYSOP needs system -- D:NEEDSYS.MSG
353. Is name searching to be disabled? ------------ NO
354. Entertaining characters cycled when working -- -\|/
355. Foreground color for extended descriptions --- Normal Cyan
356. Allow RIP detection at login? ---------------- YES



    *********** DISPLAY FILES with Menu type information ***********

A parameter for location and extension name has been added to
CONFIG for a class of files that don't really fit into a classification
of existing files.

Tentatively, the default extension for these files is .SMN
but this doesn't reflect the RBBS tradition of menus, since they are
not capable of chaining to other menus.  The SMN refers to Sub MeNu
and indicates that there are no menus below that file.

These files are:

AUTOOFF.SMN
WILD.SMN
LOGOFF.SMN
PERS.SMN

The function of these files are described elsewhere in this document.

    ************************* NEW HELP FILES *************************

Replace your existing help files with these or customize your own.

FD.HLP ----------- Enhanced F)iles D)ownload Help File
FU.HLP ----------- Enhanced F)iles U)pload Help File
UB.HLP ----------- Enhanced Help File for Time Bank (Utilities Bank)
HELP09 ----------- Enhanced Help for Graphics Option selection
NEWMAIL.HLP ------ File shown to user who turbo logs onto the system
                   and has new mail waiting

    **************** NEW PASSWORDS File Parameters ******************

Modified PASSWRDS file parameters.
   The first 13 are for stock RBBS v17.4 and the next 8 are for 17.5

Parm1  - Password that this line applies to
Parm2  - Security level for password (or user sec level this line applies to)
Parm3  - Maximum time in minutes per session
Parm4  - Maximum time in minutes per day
Parm5  - Number of days in subscription period
Parm6  - Expired security level subscription management
Parm7  - Start time for this lines actions (HHMM 24 Hr style)
Parm8  - End time for this lines actions (HHMM 24 Hr style)
Parm9  - Type of ratio method to use
                0 - Files ratio
                1 - Bytes ratio
                2 - Files/Day restriction
                3 - Bytes/Day restriction
Parm10 - Ratio field for ratio method
                0 = Record uploads, but not downloads or enforce
                    ratio
               -1 = Record uploads and downloads but do not
                    enforce ratio
                X = X sets positive ratios
Parm11 - Initial credit field. Can be used with methods 2 and 3
         from Parm9
Parm12 - Time lock in seconds for locked features
Parm13 - Maximum time a user is allowed to bank, max 255

*** ! NEW ITEMS ! ***

Parm14 - Number of logins before forcing user to change Password.
       - 0 Disables

Parm15 - Number of carrier drops before users security level is
         lowered.
       - Maximum 255, 0 Disables

Parm16 - Increment used to lower security level when Parm15 is
         invoked.  Example, a 5 entered in this parameter would lower
         a caller at security level 15 to a new level of 10.
       - Do not use plus and minus symbols.

Parm17 - Force a NEW MAIL check when the user first logs on.
       - 0=Ask, 1=Force

Parm18 - Time bank withdrawal option availability.
           (used to make the time bank withdrawal option
            unavailable during the time period set in Parm7 and
            Parm8)
       - 0=Available, 1=Disabled

Parm19 - Number of seconds for duration of auto-logoff countdown
       - Maximum 255, Minimum 1)

Parm20 - Reserved for Internode chat availailability - SET TO 0

Parm21 - 1 = enforce only 1 time lock per day.
         0 = use stock method of time lock for each sign on.




    ***************** Are you SURE you want TURBO? ******************

TURBO.HLP

Displayed to the new caller just before asking if they want to
use TURBO Keys.  Some sysops would rather a new user get familiar
with the BBS before selecting turbo key.  This gives the SYSOP
an opportunity to express that opinion. This file should be located
in the Help directory.



    ********************* Forgotten Passwords ***********************

Forgotten passwords can be a problem on some systems and a nice touch
is to display a file telling the caller what to do.
Suggesting that they leave their phone number, best time to call,
or new password are some good starts.

BADPASSW.HLP ----- A file displayed to a user failing the password check.
                   It should be located with the rest of the .HLP files



    *********************** NEWUSER WELCOME *************************

NEWUSER will allow the Sysop to create a single message addressed to the
name NEWUSER which will be shown in the Mail Scan as a message addressed
to the users name.  The user will NOT be able to kill the message and it
will not be shown to them as personal mail on future calls.



    ********************** SYSTEM INFORMATION ***********************

SYSTEM INFO will show more information about the system, to include
DOS version and DesqView Version and etc.



    ************************** STATISTICS ***************************

USER STATISTICS are displayed in color, vertically on the screen.



   ************************* SCREEN PAUSES **************************

RBBS-PC now will pause the display with "Press any Key" at appropriate
times for the NOVICE user (only).  This removes the need to have a
smart text page break {PB at the beginning of each menu.


    ************************* MORE PROMPT ***************************

The MORE prompt at the end of a message is now being split into
two line for controlled wrapping only for the sysop.  (This is due
to extra commands available only to the sysop which would cause
the line to wrap to the next line anyways, so the split makes it
easier to read.

    *************** Additional Information in MENU0 *****************

RBBS-PC now gives additional information on the "waiting for calls"
screen.  Use the new MENU0 supplied with this package for a template
screen. A dynamic file called MNEW.DEF is used to hold some of the
information for MENU0.

341. Path\Filename used to store MENU0 info. ------ D:\MNEW.DEF



    ************************* LINE 25 Info **************************

On the SYSOPS screen, while "SNOOP" is enabled, a few changes have
been made on LINE 25
1. The callers connect bps rate is shown.
2. The ACTUAL time remaining for the caller is shown.
3. If this is the FIRST call of that user, NEW is shown.



    ********************* RIP Graphics Support **********************

RIP GRAPHICS SUPPORT is provided for users that call with a terminal
program supporting RIP Graphics.

Example menus included with this package include:

MENU1R ----------- Generic Sysop Menu - RIP
MENU2R ----------- Generic Main Menu - RIP
MENU3R ----------- Generic File Menu - RIP
MENU4R ----------- Generic Utils Menu - RIP
MENU5R ----------- Generic Door Menu - RIP

  Locate these files along with the rest of your MENUS

Any menu or display that supports the text/graphic/color flavors can also
be RIP supported. Use your favorite RIP drawing program to create them.

In addition, the standard RBBS comment (remark) character has been
changed from the pipe (|) symbol to tilde (~) to allow RIP macros.

    ************************* FILESCAN.RIP **************************

Of special note in the RIP support is FILESCAN.RIP.

This RIP looks like a VCR control panel and provides smooth browsing
of files.  Locate this file in the directory your Master FMS file is in
or in your .DIR directory or wherever you define it in CONFIG.

346. Path\Filename of RIP menu when listing files - D:FILESCAN.RIP

Note: Turbo Key is disabled when viewing files with FILESCAN.RIP





             **********************************************
             **                                          **
             **  Improvements in the FILES area          **
             **                                          **
             **********************************************


The RBBS 17.5 FILE SYSTEM has many improvements, but most notable are:

  Wildcard Downloading - with improved interface over original mod
  Support for BATCH uploads and downloads,
  Ability to get descriptions before uploading,
  External file processor support (ie. RBatch),
  File_ID.DIZ and other .ZIP internal descriptors,
  Time Bank access when users told, you have X mins need Y mins,
  Allows users to edit list of Marked Files right before a transfer
  Allows users to add more files right before a transfer
  Specific support for .DIR systems include:
      - colorization
      - ability to mark files while listing
      - "Jump" support
  (.DIR is the alternate file handling system to FMS)

    ******************** Customized FMS Header **********************

FMSHEADER allows you to create your own fancy header file to be displayed
to the users when listing files in your FMS.  The headers should be in the
same directory as your master FMS files.

(Samples with this release include)

FMSHEAD.TXT ------ Sample external FMS Header
FMSHEADC.TXT ----- Color Sample external FMS Header
FMSHEAD.2 -------- (More Samples)
FMSHEADC.2 ------- (More Samples)
FMSHEAD.3 -------- (More Samples)
FMSHEADC.3 ------- (More Samples)



    ******************* COLORS in FMS and .DIRs *********************

The colors in the FMS and .DIR listings are now configurable with the
parameters in CONFIG.

The parameters in CONFIG are shown as:

323. Caller's Foreground color 1 ------------------ Bright White
324. Caller's Foreground color 2 ------------------ Bright Yellow
325. Caller's Foreground color 3 ------------------ Normal Green
326. Caller's Foreground color 4 ------------------ Bright Cyan
355. Foreground color for extended descriptions --- Normal Cyan

These parameters have in the past been used throughout RBBS, but with the
new external color definition file, they are now used almost exclusively
for the file listing as follows.

    323 = Filename
    324 = Date
    325 = File Size
    326 = First line of file description
    355 = Extended description line(s)



    ******************** Personal File Menus ************************

PERS.SMN  Menu(s) shown when the user is in FILES menu and
selects Personal Downloads.  This will allow the sysop to make
a distinction between the normal files menu and personal downloads.
This menu is optional, the function of personal downloads has not
changed.

This file is one of the new "sub-menu" files and definable in CONFIG.

342. EXTENSION of new style menu files ------------ SMN
343. Drive and path for new style menu files ------ D:\RBBS\TEXT



    ************************* FILE VIEWING **************************

VIEW.BAT --------- Batch file used for viewing archives

      Located where RBBS finds Command.Com  Parameter #105

The sample file included uses BSHOW as the file viewer.  If you are not
currently using BSHOW then you will need to edit the BSHOW.CFG to match
your system and edit the View.BAT to reflect your system setup.
         (Previous users of BShow should change %3 to %5)
BSHOW.EXE, BSHOW.CFG, and BSHOWL.CFG are included for your convenience.
The sample VIEW.BAT will look for them in C:\RBBS\BSHOW unless you modify it.

If VIEW.BAT is not found, RBBS will use the internal viewing option.



    ************************* HACK REPORTS **************************

HACKED FILE LIST Support is provided to assist in keeping unwanted files
from being uploaded.  Although a zero byte file in your FMS or .DIR will do
the trick, it is not easy to incorporate new lists of HACKED files.  This
feature allows you to use a list created specifically for BBSs.

HACK.COL --------- Hack report file that lists filenames that are considered
to be hacks or pirated files.  This file resides in the same directory as
your Master FMS file or your .DIR directory.

  The format of this file is:

; remarked line
FILE1

FILE2
FILE3

Note that there are no file extensions, and lines beginning with a semicolon
or space are ignored. This format is compatible with the hack report
maintained by Lee Jackson and available on many BBS's. The report is commonly
called HACKXXXX.ZIP where XXXX reflects the date of the report. In it,
you should find a file named HACKXXXX.COL - You must rename this file to
HACK.COL if you wish to use it.

HACK.HLP --------- File displayed to user when they try to upload a file
                   that is listed in the hack.col file.  This file resides
                   in your help directory.



    ************************ UPLOAD Message *************************

Its nice to be able to tell the caller (one more time) before they upload
that you do not want gif files, or get-rich scams, or commercial software
before they upload.

UPMSG.HLP ---------File displayed to the caller just prior to the actual
                   upload of a file or batch of files.
UPMSGG.HLP ------- Graphic version of UPMSG.HLP
UPMSGC.HLP ------- Color version of UPMSG.HLP

The files are located in the directory with the other HELP files



    ************** Restrict UPLOAD by File Extension ****************

BADEXTS is a file used to block files with the extensions listed within.
The file has the format of:

Security Level that can Override the restriction,
the actual file extension,
the filename to be displayed to the caller attempting the upload.

As shown in the example, this display file can be generic enough to support
multiple extensions.  The BADEXT file and the related help files should be
located in the directory where your HELP files are located.

SAMPLE BADEXTS FILE

170,GIF,BADGIF.HLP

(If a security level less than 170 tries to upload a .GIF, they are shown
 a file called BADGIF.HLP)

170,COM,BADFILE.HLP
170,BAT,BADFILE.HLP
170,FLI,BADFILE.HLP

(If a security level less than 170 tries to upload a .COM, .BAT, or .FLI,
 they are shown a file called BADFILE.HLP)

100,TXT,BADTXT.HLP
(If a security level less than 100 tries to upload a .TXT they are shown
 a file called BADTXT.HLP).



    ************************ UPLOAD Testing *************************

RBBS will initially look for a single batch file called TEST.BAT
to test uploads.

If TEST.BAT file is not found, RBBS will look for T<ext>.bat file for
testing (example: TZIP.BAT , TARJ.BAT , TTXT.BAT)

In either case, the parameters passed are:

    %1 path/filename
    %2 failed param (if this file is > 2 bytes, RBBS assumes failure)
    %3 Comm port
    %4 file extension


RBBS supports Plain TEXT, High ASCII, or ANSI versions of the test
batch files.  i.e Tzip.bat, TzipG.bat, TzipC.bat.



    ************************* UPLOADED By ***************************

Some sysops like to display in their file listing, the name of the
caller who uploaded the file.  RBBS-PC now supports this and is
configurable in the CONFIG.

Parameter #350. Will RBBS add 'Uploaded by...' in description? YES

WUW.DEF
If parameter 350 is set to YES, RBBS will look in the directory
where your master FMS file (or .DIR directory) resides for a file
named WUW.DEF

If this file exists, RBBS will use the contents of this file, rather
than the stock "Uploaded By" message.

Its okay to use SMART TEXT in this file but DO NOT USE COLOR Smart Text.
Also, there is no need to use {FN {LN since the user name is appended.

The maximum size of your text should be:
    2 + Max Length of file description (40 to 46)


Note: if you use an upload batch processor, such as RBATCH, this file
and parameter in config will NOT be used.



    ********************* WILDCARD DOWNLOADING **********************

In order to implement wildcard downloading, you must create a
configuration file with the name and path definable in CONFIG.

Parameter #347. Path\Filename containing wildcard xfer specs - D:FIDX.CFG

RBBS will look for this file, and if found, permit wildcard searches for
downloading.  The contents of this configuration file is as follows:

Line 1 : Maximum files to display , number of valid directories in
                                    your LIDX.DEF (non macros)

Currently, you may not set the maximum files to diplay above 100.  If
you do, only the first 100 files will be displayed.

The number of valid directories in your LIDX.DEF file refers to ALL
directories which files can be downloaded from.

When creating your LIDX.DEF file, be certain to have all downloadable
directories listed first, then the macros.

  In a sample FIDX.CFG file the first line contains the following:

100,21

The system will show the first 100 matches to the input search string, and
the first 21 lines of the LIDX.DEF file are valid downloadable directories.

Line 2 on down in the FIDX.CFG file contains the following:

<security level> , <drive>\<path>

The security level is the minimum security level that can search the directory
for matching files.  The <drive>\<path> is a directory to search. There may
be up to 99 directories to search upon.  If you're running a Fast File Search
(FFS) system, you really don't need any entries here other than your upload
directory (if you allow uploads to be downloaded) since all files will be
listed in your FIDX.DEF/LIDX.DEF FFS system files.  If you are not running
the FFS, then you would list all the directories you have listed in CONFIG
parameter #208 as download directories, plus any others you may want to list.

USE CAUTION HERE.. THE DIRECTORY WILL BE PHYSICALLY SEARCHED IF THE USER HAS
THE SECURITY LEVEL TO SEARCH IT.

So a sample FIDX.CFG file for a fast file search system would look something
like the following:

100,21
5,K:\RBBS\FILES\UPLOAD

A sample FIDX.CFG file for a non fast file search system might look something
like this:

100,10
5,K:\RBBS\FILES\UPLOAD
5,J:\RBBS\FILES\MISC
5,J:\RBBS\FILES\UTIL
5,I:\RBBS\FILES\OS2
5,I:\RBBS\FILES\WINDOWS
5,H:\RBBS\FILES\GAMES
5,G:\RBBS\FILES\BBS
5,G:\RBBS\FILES\BBS\DOORS
5,G:\RBBS\FILES\BBS\MERGES

The user can stack files and search strings in any order at the RBBS
files system prompt.  When RBBS comes to the wildcard string (which has
the "*" character at the end or beginning), and wildcards are permitted,
it will then process that request.

All matching files to the string, found thru searching the listed
directories and/or the fast file system, up to the maximum allowed by
the SysOp, will be displayed to the user.  The user can then mark the
files from the list by entering the corresponding number to the file or
a sequential group of numbers by placing a hyphen between two numbers
(ie: 1-5  3-10  1-10  etc).

After marking the files for download, RBBS will then continue on to
process all the other files/wildards in the list.  The user also can add
files already marked for download to the list and can stack the protocol
and request to auto-logoff as with  RBBS 17.4.

An example would be:

FILE Command: D ALLFILES.ZIP SHEZ* ECHO.ZIP #1BS* TIDY.ZIP Z /G

This would process the request for a file named ALLFILES.ZIP, then process
the wildcard search for all files matching the search string "SHEZ", add
all the files that the user marks from the files matching the wildcard
search string, then process the request for the file ECHO.ZIP, then process
the wildcard search for all files matching the search string "#1BS", add all
the files that the user marks from the files matching the wildcard search
string, process the file TIDY.ZIP and send all files (including those files
selected from the wildcards) using Zmodem (batch) and auto-logoff upon
successful completion.

When in non-expert mode, or when the "H" or "?" command is issued while at
the wildcard prompt, the WILD.SMN will be displayed.

WILD.SMN is one of the new "sub-menu" files and definable in CONFIG.

342. EXTENSION of new style menu files ------------ SMN
343. Drive and path for new style menu files ------ D:\RBBS\TEXT



    ********************* DOWNLOAD DISCLAIMER ***********************

DOWNLOAD MESSAGE is an option to display a file to the caller just prior
to the actual download of a file or batch of files.  A good example would
be to remind users to scan their files.

DNMSG.HLP -------- File displayed to caller before Download.
                   Located in the Help Files directory
DNMSGG.HLP ------- Graphic version of DNMSG.HLP
DNMSGC.HLP ------- Color version of DNMSG.HLP



    ************************ RATIO EXCEEDED *************************

RATIO.HLP ---------A file displayed to callers when their ratios or
                   limits have been exceeded.  Locate this file in
                   the HELP directory.  This file can be used to
                   remind users that they can help support the BBS.



    ***************** DOWNLOAD Security Violation *******************

DOWNVIO.HLP will be shown to a user when a security violation occurs
through the FILESEC rather than the more generic and abrupt SECVIO.HLP.
For example, if a user attempts to download a file that is reserved for
higher security levels, this file could be used to explain the reason for
the security violation.  Place this with the rest of your help files.

DOWNVIOG.HLP  Graphics version
DOWNVIOC.HLP  Color version



    ************************* RFM Support ***************************

RBBS-PC now includes support for the popular RFM utility.



    ************ Automatic Log Off after File Transfer **************

AUTOOFF.SMN is a "menu" displayed just prior to downloading files.
The choices for the caller is E)dit marked files, M)ark more files,
C)ontinue transfer, A)bort the transfer, or G) Automatically log off after
a SUCCESSFUL transfer.  If no menu is found, only the prompt is displayed.
This file should be located as defined in CONFIG parameter 343.
The extension (SMN) is also definable in parameter 342.

This file is one of the new "sub-menu" files and definable in CONFIG.

342. EXTENSION of new style menu files ------------ SMN
343. Drive and path for new style menu files ------ D:\RBBS\TEXT






    ************** Changes to PROTO.DEF and XFER?.DEF ***************

RBBS-17.4 did not look too closely at the results of a file transfer.
For example, if a caller had selected 10 files to download, each file
1MB in size and aborted, say after the second file, RBBS would consider the
download successful and "charge" the user for downloading 10 MB's and 10
files.

RBBS-PC now looks much closer at the transfer log files.

The transfer log file is produced by protocols such as DSZ, HS/LINK, BIMODEM,
ZSX, and perhaps others.  We assign the environment variable to XFER?.DEF
(where ? is the node number) in autoexec.bat or otherwise in the partition
or window that the node is running in by:
SET DSZLOG=XFER%NODE%.DEF   (Note: this used to be XFER-%NODE%.DEF)

This version of RBBS now uses the XFER?.DEF dynamically by

1. Examining the success status of each file
2. Updating marked files to retain the unsuccessful filenames.
3. Shows transfer statistic on each file after transfer.

In addition, PROTO.DEF has a couple of new features.

A. Force Reliable mode.  (This was in 17.4)
   If you wish to restrict certain protocols to callers who have connected
   in reliable mode, place a R in the 5th parameter of the line in proto.def.
   A caller that has not established a reliable connection will not even
   see these protocols.

B. External Batch processing
   If you wish to use RBATCH (or some other external batch uploading program)
   instead of the internal batch processing, place a N in the 5th parameter
   of proto.def.  (NOTE: If you are using external batch processing, you
   probably want to disable "Descriptions before upload" in CONFIG parameter
   348.)

C. Both
   If you want both A and B above, place RN in the 5th parameter.






D. A new variable, [UPDIR] is now available in PROTO.DEF
   This can be useful for bidirectional protocols, such as HS/LINK.
   You may pass this variable in the same fashion that you pass [PORT]
   [BAUD], [CBAUD], and etc.

E. Support for protocols that do not using the DSZLOG files.

   There are many protocols that report the status of a file transfer in
   various ways.  The vast majority report the error as the first parameter
   and 17.4 dealt with that just fine, but the filename may be listed at
   different locations in the log file.

   The 11th parameter of PROTO.DEF tells RBBS where to look for the
   information in the log file.

   For SHELLED protocols, the standard entry is 1=E
   If the protocol does NOT report using DSZLOG files, find out which
   parameter numbers the filename and success status use.
   Then modify the entry to reflect the parameter number. 1=E-#
   For example, if the filename is being shown as the 7th parameter
   in the protocol log file, the entry would be 1=E-7.
   For DOORED protocols, the same example would modify the standard
   entry (4=E=A) to be 4=E=A-7


             **********************************************
             **                                          **
             **     Improvements in the MESSAGE Area     **
             **                                          **
             **********************************************



     ************************ ANSI EDITOR ***************************

A full screen ANSI editor for messages is available in this version.
If the caller has graphics (color) enabled and can support ANSI,
they will be asked if they wish to use the full screen editor when entering
or replying to a message.

ANSIED.HLP  -- a help file for the Full Screen ANSI editor.
               Place this with the rest of your .HLP files.


    ************************ ALIAS SUPPORT **************************

Alias support is included and can be turned on for any given conference
by creating a file in the same directory that the conference USER file
resides in.  The filename is in the form of CONFa.DEF, where CONF is the
conference name.  For example, if ADULTm.DEF is the message file,
ADULTu.DEF is the user file, then ADULTa.DEF would be the alias definition
file.  The definition file should be located in the same directory that
the user file is in.  The format for the alias definition file is:

"REAL NAME","ALIAS NAME"

The first two lines should contain the sysops entries:

"SYSOP","SYSOP"  (or sysop's alias)
"SECRET NAME","SYSOP" (or alias)



    *********** Search for User Name when ENTERING Message *************

RBBS now enables a caller to type a partial user name when entering
a message.  The caller enters at least two characters of the user's
name in the "TO:" field and presses return. The system will search
for matching names and display them to the caller for selection.


353. Is name searching to be disabled? -------------- NO



    ************* SYSOP May EXPORT Messages to a FILE ***************

E)XPORT MESSAGE is a new command available to the sysop when reading mail.
The Sysop can export a message to a text file defined in CONFIG.  This file
is appended to if it already exists.

Parameter #351. Path\Filename used for exporting messages ---- D:\NODE.TXT



    ******************** NETWORKED Conferences **********************

To prevent the embarassing messages such as "please upgrade my access"
being addressed to sysop in a networked conference (or any conference)
create a file call CONFNAMEn.DEF in the same directory that your message
file is in.  For example, if you have a RBBS-PCm.DEF and want to disable
messages addressed to SYSOP in that conference, create a RBBS-PCn.DEF in
that same directory.  Incoming messages will still properly be converted
to SYSOP but outgoing addressed to SYSOP will not be permitted.



    ********************* UUCP Address support **********************

RBBS-PC now allows messages to be addressed to UUCP in networked
conferences.  If the message is addressed to UUCP, the first line
of the message CANNOT be blank.

In addition, RBBS-PC will look in you message area for a file
called <confname>I.DEF.

If the file is found, it will format the message based on
your parameters in the <confname>I.DEF.  The user will receive
a prompt "Enter Users Address".  In this initial implementation
it is expected that the caller will enter the recipients
Internet address here.

There are five parameters in the I.DEF file, each on the same
line and separated by commas.

The first parameter is the name that ALL of the messages
in the conference will be addressed to.  A prime example
is UUCP.

The second parameter allows you to define what you want to
be added to the first line of each new message.
This could, perhaps be the address of your UUCP gateway
and routing instructions (i.e. CRASH, PVT)

The third parameter lets you put specific text in the
second line of the messages.  On some mail processors,
the second line must begin with "TO: " and the users
internet address to pass on the the UUCP.

The fourth parameter defines WHICH line in the text the
information captured be the "Enter Users Address" is
appended to.  This may vary according to different
processors.

The fifth parameter is the FULL file spec (path and name)
of a help file that will be displayed before the user
enters the subject of the message.  RBBS-PC will use
all three flavors if they exist.

Example 1:

UUCP,1:109/42,TO:,2,D:\RBBS\HELP\INTRNET.HLP

This example uses the Overmail format of netmailing from a RBBS
conference to a UUCP gateway.  The example causes all messages
in the conference to be addressed to 1:109/42, a Fidonet UUCP
gateway.
The first two lines in the message text would be:

------------------------------------------
1:109/42
TO: jdoe@somewhere.com
         ^-------------depending on what the caller enters.

Example 2:

UUCP,TO:,This message is for -,1,D:\RBBS\HELP\INTRNET.HLP

This is a an example of a message addressed to a commercial
Internet gateway.  It shows the flexibility of the new feature.

------------------------------------------
TO: jdoe@somewhere.com  <- depending on what the caller enters.
This message is for -


In a conference with I.DEF, mail cannot be addressed to
SYSOP (removes the need for an extra N.DEF file)

Work is underway to improve this interface.  Since most fido
mail tossers do not have a means of handling more than one
inbound netmail area (in the same zone), it takes some
effort to separate incoming Internet e-mail from Fidonet
e-mail.




    ****************** BANNED USER per Conference *******************

Sometimes a sysop may wish to restrict a user from a particular conference,
perhaps at the request of a moderator.  To easily accomplish this, create
a file name CONFNAME.BAN in the same directory as the user file for that
conference.

For example, if the conference user file is RBBS-PCu.DEF, put the file
named RBBS-PC.BAN in the same directory.  A valid entry in this file would
be a user name (full name) on a line be itself.  If the user tries to join
the conference, s/he will be shown a file named BANMSG.HLP if it exists in
your HELP directory.



             **********************************************
             **                                          **
             **            NEW DOOR SUPPORT              **
             **                                          **
             **********************************************

    ***************** NEW parameters for DOORS.DEF ******************


MAX  SECURITY, DROPPED CARRIER and DOOR.SYS SUPPORT

A summary of the DOORS.DEF format is:

       1 - Door Name  (up to 8 Characters)
       2 - Security Level (minimum to use door)
       3 - File display when exiting door (questionaire format)
       4 - Door Exit Method ("S" for shelling, else goto .BAT)
       5 - Door Exit Template
       6 - Ask for password when returning?
       7 - File display upon return from a door (text file)
       8 - Door Times (maximum time in door)
       9 - Security Level (maximum to use door)
      10 - Drop Carrier ok?
      11 - Drop file type (S,R,D)
      12 - Registration date change
      13 - Look for door name in current directory?


Addition features for Door control include:


Parameter 9     Maximum level to enter door

The new parameter is the MAXIMUM Security Level allowed to use a door,
this will allow as an example, a way to keep verified users out of the
callback door (and increasing their security all the way up to sysop
if the door is written that poorly!)

Another use may be to restrict a mail door to a specific security level for
mail HUBs.

Parameter 10   Okay to drop carrier while in door?

  Y = allow user to drop carrier in this door without penalty
      (useful for mail doors)
  N = record drop carriers that occur in this door (default)

Parameter 11   Support for DOOR.SYS

blank  Nothing entered in the 11th parm = write out a DINF?.DEF
       file to the current directory.  Same a "D" parameter.
 S     The letter "S" in the 11th parm = write out the DOOR.SYS
       file to the current directory.
 R     The letter "R" in the 11th parm = write out the DOOR.SYS
       file to the current directory and then read the fields
       back in when returning to the BBS.
 D     The letter "D" in the 11th parm = write out a DINF?.DEF
       file to the current directory.  This is the default.

DOOR.SYS is placed in the nodewrk directory (same directory as your
callers file)

The information that is read back into RBBS using DOOR.SYS is:

Line    Function

15      Security Level
28      Total Uploads
29      Total Downloads
30      Daily Download "K" Total
42      Time Credits
47      Files DL Today
48      Total "K" Uploaded
49      Total "K" Downloaded


          !!!!!  USE THIS FEATURE WITH EXTREME CAUTION.  !!!!!
Sloppy door management with DOOR.SYS could open your BBS to security breaches.


         NEW Parameter 12  Resetting Registration Date

         New parameter added to DOORS.DEF - This value can be between
         -32768 to 32767 (same as user security levels).  If this parameter
         has a value in it and the user returns from a door where:

         - the users security level will be INCREASED by DOUTx.DEF
         (the users old level is less than what DOUT will increase
         it to)
         - the new security level will be greater than or equal to
         the 12th parameter value

         If this criteria is met, then the users registration date will
         be changed to the current day's date.

         If you have NO VALUE in the 12th parameter, than this feature
         is disabled (turned off).

example:

"WAR",5,,D,"WAR.BAT [NODE]",N,,30,20,N,D,,N
"PIT",5,,D,"PIT.BAT [NODE]",N,,30,20,N,D,,N
"MAILMGR",5,,D,"MAILMGR.BAT [NODE] [CBAUD]",N,,30,20,Y,D,,N
"TQM",5,,D,"D:\RBBS\TQM\TQM.BAT [NODE]",N,,30,20,Y,D,,N
"KOB",5,,D,"KOB.BAT [NODE]",N,,30,20,N,D,,N
"CREDIT",5,,D,"KOB.BAT [NODE]",N,,30,20,N,D,15,Y

Parameter #13 also a new parameter.  If you have a "Y" or nothing in
this field, RBBS will look for the door name + .BAT in the current
directory (just as it always has).  If you have "N", then RBBS will not
look for the door name + .BAT in the current directory and will run the
batch file listed as parameter #5.

Here is an example of a door.def file with the new parameter:

  GAMES,5,C:\RBBS\DOOR.QES,D,"GAMES.BAT [NODE]",,,,200,N,,,N
   - Do not check for door file in current directory

  GAMES,5,C:\RBBS\DOOR.QES,D,"GAMES.BAT [NODE]",,,,200,N,,,Y
   - Check for door file in current directory

  GAMES,5,C:\RBBS\DOOR.QES,D,"GAMES.BAT [NODE]",,,,200,N,,,
   - Check for door file in current directory




             **********************************************
             **                                          **
             **            OTHER IMPROVEMENTS            **
             **                                          **
             **********************************************



    *************************** ANSICHAT ****************************

ANSICHAT between Sysop and users is available if the user has ANSI
selected as their graphic setting.  When a user pages the Sysop or
the Sysop presses F10 a vertical split screen chat session will begin.

NOTE:  The standard RBBS-PC line chat is still available by
pressing  <ALT> F10.  This OVER-RIDES the split screen chat.



    *********************** KICKOFF MESSAGE *************************

KICKOFF MESSAGE gives the user a customized message when you
use the CTRL-END key to lock them out of your system.

KICKOFF.MSG ------ File displayed to user when CTRL-END is used.
                   Locate this file in the Help Files directory.
KICKOFFG.MSG ----- Graphics version of Kickoff.MSG
KICKOFFC.MSG ----- Colorized version of Kickoff.MSG



    ************************ LOGOFF Choices *************************

LOGOFF has been enhanced to allow a menu of options,

A)bort Logoff
C)omment to Sysop
B)ank my Time
G)o ahead and log me off.

 (If a user does NOT have the security required, the commands
  will be starred (*) out.)

LOGOFF.SMN     Displayed when user is logging off.

This file is one of the new "sub-menu" files and definable in CONFIG.

342. EXTENSION of new style menu files ------------ SMN
343. Drive and path for new style menu files ------ D:\RBBS\TEXT

If the file does not exist, the user will see the internal prompts
(which will NOT be starred out.)



    *********************** REASON FOR CHAT? ************************

RBBS will now prompt the user for the reason for the chat. (Paging
the SysOp) This will be logged in the CALLERS file.


    *************** You REALLY want to Chat with me? ****************

PAGE.TXT ----- Text file shown to a user who attempts to page the Sysop.
               If exists, this file is displayed just after the user
               is asked "Purpose of chat?" This gives you a chance
               to explain what you consider valid reasons for paging.

Put this file where your WELCOME files are located.
(Note: this a good file to use Smart Text in)


    ******************** SYSOP Needs the System *********************

RBBS will display a file to the caller when the Sysop has pressed
the END key to force a user off kindly because the Sysop needs the
system immediately.

NEEDSYS.MSG ------ File displayed to caller when END key is used
NEEDSYSG.MSG ----- Graphics version of file
NEEDSYSC.MSG ----- Color version of file

The location and name of this file is defined in CONFIG param 352

Parameter #352. Path\Filename shown when SYSOP needs system -- D:\NEEDSYS.MSG



    ******************** REGISTRATION EXPIRING **********************

RGXPIRE.HLP ------ will give a message to the caller who's within the number
                   of days before subscription expires as set in CONFIG
                   parameter 50.
RGXPIREG.HLP ----- Graphics version of RGXPIRE.HLP
RGXPIREC.HLP ----- Color version of RGXPIRE.HLP

Located in the directory with other HELP files.



    ********************* REGISTRATION EXPIRED **********************

RGXPIRD.HLP ------ File Displayed to callers whos Registration has
                   expired. Locate this file in the Help Files directory
RGXPIRDG.HLP ----- Graphics version of RGXPIRD.HLP
RGXPIRDC.HLP ----- Color version of RGXPIRD.HLP



    ************** LOG OFF Message by SECURITY Level ****************

EXTRA MESSAGE is a way to show an extra little something to users
of specific security levels at log off.

XMSGx.HLP -------- File containing the message, x is the security level
XMSGxG.HLP ------- Graphics version for security level x
XMSGxC.HLP ------- Color version for level x

Located in directory with other HELP files.



    ******************** DROP CARRIER ON TWITS **********************

Create your custom TWIT.MSG file(s), if desired.  This file will be
displayed when you use press CTRL-F1, this is less severe than CTRL-END.
This will drop carrier after displaying the message, but otherwise
will not penalize the caller.  Some sysops suggest putting fake line noise
in the TWIT.MSG.  The color and graphic versions are used if they exist and
smart text is supported.



    **************** MARKED TIME DISPLAY "TWIRLIE" ******************

This version of RBBS-PC has been modified to replace the "marching dots"
that were displayed to show that RBBS was busy doing something (like
loading the message base into memory).  The "Twirlie" is configurable
in CONFIG parameter 354.


Parameter #354. 4 characters displayed when reading files ---- -\|/

 If you do not enter anything in this field, RBBS will use the STOCK
 marching and declining DOTS as it always has.

   Here are some examples for you to use for twirlies:

   These characters can be made by holding down your ALT key and
   typing the numeric values given:


    250        47  /      16        220       3      180  

    249        45  -      31        222       4      193  

    111  o     124  |      17        223       5      195  

     79  O      92  \      30        221       6      194  

 When entering these into CONFIG, the 4 characters MUST be entered
 in one right after the other with NO SPACES, NO COMMAS,  NO SEMI-COLONS,
 AND NO QUOTES.

You may also use normal text.
On some systems, it may be appropriate to use the following four characters:

W
A
I
T



    ******************** QUOTING with Initials **********************

RBBS QUOTING in Messages now uses the Initials and a greater than
sign, instead of simply a greater than sign.



    ********************* Security Violations ***********************

If a caller's security level is reduced due to a security violation,
their new level is set to -32767 instead of 1 less than the current
level to log on to the current node.  This was done because different
nodes may be set up for different "log on" levels.  A user who is
reduced could potentially log back on to a different node.



    **************** New Information for DRSTx.DEF ******************

 Here is the new information written to the DRSTx.DEF file in this
 order right after the CBAUD entry:

    - Get extended desription
    - auto logoff requested
    - HS link transfer
    - was a batch transfer
    - who to personal upload
    - already given description
    - speed factor
    - MENU0 - new date
    - MENU0 - new time
    - MENU0 - new upload
    - MENU0 - new users
    - MENU0 - new calls
    - MENU0 - new sysop
    - RIP test
    - upload sub dir
    - get desc after transfer
    - ext file system processor
    - CD Rom
    - Doored to
    - is this a personal download


    ******************** COLORS Definition File *********************

With this version, RBBS-PC becomes more flexible with color definitions.
You will find that the default colors displayed throughout the system are
starting to take on an organized approach.  For example, general information
is displayed in cyan, whereas system information takes on a yellow color
for the heading and white for the data.  There is more work to be accomplished
in this area, but an understanding of why certain colors are being used will
help you understand the existance and uses of the external color file.

Parameter #344. Path\Filename of external color definitions -- D:COLOR.DEF

The important information in the COLOR.DEF file is the ANSI escape
sequences and the order in which they occur.  The tilde character (~)
causes the remaining text on the line to be ignored so a line that begins
with a ~ is skipped.

The first ansi code thats occurs is assigned to the RBBS variable ZFG1$
which is, by default, GREEN.  This variable is being used wherever you
might see green in your RBBS command line or display messages.  It is ALSO
used for Smart Text color C1.  SO if you change [0;40;32m to something else,
such as the sequence for RED [0;40;31m then you will change all of the green
displays to red. You will also change anything that is using Smart Text C1.


~ Color file for  RBBS-PC 17.5
~ Text appearing after the pipe character ("~") is ignored
~
~ ANSI Escape  Internal   Smart Text            Color Status
~  Sequence    Variable  Code & Color
~================================================================
[0;40;32m     ~ ZFG1$    C1   GREEN              Foreground
[0;40;33m     ~ ZFG2$    C2   YELLOW                 "
[0;40;35m     ~ ZFG3$    C3   MAGENTA                "
[0;40;36m     ~ ZFG4$    C4   CYAN                   "
[0;40;31m     ~ ZFG5$    C5   RED                    "
[0;40;34m     ~ ZFG6$    C6   BLUE                   "
[0;40;37m     ~ ZFG7$    C7   WHITE                  "
[1;37;44m     ~ ZFG8$    C8   WHITE ON BLUE  Foreground/Background
[1;34m        ~ ZFG9$    C9   BRIGHT BLUE        Foreground
[1;32m        ~ ZFGA$    CA   BRIGHT GREEN           "
[1;36m        ~ ZFGB$    CB   BRIGHT CYAN            "
[1;31m        ~ ZFGC$    CC   BRIGHT RED             "
[1;35m        ~ ZFGD$    CD   BRIGHT MAGENTA         "
[1;33m        ~ ZFGE$    CE   BRIGHT YELLOW          "
[1;37m        ~ ZFGF$    CF   BRIGHT WHITE           "
[0;30m        ~ ZFGG$    CG   BLACK                  "
[40m          ~ ZBG0$    G0   BLACK BACKGROUND   Background
[44m          ~ ZBG1$    G1   BLUE BACKGROUND        "
[42m          ~ ZBG2$    G2   GREEN BACKGROUND       "
[46m          ~ ZBG3$    G3   CYAN BACKGROUND        "
[41m          ~ ZBG4$    G4   RED BACKGROUND         "
[45m          ~ ZBG5$    G5   MAGENTA BACKGROUND     "
[43m          ~ ZBG6$    G6   BROWN BACKGROUND       "
[47m          ~ ZBG7$    G7   WHITE BACKGROUND       "
~================================================================
~ Maximum of 24 colors.  16 foreground, 8 background.
~ All have SmartText Codes.
~
~  {C0 is the foreground color reset

WARNING:  The COLORS.DEF file must have 24 active lines to cover
all of the ZF and ZB variables.




    ************************ NEW SMART TEXT *************************

 With the new external color definitiona file, we now have 23 Smart
 Text colors.  The defaults are:

    ----------------------------------
    C1  GREEN              Foreground
    C2  YELLOW                 "
    C3  MAGENTA                "
    C4  CYAN                   "
    C5  RED                    "
    C6  BLUE                   "
    C7  WHITE                  "
    C8  WHITE ON BLUE  Foreground/Background
    C9  BRIGHT BLUE        Foreground
    CA  BRIGHT GREEN           "
    CB  BRIGHT CYAN            "
    CC  BRIGHT RED             "
    CD  BRIGHT MAGENTA         "
    CE  BRIGHT YELLOW          "
    CF  BRIGHT WHITE           "
    CG  BLACK                  "
    G0  BLACK BACKGROUND   Background - Background RESET
    G1  BLUE BACKGROUND        "
    G2  GREEN BACKGROUND       "
    G3  CYAN BACKGROUND        "
    G4  RED BACKGROUND         "
    G5  MAGENTA BACKGROUND     "
    G6  BROWN BACKGROUND       "
    G7  WHITE BACKGROUND       "


If you use a background color, you MUST use a G0 to reset the backgound
color.  Otherwise, EVERTHING will use that background.


    The following Smart Text assignments are in addition to those
    in the 17.4 Documentation.

    The next three are used with the external FMS header
    ----------------------------------------------------
    FD  Directory to search
    FH  Search string
    FC  Category description

    LT  Time lock period elapsed
    DC  Dropped Carriers
    BA  Baud Rate
    BT  Banked Time
    TP  Transfer Protocol



    ***************** BUILT-IN CD SUPPORT Library *******************

With this version of RBBS-PC there is a new feature that will be
of great interest to the SysOp who has CD-ROM drive(s) online.
RBBS can now support all CD-ROM disk(s), while still maintaining
compatibility with the PC-SIG feature.

In addition, this support includes:

 1) The ability to copy the file from the CD to a directory on
    your hard disk drive.
 2) The creation of a semaphore file for notification to other
    nodes (in a multinode setup) that the CD is busy.
 3) Will wait 30 seconds or till clearing of the semaphore file
    (whichever is less) to copy the file.
 4) Supports as many drives as you have online (drive letters).
 5) Supports multidisk changers like the Pioneer DRM-600.

The following is the method to set up the CD-ROM feature.  It requires that you
use RBBS's FMS (File Management System) for EACH CD-ROM disk.

First, you must create an FMS listing for EACH CD-ROM disk.  Since most good
disks come with an ALLFILES.BBS, half of the work is done for you.
And best of all, since this is a CD-ROM, you only have to create the
necessary files once. You MUST create the FFS files for each disk. It is
recommended that you use a separate directory to store the files for each disk.

Consider the following example:

You have 2 CD-ROMs online.  The first, The Shareware Studio Vol. III,
has it's necessary files located in your C:\RBBS\SWS3 directory.
The second, The MegaWinOS2, has it's files located in your C:\RBBS\MEGAWIN2
directory.
If there were more disks, you could have each disks files in separate
directories (though this is not necessary).  This makes it easier if you
should have to do any trouble shooting later, or when you remove a disk.

Back to our example, here is a list of the files that might be associated
with the Shareware Studio Vol. III disk:

FMS.SW3       - the FMS file for listing
SWS3.CAT      - the directory catalogue (DIR.CAT) for this disk
DIR.SW3       - the directory of directories for this disk
CDFIDX.DEF    - the FFS file index for this disk
CDLIDX.DEF    - the FFF location index for this disk
CDFIDXT.DEF   - the FFS tabs file for this disk

ALL of the above files might reside in your C:\RBBS\SWS3 directory.

In order to signal to RBBS-PC that you are using the RBBS Library
function, you must then create a file named CDRx.CFG (x being the node number)
for EACH node.
This file is located in the node work directory (where you told CONFIG
that the CALLERS file is located).

The reason for having a configuration file for EACH node is for the SysOp
who may want to limit access by node, and for the SysOp who may have
multiple drives online, and wishes to limit which drives are accessable
from each node.

The contents of EACH line in the CDRx.CFG file is as follows:

(Sample - line wrapped for printing purposes - see sample CDR1.CFG)
Shareware St,C:\RBBS\SWS3\FMS.SW3,DIR.SW3,SWS3.CAT,CDFIDX.DEF,CDLIDX.DEF,P,Y,N,
|     1    | |         2        | |  3  | |   4  | |    5   | |   6    ||7|8|9

K:\RBBS\FILES\UPLOAD\NODE1\,5
|           10             |11

So as you can see, there are 11 parameters.  They are as follows:

1:  The name of the disk that you want shown to the user.  This will be
    truncated to the right margin the user has set.
2:  The <drive>\<path>\filen.ame  of your FMS list.  Drive and path MUST be
    included since the same drive and path is used for the following parameters.
3:  The name of your directory of directories (DIR.DIR) file.
4:  The name of your directory catalogue file (DIR.CAT).
5:  The name of your FFS file index file. (FIDX)
6:  The name of your FFS file locator file. (LIDX)
7:  The drive letter for this disk.  Used in creation of semaphore file to lock
    out only the particular physical drive.
8:  Whether to copy files to hard drive before downloading. "N" disables copy
    feature...anything else will enable.
9.  A "Y" indicates multi-disk changer(s) (like the Pioneer DRM-600).  Anything
    else indicates separate physical drives.  This parameter is used in the
    creation of the semaphore lock out file for copying files to the hard drive
    on multinode systems.  Instead of locking out the individual physical drive,
    as with separate CD-ROM drives, the semaphore will physically lock out
    the entire multichanger from access by another node while a file is being
    copied. (see separate section on multichangers below)
10. <drive>/<path> where you want the files copied to from the CD-ROM drive.
    This will be used if you have enabled the copy feature in parameter 8.
    If left blank (ie: ",,") then this defaults to one directory (named
    "NODE" + the node ID) below your upload directory as listed in CONFIG
    parameter #208.  (ie:  if your upload directory is C:\FILES\UPLOAD and
    this is node 1, the CD-ROM copy directory would be C:\FILES\UPLOAD\NODE1)
    NOTE:  The <drive> MUST be a valid drive.  A RAM disk can be used.
           Make sure there is enough space (memory) dedicated to the RAM
           disk to allowing multiple files to be copied.  When first used
           RBBS will create the path if it does not exist.
11. Security level to download/view files from this disk.  Each disk can
    have a separate security level.

You will have one line of entry per CD-ROM disk you are putting online.

THERE MUST BE 11 PARAMETERS......10 COMMAS IN EACH LINE!

The tabs file will be found from the name of the FFS file index.  ALL files will
use the same path as determined from your FMS file.  You can have as many
separate lines in the config file as you have disks that you want the user to be
able to access and string space enough to display.  All parameters MUST be
separated by commas.  There can be NO blank parameters.

You must tell CONFIG param #301 a drive letter.  Since this implementation does
not use this drive letter, you can put ANY valid drive letter in here.
You might use the drive letter of the drive where my upload directory is
located.  In CONFIG param #31 be sure to have a valid command for the Library
listed.  A lot of SysOps have replaced the "@" with a blank space to disable
the library function. In CONFIG param #130 make sure the security level to
access the "@" command is set to one your users can access.
In addition, set the "A" command (archive) to a blank in CONFIG param #310
(since the archive function is not used).  Make sure that you have enabled
the security levels for the remaining Library functions in CONFIG param #311.
Finally, you will want to have a menu for display listed in CONFIG param #309.
 You can ignore most of the other library params since they are not
implemented in this setup.

That's it.  When a user enters the library area, the CD-ROM disk listed in the
first line of the CDRx.CFG file will be the default disk.  If you have more
than one disk listed in your CDRx.CFG, then when the user enters the "C" command
(for change disk), he/she will be presented with a list of all the disks you
have listed in the CDRx.CFG file.  As each disk is selected, the file system
files that correspond to that disk will be loaded.  When the user leaves the
library, the default file system files (for your regular files system) will be
reloaded.  Since you can set download security in the library area separately
from the files area, a user can have download privileges in the files system,
and be denied download privileges in the library system.  And since EACH
CD-ROM disk has it's own security level, you can have multiple levels of
CD-ROM access allowing users with different security levels different disks
to download from.

When a user downloads a file, the file, found through the fast file system, is
copied to your hard drive.  This eliminates the excess load that can slow a
system dramatically (especially in multitasking environments).  A semaphore
file (named CDROMx.WRK - where x is the drive letter for the disk) is created
in the main RBBS directory, indicating that the CD-ROM drive is busy, and
denying other nodes from accessing the drive.  If you have MultiDisk Changer(s)
then see the note below.  Other nodes will wait till either the flag is cleared,
or time out in 30 seconds.  If the flag clears, they will then start to copy
their files.  (Thirty seconds was selected for the slower CD-ROM drives and
large files. Some may notice a big difference in time between two drives on the
same file.  One drive will take 23 seconds on a 1.1 meg file while the other
only takes 8 seconds.)  When the download is completed (or aborted), the copied
file(s) are then deleted.

* Multi-disk Changers *

     If you have a MultiDisk changer that only has one laser head and
     swaps disks or multiple MultiDisk changers (don't I wish), then set
     parameter #9 in the CDRx.CFG file to "N".  Set the drive letter for
     EACH disk in the changer to the SAME letter (the drive letter of the
     first disk) in CDRx.CFG parameter #7.  This will effectively lock out
     the entire changer when any disk from that changer is selected since
     ALL the disks from that changer have the same drive letter.  This will
     NOT affect the location of the files since the Fast File Search System
     (FFS) is utilized to locate the file.



    ****************** PERSONALIZED RING SUPPORT ********************

   In many locations, the phone companies offer a service that is known
as 'Personalized Ringing', Distinctive Ringing', and other various
names.  This service allows one phone line to have 2 or 3 phone numbers
associated with the one line. Depending upon which number is called, a
different ringing pattern will be heard on a phone connected to this
line.  For example, one line may be assigned 111-1111 and 111-2222. When
the first number is dialed by someone, the ring heard on this line will
be a regular sounding ring.  But when the second number, 111-2222, is
dialed by someone, the ring heard consists of 2 short rings in the
amount of time that 1 regular ring normally occurs. Imagine that the
dashes in the following diagram represent ringing on this line and you
will be able to see the difference:

        NORMAL RING -

      ------------------------- PAUSE -------------------------

        SHORT PERSONALIZED RING -

      ------ SHORT PAUSE ------ PAUSE ------ SHORT PAUSE ------

   This service allows a person to have 2 different phone numbers but only
have 1 phone line!  What's really great is that this service is usually VERY
inexpensive (somewhere around $5 to $8 installation and $2 per month for each
additional number past the first (up to 3 numbers total on a line).  (This
service may not be available on what the phone company calls 'hunting lines'.
A hunting line is a line on which a call can 'roll over' to or from another
line.  This is the type of line that most businesses have when they have more
than 1 line.  Personal Ring service is usually ONLY available on single,
dedicated lines, however, check with your phone company, as this may vary from
phone company to phone company).

   This is ideal for someone who wants to share 1 line with 2 or 3 different
devices.  For example, 1 line can be shared with a FAX machine and with a BBS!
The disadvantage to this arrangement is that most BBS's do not have the
capability of detecting the different ring patterns, thus an additional piece
of equipment is needed to decode these different rings. This is still better
than paying monthly for 2 or 3 lines, but it would be great if a BBS could
detect these differences without any additional hardware.

   This is where this feature for RBBS comes into play!  It allows this very
thing.  At the present time, it will allow RBBS to answer the phone on either
the regular ring or on a 2-short ring pattern as shown above. This works quite
well if RBBS is set up to answer the line that rings with a normal ring
pattern and the other device (FAX or answering machine) is set to answer on 4
or more rings.  In this case, RBBS will answer after the second normal ring
(just in case the first ring is abnormally short), but if the incoming ring is
the 2-short pattern, RBBS will ignore it and the FAX or answering machine can
then answer on the 4th (or more) ring.



                   **   USING THE PERSONAL RING FEATURE  **

   Using the Personal Ring feature is also very easy.  To tell RBBS which ring
to answer on, select parameter 225 in the RBBS CONFIG program.  Then, include
in item 2 (INITIALIZE THE MODEM) S0 = 252 to tell RBBS to answer on the
2-short ring pattern or include S0=253 to tell RBBS to answer on the regular
ring pattern.  When RBBS is running, it will decipher this MODEM INITIALIZATION
STRING and determine which number S0 is set equal to.


    *****************************************************************
    *                                                               *
    *                                                               *
    *        **********************************************         *
    *        **                                          **         *
    *        **        SUPPORT FOR UP TO 99 NODES        **         *
    *        **                                          **         *
    *        **********************************************         *
    *                                                               *
    *                                                               *
    *****************************************************************


RBBS-PC version 17.5 increases the maximum number of nodes
from 36 to 99.   However, this change means that your set up of
RBBS-PC 17.4 will not work equivalently and requires some conversion.
There are two kinds of changes:

   1)  You must edit your batch file invoking RBBS-PC (normally
       RBBS.BAT) because some system files have changed their
       names

   2)  You must change the file transfer file written out by
       external file transfer utilities, or use a batch file
       to rename or copy the file the utility writes out to
       what RBBS now expects.

   3)  Doors expecting to get their Door information from the
       BBS will either have to be told another file to look for,
       or the batch file processing the door will have to rename
       or copy the door information file RBBS writes out to the
       name the door is expecting.

   4)  If you have more than one node and are using configuration
       files in the format RBBSnPC.DEF, you must either rename
       these files or change the command line invoking RBBS-PC.EXE.

                        New Names

The added nodes require that system files of rbbs with
the node ID be redefined to have fewer characters in the file
name prefix, and requires that references to the files therefore
be converted.   The following are the name changes:

function              old name     new name

configuration         RBBSnPC.DEF  RBBSn.DEF
timed exit            RBBSnTM.DEF  RBTMn.DEF
F1 pressed            RBBSnF1.DEF  RBF1n.DEF
node work file        NODEnWRK     NWRKn
arc work file         ARCWORKn.DEF AWRKn.DEF
door information      DORINFOn.DEF DINFn.DEF
transfer report       XFER-n.DEF   XFERn.DEF

                       RBBS Batch File

The files normally referenced in your RBBS.BAT are RBBSnTM.DEF and
RBBSnF1.DEF.  Therefore, these references must be changed.  For example,

IF EXIST RCTTY.BAT DEL RCTTY.BAT
IF EXIST RBBS1F1.DEF DEL RBBS1F1.DEF
IF EXIST RBBS1TM.DEF DEL RBBS1TM.DEF
RBBS-PC
IF EXIST RBBS1F1.DEF GOTO EXIT
IF EXIST RCTTY.BAT RCTTY.BAT
IF EXIST RBBS1TM.DEF TIMEEXIT.BAT
RBBS
:EXIT

would have to be changed to

IF EXIST RCTTY.BAT DEL RCTTY.BAT
IF EXIST RBF11.DEF DEL RBF11.DEF      <-- new
IF EXIST RBTM1.DEF DEL RBTM1.DEF      <-- new
RBBS-PC
IF EXIST RBF11.DEF GOTO EXIT          <-- new
IF EXIST RCTTY.BAT RCTTY.BAT
IF EXIST RBTM1.DEF TIMEEXIT.BAT       <-- new
RBBS
:EXIT

A new, standard RBBS.BAT is enclosed.


                         File Transfer Report

RBBS now looks for the file "XFERn.DEF" instead of "XFER-n.DEF".
For DSZ, just change "SET DSZLOG=XFER-n.DEF" to "SET DSZLOG=XFERn.DEF"
(e.g. "SET DSZLOG=XFER1.DEF").   If your external protocol insists
on writing out XFER-n.DEF, then you will have to change to using
a batch file for the file transfer whose last line is

              ren xfer-%oldnode%.def xfer%node%.def

assuming that the batch variables "%node%" denotes the node number (1,..,36),
and "%oldnode%" is the old node identifier (1,...,9,0,A,...,Z).  Note that
if you have fewer than 10 nodes, you can use one variable.

                          Door Information

Doors that use the RBBS conventional file  DORINFOn.DEF will have to
be told to read DINFn.DEF.   If the door cannot be configured differently,
you will have to add the following line to the top of the door batch
file:

                 ren dinf%node%.def dorinfo%oldnode%.def

assuming that the batch variables "%node%" denotes the node number (1,..,36),
and "%oldnode%" is the old node identifier (1,...,9,0,A,...,Z).  Note that
if you have fewer than 10 nodes, you can use one variable.


                   Configuration File Changes

There are two circumstances in which you will not have to change
anything in your setup:  you have fewer than 10 nodes, and either

  1)  you have only one node and use the standard "rbbs-pc.def", or

  2)  you explicitly tell RBBS-PC on the command line what configuration
      file to use (e.g. "rbbs-pc.exe 1 rbbs-pc.def").

If, however, on the command line invoking RBBS-PC.EXE, you specify
merely the node, you must make a change.   You can either

  1) rename the RBBSnPC.DEF files as follows:

        old name         new name
        RBBS-PC.DEF     (no change)
        RBBS1PC.DEF      RBBS1.DEF
            .
            .
            .
        RBBS9PC.DEF      RBBS9.DEF
        RBBS0PC.DEF      RBBS10.DEF
        RBBSAPC.DEF      RBBS11.DEF
            .
            .
            .
        RBBSZPC.DEF     RBBS36.DEF
         (none)         RBBS37.DEF - RBBS99.DEF

or 2) you can keep the old .DEF files, but then you must specify
      the configuration file to use explicitly on the command line
      invoking RBBS-PC.EXE.   The general format for invoking RBBS-PC
      is

          RBBS-PC.EXE n <cnfgfile> /x1 /x2 /x3 /x4

      where n is node number, <cnfgfile> is the config file to use,
      and the parms beginning with "/" are for invoking RBBS-PC after
      a front end answers the phone and RBBS-PC is supposed to take
      a call in progress.   For example, if you use "rbbs-pc.exe 2"
      and want to use config file RBBS2PC.DEF with 17.4A, simply
      invoke RBBS-PC as follows:

                 RBBS-PC.EXE 2 RBBS2PC.DEF

Note:  if you have 10 or more nodes, you must change something in your
set up for nodes 10 or higher, because the nodes are no longer 0,A,...,Z
but rather now 10,11,...,36.   For example, if you invoke RBBS-PC using

                        RBBS-PC.EXE %NODE%

Then you must change the value of "%NODE%" (e.g. "SET %NODE%=0"
becomes "SET %NODE%=10").  Similarly, "RBBS-PC.EXE A" have to be changed
to "RBBS-PC.EXE 11".

NOTE:  Some doors are "hard coded" to look for the XFER-?.DEF file.
       There a nice kludge to handle this. Use a SET DSZLOG=XFER-1.DEF
       before you invoke the door and then a SET DSZLOG=XFER1.DEF after
       the door (in your batch file that calls the door).

                     Message Bases other than MAIN

The max number of nodes specified in message bases other than the
main message base used in logon can have any number of nodes, independently
of the one in main.  It is not necessary that when you increase the #
of nodes in main, that you change subboards and conferences.  RBBS 17.4A has
been modified to make this fully true.   For example, you may have 90
nodes in main, but can specify only 1 in conferences, if you choose.






     ****************************************************************

                        ---  ACKNOWLEDGMENTS  ---

   So,

   You made it all the way through this document.  Congratulations.

  You can see that this beta represents a substantial change to RBBS-PC
  The purpose of this wide beta is to provide an official cornerstone
  on which to build upon.  Your assistance is requested as we continue
  to optimize the code and incorporate features to make RBBS-PC the best
  BBS software.... at any price.


  The persons who have contributed to this release include:

           ___________________  <--  fill in your name here.


    *****************************************************************


