Beijing Paradise BBS Backup

home *** CD-ROM | disk | FTP | other *** search

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / 175B220U.ZIP / RBBSCFG.ZIP / HELPCFG.HLP < prev

Wrap

Text File | 1994-08-03 | 66.2 KB | 1,340 lines

#1#2# The RBBS-PC system operator's (SysOp) first and last name. Enter your REAL name here (the name you wish your callers to know you by). NO ONE may log in to your RBBS-PC using this name, NOT EVEN THE SYSOP! This is a security feature of RBBS-PC. The SysOp logs on with a "pseudonym" (see parameter 121). #3# The mode (EXPERT of NOVICE) for the SysOp. This option is now obsolete. The SysOp may use the RBBS-PC eXpert command. #4# The SysOp's "office hours", or when a user can page the SysOp. If a caller attempts to page you outside these hours, he will be told you are not available, and RBBS-PC will suggest that he try a MSG or a COMMENT. The times are set using a 24-hour military clock (i.e. 10:00 P.M. is 2200 hours). The SysOp can disable a caller's ability to page him COMPLETELY by pressing the function key F4 while RBBS-PC is running. F4 toggles the SysOp page status off and on. #5# Because the bell on an attached printer is often louder than the one built into the PC, the SysOp can elect to have the printer's bell used, rather than "beeping" the PC's speaker. #6# Should RBBS-PC automatically take itself off-line if a "disk full" condition occurs. In some instances, such as having a small disk volume for uploads, you may want your RBBS-PC system to remain online, even though it is getting disk space full errors. #7# The default setting for the "prompt bell". The prompt bell refers to a preference some callers have of getting a short "beep" from the system, whenever it pauses for input at a prompt. When this is on, both the remote user and the local SysOp will hear the prompt bell when input is required from the remote user, unless and until this option is changed with the Toggle command on the Utility menu. #8# The maximum amount of time (in minutes) each user is to be allowed on the system per session (the "session" refers to any individual call to the bulletin board). This is the default time limit, which only takes effect if the PASSWRDS file does not override. See section 15.3). CDOOR: Set to highest amount of time you allow for any security level as set in your PASSWRDS File #9# The default total amount of time (in minutes) a caller is allowed on RBBS-PC per day. This is the default time limit, which only takes effect if the PASSWRDS file does not override. See section 15.3). CDOOR: Set to ZERO and let PASSWRDS control Max mins per day #10# This allows a SysOp to "reward" users who upload files by adding time to the users session when they upload. This number will be multiplied by the time spent in upload, and credited to the user. Setting this parameter to 1 will give back the user as much time as they spent uploading, so their session time will look "frozen" during upload. These time credits are normally removed at the end of a day, unless the ratio you set is greater than 1. If so, CONFIG will ask if you want to make the time credits "survive." If so, the extra time granted the user will be available indefinitely, instead of only for the current day. #11# The number of months inactivity that must elapse before a user is considered a candidate for deletion from the USERS file when the SysOp "rebuilds" it. #12# Allows the SysOp to specify the name of the RBBS-PC that is to be displayed when a user first connects with the system and prior to completing the logon process. #13#14#15# Allow the SysOp to specify the colors desired for the console display. Foreground, Background, and Border may be set. When specifying colors, use the following: 0 = Black 4 = Red 1 = Blue 5 = Magenta 2 = Green 6 = Brown 3 = Cyan 7 = White Add 8 to any number to set high intensity. Add 16 to turn blink on. #16# If the RBBS-PC computer can support ANSI, RBBS-PC will send ANSI control sequences to display color and position the cursor. The local display does NOT have to support ANSI in order for callers to receive ANSI commands, although it does make the "snoop" function readable. CDOOR: Install ANSI.SYS, DVANSI.COM or any other ansi driver #17# The decimal value (0 to 255) of the character used to identify "SmartText" codes. This should ALWAYS be set to 123. See section 7.9 for a detailed discussion of SmartText. #18# The file name that contains the information to control the "automatic" RBBS-PC paging of the SysOp. See section 7.11 for a detailed description of the AutoPage feature. #19# The level of detail to use when notifying callers of electronic message. This can be set to (A)ll (old and new mail notifications), (N)ew mail only, or (S)kip (no notification). See section 18 to get a better understanding of the full flexibility of mail waiting notification that has been built into RBBS-PC. #20# Seconds for RBBS to try and establish grahics mode by communicating with the callers terminal CDOOR: set to 2 or 3 secs #21# Instructs RBBS-PC to remind users not only of the messages that are for them, but also messages that they have left. This is to encourage users to delete their old mail and help to keep the MESSAGES file to a minimum. CDOOR: Who's on will always show offline callers to sysop #22# Instructs RBBS-PC to remind users, when they login, how many files they have downloaded and uploaded. #23# Reminds users every time they log on of the preferences they have selected for such things as file transfer protocol, graphics, nulls, etc. #24# Allows users to download files immediately upon logging on to RBBS-PC. Parameter 24 is only meaningful if the RBBS-PC File Management System (FMS) has been enabled via parameter 214. RBBS-PC will scan FMS for the newest uploads. When a caller logs on, RBBS-PC will determine how many files are new since the caller last logged on. If parameter 24 is YES, the caller is offered the chance to immediately review these new files and download them, if the caller has sufficient security to download. This happens before the bulletins or messages are reviewed. RBBS-PC's that emphasize software exchange may want to enable this option, others may not want to give the caller a chance to download the new files until after bulletins and messages have been reviewed. #25# Allows the SysOp to establish a default page length for users when they log on. The valid range is 0 to 255. If set to 0, the user will receive continuously scrolling output. #26# The maximum number (from 1 to 99) of lines allowed in each message. CDOOR: you may allow up to 199 lines per msg #27# Allows the SysOp to make the system "welcome" file interruptible. The default is that YES it is interruptible. However, if the SysOp feels too many people are bypassing it and it contains essential information, the SysOp can set this parameter to NO (i.e. the user can not suspend or cancel the listing of this file at their terminal with a CTRL-S or CTRL-K). If the welcome file has intricate graphics, interrupting it may leave the caller's screen in an odd color. #28# Allows the SysOp to indicate if the system bulletins are optional for users when they log on. If bulletins are optional, callers can elect to automatically bypass old bulletins and be notified only when there are new bulletins. RBBS-PC will check the file date of the bulletins and inform the caller which are new, with the option to read all of the new bulletins. If none are new when bulletins are optional, the bulletins will be automatically bypassed. See section 7.13. #29# Tells RBBS-PC how to handle non-standard systems. The Compaq/Plus uses interrupt X'7F', which is also used by MultiLink. RBBS-PC may incorrectly detect MultiLink on a Compaq/Plus or other system that makes use of interrupt X'7F', unless you select computer type 1. The IBM PCjr's non-standard comm port mapping can be overcome if you select computer type 2. Type 0 (IBM) and 3 (other) are treated the same. #30#31#32#33#34# The symbol used to activate each online command can be changed. You can substitute any keyboard character for each command. To disable a command, enter a single space for the symbol. One reason to change commands is for macros. If you want to write an RBBS-PC macro that acts as a "front end" for the command, you should first change the symbol of the command to an unused, "hidden" symbol. Next, create the macro, naming it the same as the original key. In the macro, you can activate the original function by using the new "hidden" symbol. CDOOR: 30) Enter Yes to get '8' in sysops commands 31) change the good bye command from '@' to 'G' 33) change the who from 'C' to 'W' #35# Allows the section name to precede the command prompt. The section is MAIN, FILE, LIBRARY, or UTIL, if this option is selected. Otherwise, the prompt will begin with YOUR. Normally the section in the prompt helps the caller remember where he is, but see section 7.5 for reasons to suppress the section. #36# Suppresses the display of commands in the command prompt. By default, RBBS-PC reminds the caller what commands are available by giving a sorted list of the letters used for each command in the command prompt. RBBS-PC shows only the commands available in the section that the caller is in. #37# RBBS-PC will either restrict commands to those in the current section, or will look in ALL sections for a valid command that matches the caller's request. See section 7.4. #38# Instructs RBBS-PC to use machine language subroutines (rather than the BASIC routines) for selected functions. RBBS-PC includes both BASIC and machine language versions of several functions. The machine language version is much faster, but may cause problems with some non- standard systems. Normally, you should activate the machine language version, but if you encounter erratic behavior, especially in locating files on a machine that may not be 100% IBM compatible, try using the BASIC subroutines. #39# Instructs RBBS-PC to use the BASIC language's PRINT statement to write to the screen of the PC that RBBS-PC is being run on. This is sometimes necessary in "hostile" environments (i.e. multitasking, special screen drivers, etc.) where the use of RBBS-PC's default call to the RBBS-PC screen driver ANSI is not viable. CDOOR: this option turns on the sequential callers text logging #40# The maximum number of additional lines that a caller can use to describe a file that was uploaded. It applies to both single FMS directories and non-FMS directories. NOTE: This number counts the EXTENDED description lines. RBBS-PC always allows a single-line description. #41# Determines how callers are to be identified when they log in. By default, RBBS-PC uses the NAME field in the USER file. You may specify the starting offset of the field, and its size. WARNING: misuse of this parameter could DESTROY your USER file! #42# Allows an additional field to be used to distinguish callers with the same ID (see section 8). Normally, this item is set to 0, which instructs RBBS-PC to not allow callers with identical IDs. #43# The offset into the USER record to be used to identify a user for PERSONAL downloads. By default, RBBS-PC uses position 1, which is the start of the caller's name. #44# The length of the field used to identify a user for PERSONAL downloads. By default, RBBS-PC uses 31 (the maximum length of a user's name). The entries in the personal download directory must have exactly this many bytes at the end -- plus one (for the flag used to indicate if the file has been download). #45# The prompt that RBBS-PC should use when asking the caller for the first ID field. When prompting for this input, RBBS-PC will prepend "What is your" to the prompt. #46# The prompt that should be used for the second ID field. #47# Activates upload/download ratios. See section 15.3 for a discussion of the flexibility of RBBS-PC ratios. NOTE: If you elect to enforce ratios, fields in the USER record are used to store ratio information. See Appendix A for details. #48# Activates automatic security level reduction via Subscription date. See section 9 for a complete explanation of subscriptions. #49# The security level to which callers will be set when their subscription expires (see section 9). #50# The number of days BEFORE a caller's subscription is to expire that RBBS-PC will send warnings. The file RGXPIRE.HLP can be customized to inform the caller that the subscription is about to expire, and what to do. #51# The default number of days in a subscription period. When a caller logs in this many days after their subscription began, RBBS-PC will notify them of the expiration, display the file RGXPIRD.HLP, and reduce their security to the level specified in parameter 49. #52# Instructs RBBS-PC to turn off printer logging each time RBBS-PC "recycles" at the end of a call. Since printer errors will often "hang" a system (especially if no printer is present), this function can avoid errors caused by the SysOp accidentally activating RBBS-PC's printer log function. Of course, if you wish to use the printer logging feature, you must set this parameter to NO. #53# Instructs RBBS-PC to play musical themes for auditory feedback on what is happening on the BBS. This can be important for SysOps that are sight impaired. These musical themes are "played" on the speaker of the PC that is running RBBS-PC, but not transmitted to the caller. #54# The buffer size used internally by RBBS-PC when displaying text files such as menus, directories of files, etc. The size can range from 32 to 4096 characters. The bigger the buffer, the fewer disk accesses necessary to display the file and the faster the display will be. The default of 128 is the minimum recommended. Increasing this to 512 will increase the speed of text displays. However in some environments where it is important to respond quickly to XON/XOFF control, this should be set to the minimum of 32. CDOOR: set to 32 #55# Sets the size of RBBS-PC's internal "stack." The internal stack is used by RBBS-PC to keep track of program flow. The recommended value is 2048. If you must conserve RAM usage, this number can be decreased, but program errors such as "Stack overflow" and "String Space Corrupt" could result. CDOOR: set to 2048 #56# empty #57# Specifies the prompt RBBS-PC should use when requesting the caller's city & state. If you would like to record information other than city & state in this USER field (telephone number, for example), change this prompt accordingly. #58# Specifies how directories are sorted when a caller requests a list of ALL download directories. You can either specify no sort, or the directories can be shown in the order they appear in the "directory of directories." #59# Specifies the buffer sized used during INTERNAL protocol transfers. This is the amount of data stored before it is written to disk on upload, or the amount read from disk at a time on download. The range is 128 to 8192 characters (1024 is recommended). #60# Specifies that either a Computalker (B.G. MICRO, P.O. Box 280298, Dallas, Texas 75228) or HEARSAY 1000 (HEARSAY Inc., 1825 74th Street, Brooklyn, N.Y. 11204) speech board is being used. This is in support of the sight impaired SysOps. These voice synthesizers can speak status messages that are usually either written to the CALLER log or printed to the printer. With this, a sight-impaired SysOp can hear what the caller on the BBS is doing. CDOOR: removed, set to none #61# The path and name of the text file that describes the BULLETINS. RBBS-PC uses the path of this file to find ALL bulletin files. #62# Instructs RBBS-PC to use "numbered" bulletins, and tells RBBS-PC how many numbered bulletins to look for (see section 7.13). #63# Specifies the PREFIX of the Bulletin files. Ex: If the prefix is "B", and a user asks to see bulletin INFO, RBBS-PC will look for the file "BINFO" in the same directory as the file specified in parameter 61. Additionally, if the file "BINFO.MNU" is found, RBBS-PC will activate the Sub-Menu feature (see section 7.7). If the user has specified graphics or color display, the files, RBBS-PC will also search for the files "BINFOG" and "BINFOC" (see section 6.3). #64# Specifies the disk drive and path on which RBBS-PC will find on-line "help" files. #65# Specifies the prefix for the last remaining "old-style" help files. These files are supplied with RBBS-PC, and the prefix is "HELP." There is no reason to change this parameter. #66# Specifies the EXTENSION for the "new-style" help files. A full set of online help is provided with RBBS-PC. There is no reason to change this parameter, but if you do, all .HLP files must be renamed. Any additional help files you wish to create should have this extension, and be in the directory specified in parameter 64. If so, RBBS-PC will treat your help files as if they were part of RBBS-PC, displaying them to callers when they are requested. #67# The help file shown to callers when RBBS-PC asks them to categorize an upload. With FMS directories (see section 12), a caller can specify the category code for their upload. You need only specify the base file name in this parameter. RBBS-PC will add the help file PATH (as specified in parameter 64) and the EXTENSION (as specified in parameter 66). This file should contain a description of each category, so the uploade can properly categorize the upload. #68# The path and filename of the file new users see when they first log on and before they "register" themselves in RBBS-PC's USERS file. A user sees it once and only once during his first session. #69# The path and filename of the file each user sees EVERY time AFTER they log on. #70# The path and filename of the SysOp command menu, shown to callers in NOVICE mode who have access to SysOp commands. #71# The path and filename of the MAIN section menu. #72# The path and filename of the FILE section menu. #73# The path and filename of the UTIL section menu. #74# The path and filename of the Conference description file. RBBS-PC uses this file to when a caller asks for a list of your conferences, and also uses the file to validate a JOIN command. In order for the JOIN to work, the conference name (seven characters or less) must appear IN CAPS, at the beginning of a line (preceding spaces are allowed). The SysOp must already have pre-formatted the messages and users files associated with the conferences (see section 17.3). RBBS-PC will look for conference MESSAGE files in the path specified in this parameter after searching where the main MESSAGE file is located. #75# The path and filename containing the list of the questionnaires callers can answer on-line (see section 19). Before RBBS-PC will allow a caller to answer a questionnaire, it will look for the questionnaire name specified (seven characters or less), IN CAPS, at the beginning of a line in this file (preceding spaces are allowed). #76# The drive and path where the questionnaire files are located. #77# The path and filename of the "Programmable User Interface" to be used. See section 7.6 for a fuller description of RBBS-PC's PUI. CONFIG will add the extension ".PUI" to this file. If this file is not found, RBBS-PC uses the standard interface. #78# Specifies whether RBBS-PC should insert page-breaks in menus. Normally, you will want RBBS-PC to insert page-breaks when needed, unless you have written "full-screen" menus which do ANSI cursor positioning. In this case, the lines in the menu files may not accurately reflect the lines used on the callers screen. #79# The drive and path where RBBS-PC macros are stored. #80# The extension for RBBS-PC macro files (usually .MCR). See section 7.8 for a full description of RBBS-PC's macro capabilities. #81# The path and filename of the "illegal name" file. This file is used when a new user signs on. The new users first and last name are each individually checked against the names in this file, as well as the entire name. The format of this file is as follows: <name>, The comma is optional after each name. However, it does help in delineating exactly what character strings are being searched for and compared against (some text editors may add extraneous and non-visible characters to a line). All names should be UPPER CASE! #82# The path and filename of the "required" questionnaire. RBBS-PC records in the users record when the required questionnaire is answered so that it will only ask each caller once. Both first-time and old callers will be required to answer this questionnaire. When you install a new required questionnaire, use CONFIG parameter 186 to mark all user records so they will once again be required to answer the questionnaire. NOTE: Parameter 82 allows you to specify a path. RBBS-PC will not automatically look in the path specified in parameter 76. #83# The path and filename displayed to callers as soon as carrier is detected and BEFORE a user can log on. It is displayed immediately after the name of the RBBS-PC is shown (see parameter 12). SysOps should use this file to convey such information as whether real names are required, 300 baud users will automatically be denied access, etc. #84# The path and filename of the optional questionnaire RBBS-PC will require new users to answer on their first call. See section 19 for details on RBBS-PC questionnaires. #85# The path and filename of the optional questionnaire RBBS-PC will ask each caller when they log off each time from your RBBS-PC (see section 19). #86# The path and filename of the RBBS-PC message file. This file contains all messages entered by callers, as well as configuration data. If this file does not exist when you run CONFIG, CONFIG will ask if it should create the file. NOTE: Read section 18 if you want to include the main message file in the scan for conference mail waiting. #87# The path and filename of the RBBS-PC USER file. This file is where RBBS-PC keeps track of the name and profile for each caller. #88# The path and filename where RBBS-PC will store comments that callers leave to the SysOp. Even if comments are recorded as private messages (see parameter 89), you should specify a COMMENTS file, since RBBS-PC will place comments here if the MESSAGE file is full. RBBS-PC will automatically create the COMMENTS file when needed. #89# allows SysOps to have comments recorded as private messages to them in the main messages file providing there is any room. This allows replies to comments to be done much more easily. #90# The path and filename for RBBS-PC's CALLER log. RBBS-PC will create this file, and log the date and time of each caller to the BBS. Information such as uploads and downloads, security violations and communications parameters are also logged. SysOp function 2 will display this information. #91# Specifies that RBBS-PC should log the following additional information in the callers log: 1) Connect not completed 9) Left comment at time 2) Sleep disconnect 10) Logged off at time 3) Caller changed name/address 11) Carrier dropped at time 4) Newuser 12) Message # xxxx left at 5) Bulletin x read 13) Read Messages ... 6) SysOp initiated Chat 14) Answered questionnaire xxx 7) Entered Conference/Sub-board x 15) Killed msg # xxxx 8) Time limit exceeded NOTE: Each CALLER log entry uses 66 bytes of disk storage. Using parameter 91 can provide useful information, but you should monitor the size of your CALLER log so it does not consume your entire disk! #92# empty #93# The path and filename for the conference mail-scan file. This file tells RBBS-PC which conferences should be checked when a caller wants to scan for new mail. The format of this file and the flexibility it affords the RBBS-PC SysOp is described more fully in section 18. #94# The maximum number of "working variables" that RBBS-PC allocates for questionnaires and macros. A "working variable" is simply a place in which RBBS-PC can store a response or a set of characters. These "working variables" can then be used to create parameters that can be passed to "DOOR"s (see section 14.3) or written out to data bases (see section 7.8.4). #95#96#97#98#99#100# empty #101# Activates the DOOR function. See section 14 for a complete description of the RBBS-PC door subsystem. #102# The path and filename of the DOOR menu, which RBBS-PC will show to the caller when a list of doors is requested. Before RBBS-PC will allow a caller to open a door, it will look for the door name specified (seven characters or less), IN CAPS, at the beginning of a line in this file (preceding spaces are allowed). #103# The path and filename of the .BAT file RBBS-PC should create when building a "door" exit. The batch file that invokes RBBS-PC must check if this file exists whenever RBBS-PC terminates and (if it exists) execute it (see section 13). This is also the same file name that is used when the SysOp exits to DOS. #104# The path and filename of the .BAT file used to start RBBS-PC. This is used to re-invoke RBBS-PC after a door (see section 13). This is also the same file name that is used when the SysOp returns from exiting to DOS. #105# The DOS subdirectory where RBBS-PC can find the DOS command processor (COMMAND.COM). This is also the location for the .BAT files which test and convert compressed uploads. CDOOR: set to same location as your rbbs home subdirectory #106# The method used to redirect I/O when dropping to DOS as a remote SysOp (command "7"). Answering YES selects the standard DOS "Change Console Command" (CTTY), NO selects the DOS redirect function (">" or "<"). This parameter allows you to specify if the redirected output is to be handled by a SysOp-supplied device driver. If you don't elect to use a special device driver, RBBS-PC will redirect the output directly to the communications port by building the command "CTTY COMx" or ">COMx and <COMx" , where "x" is based on the communications port the node was configured for. If you specify the name of a device driver, RBBS-PC will build the command CTTY [driver name]. #107# The path and filename of a program (i.e. an .EXE or .COM file) that is to run when a new users logs on. This feature is intended for those who feel the need to perform an extensive verification of new users that is not met by RBBS-PC's built in scripting capability or automatic subscription functions. #108# Allows the external program designated via parameter 107 to be invoked for not only new users, but also for callers who have a security level equal to or less than the security level specified in parameter 108. #109# The path and filename of the "DOORS" control file. See section 14.3 for more information. #110#111#112#113#114# empty #115#116#117#118#119# empty #120# empty #121# The first and last name of the SysOp pseudonym. It is this name that causes RBBS-PC to recognize the remote caller as the SysOp and not simply a user with a security level equal to that of the SysOp. This should be a first and last name combination that is not likely to be selected by other callers. The name supplied in parameters 1 and 2 cannot be used by ANYONE to log on. If the SysOp wants to log on remotely, the name in parameter 121 must be used. CDOOR: If offical name and secret name are the same enter here in mixed case #122# If YES, specifies that a LOCAL logon (via the ESC key) should logon as the SysOp automatically. NO will prompt for a name before allowing anyone to log on locally. #123# The minimum security level users need in order to log onto RBBS-PC. Callers with a security level less than this number will be given an "ACCESS DENIED" message and immediately disconnected. #124# The security level assigned to new users. If this security level is less than the minimum security level to log on, no new users can log on. This means that no new users are allowed and access is limited only to pre-registered users. #125# The minimum security level a user must have in order to be considered a SysOp. Even if a user has a high enough security level to see the SysOp menu and execute some or all of the SysOp commands, the user will not be treated as a SysOp (i.e. allowed to see the files upload/download when viewing the CALLERS file) unless the users security level is equal to or greater than that specified by this parameter. #126# The minimum security level required to see the SysOp menu. This does not give a user SysOp access, it only allows him to see the menu of SysOp commands. #127# The minimum security level a user must have to leave an extended (i.e. multiple line) description of a file that was uploaded. See parameter 40 for the maximum number of lines that an extended description will be allowed to have. #128# The maximum number of security violations (i.e. attempts to download protected files) before the user is logged off and locked out. #129# The minimum security level to access each SysOp function. These may all be set to the same level, or each command can have a different minimum security level. #130# The minimum security level to access the MAIN commands. These may all be set to the same level, or each command can have a different minimum security level. CDOOR: Goodbye security should be min needed to log on #131# The minimum security level to access the FILE commands. These may all be set to the same level, or each command can have a different minimum security level. #132# The minimum security level to access the UTILITY commands. These may all be set to the same level, or each command can have a different minimum security level. #133# The minimum security level to access the GLOBAL commands. These may all be set to the same level, or each command can have a different minimum security level. #134# The maximum number of times a user can change their password in a given session. This prevents a caller from "fishing" for special passwords. #135# The minimum security level required in order for users to access privileged group passwords. If the user's security is less than this level, ALL password changes that they make will be permanent -- even if the password they select is in the temporary password file named in parameter 146. #136# The minimum security level required to overwrite on uploads. Users with this security level can REPLACE EXISTING FILES by uploading a file with the same name. #137# The minimum security level "exempt" from packing. When the SysOp packs the user file, callers with this security level or greater will NOT be removed from the user file, even if they have not called in the number of months specified in parameter 11. #138# The default security level of new PRIVATE messages. Only those with this security level or higher can read new private messages -- even if they have been addressed to them. This allows the SysOp to "preview" messages, and then lower the security level of each message so that the addressee can read it. #139# The default security level of new PUBLIC messages. Only those with this security level or higher can read new public messages -- even if they have been addressed to them. This allows the SysOp to "preview" messages, and then lower the security level of each message so that the every user can read it. #140# The minimum security level required to change the security level of a message. #141# empty #142# The drive and path where the "personal" files are located. If a file listed in the directory is not found here, the download drives will then be searched, so it is not necessary to have a copy of a file here in order to use personal downloads. However, files in this directory can be protected so that ONLY personal download will access the files. #143# The name of the "personal directory." If no extension is specified, ".DEF" will be used. If not path is specified, the path in parameter 142 will be used. #144# The default protocol to be used when downloading personal files. If no protocol is specified, the "P" command behaves exactly same as the D)ownload command. If a protocol is specified, it will be used unless overridden by the command line (i.e. "P file.ext Z"). #145# The path and filename of the "file security" list. See section 15.4 for more information. #146# The path and filename which contains the privileged group passwords and security-level limits. See section 15.3. #147# Specifies that multi-file personal downloads using ASCII should be done "non-stop." This is useful if the SysOp wants users to download to a continuous feed printer. #148# The minimum security a user must have in order to "categorize" uploads when the SysOp is using the File Management System (FMS). Uploads by callers with insufficient security to categorize will be placed in the default "upload" category. #149# The minimum security to view NEW uploads. RBBS-PC will omit either ALL files in the "upload" directory, or only those files in the "upload" category (if the upload directory is the master FMS directory). #150# The minimum security to bypass the "epilog" questionnaire, specified in parameter 85. #151# The minimum security level required to automatically add a user to a conference. This parameter is only activate when CONFIG is in "conference maintenance" mode (see parameter 167). If a caller tries to join a conference, they will be denied access unless they are already a member, or their security is at or above this level. Each conference may have a different setting for this parameter. NOTE: Sub-boards do NOT use this feature. To restrict access to a Sub-board, use parameter 123. #152# The minimum security level for a caller to "turbo logon". This feature allows a caller to go DIRECTLY to the main menu, bypassing the welcome, new upload and bulletin displays. To use "Turbo logon", the user must answer the "What is your FIRST name" prompt with: firstname lastname password ![conference] The "!" after the password signals RBBS-PC to use "turbo." If the conference name is omitted, the caller will be left in the MAIN conference. If the caller substitutes a "$" for the "!", Only the WELCOME will be bypassed. This is helpful for systems with extensive ANSI welcome screens that can be tedious for old callers. #153# The minimum security required by a caller to add a description for an existing file. Typically this is restricted to the SysOp only. It can be used by the SysOp to create FMS directories. After placing the files in the upload subdirectory (or anywhere in the download path) the SysOp can use RBBS-PC to add descriptions for the files. RBBS-PC will first ask if you wish to OVERWRITE the file. If you answer NO, RBBS-PC will then ask if you wish to add a description. In this way, RBBS-PC will properly build the directory entry. #154# The name of the help file that is shown to a caller whenever the caller incurs a security violation. RBBS-PC will add the HELP directory and EXTENSION (from parameters 64 and 66). #155# Denies callers access to one or both of RBBS-PC's "premium features -- DOORS and file downloading, for a specific period of time. This can be used to direct the callers' attentions to other features of RBBS-PC (such as message bases). The PASSWRDS file (see section 15.3) specifies how many SECONDS the caller must be online before the premium features are available. If a caller tries to use a locked feature before the time has elapsed, the caller will be given a message and denied access. This is *NOT* recorded as a security violation. The file TIMELOCK.HLP should be placed with the other RBBS-PC HELP files. This file (if found) will be shown to a user who is locked out of a command. If the TIMELOCK.HLP file is not available, the caller will be given a "canned" message: "Sorry, (name), try that function later." #156# The minimum security to be exempt from automatic security updates. If the caller's MAIN security level is changed, their security level in conferences will also be changed if their security in the conference is less than this setting. This allows the SysOp to adjust their security in the MAIN conference, and RBBS-PC will make the adjustments in each conference and sub-board. If the SysOp increases a caller's security in a conference (to make them a "SIGOp"), The caller will maintain this increased security only if it is above this setting. #157# The minimum security a caller must have to be able to read and kill all messages (in the message base for which this is a .DEF file). This allows the SysOp to create an "assistant MESSAGE SysOp" who can police message traffic, without granting that user full SysOp privileges. #158# Specifies a text string that, if found at the start of a message line, will NOT be shown to the caller. This can be used to hide the sometimes enormous network routing data found in network mail. #159#160# empty #161# The maximum number of RBBS-PC nodes. Up to 36 RBBS-PC's can share the same files. Different environments have different maximum number of nodes that they can effectively support. Setting this parameter configures the MESSAGE files so they contain the appropriate number of "node" records. #162# The environment that multiple copies of RBBS-PC will be sharing files in. This is necessary so that RBBS-PC can use the mechanism that is appropriate to the specific environment when sharing files. RBBS-PC currently can handle the following environments for multiple RBBS-PC's: 0) Single node under DOS 1) MultiLink (The Software Link, Inc.) CDOOR: not avail 2) OmniNet (Corvus) 3) PC-Net (Orchid) 4) DESQview (Quarterdeck Office Systems) 5) 10 Net (Fox Research) 6) IBM's NETBIOS NOTE: Many manufacturers utilize Orchid's network conventions. As an example, AST and Alloy are both vendor's whose "network" is .EXE file- compatible with Orchid's. If you have a network of PC's, check with the vendor to see how compatible their network is with those supported by RBBS-PC. #163# Specifies the method RBBS-PC uses to recycle after a call. INTERNAL recycling is done within the RBBS-PC.EXE file. SYSTEM recycling exits RBBS-PC, and expects the invoking .BAT file to recycle. Internal is faster, but System allows an external event to be processed after each caller. #164# The number of records in the USERS file. This number must be an even power of 2 (256, 512, 1024, 2048, etc.). When the USER file is almost full, the SysOp will either have to "rebuild" the user file (see parameter 182) or increase this file size. The SysOp can check on the freespace in this file with the RBBS-PC "statistics" command (UTIL section). Parameter 291 lets new users on even if the users file is full. #165# Specifies the default number of records in the MESSAGES file. Each file is 128 bytes. The number of messages that can be stored is a function of the number of lines allowed per message. The minimum size of the MESSAGES file is equal to 1 (The "checkpoint" record) plus the maximum number of concurrent RBBS-PC's ("node" records) plus the maximum number of messages allowed multiplied by 5 (each messages is assumed to average five 128-byte records) #166# The maximum number of messages allowed in the message file at any one time. The absolute upper limit on the number of messages is 999. If you specify 250 messages, you can expect that the MESSAGES file will be formatted to more than 160K in size. If you allow the message file to grow (parameter 170), only parameter 166 will limit the growth of the file. If your message file does not grow, both the number of messages, and the number of records will limit how many messages can be left. #167# Enters "conference maintenance" This allows you to set features or do maintenance on CONFERENCES (not Sub-boards!). You will be asked for the conference name, which can be up to 7 characters (CONFIG will add an "M" to the conference MESSAGE filename, and a "U" to the USER file name). While in conference maintenance mode, you can create conference message and user files, perform maintenance on them, or set conference variables (see parameter 151. To perform maintenance on a Sub-board, you should start config with the sub-board .DEF file (i.e. CONFIG MYSUBC.DEF). If you change the size of a conference MESSAGE or USER file, the change will take place when press the END key while in conference maintenance mode. #168# The default file extension for uploads and downloads. If a file is UPLOADED, and the user does not specify an extension, this default will be used. If a file DOWNLOAD request does not specify an extension, the default will be used. In order to upload files with NO extension, a "." must follow the name (i.e. U MYFILE. Z). #169# Additional file extensions in addition to the default, to search when looking for an uploaded file, to decide if it is already present. A file will be considered already in the catalog if the prefix matches. Warning: this search can be time consuming unless you have installed the Fast File Search. Every extension listed should begin with a period. E.g. ".ARC.PAK" would count an upload of XYZ.ZIP as a duplicate if the file XYZ.PAK or XYZ.ARC exists. #170# Allows the MESSAGE files to "grow." If the limit on active messages (parameter 166) has not been exceeded, and the number of records has been exhausted, RBBS-PC will increase the size of the message file to accommodate more messages. NOTE: The Corvus Network software does not allow a message file to grow. #171#172#173# #174# CDOOR: if set to yes you must upgrade your fms.dir #175#176#177#178#179#180# empty #181# Packs the message base. When a message is "killed," the space used by that message is not freed (this allows a message to be "resurrected). Parameter 181 makes a backup of the message file, then reclaims the space used by killed messages. #182# Removes deleted users and users who have not been on the system within the number of months specified in parameter 16. You should have enough free disk space for a second copy of the users file (with a qualifier of ".BAK") or the rebuilding will terminate abnormally (the users file will be restored). NOTE: Locked-out users (security less than 0) will not be removed from the file. #183# Displays the message headers of all messages, active and killed, that are present in the message file. This is left over from one of the many "debugging" stages of RBBS-PC prior to CPC09. Following the policy of making all changes "additive", this function has been retained. It may help some SysOps recover from disk hardware failures. #184# Renumbers messages. An RBBS-PC message number cannot be higher than 9999. This function will renumber the active messages, utilizing numbers once used by deleted messages. Also, each caller's high- message pointer will be updated to reflect the renumbered message. #185# Scans the message file and reconstructs the chains that link the messages together. Message files that have "blank" messages or abbreviated messages (i.e. some lines of text are missing) can be repaired with this facility. #186# Sets a flag in all USER records that will require the user to answer the required questionnaire (see parameter 82). #187# Scans the FMS directory to be sure each record conforms to the exact format required by the FMS (in case the text editor used by the SysOp to edit the file inserted tabs or shorten lines that had trailing blanks at the end of them). #188# Scans the PERSONAL download directory to be sure the format is proper for a PRIV.DEF file. #189# This parameter will guide the SysOp, sequentially, through only those parameters that would normally have to be changed when setting up a new RBBS-PC. #190# This parameter will guide the SysOp, sequentially, through the parameters that are new and/or changed for the current release of RBBS- PC. #191# Will turn the "printer enabled" flag off in all the node records. This is useful if somehow the printer is accidentally enabled, but no printer exists (a condition which will halt RBBS-PC). #192# Scans the USER file and turns the "highlight" feature off for any user who did not select COLOR. This will rescue confused callers from the problem of receiving ANSI sequences when their terminal does not support ANSI. #193# CDOOR: If you are changing to Cdoor from another mod or stock set this to Yes. Changes in the way CDOOR uses the USERS Record require this #194#195#196# empty #197#198#199#200# empty #201# The drive letter where uploads should be placed. Enter only the DRIVE letter here. The exact subdirectory can be entered in parameter 208. #202# The name of the directory file where RBBS-PC should place upload descriptions. This upload directory can be the master FMS directory, or a separate upload directory. #203# The drive/path were the upload directory is to be found. #204# The letters of the drives from which files can be downloaded. The order in which they are specified is the order in which the drives will be searched. If the order is BAC, then drive B will be searched first for the file, then drive A, and finally drive C. While there can be duplicate files on each of the drives, the first file found will be the one downloaded to the user. #205# Specifies that DOS subdirectories are used. This is a reflection of RBBS-PC's early history (before DOS supported subdirectories) and should always be set to YES. CDOOR: YES #206# Specifies that uploads are to be sent to DOS subdirectories. This is a reflection of RBBS-PC's early history (before DOS supported subdirectories) and should always be set to YES. #207# Specifies that downloads are separated into DOS subdirectories. This is a reflection of RBBS-PC's early history (before DOS supported subdirectories) and should always be set to YES. #208# Specifies the DOS subdirectory where UPLOADS are placed, and a list of subdirectories where DOWNLOADS are searched. This is only functional if you have responded "Yes" to either parameter 206 or parameter 207. The FAST FILE SEARCH can be used in conjunction with this directory list to find downloads (see section 12.9) CDOOR:your UPLOAD dir should also be your first DOWNLOAD directory for the FFS #209# The file extension for RBBS-PC directory files. #210# An alternative extension to be used for "directory" files. The main use for an "alternate" extension is to allow "sub-boards" to share directories using the main extension (parameter 209), but also have some directories unique to the "sub-board" that are not shared with others. #211# The name (prefix only) of the directory of directories. This file lists either the names of other .DIR files, or FMS category codes (see section 12). #212# Allows the SysOp to exclude the directory of directories from the search done by the New command. If your directory of directories does not contain FILE descriptions, but only directory descriptions, you will probably not want it searched by the "new" command. #213# Specifies an additional file to place upload descriptions. This could be used to maintain a downloadable list of ALL files, or a bulletin of NEW uploads. #214# The name (without path or extension) of the master FMS directory. See section 12.3 for a full description of the advantages of using FMS #215# Limits the search for directories to the master FMS directory. If you have multiple .DIR files, set this parameter to NO. If you only use FMS, set this parameter to YES to increase the speed of directory searches. CDOOR: NO #216# The default category code for uploads. This parameter is how uploads get classified in the FMS directory if the uploader does not have sufficient security to categorize an upload. If this category is "***," only the SysOp will see the new upload. #217# The name of the file which tells RBBS-PC what categories are included in the FMS directory. The format of the file is described in section 12.5. #218# Specifies what directories will be listed in a request for "all" directories. This parameter is REQUIRED in order for "all" to be defined as an option. Begin with "@" if you want to specify a list of directories. For example, "@C:\RBBS\ALLDIR.LST" means that the text file "ALLDIR.LST" on drive C in subdirectory ALLDIR contains a list of directories to search when "all" is specified. The directories in ALLDIR.LST should use the same names as the caller would type in, one to a line. E.g. if "all" is the search directories 1,3, and 4, ALLDIR.LST should contain 1 3 4 You can also specify a specific directory to confine all to by including an entry not beginning with "@", e.g. "FMS" would list directory FMS.DIR, located in the drive/path specified where directory files go. If you want to disable the search for "all", just press Enter in response to this parameter. CDOOR: change to @DRV:\DIR\MAIN.LST #219# The maximum length of the description that can be given to an uploaded file. RBBS-PC can be configured so that those who upload files can provide a description of the file they upload. This description informs others what the file does and helps them decide whether they want to download the files. The maximum length of the description can be set to any value between 40 and 46. WARNING: If you change this option, you must manually change all existing directories. #220# The drive and directory where all directory files must be put, except possibly for the upload directory. Only in this DOS directory does RBBS-PC look for RBBS-PC directory files, with the sole exception of the upload directory when the caller's security level permits the upload directory to be viewed (see parameter 149). #221# The communication port that RBBS-PC will use. If you specify COM0, RBBS-PC will run in "local" mode, allowing you to run RBBS-PC without a modem. RBBS-PC can support COM1 and COM2 directly, or it can support a FOSSIL driver, and thereby support any communications port supported by the FOSSIL. #222# The number of seconds that RBBS-PC should wait after initializing the modem with a "reset" command. Many modems require only 1 second to reset, however some may require much (MUCH) longer. #223# The number of seconds to wait prior to issuing a modem command. This is most useful when you have configured RBBS-PC to only issue commands between rings and want the modem to "settle down" after a ring has ended. If you find that 2400 baud calls are improperly connected at 1200 baud, increase the wait. Some modems take longer to connect at 2400 than at lower speeds. #224# The number of rings to wait before answering the phone. Specifying zero rings means that the modem (not RBBS-PC!) will answer the phone as soon as it rings. NOTE: RBBS-PC's control of answer mode is an important part of its security. Setting parameter 224 to ZERO bypasses this security! If you specify one or more rings, the modem must be able to tell RBBS-PC when the phone is ringing (via RS-232 pin 22 or the "RING" response string). The modem must also be able to count rings in its S-registers. You can also specify "Ring-Back." This instructs RBBS-PC to IGNORE a ringing phone, but if the phone stops ringing (for more than 10 but less than 45 seconds) and then starts ringing again, RBBS-PC will answer. This is useful for non- dedicated phone lines, or hearing-impaired SysOps who want to use both TDD (telecommunications device for the deaf) and RBBS-PC. A caller who wants the SysOp to use TDD will let the phone ring until the TDD connects, but will call, let the phone ring once then hang up, and then call BACK to get RBBS-PC to answer the phone. #225# Sets the commands RBBS-PC uses to communicate with the modem. A list of SysOp-supplied settings for various modems is also available (See section 11). #226# Activates software-based MNP support. This option is no longer available, unless Microcom can supply a library that is compatible with current Microsoft BASIC compilers. RBBS-PC does support MNP protocol that is hardware-based (i.e. built into the calling and answering modems). #227# Restricts RBBS-PC so it will only issue modem commands BETWEEN rings. Some modems cannot handle the telephone ringing and accept modem commands simultaneously. Most modems do NOT require this restriction. #228# The speed RBBS-PC should initialize the modem to. Most modems will only REDUCE speed when automatically detecting baud rate, so this value should be set to the maximum speed supported by your modem. #229# The number of seconds RBBS-PC will wait before disconnecting an "idle" caller. If a caller walks away from an RBBS-PC session, RBBS-PC will first warn the caller, then disconnect the call after the specified number of seconds. #230# Specifies a "dumb" modem is being used. Selecting this means that no modem commands are sent from RBBS-PC to the modem. This can be used to connect RBBS-PC to a communications network (i.e. TymNet) or local area network that supplied a simple RS-232 interface. Selecting this option causes RBBS-PC to - Issue no Hayes commands, - Depend on no Hayes-like responses, - Control the interface with the Data Terminal Ready (DTR), - Assume somebody has called whenever Carrier Detect (CD) is detected, and - Assume that whomever calls is at the baud rate selected in CONFIG parameter 228. #231# Initializes the modem's firmware for use by RBBS-PC. The commands used to perform firmware initialization can be modified with parameter 225. #232# The number of seconds to wait after dropping DTR (Data Terminal Ready). RBBS-PC drops DTR in order to disconnect a caller. Too short a delay will cause the modem not to re-initialize properly. #233# The path and filename of the external protocol driver file (see section 20). #234# Activates RBBS-PC's check for AutoDownload support (supported by the PC-TALK terminal emulator) at the start of each call. This check is incompatible with some terminals and communications packages, causing them to stop displaying on the local screen. The caller can control whether autodownload is used with the T)oggle command in utilities. It is recommended that this option NOT be enabled. #235# Instructs RBBS-PC to force downloads with "binary" file extensions (i.e. .ARC, .ZIP, .EXE, .COM, .OBJ, .WKS, .BAS, or whose second letter of the extension is Q) to non-ASCII protocols. #236# Instructs RBBS-PC to "recycle" after a number of minutes passes without receiving a call. This may help recover from a modem malfunction. Set this value to the number of minutes an "idle" RBBS-PC could mean a modem problem. Specifying 0 means that RBBS-PC will not re-cycle, no matter how many minutes elapse between calls. #237# Forces RBBS-PC to leave the modem at the baud rate it was initially opened at rather than automatically matching the baud rate of the caller. RBBS-PC normally changes the baud rate in the RS-232 interface to match that of the callers. Some modems allow RBBS-PC to transfer at maximum speed on all calls, while the modem handles the speed conversion. In this case you would set parameter 237 to YES. #238#239#240# empty #241# Instructs RBBS-PC to switch back to the original parity/word length setting after a binary transfer. If a caller using 7bit, even parity requests a binary transfer, RBBS-PC will switch to 8bit, no parity. Parameter 241 controls whether RBBS-PC stays at 8bit or reverts to 7bit after the transfer. Most environments can remain at 8bit after a transfer. #242# Specifies the minimum modem speed that new callers can have. If a new caller connects at a speed less than that specified, RBBS-PC will deny access to that caller. #243# Specifies the minimum modem speed for OLD callers. With this parameter, you can block any NEW callers at 300bps, but allow a pre- registered caller access at that speed. #244# Activates CTS (clear to send) and RTS (request to send) flow control. This hardware flow control uses RS-232 pins 4 and 5 to control the flow of data between RBBS-PC and the modem. #245# Activates XON/XOFF flow control. This software flow control uses ASCII codes to control the flow of data between RBBS-PC and the modem. NOTE: RBBS-PC only supports XON/XOFF at the end of each buffer. If RBBS-PC is to quickly respond to XON/XOFF, set parameter 54 to a small number. #246# The maximum time to RBBS-PC should wait for carrier after answering the phone. #247# CDOOR: set to the string your modem reports for a caller ID Number. If you do not have this set to none #248# CDOOR: set to the string your modem reports for a caller ID BLOCKED Number. If you do not have this set to none #249#250#251# empty #252#253#254#255#256# empty #257#258#259#260# empty #261# Specifies the time of day in HHMM format at which RBBS-PC is to perform a "daily event." At this time, RBBS-PC will create a "daily event" signal file, and exit to DOS. The signal file is in the form "RBBS?TM.DEF", where ? is the node number. See section 13 for a complete description of the requirements for .BAT files when doing daily events. #262# Selects a network "front end" for use with RBBS-PC. Currently, RBBS-PC supports the following front-ends: SeaDog and BinkleyTerm (see Appendix S). By enabling this option, the SysOp assumes the responsibility of configuring the "net mail" application to: 1. answer the phone and determine if the caller is sending "net mail". 2. if the caller is not sending "net mail", the net mail application must invoke RBBS-PC with the following command line: RBBS-PC.EXE nodeid filename /time /baud /RELIABLE where: - "nodeid" is the node ID in the range 1-9, 0, or A-Z. - "filename" is the fully qualified file name to use as the RBBS-PC ".DEF" file. - "/time" is the time of day for RBBS-PC to return to the "net mail" application that called RBBS-PC. - "/baud" if the baud rate that the caller dialed in at. - "/RELIABLE" tells RBBS-PC whether the connection has error correction built into the connected modems #263# The command to turn on intermediate host echo. This is intended to be used when RBBS-PC is connected to a public data network (PDN) as a "node" -- not all systems that people log into on a PDN need be "main frame" computers! When RBBS-PC is a node on a public data network, typically the network will do the echoing -- between the caller and the port they access on the PDN and between RBBS-PC and the port RBBS-PC accesses on the PDN. This causes file transfers to be a problem because the PDN will continue to echo. Therefore it is necessary to be able to go into an "image" mode where data is passed through the PDN intact with no echoing. The contents of this string will be sent AFTER a file transfer so the network will resume echo. Any character can be included in the string using it's decimal ASCII equivalent simply by putting a number inside square brackets. Characters not in square brackets will be transmitted as they were entered. The string "a[32]" will be interpreted as a lower case letter "a" followed by a blank. #264# The string that sent BEFORE a file exchange that causes the PDN to STOP echoing. As with parameter 263, the contents of this string is entirely dependent on the predilections of the PDN that RBBS-PC is attached to. #265# Specifies who should echo characters sent to RBBS-PC. Normally, RBBS-PC echoes back to the caller, but un a PDN, or callers who use TDDs may want to change this value to either an intermediate host, or to the caller's system. #266# The string RBBS-PC will use to acknowledge each line in an ASCII protocol upload. Typically, an ASCII upload is characterized by two fundamental features -- it contains no unprintable characters and it does not require any "error checking". Under some circumstances a callers communications protocol may require a response from RBBS-PC (i.e. a line feed) before the next line will be transmitted. #267# The path and filename of the FFS (Fast File Search) sorted names file (see section 12.9). #268# The path and filename of the FFS (Fast File Search) "tabs" file (see section 12.9). #269#270#271#272#273# empty #274#275#276#277#278# empty #279##280# empty #281# Instructs RBBS-PC to allow new callers to set their default system values. RBBS-PC typically asks new users their choice of line feeds, graphics, transfer protocol, and "turbo-key". Sometimes these questions confuse new users, who lack the knowledge to answer them. #281# empty #282# CDOOR: Set to YES to have callers read new messages #283#284#285# Not implemented in this release of RBBS-PC. #286#287#288#289# Not implemented in this release of RBBS-PC. #290# Specifies new users should be saved in the USER file. If set to NO, new users may log in, but RBBS-PC will not "remember" them on subsequent calls. #291# Instructs RBBS-PC to allow new users when the USER file is full. In this case, RBBS-PC will not "remember" new callers on subsequent calls, until the USER file is expanded to accommodate more records. #292#293#294#295#296# empty #297#298#299#300# empty #301# Activates the Library Sub-System (see section 12.6). Specify a drive, which must NOT be a drive used by any other RBBS-PC function. CDOOR: Select a Drv Path for the internode chat file, make sure it is the same as for all other rbbsXpc.def files #302# The drive/path where RBBS-PC will find the upper directory (CDR.CDR is the default name). #303# The file extension that identifies library directory files. CDOOR: enter path and file for RBBS-PC.LNG file #304# The drive/path of the Library "work disk." This is where the Library sub-system creates archive files for transmission. Normally, 360K of free space is required, so a RAM disk is suitable. #305# The number of disks available in the library. #306# The maximum number of upper level directories that will be found on the Library disk. The PC-SIG CD-ROM is organized with 10 upper level directories, 1-100, 101-200, 201-300 etc. and each of these contain 100 directories, DISK001, DISK002 etc. #307# The maximum number of subdirectories that each upper level directory can contain. #308# The prefix of the lower level directories. Since the user enters only the disk number that is desired, RBBS-PC creates the subdirectory name based on this parameter and the number entered. #309# The drive\path\name of the Library Sub-system menu. CDOOR: enter the location for you RIP ICON file for users to download #310# The list of command symbols that are available from the Library Sub-System menu. #311# The security values related to the symbols listed in parameter 310. #312# The drive\path where the archive utility program can be found. #313# The archive utility that will do the archiving on Library disks. When answering the questions to this parameter you will also be asked what the CREATE parameter is. For PKARC and ARC the correct response is "A". If using ARCA there is no CREATE parameter since CREATE is the only function that it can do. #314#315#316#317#318# empty #319#320# empty #321# The string that turns ON highlighting or emphasizing of characters in text strings displayed to the caller (see section 7.10). #322# The string that turns OFF highlighting or emphasizing of characters in text strings displayed to the caller. #323# Foreground color 1. The SysOp can select this color in menus and text by using the SmartText command C1. #324# Foreground color 2. The SysOp can select this color in menus and text by using the SmartText command C2. #325# Foreground color 3. The SysOp can select this color in menus and text by using the SmartText command C3. #326# Foreground color 4. The SysOp can select this color in menus and text by using the SmartText command C4. #327# The background color used against the preceding four foreground colors. #328# CDOOR: set to 25, 43, or 50 #329# CDOOR: set to preference #330# CDOOR: set to [27][1;47;37m for use with the included MENU0 and SYSOP5 #331# CDOOR: reccomended to be set to yes for best display #332#333#334#335# empty #336#337#338#339# empty #340#341#342#343# empty #344# CDOOR: if you want RBBS to go off hook after a call set to NO #345#346# empty #347# CDOOR: No will keep a caller from being locked out #348# CDOOR: tells recepient of msg to kill their msg after reading #349# CDOOR: time on line is frozen while reading msgs if yes #350# CDOOR: time on line is frozen while reading bulletins #351# empty #352# CDOOR: No will always have GIF dimemsions to uploads #353#354#355#356#357#358# empty #359# CDOOR: if you want new users to start with a new user record when joining a subboard set to YES #360# CDOOR: if YES a users registration date will be set to the date that it expired on. #999#