±±Ü ±±Ü ±±Ü ±±±±±±Ü ±±±±±±Ü ±±±±±±Ü ±±±±±Ü ±±±±±Ü ±±±±±Ü ±±Û ±±Û ±±Û ß±±Ûßß ±±Ûß±±Û ±±Ûß±±Û ±±Ûß±±Û ±±Ûß±±Û ±±Ûßßß ±±Û ±±Û ±±Û ±±Û ±±±±±Ûß ±±±±±±Û ±±±±±Ûß ±±±±±Ûß ±±±±±Ü ±±Û ±±Û ±±Û ±±Û ±±Ûß±±Ü ±±Û ±±Û ±±Û ±±Ü ±±Û ±±Ü ß±±Û ±±±±±±Û ±±±±±±Ü ±±Û ±±Û ±±Û ±±Û ±±Û ±±±±±Ûß ±±±±±Ûß ±±±±±Û ßßßßßß ßßßßßß ßß ßß ßß ßß ßß ßßßßß ßßßßß ßßßßß UltraBBS Version 3.01 UltraBBS by Craig Baker Based on the Original Program by Bob Farmer Copyright (c)1991-1993 Craig Baker, All Rights Reserved. Your patience is APPRECIATED. The UltraBBS 3.00 project was a BIG one, and MANY MANY improvements and enhancements have been added since version 2.09. To have accomplished all this in just over SIX MONTHS has been a mammoth effort. PLEASE make SURE you have all files backed up if you are converting from 2.09. I *DONT* want to have folks wind up with anything messed up! WE'VE tried our BEST to make sure the software works and works WELL! any bug reports will be VERY welcome. Support: Voice: 303-444-7071 (Craig D. Baker) Pinecliffe BBS: 303-642-7463 (mail to Sysop or Craig D. Baker) Internet address: cdb@pinecliffe.com THIS DOCUMENTATION IS PRELIMINARY. Dated 3/3/94. UltraBBS 3.01 Documentation Page 1 TABLE OF CONTENTS ------------------------------------------------------------------------- Copyrights............................................................2 Disclaimer............................................................3 Welcome to UltraBBS...................................................4 Minimum Requirements..................................................5 Multinode Operation Information.......................................6 Beginning Setup.......................................................7 Directory Structure...................................................8 Installation and Configuration........................................9 U3SETUP Program......................................................11 Explanation of UltraBBS Data File Use................................26 U3MANAGE Program.....................................................27 Command Descriptions.................................................32 CONVERT Program......................................................39 UTI Files............................................................40 PCBVerify Support....................................................41 Offline Reading Support (.QWK/.REP)..................................42 Message Commands.....................................................43 Remote DOS Setup.....................................................45 ANSI Music...........................................................49 Modem Configuration..................................................47 Doors................................................................48 Questionnaires.......................................................49 Events...............................................................51 Text Files...........................................................52 Call Waiting Screen..................................................54 Local Function Keys..................................................55 Front-End Operation..................................................56 U3MANAGE Command Line Parameters.....................................57 File Formats.........................................................61 Questions and Answers................................................70 UBBSWHO Program......................................................71 FIDOCVT Program......................................................72 Networks and Netmail.................................................62 Changes from UltraBBS v2.09..........................................62 Converting from UltraBBS v2.09 to 3.0x...............................63 Errors...............................................................64 Registration.........................................................65 Contacting the Author................................................66 Thanks...............................................................67 UltraBBS 3.01 Documentation Page 2 COPYRIGHTS ------------------------------------------------------------------------- While every precaution has been taken in the preparation of this manual, the author(s) assume no responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained herein. Proceeding further indicates your agreement with this. UltraBBS, including but not limited to: UBBS.EXE, U3MANAGE.EXE, U3SETUP.EXE, CONVERT.EXE, UTI*.EXE, PCBVUPDT.EXE, UBBSWHO.EXE, FIDOCVT.EXE are copyrighted (c) 1991-1993 Craig Baker, All Rights Reserved. PCRelay, MegaMail, and UTI are copyrighted by Kip Compton. IBM is a trademark of International Business Machines Corporation. DoorWay is copyrighted by Marshall Dudley. Hayes and Smartmodem are trademarks of Hayes Microcomputers Products. Courier HST is a trademark of USRobotics. PCBVerify is copyrighted by Curtis Kowalski. PCBoard is a trademark of Clark Development Company. MSG is copyrighted by Ron Bemis. SMLNET is copyrighted by Darwin Collins. UltraBBS 3.01 Documentation Page 3 DISCLAIMER ------------------------------------------------------------------------- IN NO EVENT SHALL THE AUTHOR(S) OF ULTRABBS BE RESPONSIBLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES OR LOST PROFITS TO YOU OR ANY OTHER PERSON OR ENTITY REGARDLESS OF THE LEGAL THEORY, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. CONTINUING FURTHER INDICATES YOUR ACCEPTANCE OF THIS AGREEMENT. If you are an UltraBBS 2.09 sysop, please read the following WARNING!! MAKE SURE YOU BACK UP ALL FILES PRIOR TO CONVERSION to 3.00!!!! Read the page concerning CVTUBBS.EXE to do the conversion. UltraBBS 3.01 Documentation Page 4 WELCOME TO ULTRABBS ------------------------------------------------------------------------- This manual was written to assist you, the new UltraBBS sysop, to install, run, and maintain the UltraBBS software. Our goal is to get you up and running in the shortest possible time and to answer any questions which you may have. Before beginning the installation process, please read this document carefully. Installing a BBS system can be complicated due to the many individual files involved. Current UltraBBS Sysops may want to read the appendix on converting from 2.09 to 3.00 first. UltraBBS 3.01 Documentation Page 5 MINIMUM REQUIREMENTS ------------------------------------------------------------------------- IBM compatible computer running MS/PC-DOS or DesqView. Compatible with Novell and Lantastic. 640K system. The UBBS.EXE version requires 430k during Operation When we shell to a door, UBBS shrinks to only 3k! Fixed disk drive (at least 20 megabytes recommended). MDA/Hercules/CGA/EGA/MCGA/VGA/XGA or compatible card and monitor. Hayes (AT) command-set compatible modem. DOS 3.1 or greater, with SHARE.EXE loaded. Revision 5 FOSSIL Driver. FOSSILs can be found for download on most BBSes. They are public domain or shareware, and one MUST be loaded for UltraBBS to operate. (this is a requirement in 3.0x. But future releases may have the fossil driver built in). UltraBBS has been test successfully with: Opuscomm BNU X00.SYS UltraBBS 3.01 Documentation Page 6 MULTINODE OPERATION INFORMATION ------------------------------------------------------------------------- To run multiple nodes of UltraBBS, you must have some method of running multiple copies of UltraBBS concurrently. Two ways of doing this are networking and multitasking. With multitasking, on a reasonably fast computer (ie: a 386/25 MHz), you should be able to run 2, 3, or possibly even 4 copies of UltraBBS per computer with acceptable speed. UltraBBS requires approximately 370K per copy, so you must have enough memory to assign that much to each task, and have enough to create the required number of tasks. Two of the most popular multitasking programs are DESQview, and Microsoft Windows. UltraBBS has been tested under both, and performs well. Although any multitasker which correctly supports file sharing should work, no guarantees are made for other multitasking programs. If, on one computer, you use both COM1 and COM3, or COM2 and COM4, make sure you have a FOSSIL driver that correctly supports the sharing of interrupts, such as the X00 driver. UltraBBS has been tested with two of the major networks, LANtastic and Novell. Any networking program that leaves you with 380K free memory, and correctly supports DOS file sharing should work, however no guarantees are made. Under some networks, you may be even able to multitask on the networked computers, and run 2 or 3 nodes per computer; however, this will obviously result in slower speeds. UltraBBS 3.01 Documentation Page 7 BEGINNING SETUP ------------------------------------------------------------------------- A working knowledge of DOS is mandatory. The ability to create and understand batch files is needed. If you are planning on running a multinode system, you should already know how to set up your network or multitasker before attempting to install UltraBBS. We do not provide any setup information for networks since such information takes volumes and our main concern is with getting your UltraBBS system installed as quickly as possible. Since UltraBBS was designed for the professional, this document assumes the sysop has a fair amount of knowledge concerning BBS operation and DOS essentials. You should have or create a CONFIG.SYS file with the following parameters: FILES=25 BUFFERS=30 If you are running UltraBBS in a multitasking environment, such as DESQview or Microsoft Windows, you will need to increase the value of the FILES parameter depending on how many copies of UltraBBS, and any other programs, are running on that computer concurrently. IMPORTANT NOTE: UltraBBS by default stores all dates in United States format. That is, dates are in MM/DD/YY format, and times are either in HH:MM format or HH:MM:SS format. HOWEVER -- you may in U3SETUP have it accept dates in the European Format -- DD/MM/YY. UltraBBS 3.01 Documentation Page 8 DIRECTORY STRUCTURE ------------------------------------------------------------------------- In order to insure optimal operation of UltraBBS, the following directory structure is recommended: Root Directory | | UBBS | | --------------------------------------------------------- | | | | | | | | | | | | | | HOLD FILES DOWNLOAD HELP SCRATCH BATCH ATTACH FILES - contains all data files and text for the main conference area as well as for all other conferences. DOWNLOAD contains all uploaded and downloadable files. You may wish to break this directory into seperate upload and download directories. Note that full pathnames are specified in the FILEBASE.DAT file, so that your Files may exist in many areas and many drives. HELP contains all help text files. SCRATCH is used for several of the UltraBBS commands and should be an empty directory. BATCH is the directory where all files are stored when a batch upload is performed until the software moves them to the correct directory, and should also be empty. HOLD is where all duplicate files that are uploaded are stored, and also where files are placed when the user does not have the required security to upload that file. ATTACH is used to store files that are attached to messages (the files are stored in subdirectories that UltraBBS creates off of the ATTACH directory). THIS MUST BE THE SAME DIRECTORY ACROSS ALL NODES, OR SOME NODES WILL NOT BE ABLE TO DOWNLOAD ATTACHED FILES. WARNING: ======== Please make sure ALL the above directories EXIST. UltraBBS will however create many of them if they don't. In the distribution archive, TESTBBS is used to contain the example FILEBASE.DAT, USERS.DAT and ULTRABBS.NDX files. Also the encryption file UBBSENC.DAT is located here. This is so as not to overwrite existing files if you do a pkunzip -d. UltraBBS 3.01 Documentation Page 9 INSTALLATION AND CONFIGURATION ------------------------------------------------------------------------- When you first extract the UltraBBS distribution files from their archive(s), you will need to change all the paths and directories in U3SETUP to match your system. See the U3SETUP section below for the meaning of each parameter in the U3SETUP program. Before you can run any of the UltraBBS programs you must create and/or verify that the start-up batch file is correct. A sample batch file was provided (RUNBBS.BAT). The file should appear similar to the following: RUNBBS.BAT -------------------------------------------------- echo off cls :start ubbs if errorlevel 9 goto event5 if errorlevel 8 goto event4 if errorlevel 7 goto fatal if errorlevel 6 goto event3 if errorlevel 5 goto event2 if errorlevel 4 goto exit if errorlevel 3 goto fatal if errorlevel 2 goto external if errorlevel 1 goto event1 if errorlevel 0 goto start :external command /C rundoor.bat goto start :fatal cls echo Fatal Error Occurred! Check UBBS.ERR. goto start :event1 echo Event # 1 operations go here goto start :event2 echo Event # 2 operations go here goto start :event3 echo Event # 3 operations go here goto start :event4 echo Event # 4 operations go here goto start (continued next page) UltraBBS 3.01 Documentation Page 10 :event5 echo Event # 5 operations go here goto start :exit cls echo UltraBBS Exiting to DOS! :end -------------------------------------------------- To insure proper operation of the BBS, UltraBBS MUST be run from the RUNBBS batch file! This document will describe the configuration of a single node system only. If you are running a multi-node system, you will need to perform the configuration from each of your node's default (UBBS1\, UBBS2\, UBBS3\, etc) directories. It is not necessary to have multiple copies of any of the EXE programs if you have a DOS path set to your main node's default directory (however, in some cases, you will need to set the EXE files' read-only attribute!). Your shared files (text files, data files, etc) should be in a single directory, and all nodes can access the files. All that you need to keep in the UBBS1\, UBBS2\, UBBS3\, etc directories would be your UBBS.DAT, UBBS.REG, protocol batch files, door batch files, remote DOS batch file, RUNBBS batch file, and the post-upload batch file. UltraBBS 3.01 Documentation Page 11 U3SETUP PROGRAM ------------------------------------------------------------------------- UltraBBS SETUP Program (U3SETUP.EXE) Copyright (c) 1991-1993 Craig Baker, All Rights Reserved (NOTE: Whenever possible in UltraBBS's U3SETUP program, you should specify COMPLETE pathnames, including the drive letter!) ULTRABBS CONFIGURATION FILE PATHS #1 ------------- FILE HOLDING DIRECTORY (ex: C:\UBBS\HOLD): UltraBBS will place all uploaded files that are duplicate files, or that were in the NOUP.DAT, in this directory. These files will NOT be placed into the FileBase. You will probably want to clean it out from time to time. It should be a common directory for all nodes. YOU MUST CREATE THIS DIRECTORY. SCRATCH DIRECTORY (ex: C:\UBBS\SCRATCH): This directory is a temporary directory used by UltraBBS. This directory should be left empty. This directory MUST be different for all nodes. YOU MUST CREATE THIS DIRECTORY FOR EACH NODE. BATCH UPLOAD DIRECTORY (ex: C:\UBBS\BATCH): This is also a temporary directory used by UltraBBS. It stores all files during a batch upload. The program will automatically empty this directory by moving the files into the upload directory. This directory MUST also be different for all nodes. YOU MUST CREATE THIS DIRECTORY FOR EACH NODE. USER SECURITY FILES DIRECTORY (ex: C:\UBBS\FILES): This directory stores all security information text files. The software allows sysops to display a different file to each security level. The file names are simply the corresponding security level. For example, if you want to make a text file to be displayed to all security level 10 users, you would call the file '10' without an extension. Color files can be made, such as '10G' for security level 10 ANSI users. This directory will generally be common to all nodes. YOU MUST CREATE THIS DIRECTORY. FILE ATTACH BASE DIRECTORY (ex: C:\UBBS\ATTACH): This directory is where user's attached files will be placed (subdirectories will be created. IT MUST BE COMMON TO ALL NODES OR THE ATTACH-FILE-TO-MESSAGE function will NOT work. YOU MUST CREATE THIS DIRECTORY. FILEBASE FILE NAME (ex: C:\UBBS\FILES\FILEBASE): This is the filename of the file that will store information on all files on the BBS. It is a random access file, with indexes. This filename should not have an extension. This file is edited with UltraBBS's U3MANAGE program. ALL NODES must refer to the same directory to access the same FileBase. UltraBBS 3.01 Documentation Page 12 LIMITS FILE NAME (ex: C:\UBBS\FILES\LIMITS.DAT): This file stores the information on time limits and ratios for all security levels, and is edited with "Edit Current Limits File" from U3SETUP's You may have this file common to all nodes, or different for say public vs. private lines. NODE INFORMATION FILE NAME (ex: C:\UBBS\FILES\NODEINFO.DAT): This file contains information such as who is on the BBS, what they are doing, and where they are from. It also stores information pertaining to the events. Additionally, this file is also used when one node is paging another node. THIS FILE MUST BE THE SAME FOR ALL NODES! PROTOCOL FILE NAME (ex: C:\UBBS\FILES\PROTOCOL.DAT): This file contains the information on all of the protocols available for file transfers. It is edited with "Edit Current Protocols File" from U3SETUP. USER FILE NAME (ex: C:\UBBS\FILES\USERS): This file contains the information on every user on the BBS. Everything that is known about the user's location, phone numbers, birthdate, security level, etc is found in this file. This file can be edited with UltraBBS's U3MANAGE program. This file should not have an extension. CONFERENCE DATA FILE (ex: C:\UBBS\FILES\CONFDATA.DAT): This file contains the information on all conferences, their questionnaires, doors, bulletins, voting booths, text files, etc. This file is edited with SETUP's "Conferences" selection from the main menu. NODE CHAT FILE NAME (ex: C:\UBBS\FILES\NODECHAT.DAT): This file is used during node to node chat. For best results, it is highly recommended that this file be on a RAM drive. This file MUST be the same for all nodes. NEW USER QUESTIONNAIRE FILE NAME (ex: C:\UBBS\FILES\NEWQUES.DAT): This is a standard questionnaire file which is given to all new users who log onto the BBS. See the Questionnaire section for more information on questionnaires. NEW USER ANSWER FILE NAME (ex: C:\UBBS\FILES\NEWANSW.DAT): This file serves as the users' answer file from the above option. COMPRESSION FORMAT FILE NAME (ex: C:\UBBS\FILES\COMPRESS.DAT): This file contains all information on the file compression types supported by your BBS (ex: ZIP, LZH, ARC, etc). This is edited with "Edit Current Compression Methods File" from SETUP's main menu. PAGE BELL MUSIC FILE NAME (ex: C:\UBBS\FILES\PAGEBELL.DAT): This file contains music compatible with BASIC's PLAY command, or ANSI music. This file is played when a user pages the sysop. The first line contains the number of times to play the song which is found on the second line and those thereafter. The lines of the song must not begin with ANSI codes. EXPIRED SUBSCRIPTION FILE NAME (ex: C:\UBBS\FILES\EXPIRED): This is the text file displayed to users whose subscription date have expired. UltraBBS 3.01 Documentation Page 13 POST-UPLOAD BATCH FILE NAME (ex: C:\UBBS\UPLOAD.BAT): This is the batch file run after all uploads. You must make sure you have this feature enabled for this to take effect. Some common things that can be done with this are to convert uploaded files from ARC to ZIP, remove ZIP comments, etc. When this batch file is executed by UltraBBS, the uploaded file(s) will be in the batch dir, and this batch file will be executed from the system dir. UltraBBS will SHELL to run this file, and it may contain any collection of utilities. These utilities must operate on files in the BATCH subdirectory. Simply DELETE any files from this directory if errors or viruses for example are found. Only files present in the BATCH directory AFTER the POST-UPLOAD batch file is run will be added to the FileBase. PRE-UPLOAD FILE NAME (ex: C:\UBBS\FILES\PREUPL): This is the text file that is displayed before each upload. Usually it will explain which file formats you prefer to be uploaded, and which ones you do not want to be uploaded. FILE PATHS #2 ------------- CALLER FILE PREFIX (ex: C:\UBBS\FILES\CALLER): This is the prefix for the file name used for the callers log. This file contains information on users who have called and what they did. This file should be the same for all nodes. The node number is appended to the prefix when the file is actually used. For example, Node 1's callers log would actually be called 'CALLER1', and for this reason, the name of the caller's log should be no more than 6 characters long. This file can be viewed with a text editor, but should NOT be edited, as it is stored in a special, random format. It can also be viewed in a reverse order with UltraBBS's (1) main menu command, and searched with UltraBBS's (10) main menu command. NO UPLOADS FILE NAME (ex: C:\UBBS\FILES\NOUPS.DAT): This is the file that contains the names/wildcards that should not be uploaded, or that require a specific security level to upload. This is edited with SETUP's main menu "Edit Current No Uploads File" selection. ALIASES FILE NAME (ex: C:\UBBS\FILES\ALIASES.DAT): This is the file that contains names of people who cannot logon new to the BBS. This is a plain text file (to be edited with DOS's EDLIN or a similar editor) which contains the list of names, one name per line. CONFERENCE MENU FILE NAME (ex: C:\UBBS\FILES\CONFS): This is a text file that contains a list of all conferences available on the board. This is displayed to the user when they use the (J) command. GOODBYE FILE NAME (ex: C:\UBBS\FILES\GOODBYE): This is the text file that is displayed to the user when he logs off the system. WELCOME FILE NAME (ex: C:\UBBS\FILES\WELCOME): This is the text file that is displayed to all users upon logon, after the BBS checks for ANSI. UltraBBS 3.01 Documentation Page 14 NO NEW USERS FILE NAME (ex: C:\UBBS\FILES\NONEW): This is a text file that is displayed to new users if you have new user logons disabled in the SETUP program. HELP FILES PREFIX (ex: C:\UBBS\HELP\HLP): This is the prefix for the UltraBBS help files. These files come with the UltraBBS distribution diskette, but may be modified as a normal text file. NO REGISTRATION FILE NAME (ex: C:\UBBS\FILES\NOREG): This is the text file displayed to new users if they decide not to register. LOW SECURITY FILE NAME (ex: C:\UBBS\FILES\LOWSEC): This is the text file displayed if a user's security level is too low to log onto the board, but is above 0. NEW USER FILE NAME (ex: C:\UBBS\FILES\NEWUSER): This is the text file displayed to all new users, before they are asked whether or not they wish to register with the BBS. REMOTE DOS BATCH FILE NAME (ex: C:\UBBS\REMOTE.BAT): This is the batch file used to allow remote sysops (or co-sysops) to shell to DOS with UltraBBS's (7) command. A sample batch file is provided. See the Remote DOS Setup section for more information. BIRTHDAY FILE NAME (ex: C:\UBBS\FILES\BDAY): This is the text file that is diplayed to a user when they log on and their birthdate matches the current date (ie, it is their birthday!). CALLER NUMBER FILE NAME (ex: C:\UBBS\FILES\CALLNUM.DAT): This is the data file that contains the system's caller number. To keep a total number of callers on the system, this value should be set the same for all nodes. If you wish for each of your nodes to keep a separate caller number, you will want to set a separate name for this file on each node. If, for some reason, you wish to reset your caller number, you can delete this file. BBS LISTING FILE NAME (ex: C:\UBBS\FILES\BBSLIST.DAT): This is the data file that contains the BBS List. These are Bulletin Board Numbers that are entered by the callers. LANGUAGE FILE NAME (ex: C:\UBBS\FILES\LANGUAGE.DAT): This is the data file that contains language information. Will be implemented by version 3.10. PASSWORD FAIL FILE NAME (ex: C:\UBBS\FILES\PWDFAIL): This is a file that is displayed to users that have FAILED to enter the correct password for a given account. Typically it would contain instructions for a user to satisfy the sysop that he/she IS the account holder. NODELIST PATH (ex: C:\UBBS\NODELIST): This is the path to the nodelist data files. Not currently implemented but will be so by version 3.10. UltraBBS 3.01 Documentation Page 15 QUOTE & HISTORY DIRECTORY (ex: C:\UBBS\QUOTES): This is the path to the directory containing the QUOTES.DAT (an ascii file from which a quote is selected, with a blank line separating quotes) and this TODAY.xxx files. The TODAY.xxx files are files from the popular 'Today in History' package NEW USER HELP: This is the file NAME of a newuser help file, which may be downloaded to the user on their first call. It *MUST* be a file that is locatable in the filebase. ONLY THE FILENAME is specified, NOT the full path. BBS PARAMETERS/SWITCHES ----------------------- BBS NAME (ex: Bits & Bytes): This is the name of your BBS. SYSOP'S FULL NAME (ex: CRAIG BAKER): This is the full name of the sysop--the name he uses to log into the BBS with. You may want to log on with your real name, or the name 'SYSOP' as it is done on some other BBS packages. SYSOP START TIME/SYSOP END TIME: This is the beginning and end of the sysop page bell hours. If the sysop has turned on his page bell (with (Alt-P)), then users will always be allowed to page the sysop. If the page bell is off, then the page bell hours will be checked and if they are currently active, the page will be allowed. FORCE USERS TO FILL BLANKS: Makes users fill in fields that are blank. This includes the mother's name, birthday, address etc. INSTANT LOGON PASSWORD: This is the password that is required to perform an "instant logon". An instant logon is performed by stacking an equal sign ('=') at the logon graphics prompt. (eg 'C =' instead of simply 'C' for color. NOTE THE SPACE in 'C ='). The user will then be prompted for the instant logon password, his name/password, and will be placed at the main menu. If you wish, you may place all input info on the password line, separated by tildes (~) (as you can on most prompts). This feature is especially useful for local/remote sysops, or mail systems that operate through doors (such as PCRelay, etc). During an instant logon, all text files are skipped and the mail scan is skipped. ALLOW USERS TO SKIP WELCOME: If you want the users to be able to skip the welcome screen by stacking a 'Q' at the logon graphics prompt, set this to 'Y'es. UPLOAD TIME CREDIT FACTOR (ex: 1): This will take the number of minutes used to upload file(s), multiply it by this number, and give a user that much more time after an upload. If it is set at '0', they will lose all of the time it takes to upload. If it is set to '1', they will neither lose nor gain time. If it is set to '2', they will receive twice the amount of time that they spent in the upload, etc. Decimals are allowed in this field. UltraBBS 3.01 Documentation Page 16 USE POST-UPLOAD BATCH FILE: If you want to use the UPLOAD.BAT file as described earlier in the manual, set this to 'Y'es. TEST UPLOADS: Set this to 'Y'es if you would like UltraBBS to test the integrity of all supported compressed files when they are uploaded. Setting this option to 'Y'es is highly recommended, as it helps to filter out aborted and bad uploads. DIRECTORY ID FOR '/' FILES: This is the directory ID that will be placed on all files that start with a '/' in the description. You will probably want to set up a directory with this ID and its security set at sysop level, so that you can look through the privately uploaded files. Also, all files uploaded without descriptions (for example, the user wasn't around when the upload was finished) will be placed in the private directory! USE TERSE CALLER LOGGING: Set this to 'Y'es if you wish to tersely log calls. In terse call logging mode, only the logon/logoff/event messages are recorded to the log, instead of the more detailed messages that are recorded in verbose logging mode. SHELL TO REMOTE DOS: UltraBBS can either exit to remote DOS, or shell to remote DOS. This allows the caller access to the operating system. If you set this to 'Y'es, then UltraBBS will shell to DOS. This is much quicker than exiting, and UltraBBS stays in memory, shrinking down to only 3k. Setting it to 'N' will cause UltraBBS to exit, using the REMOTE.BAT file as if it were a door. Note that when you are at the DOS prompt, you type EXIT to return to the BBS. You don't need to return to the home directory (UBBS3 for example) as UltraBBS does that when it regains control. SHELL TO DOORS: This is the same as the above option, except it applies to the doors instead of remote DOS. UltraBBS shrinks to 3k if 'Y'es. CHECK MESSAGE 'TO': If this flag if set, the then 'To' field of a message will be checked when a user enters a message to make sure that the user actually exists. If the user does not exist, the message enterer will be allowed to reenter, abort, or continue with the message. ALLOW NEW USERS: Set this to 'Y'es if you would like new users to be able to log onto the board. ALLOW ALIASES/HANDLES: Set this to 'Y'es if you would like users to be able to log on with names that are less or more than 2 words in length. This also permits 'handles' to be used, which are selectable by the callers. DELETE FILE FOR USER: If this flag is set, then after a user's individual file (in the file for user field of the user record) is displayed, it will be deleted and the field cleared in the user's record. UltraBBS 3.01 Documentation Page 17 (TI)ME BANK MAXIMUM: This is the maxium amount of time (in minutes) that a user can store in the BBS's time bank (TI) command. USE BIOS OUTPUT: If this is set to 'Y'es, then BIOS output will always be used instead of direct screen writes. If you have an older video card and don't want the "snow", or if you are running under a multitasking program that cannot intercept direct screen writes, you may want to set this to 'Y'es. Screen writes are normally slower when this is turned on. SHOW SECURITY LEVEL SCREEN AT LOGON: If this is set to 'Y'es, then the file SEC (where SEC is the security level of the caller) will be shown. For example a caller with security 200 would be shown the file 200 or 200G. SHOW NEW FILES AT LOGON: Obsolete. You may set this in the LOGON MACRO. ALLOW AUTOPOSTING: If this is set to 'Y'es, the AUTO command is enabled, allowing users to leave messages for the next callers to the BBS. PASSWORD ATTEMPTS: This is the number of attempts that will be permitted. NUMBER OF CONFERENCES: This is the maximum allowable number of conferences. Default is 200, but may be set to virtually any number. OPTIONAL FIELD NAME: This is the name for an 'extra' field usable for any reason by the bbs sysop. It is suggested it be called the 'Mother's Name' field allowing some extra security in case of a lost password. But it could also be Company name, or any other title the sysop wishes. If the user is forced to fill in blanks, this field MUST be filled. If the Optional Field name is blank, the user will NOT be prompted to enter any information. NUMBER OF DESC LINES: This is the number of file description lines permitted. Currently fixed at 10, this will be selectable by version 3.10. NET #x Type y Address z LINES: These are the network definition lines. You may specify any given conference as being a member of network 1-7. That network is of TYPE y. Currently defined networks: 1 = Fidonet, 2 = UUCP network. The rest of each line is the full address of the BBS within that net. Eg. 'pinecliffe.com' is Pinecliffe's UUCP address. COMMUNICATIONS SETTINGS: ----------------------- NODE # OF THIS NODE (ex: 1): This is the number of the current configuration file's node number. If you are running a single node system, set this number to '1'. TOTAL NODES IN SYSTEM (ex: 1): This is the total number of nodes on the system. Single node boards should set this to 1. UltraBBS 3.01 Documentation Page 18 COMMUNICATIONS PORT (ex: 1): This is the communications port used: 'X'=Local, '1'=COM1, '2'=COM2, '3'=COM3, etc. It will support up to 8 COM ports, as long as your FOSSIL driver does. MODEM INITIALIZATION COMMAND: This option varies greatly from modem to modem; however, this does need to do several things: put the phone on the hook, disable auto-answer, turn on extended response codes (CONNECT 2400, etc), and activate the DTR and DCD signals. Read your modem manual for specific information on setting up your modem. See the Modem Configuration section to see if your modem type has been specifically documented. MODEM INITIALIZATION BPS RATE: This is the baud rate to initialize the modem with. UltraBBS supports from 300 to 38400 baud. LOCK MODEM'S BPS RATE: Set this switch to 'Y'es if you would like to lock your modem in at the baud rate entered in the 'F' field of this menu. This is often used on high speed modems, such as the USR HSTs. When you set UltraBBS to lock at the baud rate specified, you should also set your FOSSIL to lock at that baud rate. See the manual of your specific FOSSIL for information on how to do this. LOWEST BPS RATE ALLOWED (ex: 1200): This is the lowest bps (baud) rate you want to allow on your BBS. For example, if you want to allow only 2400 and above, then set it to 2400. If you want to allow only 9600 and faster, then set it to 9600. RTS/CTS FLOW CONTROL: Flow control is needed by many of the newer high speed modems. Set to 'Y'es if your modem needs RTS/CTS flow control. MODEM ANSWER COMMAND (ex: ATA): This is the modem command to make the modem answer the phone. Most modems would use 'ATA' for this command. MODEM OFF-HOOK COMMAND (ex: ATH1): This is the modem command to take the phone off-hook. This command is used each time UltraBBS exits, except in the case of a fatal system error. ALLOW 7E1 CALLERS: Set this to 'Y'es if you would like to support callers using 7E1 or set it to 'N'o if you would like to deny access to 7E1 callers. In some cases, 7E1 callers will cause problems with external door programs. CONTINUE AFTER INIT FAILURE: Set this to 'Y'es if you want UltraBBS to continue as if there was no error after an initialization fails. Under most conditions, you will want to set this to 'N'o as the initialization string places the modem on hook and performs other critical operations. UltraBBS 3.01 Documentation Page 19 NUMBER OF RINGS TO SKIP BEFORE ANSWERING (ex: 0): This option specified the number of rings to wait before answering an incoming call. Setting it to '0' causes UltraBBS to answer immediately (ie: on the first ring), setting it to '1' would cause UltraBBS to skip the first ring (thus answering on the second), and etc. REMOTE DOS REBOOT ON HANGUP: If this option is set to 'Y'es, UltraBBS will reboot the computer if a remote user hangs up after shelling to DOS but before returning to the BBS. SECONDS BETWEEN NODE CHECKS (ex: 5): This sets how often, on multi- node systems, that UltraBBS will check for lock out or log off functions performed by a sysop on another node. It also checks to see if another node would like to chat. On single node systems, for optimum performance, this should be set to 0 (which will NEVER check)! SECONDS TO CONNECT (ex: 30): This is the number of seconds that the user's modem has to connect to the bbs. SECONDS FOR REGISTRATION (ex: 180): This is the number of seconds that a new user has available to register. SECONDS OF IDLE TIME ALLOWED (ex: 180): This is the number of seconds of inactivity (no keyboard input) before UltraBBS hangs up the user for inactivity. SECURITY LEVELS --------------- (B) - (11) SECURITIES: All of these are the security levels for the commands shown. For information on these commands, see the commands section of this manual. MINIMUM LOG ON SECURITY: This is the minimum security required to log onto the board. (G X) SECURITY: Typing 'G X' from the main menu causes UltraBBS to exit to DOS after it logs off the user. This is a remote sysop oriented command and should be set high enough so that normal users can not take down the board. SYSOP MENU SECURITY: This is the security level required to show the user the sysop menu. OVERWRITE FILES SECURITY: This is the security level required to overwrite existing files on an upload. MULTIPLE SAVE SECURITY: This is the security level required to use the multiple save command. The multiple save command allows a user to send one message to more than one person. UltraBBS 3.01 Documentation Page 20 READ KILLED SECURITY: This is the security level required to read a message that has been killed. Packing the message base will remove all killed messages permanently. This option should be set at the sysop level. EDIT/MOVE SECURITY: This is the security level required to either move a file from one message base to another or to edit an existing message. KILL ANY MESSAGE SECURITY: This is the security level required to kill all messages, whether it is from/to the user or not. This option should be set at the sysop level. SKIP MESSAGE PASSWORD SECURITY: This is the security level required to skip the password protection prompt on password protected messages. This option should be set at the sysop level. Note that if a message is encrypted, you will NOT be able to read it without the key. TO-SYSOP MESSAGE SECURITY: If you would like for users to be able to leave messages to the sysop, but not to other users or public messages, you can set the 'E'nter Message security level command above their security level, and place this at or below their level. They will then be allowed to leave messages to the sysop, but not to other callers, or to 'ALL'. The only exception to this security requirement is when a user repeatedly fails the password entry at login and he is allowed to enter a message to the sysop explaining the problem if he wishes. FILE CLASSIFICATION SECURITY: This is the security level required to for a user to be able to specify the directory that his upload goes in. READ PRIVATE MESSAGE SECURITY: This is the security level required to read all private messages, whether it is from/to the user or not. This option should be set at the sysop level. Encrypted Messages CANNOT be read! NEW USER SECURITY: This is the security level given to all new users when they sign up. EDIT ANY DESCRIPTION SECURITY: This is the security level required to edit the description of any file, whether it was upload by the user or not. If you trust your users, you may want to set this to normal security levels. IMPORT INTO MESSAGES SECURITY: This is the security level to import a file into the message base. The command to use this is 'F' from the Message Editing Command prompt. RETURN RECEIPT SECURITY: This is the security level that the user must have in order to request a return receipt on a message. FORWARD MESSAGE SECURITY: This is the security that the user must have to forward his messages (after receiving them) with the (F) end-of- message command. UltraBBS 3.01 Documentation Page 21 PAGE UNAVAILABLE SECURITY: This is the security required to page unavailable users with the (N) command. EDIT HIS OWN MESSAGES SECURITY: This is the security required for a user to edit the text of messages that he entered. NEW USER CONFERENCES/QMAIL PARAMETERS ------------------------------------- NEW USER CONFERENCES: This is the conference string which will be assigned to new users when they first sign up. This string will also be copied into their expired conferences string. The conferences are entered numberically as a string, with ranges permitted. For example: 0-20,33,90-100 will give new users access to conferences 0 through 20 inclusive, 90 to 100 inclusive and 33. NEW USER LOGON MACRO: This string is a series of UltraBBS commands, separated by semi-colon characters. They are executed each time the caller logs onto the BBS. This initial string may later be altered by each caller to suit their own tastes. Some commands have special 'LOGON' versions. For example, $N is a New files listing (with the ability to abort). $B lists the Page Bell hours. $P does a pause-for-any-key. $Y is a mail check command (Y) but allows you to skip the check. So the macro: $N;$P;Y Does a New files listing, followed by a Page bell hours-display, followed by a Y)our Mail scan upon each logon. OFFLINE READING PACKET ID: This is the ID (maximum 8 letters) that will be used to make the filename used in Qmail packets that are received or sent from your BBS. BBS LOCATION: This is the city and state of your BBS, for use in Qmail packets. BBS PHONE NUMBER: This is the phone number of your BBS, for use in Qmail packets. QMAIL MENU FOR PACKET: This is the full path of the Qmail menu that will be placed in with the Qmail .QWK packets. The path should point to a ANSI version (if you have one), since non-ANSI versions will never be used. MAXIMUM NUMBER OF MESSAGES FOR (O), (D C) PACKET: This is the maximum number of messages that a user may pack up in a single (O)ffline or (R)ead (C)apture session. EVENT # 1 - 5 TIMES: This is the time at which these events will be executed. The time '00:00' would cause the event to run at midnight. All times are in 24-hour military format. UltraBBS 3.01 Documentation Page 22 EVENT # 1 - 5 ACTIVE FLAGS: If an event's active flag is on, then the event will be executed, otherwise they will not be. EVENT # 1 - 5 GUARD TIMES: This is the number of minutes before each event during which uploads are not allowed. Uploads must be prohibited, since once they begin, they cannot be controlled and may cause the BBS to be unable to exit at the required event time. CONFERENCES: QUESTIONNAIRES, BULLETINS, DOORS, VOTING BOOTHS From the conference selection screen, you can (Alt-A)dd conferences and (Alt-D)elete conferences. You may only delete the last conference, and to delete it you must have it highlighted (this is to provide a safety guard against accidentally deleting a conference). When you add a conference, you will have the option to copy the data over from another conference so that you can more quickly and easily create new conferences that use similar files and similar parameters. CONFERENCE PARAMETERS --------------------- CONFERENCE NAME (ex: General): This is the name of the conference (up to 40 characters). MESSAGE FILE NAME (ex: C:\UBBS\FILES\GENERAL): This is the name of the conference's message file on the drive. This file should not have an extension, since indexes are used. This parameter should be set differently in each conference, otherwise they will share the same message file, and hence, the same messages! MAIN MENU FILE NAME (ex: C:\UBBS\FILES\MMENU): This is the name of the conference's main menu text file. SYSOP MENU FILE NAME (ex: C:\UBBS\FILES\SMENU): This is the name of the conference's sysop menu text file, displayed to users who have high enough access to see it. NEWS FILE NAME (ex: C:\UBBS\FILES\NEWS): This is the name of the conference's news text file, displayed each call when the user first enters that conference. In conference # 0, this file is displayed when the user first logs on each day. DOORS MENU FILE NAME (ex: C:\UBBS\FILES\DOORS): This is the name of the text file that lists all doors and possibly a brief description for them. This file is displayed to users who select the (OP)en or (DO)or option. DOORS DATA FILE NAME (ex: C:\UBBS\FILES\DOORS.DAT): This is the name of the file that stores the information on each door. This can be edited with SETUP's "Edit Current Doors File" selection from the "Conference Setup" menu. For more information on doors, see the "DOORS" section of this manual. UltraBBS 3.01 Documentation Page 23 BULLETINS MENU FILE NAME (ex: BLTS): This is the name of the text file, shown to users, that lists all bulletins and possibly a brief description for them. BULLETINS DATA FILE NAME (ex: BLTS.DAT): This is the name of the file that stores the information on each bulletin. Bulletins are general text files that users can view from the main menu with the (B) command. This can be edited with SETUP's "Edit Current Bulletins File" selection from the "Conference Setup" menu. QUESTIONNAIRES MENU FILE NAME (ex: QUES): This is the name of the text file, shown to users, that lists all questionnaires and possibly a brief description for them. QUESTIONNAIRES DATA FILE NAME (ex: QUES.DAT): This is the name of the file that stores the information on each questionnaire. This can be edited with SETUP's "Edit Current Questionnaire File" from "Conference Setup". DIRECTORIES MENU FILE NAME (ex: DIR): This is the name of the text file, shown to users, that lists all directories and possibly a brief description for them. VOTING BOOTHS MENU FILE NAME (ex: VOTING): This is the name of the text file, shown to users, that lists all voting booths and possibly a brief description for them. VOTING BOOTHS DATA FILE NAME (ex: VOTING.DAT): This is the name of the file that stores the information on each voting booth. This file is edited with SETUP's "Edit Voting Booth File" selection from the "Conference Setup" menu. UPLOAD DIRECTORY: This is the physical directory where all newly uploaded files in this conference will be placed. WARNING FILE FOR POST: This is a file shown to users to warn them about posting messages in this conference. Typically you might list warnings about forbidden topics (eg DRUGS in the ENVIROMENTAL echo), to save the user problems with the echo coordinator. Optional. CONFERENCE TAG FIELD: This field is optional and describes this conference to other utilities. For example, this field may contain the AREAS.BBS AREANAME field. Not currently used, but will be by 3.10. ALLOW UPLOADS HERE: If you set this to 'N'o, then users will not be allowed to upload when in this conference. ECHO MAIL: If this flag is set, users will be asked whether or not their message should be set to 'Echo'. This is used by several mail systems, including PCRelay and UltraBBS's FIDOCVT. For normal message base operation, set this to 'N'o. UltraBBS 3.01 Documentation Page 24 NET MAIL CONFERENCE: If the ECHO MAIL flag is set to yes, and the NETMAIL flag is also YES, this conference is known to FIDOCVT and others as a NETMAIL conference. Action is taken depending on the: CONFERENCE NETWORK#: This informs utilities like FIDOCVT the NETWORK that this conference is a part of. For example, if it is a NETMAIL conference, in NETWORK 2 which happens to be of type 1 (FIDONET) this will prompt the user for a FIDONET NODE # (and it must be a known FIDONET address). IF it is a UUCP type Network (Type 2), the user is prompted for a UUCP style address (which is of form 'cdb@pinecliffe.com' for example. ALIASES IN MESSAGES: If this flag is set, the user's HANDLE field is used as the FROM field. If aliases are NOT permitted, ths user's REAL NAME is used, even if the user logged in under his handle. This allows you for example to specify a 'handle' to use for your internet name. Then when you post mail from an internet conference, it goes out under that name, not your real name. ESC CODES IN MESSAGES: If this flag is set, users will be allowed to enter escape codes (ANSI sequences) in their messages left in this conference. DEFAULT FILE DIRECTORY: This is the file directory number in this conference to which unclassified uploads will be assigned. FILE DIRECTORY CONFIGURATION ---------------------------- In the file directory configuration screen, you will be displayed the settings of the directory numbers that are defined in this conference. You can modify the four-character, alphanumberic DIRECTORY ID and the DIRECTORY SECURITY for each directory number. Through the Global Changes menu, you can copy the complete file directory settings (including default file directory from the conference parameters screen) from one conference to another. All files, when uploaded, will be given the directory ID of the directory # that they are classified into. Using the directory IDs, you have a great deal of flexibility in how you set up the file directory numbers in different conferences. For example, you could set Directory 1 in Conference 0 for directory ID "GNRL", and set Directory 5 in Conference 12 for "GNRL", and they would contain the exact same files. You may have up to 300 directories per conference. GLOBAL CONFERENCE CHANGES ------------------------- COPY FILE DIRECTORY SETTINGS FROM ONE CONFERENCE TO ANOTHER: This command allows you to duplicate the file system settings from a conference, and place them into another conference. CHANGE UPLOAD DIRECTORY: This command changes the physical upload directory for selected conferences. UltraBBS 3.01 Documentation Page 25 CLEAR USERS' MESSAGE POINTERS IN A CONFERENCE: This command allows you to clear all users' last read message pointers in a specific conference. You should use this after manually deleting a message base, etc. EDIT CURRENT QUESTIONNAIRES DATA FILE ------------------------------------- You may have up to 500 questionnaires per conference. This option allows you to edit the questionnaire data file that is specified in the current conference. QUESTIONNAIRE NAME: The name of this questionnaire (up to 20 characters). QUESTIONNAIRE FILE NAME: The file name of the file that contains the questionnaire's commands. See the questionnaire section of this manual for information on the commands that can be put in this file. ANSWER FILE NAME: The file name of the file to write the questionnaire answers to. SECURITY LEVEL: The security level required for a user to answer the questionnaire. PASSWORD: The password required to answer the questionnaires. EDIT CURRENT BULLETINS DATA FILE -------------------------------- You may have up to 1000 bulletins per conference. This option edits the bulletins data file specified in the current conference. BULLETIN FILE: This is the file name of the bulletin. SECURITY LEVEL: This is the security level required to view this bulletin. PASSWORD: This is the password required to view this bulletin. EDIT CURRENT DOORS DATA FILE ---------------------------- You may have up to 625 doors per conference. This option allows you to edit the doors data file specified in the current conference. DOOR NAME: This is the name of the door (up to 20 characters). BATCH FILE NAME: This is the name of the batch file that runs the door. It should have the extension of .BAT. When this file is executed (the file RUNDOOR.BAT is generated), the node number is passed as a parameter so that the called door batch file can know what node entered the door. SECURITY LEVEL: This is the security required to enter the door. UltraBBS 3.01 Documentation Page 26 PASSWORD: This is the password required to enter the door. BBS TYPE: This is the BBS type of the door. It can be set to PCB14, WILDCAT, RBBS, GAP, UTI, or WWIV. Respectively, the door files created are: PCBOARD.SYS, CALLINFO.BBS, DORINFOx.DEF, DOOR.SYS, UTI.TXT, and CHAIN.TXT. REBOOT ON LOST CARRIER: This flag determines whether UltraBBS will have the FOSSIL reboot the computer if carrier is lost in this door. Under most conditions, you will not want to use this. SINGLE USER: This flag if set to Y will cause UltraBBS to disallow multiple nodes access to the door at the same time, greatly simplifying door batch files. Once a node is in the door, other nodes will get a 'single user door in use' message if they try to execute the door. TEMPORARILY DOWN: This flag if set to Y (the 14 command) will cause ANY access to the door to be rejected with a 'This door is temporarily down' message. EDIT CURRENT VOTING BOOTHS DATA FILE ------------------------------------ You may have up to 45 voting booths per conference. This option allows you to edit the voting booths data file specified in the current conference. VOTING TOPIC: This is the question to be voted on. SECURITY FOR VOTING BOOTH: This is the security level required to vote on this topic. VOTING RESULTS DATA FILE: This is the data file in which the results of this vote will be stored. PASSWORD FOR VOTING BOOTH: This is the password required to vote on this topic. VOTING CHOICES: These are the possible answers which can be voted for. EDIT CURRENT LIMITS DATA FILE You may have up to 256 limits entries defined. This option edits the limits data file that is specified in the current node's configuration. SECURITY LEVEL: This is the security level for which the following parameters will apply. MINUTES PER DAY: This is the total number of minutes that users of the above security level will get each day. UltraBBS 3.01 Documentation Page 27 DOWNLOADS PER UPLOAD: This is the total number of files that the user can download for each file he uploads. If you set this to 0, the user will have no upload/download file ratio. DOWNLOAD KILOBYTES PER UPLOAD KILOBYTE: This is the total number of kilobytes that the user can download for each kilobyte he uploads. If you set this to 0, the user will have no upload/download kilobyte ratio. AUTO LOGIN DOOR NUMBER: This is the door number which users of this security level will automatically be placed in whenever they login. To disable this feature, set this parameter to 0. When a user logs in, this door number is always opened, with no security level checking for the (DO)or command, or the door # itself. DAILY DOWNLOAD K LIMIT: This is the maximum number of kilobytes that a user of this security level can download in one day. EDIT CURRENT NO UPLOADS DATA FILE You may have up to 1450 no upload entries defined. This option edits the no uploads data file that is specified in the current node's configuration. WILDCARD SPECIFICATION: This is the wildcard specification for which the following parameter will apply. SECURITY LEVEL: This is the security level required to upload any file matching the above wildcard. If a user, in a batch transfer, uploads a file that he does not have high enough security to upload, it will be placed in the file holding directory and he will receive no credit. EDIT CURRENT PROTOCOLS DATA FILE You may have up to 256 protocols defined. This option edits the protocols data file that is specified in the current node's configuration. The default protocols data file that comes with UltraBBS contains the main protocols used today, and uses the DSZ and BIMODEM drivers. If you wish to use the protocols data file and the protocol batches that come with UltraBBS, you will need to acquire these two programs (DSZ and BIMODEM). They are available on most BBSes, including the UltraBBS test sites. PROTOCOL LETTER (ex: Z): This is the letter with which the user will select this protocol. PROTOCOL TYPE (ex: M): This is the type of protocol--'S'ingle File or 'M'ultiple File Support, or 'B'idirectional Transfer Support. UltraBBS 3.01 Documentation Page 28 UPLOAD BATCH FILE (ex: RZ.BAT): This is the name of the batch file that is invoked by UltraBBS to receive a file from the user. The parameters passed to it are: %1 = Port Number (1, 2, 3, etc), %2 = Baud Rate (300, 1200, etc). On non-@-supporting protocols, %3 - %9 = File Names to Send, and on @-supporting protocols, %3 = File Name of the "@" list file. DOWNLOAD/BIDIR BATCH FILE (ex: SZ.BAT): This is the name of the batch file that is invoked by UltraBBS to send a file to the user. The parameters passed to it are: %1 = Port Number (1, 2, 3, etc), %2 = Baud Rate (300, 1200, etc), %3 = File Name to Receive (Only on non- batch protocols). This batch file is also invoked when a bidirectional transfer is executed. The parameters passed to a bidirectional batch file are: %1 = Port Number (1, 2, 3, etc), %2 = Baud Rate (300, 1200, etc). On non-@-supporting protocols, %3 - %9 = File Names to Send, and on @-supporting protocols, %3 = File Name of the "@" list file. PROTOCOL NAME (ex: Zmodem): This is the name of the protocol. BATCH "@" SUPPORT (ex: Y): This flag designates whether or not the protocol supports the "@" filename list parameter. This allows the user to download up to 99 files on a batch transfer. Without this, the user can only transfer several files at a time. DSZ.LOG WRITING SUPPORT (ex: Y): This flag designates whether or not the protocol writes a DSZ.LOG-format file. If you set this flag, you must have your DSZLOG environment variable set (via the DOS "SET xxx=yyy" command) to a legitimate filename (complete, with drive and path). This file will be created by the protocol driver, and need not exist. If your protocol does write a DSZ.LOG-format file, it is strongly recommended that you use this option, as it greatly improves the download capabilities of the BBS. On multi-tasking systems, the DSZ.LOG file paths MUST be different for each node (task). If the protocol does not write a DSZ.LOG file, then UltraBBS assumes the transfer was successfully completed, unless it finds a file called ABORT (which should be created by your batch file) in the UltraBBS directory, in which case it assumes the transfer was aborted. EDIT CURRENT COMPRESSION METHODS DATA FILE You may have up to 275 compression methods defined. This option allows you to edit the compression methods data file which is specified in the current node's configuration. NOTE: The first compression method specified in this data file will act as the default compression method for commands such as (O), (R D), etc. COMPRESSION EXTENSION (ex: ZIP): This is the extension used by this compression type. UltraBBS 3.01 Documentation Page 29 COMMAND FOR VIEWING (ex: zip -v $FILE$ >$OUT$): This is the command executed by UltraBBS to view the contents of a compressed file. $FILE$ = File name of the compressed file, $OUT$ = File name to send output to. COMMAND FOR ADDING (zip -a $FILE$ $LIST$): This is the command executed by UltraBBS to add a file to a compressed file. $FILE$ = File name of the compressed file, $LIST$ = List of file names to add to the compressed file. COMMAND FOR EXTRACTING (unzip $FILE$ $LIST$ $DIR$): This is the command executed by UltraBBS to extract a file from a compressed file. $FILE$ = File name of the compressed file, $LIST$ = List of file names to extract from the compressed file, $DIR$ = Directory to extract the files to. COMMAND FOR TEST (unzip -t $FILE$ >$OUT$): This is the command executed by UltraBBS to test a compressed file's integrity. $FILE$ = File name of the compressed file, $OUT$ = File name to send output to. TEXT TO INDICATE ERROR (ex: contains error): This is the text to check for in the output file after a compressed file integrity check. If this text is found in the file, it is assumed that the compressed file is corrupted. EXPLANATION OF ULTRABBS DATA FILE USE ------------------------------------------------------------------------- The use of data files by UltraBBS, such as the data files for questionnaires, voting booths, doors, bulletins, limits, no uploads, protocols, compression methods, conferences, and others allows the sysop of an UltraBBS a lot of flexibility. The names of some data files (such as compression methods, conferences, limits, no uploads, protocols) are specified from the main BBS parameter screens in U3SETUP. These data files can be the same or different on all nodes in your system (if you run a multinode system). To edit the data file which is specified in the currently loaded copy of U3SETUP, select the appropriate main menu option in U3SETUP (for example, "Edit Current Compression Methods Data File", "Conferences: ...", etc). The names of other data files (such as doors, bulletins, questionnaires, and voting booths) are specified from the Conferences Parameters screen. These data files can be the same or different in different conferences. The data file specified in the your current conference is edited by selecting the appropriate option from the Conference Setup menu (for example, "Edit Current Doors Data File"). This system allows you to, for example, have a different set of doors in conference # 1 than are in conference # 0. Simply specify different doors data file names in each conference, and set them up. On the other hand, you could set all (or some of) your conferences to read UltraBBS 3.01 Documentation Page 30 from the same doors data file, and they would all have the same set of doors, because if the data file name is the same, then editing that data file in one conference's setup is going to make the same change in all other conferences that read from that same data file. UltraBBS 3.01 Documentation Page 31 U3MANAGE PROGRAM ------------------------------------------------------------------------- UltraBBS Manager Program (U3MANAGE.EXE) Copyright (c) 1991-1993 Craig Baker, All Rights Reserved USER FILE EDIT -------------- USER NAME: This is the name that the user uses to log in, and cannot be changed for indexing purposes. LOGON FILE NAME: This is the file that will be displayed to the user when he logs in to the BBS. SYSOP COMMENT: This is an optional field where the sysop can jot down any general comments about a user, for future reference. VOICE TELEPHONE NUMBER: This is the user's voice telephone number. DATA TELEPHONE NUMBER: This is the user's data telephone number. LAST DATE ON: This is the user's last date on the BBS. LAST TIME ON: This is the user's last time on (on the above date). LAST FILE CHECK: This is the last date that the user did a new file search. BIRTH DATE: This is the user's birth date. EXPIRATION DATE: This is the date that the user's subscription to the BBS expires and his security level and conferences are set to the expired values. SECURITY LEVEL: This is the user's security level. EXPIRATION SECURITY LEVEL: This is the security level that the user will receive after his subscription expires. NUMBER/KILOBYTES OF DOWNLOADS: This is the user's number & kilobytes of downloads. NUMBER/KILOBYTES OF UPLOADS: This is the user's number & kilobytes of uploads. PASSWORD: This is the user's password MOTHER'S NAME: This is the user's mother's name. Useful for security. ADDRESS: This is the user's address field (not including city/state). CITY/STATE: This is the user's city/state. UltraBBS 3.01 Documentation Page 32 HANDLE/ALIAS: This is an alternate logon that permits the user to access the BBS with EITHER account 'name'. If the BBS is set to not permit handles, then this field is ignored. Although either name can be used to access the BBS, UltraBBS keeps track of time usage etc only in a combined manner. In conferences that don't permit 'handles' your real account name is substituted in the FROM field of a message, even if you log in under the handle. ELAPSED MINUTES: This is the user's total elapsed minutes on his last date called. PAGE LENGTH: This is the user's page length. MASTER USER: This flag if set identifies this account to UltraBBS as a MASTER account. It is not logged off for any reason, and is permitted access EVEN if it is already online or the BBS is down. MASTER USERS can also bring down the bbs, log all callers off and other system-level tasks. TIMES ON: This is the user's number of times on. DEFAULT TRANSFER PROTOCOL: This is the user's default transfer protocol. AUTO PAGE FLAG: This determines if/how the sysop will be paged when the user logs on. If set to 'N', the sysop will not be paged. If set to 'V', the sysop will be paged and the user will be notified. If set to 'I', the sysop will be paged and the user will not be notified. EXPERT MODE: This is the user's expert mode flag. DELETE FLAG: If this flag is set, then the user will be deleted when the user file is packed. FULL SCREEN EDITOR: If this flag is 'Y', the user will be put in the full screen message editor whenever possible. If 'N', the user will never be put into the full screen editor. If 'A', the user will be asked whether or not he wishes to use the FS editor. DOORS ENTERED: This is the number of doors that the user has entered. MESSAGES ENTERED: This is the number of messages that the user has entered. CLEAR SCREEN: This flag specifies whether or not the screen will be cleared before reading a message. UltraBBS 3.01 Documentation Page 33 QWK NET STATUS: This flag sets the user's net status for QWK packets. If this it activated, then all QWK packets downloaded by the user through the (O) command will have full net status, and all REP packets received from the user will be treated as net packets. If this flag is not activated, normal QWK operation will occur. Do not activate this flag unless you are fully aware of its effects. TIME STORED: This is the amount of time that the user has stored in the (TI)me bank. KILOBYTES DOWNLOADED TODAY: This is the amount of kilobytes that the user has downloaded on his last date on. CONFERENCES: This is the user's conference string. The conferences which are marked with an 'X' are the conferences which the user can enter. EXPIRED CONFERENCES: This will be set as the user's conference string when his subscription expires. SCAN CONFERENCES: This is the user's scan conference string. The conferences that are marked with an 'X' are scanned/auto read. USER FILE PACK -------------- This commmand allows you to remove deleted users, users with low security, or users that have not called in a specified amount of time. It also updates the user indexes (in ULTRABBS.NDX) and alphabetizes. USER FILE GLOBAL CHANGES ------------------------ ADD/REMOVE CONFERENCE: This allows you to add or remove conferences from users' conference strings (normal, expired, scan, or all of them). You can specify the minimum security and maximum for the change to take place. CHANGE SECURITY LEVELS: This allows you to change a range of user security levels (normal levels and/or expired levels). FLAG/UNFLAGE ALL USERS OF SPECIFIC SECURITY LEVELS FOR DELETION: This allows you to flag or unflag a range of security levels for deletion. You will be prompted for the security level range, and then whether you wish to flag these securities for deletion, or unflag them. FILEBASE FILE EDIT ------------------ FILE NAME: This is the name of the file, and cannot be changed for indexing purposes. TIMES DOWNLOADED: This is the total number of times that this file has been downloaded. UltraBBS 3.01 Documentation Page 34 LAST DATE DOWNLOADED: This is the last date on which this file was downloaded. FREE FILE: If this flag is set, then the file will not be penalized to the user's upload/download ratio. TRULY FREE FILE: If this flag is set, the file will be downloadable EVEN if the caller has too little time left. NEW FILE: If this flag is set the file is ALWAYS shown on a NEW FILES listing. ONE DOWNLOAD ONLY: If this flag is set the file is killed after a single download. INVISIBLE: If this flag is set the file is downloadable but NOT visible to any search or list. RETURN RECEIPT: If this flag is set the sysop will see a return receipt message any time the file is downloaded, listing the downloader and time. DATE OF UPLOAD: This is the date that the file was uploaded to the BBS. DIRECTORY ID: This is the directory ID that the file has been assigned. FILE SIZE: This is the size, in bytes, of this file. If the size is set to 0, then the actual size of the file on the disk will be checked instead of using this value. DELETE FLAG: If this flag is set, this file will be deleted in a pack (if you specify). UPLOADED BY: This is the name of the user who uploaded the file. In the case of a TIC file uploaded via U3MANAGE, this field contains the TIC area name, together with the originating Node. FILE LOCATION: This is the full path and file name of this file on the physical drive. (NOTE: It is recommended, although not required, that the NAME of the file on the FILE LOCATION parameter be the same as the NAME of the file in the above FILE NAME parameter; however, the DIRECTORY of the file in the FILE LOCATION parameter can be whatever you wish. If you do use a different name on the FILE LOCATION parameter, problems can occur with protocols that allow users to add files during a transfer--such as BiModem.) DESCRIPTION: This is a description (10 lines) of the file. Note - if a file is uploaded to the BBS that contains a .DIZ or an .SDI entry (a special file withing the archive that contains a detailed description) that description is automatically entered by the BBS, and the user is NOT required to furnish one. UltraBBS 3.01 Documentation Page 35 MOVE FILE COMMAND: This can be used to move a file from one physical drive directory to another. When asked for the new file name, you must type a complete path/file name. CHECK EXISTENCE/SIZE COMMAND: This can be used to check the existence of a file and the size of the file of it exists. After you execute this command, you will be told whether or not the file exists. If the size is wrong, you will be given the option to adjust it. FILEBASE FILE PACK ------------------ This command allows you to removed deleted files, old files, or files that have not been downloaded in a long time. It also updates the FileBase index (in ULTRABBS.NDX), and alphabetizes the file listing. The files are reindexed, (on the keywords in the description) and this takes considerable time. FILEBASE FILE GLOBAL CHANGES ---------------------------- CHANGE FILE DIRECTORY IDS: This allows you to change files' directory IDs. You will be prompted for the directory ID to change, and what you wish to change it to. FLAG/UNFLAG ALL FILES OF SPECIFIC DIRECTORY ID FOR DELETION: This allows you to flag or unflag all files of a certain directory ID for deletion. You will be asked for the directory ID, and then whether you wish to flag them for deletion, or unflag them for deletion. CHECK EXISTENCE/SIZE OF ALL FILES: This command goes through all files in the FileBase and checks for their existence. If they do not exist, it will prompt you to either flag them for deletion, ignore them, change their path, or abort the checking. If they do exist, their size will be checked. If their size is not the same size as the size on the actual file on disk, you will be prompted as to whether or not you wish to correct the size on the file. CHANGE DRIVE/PATH ON FILES IN FILEBASE: This command allows you to change all files in the FileBase with a specific drive/path to a different drive/path. PACK AND/OR RENUMBER MESSAGE FILES ---------------------------------- This command is used to pack and/or renumber the system's message files. You will be presented with the option to choose a specific conference, or (A)ll conferences. You will also be presented with options to kill specific types of messages. A message that meets any of the kill qualifications will be killed. When packing, the message numbers remain the same, and specified messages/killed messages are removed from the message file, thus making the file smaller. When renumbering, the message numbering restarts at your specified value. All message reference numbers, user last read message pointers, and attached files are updated during a message pack. UltraBBS 3.01 Documentation Page 36 GENERATE A MASTER FILE LIST --------------------------- This command allows you to create a list of all files available on your BBS for download by your users. You will be asked for the conference. This produces a sorted list in a file generated from the first four letters of the bbs name followed by '....ALL.TXT'. Additional files are generated on a per directory basis. E.g. '....001.TXT' would be a list of all files in directory 001. IMPORT A TEXT DIRECTORY INTO THE FILEBASE FILE ---------------------------------------------- This command allows you to import a variety of text files into the UltraBBS Filebase. 1) PCBoard-style DIR files 2) OPUS-style FILES.BBS files 3) DOS text directories (obtained by redirecting the DIR command) 4) TIC files. (files from the various File distribution Networks) 5) CD Rom disks, as a unit. U3MANAGE can import a whole CD at at time, and has been tested with Night Owl, Phoenix, Black Box, Software Vault. In fact, ANY CD-Rom what has FILES.BBS or SFFILES.BBS files in the directories along with the files themselves will more than likely be imported properly. Please contact the author if you have any problems here. When you tell the program to import a CD, it prompts you for the Drive letter (eg. F). Then the whole CD is scanned for FILES.BBS entries. Each one found will have the first screen or two of files listed, and you will be prompted for the UltraBBS DIR ID for this directory. When all directories have been processed, U3manage will give one final chance to abort the process. If U3manage is told to continue, ALL files on the CD Rom will be imported into the filebase. If needed, it will ask for many of the fields that are required, such as what directory ID to give the files, etc. When you use this command, all files in the text directory must be in the same disk directory, and must all be getting the same directory ID (except for .TIC files, which use information contained in an AREAS.TIC file). Otherwise, you must split up the text file and import the sections individually. Files in the directory that already exist in the FileBase will not be imported. READING .TIC files: This is optionally available at the command prompt as U3MANAGE /IMPORTTICS. U3MANAGE reads a file AREAS.TIC containing lines like the following: TICDIR P:\FILES\INBOUND TICDIR P:\FILES ; ^ informs U3MANAGE of a directory to be searched for .TIC files ; comments start with a ; AREANAME UDIR P:\FILES\DOWNLOAD ; ^ the TIC AREA name ; ^ <- the UltraBBS 4 letter DIRECTORY ID for the new file ; ^ where the file is to be MOVED after importation. UltraBBS 3.01 Documentation Page 37 An alternative to this command is the (U)pload command while logged in locally. This will allow you to move the files you wish to "upload" into the system's batch directory, and it will then process them and ask you for descriptions. This method is preferable for a sysop who wishes to post files on his system. However, for doing initial BBS conversions from PCBoard (or other software) to UltraBBS, the import would be much faster. ADD .GIF RESOLUTIONS TO FILE DESCRIPTIONS ----------------------------------------- This command adds the resolution of all .GIF files to their description. It detects resolutions already in the description, so running it more than once will not add the resolution multiple times. The resolution will be placed in the form "(800x600x256)", etc. It will be placed at the end of the first line of the description that has enough space at the end. IMPORT A PCBOARD 14.X USER FILE ------------------------------- This command allows you to import a PCBoard user file into the UltraBBS user file. All users from the PCBoard user file will be added to the current UltraBBS user file. All of PCBoard's fields except the user- maintained comment field (C1) are converted; however, when you use this option, users will have no birth dates set and will be asked for their birthdate next time they log on. Users in the PCBoard user file who already exist in the UltraBBS user file will not be imported. UltraBBS 3.01 Documentation Page 38 COMMAND DESCRIPTIONS ------------------------------------------------------------------------- (A)BANDON CONFERENCE Subcommands: None. Description: Returns you to conference 0. (AUTO)post. Subcommands: None. Description: Takes up to a 5 line message to be presented to all callers upon login. Disabled if the global 'AUTOPOST' Flag is set to NO. At most 4 messages are visible at the same time, with the oldest message being overwritten by the next. (B)ULLETINS Subcommands: (#) Bulletin # to View. (L) List the Bulletin Menu. Description: Allows viewing system Bulletins. Numbers can be "stacked" such as "7 3 1" or "2;1;5". (BB)S LISTING Subcommands: (A)dd a BBS to the Listing, (D)elete a BBS from the listing, (M)odify a BBS on the Listing, (L)ist the BBS Listing. Description: Allows viewing and changing the BBS Listing that is maintained by the BBS. (BI)DIRECTIONAL TRANSFER Subcommands: (filename) Names of file(s) you wish to download (extension is not required if you are downloading a file that has one of the supported compression extensions). Description: Allows a bidirectional transfer, which transfers files simultaneously between you and the BBS. After UltraBBS determines your protocol type (commonly BiModem), you will be prompted for the filename(s) you wish to download. After the transfer, UltraBBS will automatically determine if/what files were uploaded, and prompt you for their descriptions and directory number. Consult your local sysop for more details on bidirectional transfers. (BR)OADCAST: Subcommands: None. Description: Allows a message of up to 5 lines to be displayed to all users online, or who log in to the system while this broadcast is still active. For a master user, it also allows the automatic logging off of users who have read the Broadcast, and bringing down the BBS (displaying this same message to any new caller, then logging them off autmatically as well). (C)OLOR (ANSI) MODE Subcommands: (N)o ANSI color/graphics, (B)lack and White ANSI graphics, (C)olor ANSI graphics, (R)ip graphics. Description: Changes your screen display mode. If you select graphics and get a lot of ([31;1m, etc) displays on your screen mixed in with the normal text display, your software does not support ANSI graphics and you should toggle ANSI off. UltraBBS 3.01 Documentation Page 39 (CH)AT WITH OTHER (NO)DES Subcommands: (T) Toggle your available for chat flag. This can be stacked at the command line. Also available at the node chat menu. (Q) Exits node chat. Available at the node chat menu. (P) Page a node to the main channel. Available at the node chat menu. (C) Change node chat channels. Available at the node chat menu. (B) Broadcast message to other users. Available at the node chat menu. (H) Handle change (alias selection) Available at the node chat menu. (W) Who's online. (L) List active public conferences. Description: Allows you to talk to users who are on other nodes, if the BBS is a multi-node system. You may page other users to the main node chat channel with the (P) subcommand. If you wish to start a separate conversation, you can change channels using the (C) subcommand. When you change channels, you are permitted to select a channel number from 1 to 99. Channels 90-99 are for private conversations (two users only), whereas channels 1-89 are for public multi-party discussions. The first user into one of these channels may optionally declare a NAME for the chat channel, together with a Password. When the last user exits a public named channel, the name is discarded. During chat, everything you type will be sent to all other users who are in your node chat channel. You will also be notified whenever anybody exits or enters your node chat channel. Before any characters you type are displayed, a header is generated on all nodes informing them of the node that is now typing, including the name of that caller. (H) allows you to select a handle (temporary alias only valid during this nodechat session). (B) allows you to broadcast to other users on the BBS. (D)OWNLOAD A FILE Subcommands: (filename) Name of the file(s) you wish to download (extension is not required if you are downloading a file that has one of the supported compression extensions). Description: Allows download files from the BBS to your computer. After UltraBBS determines your protocol, you will be for the filename(s) (depending on whether or not you using a batch transfer) you wish to download. After selecting the filenames, you will have the choice of selecting (G)oodbye after transfer, which, if selected, will give a 15-second countdown at the end of the transfer, after which, if you do not abort it, will log you off automatically. UltraBBS 3.01 Documentation Page 40 (E)NTER MESSAGE Subcommands: None. Description: Allows you to place a message on the BBS. If aliases are allowed in the current conference your FROM field will reflect your handle (if that is what you used to login), or your real name if aliases are NOT permitted. You will then be prompted for who to send the message to. You may enter 'S' to send it to the sysop. Hitting (Enter) will send the message to "ALL". Next, you will be prompted for the message subject. If you hit (Enter) at this prompt, you will be returned to the main menu. After entering the subject, you will be prompted for the message security type. You can get help on security types by selecting '?'. A message may be (U)nprotected, (R)eceiver Only, (P)assword protected, or (E)ncrypted. Receiver only means only the addressee may read the message. Password protected will prompt for a password and the recepient will need to supply it to read the message (or have sufficiently high security to be able to skip these two requirements. ON ENCRYPTION: Encrypted messages may be read by NO ONE, without the encryption key. A cryptologically secure (as far as is known at this time) method is used. It would take years (or hundreds of years) to discover the key by brute force attacks. If the key is lost, the message is essentially lost as well. A sysop may KILL an encrypted message but NOT read it! The encryption method requires the existance of the file UBBSENC.DAT located in the same directory as ULTRABBS.NDX and FILEBASE.DAT. If the sysop removes this one file, encryption is disabled and users will be told encryption is not permitted on this BBS. UltraBBS is the ONLY BBS package featuring this sort of message capability. After message security, you will be prompted, if you have ANSI on, whether you wish to use the full screen message editor, a vast improvement over the line editor (if you have a full screen editor default set, then you will not be asked the full screen editor question). Lastly, if the message is not to "ALL", you will be prompted whether you wish to receive a "return receipt" when the message is read by the receiver. This is a short notification message that is sent to you by UltraBBS that tells you your message was received. After this, you will be able to enter the text of the message. Further help is available from most of the other command line prompts. (ED)IT DESCRIPTION OF A FILE Subcommands: (filename) Name of the file that you wish to edit the description of. Description: Allows you to edit the description of a file that you have uploaded. After entering a valid filename, you will be displayed the old description, and prompt for a new description. This option can be used if you mistype a description, or if you entered incorrect data. UltraBBS 3.01 Documentation Page 41 (F)ILE DIRECTORY LISTINGS Subcommands: (E)xtended or (S)tandard directory display type. (#) File directory number(s) to display, stacking allowed. (L) Display a list of all file directories available. (D)ownload, (F)lag Files, and (VI)ew Compressed Files are available on this menu and perform the same function as their equivalent commands on the main menu. Description: Allows you to list out the file directories, or get a list of all file directories. (FL)AG FILES FOR LATER DOWNLOAD Subcommands: (filename) Names of file(s) you wish to flag for download. (D) Clear list of flagged files. Description: Allows you to flag files for later download. The filenames you specify (stacking allowed) will be added to a "queue" which will be used by the (D) and (B) commands when you begin a transfer. The (D) subcommand can be used to clear this queue. (G)OODBYE Subcommands: None. Description: Disconnects you from the BBS. (I)NITIAL WELCOME/NEWS Subcommands: (W) Redisplays the initial welcome screen. (N) Redisplays the news file for the current conference. Description: Redisplays the initial welcome screen or the news file for the current conference. The initial welcome screen also includes the BBS name, node number, and the version of UltraBBS. (J)OIN A CONFERENCE Subcommands: (#) or (Name) Any valid conference number or name. (+) or (-) Move backward of forward through conferences. Description: Allows joining a conference on the BBS. The conference number to be joined can be stacked with the (J) command if desired. If you are not registered in the conference requested, you will be notified and returned to the main menu. A (J 0) or an (A) command will return you to the main conference. (K)ILL A MESSAGE Subcommands: (#) Any valid active message number. Description: Allows marking a message as inactive (killed) so that users can no longer read it. When the sysop packs the message base, the message will be purged from the system (unless it is restored). (L)OCATE A FILE BY NAME Subcommands: (N) Searches through only the new files (must be stacked on command line, ie: (L N) from main menu). (E)xtended or (S)tandard directory display type. (wildcard) Wildcard to search for. (dir number) The directory number(s) (separated by spaces) which you wish to search in--(Enter) means all directories and a (D) specified the default directory (usually the upload directory). Description: Allows you to search the file directories for filenames which match the DOS wildcard specification you enter. The standard DOS wildcard '*' and '?' may be used, but do not have to be used. However, the wildcard specification cannot start with a wildcard character. (M)ODIFY SCAN CONFERENCES Subcommands: (Y/N) Use Yes/No Scan Update Method?. Description: Allows updating of your scan conferences string. This string is used for such commands as (R A), (Y), and (O). UltraBBS 3.01 Documentation Page 42 (N)EW FILE SCAN Subcommands: (E)xtended or (S)tandard directory display type. (MM/DD/YY) Date to search from, (Enter)=last date checked. (dir number) The directory number(s) (separated by spaces) which you wish to search in--(Enter,A) means all directories and a (D) specified the default directory (usually the upload directory). Description: Allows you to search the file directories for files that were uploaded on or after the date specified. The date defaults to the last date you used the (N) command. (O)FFLINE MESSAGE READING Subcommands: (U) Allows you to upload a .REP file for the BBS. (D) Creates a .QWK file for the BBS to send to you. (S) Selects conferences for inclusion in .QWK file. Description: .QWK files sent by UltraBBS are Qmail-compatible, and can be used by most popular offline reading programs, such as EZ-Reader, Qmail DeLuxe, Session Manager, or SLMR. After replying to messages using one of these programs, you will upload your replies as a .REP file and they will be placed into the BBS's message bases. (OP)EN A (DO)OR Subcommands: (#) or (Name) Number or name of the door to open. Description: Runs an external program, outside of the UltraBBS program. There are many different door applications available, check with your sysop for questions on specific doors. Note: using the (DO) or (OP) command is not required, you may type in the partial or complete name of a door at the main command line. (P)AGE SYSOP TO CHAT Subcommands: None. Description: Allows paging of the sysop to come to the keyboard and chat with you. (Ctrl-X) aborts. (Q)UESTIONNAIRES Subcommands: (#) Questionnaire # to answer. Description: Allows you to answer a questionnaire which the sysop has created. Descriptions of the available questionnaires can be found in the menu which is displayed when you type (Q). (R)EAD MESSAGES Subcommands: (A) Reads new messages in all of your selected conferences. (S) Reads all messages since your last read. (#) A valid message number to read, with a (+) or (-) optional. (+) Reads messages forward from current message. (-) Reads messages backward from current message. (F) Selects "only messages from you" mode. (Y) Selects "only messages to you" mode. (YA) Selects "only messages to you and ALL" mode. (T) Selects "text search" mode (AND/OR searches allowed). (N) Returns to normal mode (cancels all modes). (U) Selects "only messages to/from another user" mode. (O) Selects "read only" mode (last message read pointers not updated). (J) Join a conference (same as on main menu). (RE)set last read message pointers (same as on main menu). (I) Switches between message read and message scan. (C) Selects "message capture to disk" mode. (D) Downloads the capture file made from the (C) command. Description: Allows reading messages left on the BBS. All public messages will be displayed, along with private messages left either by you or for you. Messages with password protection will prompt you for their password before displaying. After each message display, you will be presented with a set of options for what to do next and you may obtain further help if needed from there. UltraBBS 3.01 Documentation Page 43 (RE)SET LAST READ POINTER Subcommands: (#) Message number to set your last read message pointer to in this conference. Description: The (RE)set command allows you to set your last read message pointer to whatever message number you wish in the current conference. This is especially useful for users who read their mail offline with an offline reader system like Qmail/MarkMail/MegaMail. (S)CAN MESSAGES Subcommands: (A) Scans new messages in all of your selected conferences. (S) Scans all messages since your last read. (#) A valid message number to scan, with a (+) or (-) optional. (+) Reads messages forward from current message. (-) Reads messages backward from current message. (F) Selects "only messages from you" mode. (Y) Selects "only messages to you" mode. (YA) Selects "only messages to you and ALL" mode. (T) Selects "text search" mode (AND/OR searches allowed). (N) Returns to normal mode (cancels all modes). (U) Selects "only messages to/from another user" mode. (J) Join a conference (same as on main menu). (RE)set last read message pointers (same as on main menu). (I) Switches between message read and message scan. Description: Allows scanning the headers of all messages. All public messages will be displayed, along with private messages left either by you or for you, and password protected messages. Scanning does not update your last read message pointers, and can be used as a way to "look ahead" into your unread messages. SysOps will see a 'K' after the number of any killed messages. (T)RANSFER PROTOCOL Subcommands: (p) Any valid protocol that is defined on the BBS. Description: Allows setting your default transfer protocol for use on the BBS. Before selecting your protocol, you will be displayed a listing of all protocol available on the BBS. If you choose 'N' (None) , you will be prompted for a protocol each time you request to transfer a file. For more information, consult your sysop. (TI)ME BANK Subcommands: None. Description: Allows you to store extra time in a time bank. You will be displayed the amount of time in the bank, the maximum you can store in the bank, and your total time available. You will be prompted for the amount of your total time which you wish to place in the bank. If you ever run out of time on the BBS, you will be allowed to retrieve extra time from the time bank, or you can retrieve time at any time using the (TI) command. (U)PLOAD A FILE Subcommands: (filename) Only required in a non-batch transfer. Description: If you use a non-batch protocol, you will be prompted for the filename before the transfer. If not, the filenames are automatically determined by UltraBBS. After the upload, UltraBBS will check all the files, and prompt you for their descriptions. You have up to 5 lines for each description, and after entering descriptions, if the sysop desires, you will be prompted for the directory number to place the file into. It is always recommended that you use the (F) command to make sure that none of the files that you are going to upload already exist on the BBS. (NOTE: Local users can 'upload' files by using the (U) command. A special 'local upload mode' will be activated and you will be able to copy the files you wish to upload into the batch directory.) UltraBBS 3.01 Documentation Page 44 (US)ER LIST/SEARCH Subcommands: (text) Text to search for in user file. Description: Allows listing the users who have access to your current conference, with an optional search string. (V)OTING BOOTHS Subcommands: (#) Voting booth # to participate in. Description: Allows participating, or viewing the results in, a voting booth set up by the sysop. (VER) command. No subcommands. Gives information on the compilation date, free memory, number of nodes, and time on the BBS. Useful for checking on the status of a node remotely. (VI)EW COMPRESSED FILE Subcommands: (filename) Name of the compressed file that you wish to use (extension is not required if you are viewing a file that has one of the supported compression extensions). Description: Allows you to view a compressed file (ex: ZIP, ARC, LZH, etc). Before being prompted for the filename, you will be displayed a list of all supported compression types on the BBS. Only files of those types are valid choices. Once you have selected a file, you are able to (T)est the compressed file's integrity, (L)ist the contents of the compressed file, (V)iew a text file from within the compressed file, or (E)xtract files from within the compressed file, and download them. (W)RITE/VIEW USER STATISTICS Subcommands: Described below. Description: Allows changing some of your data base information stored on the BBS, including: your ANSI mode, your city/state, your voice phone number, your data phone number, your expert mode, your date of birth, your default page length, your full screen editor default, your password, your default transfer protocol, your clear screen flag, and your scan/auto read conference string. Allows viewing your current user settings, including: your name, the number of files you have downloaded, the number of files you have uploaded, the number of doors you have entered, the number of messages you have entered, the number of times on by you, your page length, ANSI mode, your default transfer protocol, the date of your last new file check, your voice phone number, your data phone number, the next event time, the next event date, the current date, the current time, your last date on, your last time on, your logon date, your logon time, your date of birth, your city and state, your expiration date, your security level, your menu expert mode, sysop page bell on/off, your full screen editor default, the conferences you have access to, your clear screen flag, and the conferences which you have selected to scan or auto read. (WH)O'S ON OTHER NODES Subcommands: None. Description: Displays to you the status of other nodes, if any, in the BBS system. (X)PERT TOGGLE Subcommands: None. Description: The (X) command toggles between expert and novice mode. When the expert mode is on, the main menu is never displayed, and most command line prompts are considerably abbreviated. UltraBBS 3.01 Documentation Page 45 (Y)OUR PERSONAL MAIL SCAN Subcommands: None. Description: Allows checking for unread mail to you in the current conference, or scanning all conferences for new messages, using or not using your conference scan string. To change your conference scan string, use the (C) command. (Z)IPPY SEARCH FOR FILE BY TEXT Subcommands: (N) Searches through only the new files (must be stacked on command line, ie: (Z N) from main menu). (E)xtended or (S)tandard directory display type. (text) Text to search for. (dir number) The directory number(s) (separated by spaces) which you wish to search in--(Enter) means all directories and a (D) specified the default directory (usually the upload directory). Description: Allows you to search the file directories for specified text. A case-insensitive search is done, and all files, with matching text in their description or name, are displayed. One major advance in UltraBBS 3.0x is that Z is now very FAST and allows complex searches with AND (&), OR (|) and wildcards. For example, searching for (DEEP & SPACE) | STAR* would get anything containing the words DEEP AND SPACE - or with any word starting with STAR like STARTREK. ALL words in all descriptions are keywords available for the search, and many common constructs are recognized. For example, 1024x768x256 (a common GIF resolution) is recognized as a whole, but also as the fragments '1024' '1024x768' etc. (1)DISPLAY CALLERS LOGS Subcommands: (#) Node # to view callers log of. Description: Allows sysop level users to view the callers log of a node. Entries are highlighted according to their importance and function. (2)DOS FUNCTION Subcommands: (command line) Command line to shell to. Description: Allows sysop level users to execute the specified command line, via a shell to the operating system. After the command line is executed, UltraBBS execution resumes. (3)RECOVER MESSAGE Subcommands: (#) Message # to recover. Description: Allows sysop level users to recover a killed message, thus allowing users to see it again, and preventing it from being removed during the next message base pack. (4)VIEW TEXT FILE Subcommands: (file name) File name of text file to view. Description: Allows sysop level users to view any text file in the system. (5)PAGE BELL TOGGLE Subcommands: None. Description: Allows sysop level users to toggle the sysop's page bell on/off. (6)QUICK FILE EDITOR Subcommands: None. Description: Allows sysop level users to quickly edit a file's vital information from within the BBS. UltraBBS 3.01 Documentation Page 46 (7)REMOTE DOS SHELL Subcommands: None. Description: Allows sysop level users to shell to DOS, via a pre-made remote batch file. (8)LOG OFF/LOCK OUT OTHER NODE Subcommands: (#) Node # to log off/lock out. Description: Allows sysop level users to log off or lock out a user who is on an alternate node in a multi-node system. After entering the node number, you will then be prompted whether you wish to log off, or lock out the user. (9)QUICK USER EDITOR Subcommands: None. Description: Allows sysop level users to quickly edit a user's vital statistics from within the BBS. (10)SEARCH CALLERS LOGS Subcommands: (#) Node # to search callers log of. Description: Allows sysop level users to search the callers log of a node. Entries are highlighted according to their importance and function. When a call is located that matches the search string, that whole call will be displayed. (AND/OR searches are allowed.) (11)DROP OTHER NODES Subcommands: (#) Node # to drop to DOS. Description: Allows sysop level users to drop other nodes to DOS. If there is no caller on the node, it will be immediately exited. If there is a caller, it will exit after the caller logs off. If you then wish to logoff the caller immediately, you may use the (8) command. (12) Broadcast. Alternate form of this command. Master users are allowed to log off online callers after entering a message, and bring the BBS down. (13) Clear Other Node records. Zeroes out information in a node record, particularly if that node is currently hung (and would prevent that caller from calling in under another line. (14) Clear Door INUSE flags, and optionally toggles the door DOWN bit. Allows a master user to reset the Door Inuse flag (for a single user door, UltraBBS can prevent more than one caller from being in the door at the same time, greatly simplifying the door batch files! This command also allows a master user to toggle the up/down state of a door. A door can be taken temporarily offline (with an appropriate message being displayed to a user trying to enter the door) or brought back online. (15) Message base manipulation. A master user can use this command to examine or alter the message pointers associated with a conference. In particular, it could be used to rescan messages for export (by lowering the last-fido-message-exported number) in case an outgoing mail packet got lost. (16) Toggle BBS UP/DOWN state. If you are taking the BBS down, you are prompted for a 5 line message to be displayed to current callers (they then will be forced off the BBS) and to any new logins (which will also be forced off the BBS after viewing this message). Using the command again later will bring the BBS back up and permit normal logins. UltraBBS 3.01 Documentation Page 47 CONVERT PROGRAM ------------------------------------------------------------------------- UltraBBS Door Conversion Program (CONVERT.EXE) Copyright (c) 1991-1993 Craig Baker, All Rights Reserved This utility allows UltraBBS to run GAP, PCBoard 14, RBBS-PC, Wildcat!, UTI, and WWIV doors. The utility is run by typing the utility name followed by one of the following command lines: GAP, PCB14, RBBS, WILDCAT, UTI, or WWIV. It must be run in the UltraBBS main directory, since it reads from the UBBS.SYS user info file that UltraBBS creates whenever a user exits to a door or remote DOS. UltraBBS automatically runs this utility if one of the above door types is specified in the Doors Data File; however, you may want to use this utility in your remote DOS batch file. UltraBBS does not have its own exclusive door type, so sysops should use one of these door types to run their door programs. UTI FILES ------------------------------------------------------------------------- UltraBBS UTI Programs (UTI*.EXE) Copyright (c) 1991-1993 Craig Baker, All Rights Reserved UTI stands for Universal Text Interface. These UTI Revision Level 2 programs are used in conjunction with PCRelay, MegaMail, TNet, or any other UTI software. PCRelay is an echomail system by Kip Compton; MegaMail is an offline message reading system, also by Kip Compton; TNet is a QWK/REP networking program by Greg Hewgill. A two-line file named UTI.CFG must exist in the directory that your UTI*.EXE programs are run from. This file is as follows: Line 1 contains the complete path/filename of your Conference Data File, and Line 2 contains the complete path/filename (without extension) of your Users File. For further information on the use of the UTI programs, consult your PCRelay, MegaMail, or TNet manuals. PCBVERIFY SUPPORT ------------------------------------------------------------------------- UltraBBS PCBVUPDT Program (PCBVUPDT.EXE) Copyright (c) 1991-1993 Craig Baker, All Rights Reserved. PCBVUPDT.EXE, which comes with UltraBBS, allows UltraBBS systems to run callback verification programs such as PCBVerify. The program requires six command line parameters: Security to give user, path of user file (without extension!), new kilobyte ratio, new file ratio, minutes to add to user's time, and new daily download limit to give the user (in K). The program must be run from the UltraBBS directory. Here is an example of a batch file that would run PCBVerify and correctly update the user: cd\pcbv if exist results del results pcbv30 pcbv.cnf cd\ubbs if exist \pcbv\results pcbvupdt 20 d:\ubbs\files\users 10 10 9 10 UltraBBS 3.01 Documentation Page 48 The batch file would go into the PCBVerify directory, delete the RESULTS file (you must configure PCBVerify to write a RESULTS file), run PCBVerify, and then update the user if the validation is successful. In this case, the validation gives the user security level 20, a kilobyte ratio of 10, a files ratio of 10, adds 9 minutes to the user's time, and gives him a download limit of 10K per day. OFFLINE READING SUPPORT (.QWK/.REP) ------------------------------------------------------------------------- UltraBBS allows users to download messages for offline reading and send their replies to any of the messages back to the BBS to be placed in the message bases. The .QWK file that is sent is compatible with the standard .QWK packet format and the reply file (.REP) can be created by any .QWK compatible offline reader. Some of the most popular offline readers are SLMR, Qmail DeLuxe, EZ-Reader, Session Manager, PowerQWK, and KingQWK. Most of these readers are shareware and are available at a offline-reading-capable BBS near you. MESSAGE COMMANDS ------------------------------------------------------------------------- FULL SCREEN EDITOR COMMANDS Function Key/Sequence DoorWay Code/Key --------------------- ---------------------------- ------------------ Up ^E or (Esc)[A (NUL)H (Up) Down ^X or (Esc)[B (NUL)P (Down) Left ^S or (Esc)[D (NUL)K (Left) Right ^D or (Esc)[C (NUL)M (Right) Word Left ^A (NUL)s (Ctrl-Left) Word Right ^F (NUL)t (Ctrl- Right) Page Up ^R or (Esc)[r (NUL)I (PgUp) Page Down ^C or (Esc)[q (NUL)Q (PgDn) Start of Line ^W or (Esc)[H (NUL)G (Home) End of Line ^P or (Esc)[K (NUL)O (End) Delete Line ^Y Delete Word ^T Delete Left of Cursor ^H (Backspace) (Backspace) Delete Under Cursor ^G or ASCII #127 (NUL)S (Del) Split Line ^N Join Lines ^J Insert Toggle ^V or (Esc)[n or (Esc)[24~ (NUL)R (Ins) Quote Original ^Q or ^O Help ^Z Redraw Screen ^L Done With Message ^[ (Esc) or ^U or (Esc)[23~ (Esc) UltraBBS 3.01 Documentation Page 49 MESSAGE SECURITY (R)eceiver makes the messages readable by only the sender, and the receiver. (U)nprotected, or (Enter), makes the message public and readable by all users. (P)assword allows you to put a password on the message, and requires users to enter the password before reading the message. (K)ill protection is used for public messages to a specific person when you don't want to receiver to be able to kill the message. (E)ncrypt uses an unbreakable algorithm to encode the message. It can only be decrypted with the same encryption key. A sysop may delete an encrypted message, but NOT read it. END OF MESSAGE (Y) or (Enter) Continues reading messages as you have specified. (N) Stop reading messages. (C) Continuous (nonstop) reading of messages. (#) Message number to skip to, with an optional (+) or (-). (+) Reads messages forward from current message. (-) Reads messages backward from current message. (R) Leave a reply to the message. (K) Kill the message, if you have enough security to do so. (E) Edit all information pertaining to a message, including the text - this is available to sysop level users only. (M) Copies the message into another conference - this is available to sysop level users only. (S) Skips the current conference (valid in an (R A) message read). (G) Goto the user in the FROM field's record - this is available to sysop level users only. (T+/-) Threads reverse or forward from the current message for messages with the same subject. (RR) Read the refer-to message. MESSAGE EDITING (A) Abort message entry and return to the main menu. (C) Continue entering the text of the message. (D) Delete line(s) in the message. (E) Edit a line of the message. (F) Allows sysop level users to import a file into the message. (I) Inserts line(s) in the message. (L) Lists the full text of the message. (M) Save and send multiple copies to other users. (S) Save the message (use when finished with message entry). (Q) On a reply, use this to quote lines from the original message into the current messages, preceded by a '>'. (T) Attach file to the message, for the receiver(s) to download. UltraBBS 3.01 Documentation Page 50 REMOTE DOS SETUP ------------------------------------------------------------------------- You can use DOS remotely in several ways. One way is with DOS's CTTY command to redirect CON to COMx. A slightly better way is to use the GateWay .SYS driver and use CTTY to redirect CON to GATEx. The best way is to use Marshall Dudley's DoorWay. Following are batch files for both CTTY and DoorWay usage. More information on DoorWay will follow. REMOTE.BAT -------------------------------------------------- ECHO OFF CTTY COM1: CLS ECHO ************************************* ECHO ** Type EXIT to return to UltraBBS ** ECHO ************************************* COMMAND C: CD\UBBS CTTY CON: -------------------------------------------------- (NOTE: This would be for COM1. When using CTTY, you should turn on UltraBBS's watch carrier function in SETUP. If you use GateWay, change to COM1: to GATE1:) REMOTE.BAT ---------------------------------------------------------------- DOORWAY COM1 /g:on /a:on /b:m /c:dos /V:D^O /s:* /l: /o:T /M:200 C: CD\UBBS ---------------------------------------------------------------- DoorWay is highly recommended for your remote DOS function, as it can redirect programs that use DOS, BIOS, or direct screen writes (required to run UltraBBS's U3MANAGE or SETUP programs!), while CTTY is much more limited. DoorWay also allows function keys to be entered from remote, with the "DoorWay" mode of many popular communications programs. Additionally, DoorWay can monitor time and carrier while the user is in DOS. DoorWay can be found on many BBSes or can be obtained from the author's BBS (Data World BBS, (615)966-3574, Hayes 9600-V). UltraBBS 3.01 Documentation Page 51 ANSI MUSIC ------------------------------------------------------------------------- Music can be put into your BBS text files such as the welcome, logoff, bulletins, menus, etc. ANSI Music is supported in several communication programs. Some communication programs that support ANSI Music are as follows: Telemate PC-Talk 4.65+ Qmodem GT Power Here is a one-line musical score that if you place in any of your BBS text file will play "Happy Birthday". (You must replace the "ESC" with an actual escape code, ASCII 27.) ESC[MFT120L4MFMNO4C8C8DCFE2C8C8DCGF2C8C8O5CO4AFED2T90B-8B-8AFGF2 These notes are all compatible with BASIC's PLAY command. A sample BASIC program which would do the same thing would look like. 10 PLAY "t120 l4 mfmn" 20 PLAY "o4 c8 c8 d c f e2" 30 PLAY " c8 c8 d c g f2" 40 PLAY " c8 c8 o5 c o4 a f e d2" 50 PLAY "t90 b-8 b-8 a f g f2" The strings of ANSI music are mostly compatible with BASIC's PLAY command. Music written for BASIC can be converted to ANSI music by simply inserting escape codes and "[MF" before the music strings. Each ANSI Music line should begin with an ESC[MF or ESC[MB and terminate with a Ctrl-N (ASCII 14). All ANSI Music should be in caps. Spaces between the notes or music directives are optional. VALID ANSI MUSIC COMMANDS A-G Musical notes # or + Following A-G note means sharp - Following A-G note means flat < Move down one octave > Move up one octave . Period acts as dotted note (extend note duration by 3/2) MN Music note duration Normal (7/8 of interval between notes) MS Music note duration Staccato (decrease duration of following notes) ML Music note duration Legato (increase duration of following notes) Ln Length of note (n=1-64, 1=whole note, 4=quarter note, etc) Pn Pause length (same n values as Ln above) Tn Tempo, n=notes/minute (n=32-255, default n=120) On Octave number (n=0-6, default n=4) UltraBBS 3.01 Documentation Page 52 There are several ways of making ANSI Music in your text files without having to try and figure all of them out for yourself. You can get the utility called MOONSONG (available on many BBSes) which will create ANSI Music text files. ANSI Music is only played to the sysop's console during local logons, and when beeps are turned on. MODEM CONFIGURATION ------------------------------------------------------------------------- UltraBBS will work with virtually any type of modem that supports the standard "ATA" command set, can send back verbose (CONNECT 2400, etc) response codes, and that correctly supports the DCD and DTR signals. Different modem initialization strings and modem DIP switch settings will be made available as they are given to us. One common init string for a standard, 1200/2400, Hayes compatible modem is: ATE0M0&D2&C1H0S0=0V1Q0 The E0 turns the command echo off. This function is not vital, but makes it easier on the BBS. The M0 command turns the modem's speaker off. Again, this is not vital, but usually sysops prefer to have it off. The &D2 and &C1 commands turn on proper DTR signal response, and proper DCD signal handling, respectively. These two commands are vital to the BBS's operation, and may be different for your specific modem; check your modem's manual. The H0 commands puts the modem on the hook. The S0=0 command turns auto answer OFF. The V1 and Q0 commands turn on verbose responses (necessary!) and tell the modem to NOT be quiet (which means to go ahead and send response codes). USROBOTICS COURIER 14.4K HST OR DUAL STANDARD SETTINGS Use any communications program and set your NRAM to the following setting. You can use ATI5 to check your NRAM setting. To change NRAM, type 'AT' followed by the settings to change, followed by a '&W'. See your USR owners manual for further information. B1 F1 M0 X6 &A0 &B1 &G0 &H1 &I0 &K3 &L0 &M4 &N0 &P0 &R2 &S0 &T5 &X0 &Y1 %R0 S02=043 S03=013 S04=010 S05=008 S06=002 S07=200 S08=002 S09=006 S10=005 S11=060 S12=050 S13=000 S15=000 S19=000 S21=010 S22=017 S23=019 S24=150 S26=001 S27=000 S28=008 S29=020 S32=003 S33=000 S34=000 S35=000 S36=000 S37=000 S38=000 1234567890 Dip switches in the back of modem: UUDDDUUDDU UltraBBS 3.01 Documentation Page 53 In UltraBBS, you should turn on bps rate locking and lock at either 19200 or 38400. If you have not installed a 16550A UART, then you should use 19200. You must also enable RTS/CTS. HAYES V-SERIES HIGH SPEED MODEMS Hayes V-Series high speed modems seem to work best with UltraBBS when they are set (using the proper S-register commands) to maintain a constant DCE/DTE rate, and UltraBBS is set to lock at 9600 or 19200 bps. The information on the specific S-registers that should be set is not available at this time. RTS/CTS must be turned on in SETUP. DOORS ------------------------------------------------------------------------- Doors are programs that can be run outside of the UltraBBS software. Doors can be utilities, games, or other programs. UltraBBS will either shell to doors or exit to doors depending on how you have it setup. Doors can be added to UltraBBS with the UltraBBS SETUP utility. For more information on setting up doors, consult the documentation of the door you are attempting to setup. (NOTE: At the end of your door batch files, you should return to the UltraBBS drive and directory, but you should NOT run the UltraBBS batch file! The door batch file is executed under the original UltraBBS batch file, and thus will return control to the batch file after finishing.) UltraBBS 3.01 Documentation Page 54 QUESTIONNAIRES ------------------------------------------------------------------------- Questionnaires are "semi-intelligent" in UltraBBS. They can perform simple security/conference operations. Each questionnaire is a text file, with one command per line of the file. Following is a list of the UltraBBS questionnaire language commands: EXIT Terminates the questionnaire CONFS string Changes the user's conference string to CONF(x) [ON,OFF] Add user (ON) or remove user (OFF) from conference x SECURITY x Sets user's security level to x (will NOT lower user's security) DISPLAY filename Displays filename to the user [RED,GREEN,YELLOW,BLUE,MAGENTA,CYAN,WHITE] Changes the current text color PUTANS string(;) Prints string to the answer file, append the ';' for no (Enter) PUTANS *(;) Prints current user answer to the answer file, append the ';' for no (Enter) LOGOFF Logs off current user, with no warning LOCKOUT Locks out (sets user's security at 0) current user, with no warning PAGESYSOP Pages the SysOp PUTTEXT string(;) Prints string to display, append the ';' for no (Enter) PUTTEXT *(;) Prints user's last answer to display, append ';' for no (Enter) UltraBBS 3.01 Documentation Page 55 GETANSWER x|prompt Prints prompt, and gets answer string of no more than x characters MULTCHOICE validchars|prompt Prints prompt, and gets a character that must be in the validchars string IF string ... commands ... ENDIF If user's last answer is different from string, then skip all commands, until an ENDIF is encountered; an IF with nothing after it checks for a blank response SKIPLINE Displays a blank line PUTANSINFO Prints user's name, the current date, and the current time to the answers file GOTO label label: Goes to a specific line label (the line label should be on its own line with a colon after it) ADDMINUTES x Adds x minutes to the current user's time for today. For an example of the use of many of the questionnaire features, see the NEWUSER.DAT questionnaire that comes with the UltraBBS package. UltraBBS 3.01 Documentation Page 56 EVENTS ------------------------------------------------------------------------- Events are daily batches that are run at any specified time. Typically, events are used for such things as message packing, door game maintenance, or echomail operation. For information on how to use UltraBBS's U3MANAGE program in your events, see the section in this manual about U3MANAGE's command line parameters. When the event is run, UltraBBS exits to the BBS batch file with errorlevel 1, 5, or 6 for events 1, 2, and 3, respectively. Users who logon before an event will have their time shorted for that call to avoid delaying the event. It is recommended that you not schedule events that are very close to midnight (2 or 3 minutes before or after), since time rollover could possibly cause problems. Also, you should not schedule events that may be overlapped by other events or events that are very close to each other. UltraBBS 3.01 Documentation Page 57 TEXT FILES ------------------------------------------------------------------------- There are many files used to customize your BBS. These include the welcome, logoff, bulletins, menus, etc. All text files have ANSI and non-ANSI versions. The ANSI versions have a 'G' appended to the end of the filename (ex: GOODBYE for normal screen and GOODBYEG for the ANSI version). Also, RIP versions may be specified with an 'R' appended to the file. If the ANSI version does not exist, or if the user is not in ANSI graphics mode, the non-ANSI version will be displayed to all users. Also, most text files can be displayed only to individual security levels if you wish. This is done by adding a file extension of the desired security level (ex: MMENU.50/MMENUG.50). If a specific security level file is not found, the regular file will be displayed. Variables can also be put into your text files, and UltraBBS will substitute the appropriate information in place of the $...$ variable when it occurs.. The variables which are currently supported are as follows: $USERNAME$ The name of the user, in all capitals If you place this variable in the 'To' field of a message, the message will be to all users and they will be notified of it in a scan. $x$, $x-y$ (Valid only in the 'To' field of a message) When this variable is used in the 'To' field of a message, the message will be to all users of x security level or in the x - y security range and they will be notified of it in a scan. $CALLERNUM$ The current number of calls to this BBS to date $USERNAMEM$ The name of the user, in mixed case $PASSWORD$ The user's password (use with caution) $CITYSTATE$ The user's city/state $BBSVERSION$ The BBS name and version (ex: UltraBBS v3.10) $SYSOPNAME$ The name of the sysop, in all capitals $SYSOPNAMEM$ The name of the sysop, in mixed case $BBSNAME$ The name of the BBS $VOICENUM$ The user's voice telephone number $DATANUM$ The user's data telephone number $EXPIREDATE$ The user's subscription expiration date $LASTDATE$ The user's last date on $LASTTIME$ The user's last time on $CURRENTDATE$ The current system date $CURRENTTIME$ The current system time $CONFNAME$ The name of the conference the user is in $BAUDRATE$ The current baud rate of the connection $DOWNLOADS$ The user's number of downloads $UPLOADS$ The user's number of uploads $PAGELENGTH$ The user's page length $TIMESON$ The user's total number of logins UltraBBS 3.01 Documentation Page 58 $DOORSENTERED$ The user's total number of doors entered $MSGSENTERED$ The user's total number of messages entered $SEC$ The user's security level $BIRTHDATE$ The user's date of birth $MINSPERDAY$ The user's daily time limit in minutes $MINSLEFT$ The user's minutes left for this call $DOWNLOADK$ The user's download kilobytes $UPLOADK$ The user's upload kilobytes $DLKBSPERULKB$ The DL KB/UL KB ratio the user must maintain $DLFSPERULF$ The UL/DL ratio the user must maintain $SYSOPSTART$ The starting time of the sysop page bell $SYSOPEND$ The ending time of the sysop page bell $FIRSTNAMEM$ The user's first name, in mixed case $NODENUM$ The node number of this node $MINSUSED$ The number of minutes the user has used today $EVENTTIME$ The time of the daily event $DLKPERULK$ The user's number of DL KB per 1 UL KB $DLSPERUL$ The user's number of DLs per 1 UL $CLS$ Clears the screen $MORE$ Brings up a yes/no/etc prompt $MOREON$ Turns yes/no/etc prompts on $MOREOFF$ Disables yes/no/etc prompts $BREAKON$ Allows aborting with (Ctrl-X) or (N)o at prompt $BREAKOFF$ Makes file unabortable $ANYKEY$ Brings up a press any key to continue prompt Special variables that may only appear by themselves at the beginning of a line: $QUOTE$ Reads the file QUOTES.DAT and gives the caller a 'quote of the day'. This file is a simple ASCII text file, with blank lines as the separators between quotes. UltraBBS generates and maintains a file QUOTES.NUM containing the offset of the LAST generated quote. It will wrap around at the end of the file. Make sure the QUOTES.DAT is in the QUOTES/HISTORY directory (settable in U3SETUP). $HISTORYxnn$ This variable causes items to be listed from the popular (and excellent) 'Today in History' files. These files have items categorized in various groups. The 'x' after HISTORY selects the category: 'B' is birthdays, 'D' deaths, 'S' events, 'H' holidays etc. nn is a one or two digit number for the NUMBER of Items displayed. Eg: $HISTORYB5$ would cause 5 birthdays to be listed. Make sure the files TODAY.JAN, TODAY.FEB..TODAY.DEC are in the QUOTES/HISTORY directory. UltraBBS 3.01 Documentation Page 59 CALL WAITING SCREEN ------------------------------------------------------------------------- The call waiting screen is displayed whenever UltraBBS is ready to receive calls. This screen contains a great deal of information. The screen displays the name of the BBS, the UltraBBS version and copyright, and the name of the sysop who the UltraBBS is registered to. It also tells whether beeps and page bell are on/off. It displays the last event and time as well as the next event and time. The current baud rate tells you what baud rate your modem is initialized at. Idle time tells you how many minutes have elapsed since the last caller. Status is shown as "Waiting" if it is waiting for calls. The modem session is also displayed to help you in tracking down any problems. The following commands are available from the call waiting screen: (Esc) Exit to DOS (L) Local Logon (S) Snoop Logon (Alt-B) Beeps Toggle (Alt-J) Shell to DOS (Alt-P) Page Bell Toggle During a snoop logon, the phone is left on the hook. When the phone rings, you will be notified on that status line. You can then log off if you wish and have the BBS answer the call. UltraBBS 3.01 Documentation Page 60 LOCAL FUNCTION KEYS ------------------------------------------------------------------------- When a caller is logged onto UltraBBS, the sysop has the following keys available to him: (Alt-B) Beeps Toggle (Alt-H) Hang Up User (no log off message, etc) (Alt-J) Jump to DOS (Shell) w/swap if specified in SETUP (Alt-K) Disable Remote Keyboard Toggle (Alt-L) Lock Out and Log Off User (Alt-N) Fake Line Noise Log Off (displays some junk chars) (Alt-P) Page Bell Toggle (Alt-U) Update User's Conferences and Security Level (Alt--) Decrease Time by One Minute (Alt-+) Increase Time by One Minute (Alt-C) SysOp Chat Mode (Alt-X) Exit the BBS After This Caller Logs Off The (F1) through (F7) keys can be used to toggle between different status lines. One of the 7 status lines is a help screen listing all available keys. UltraBBS 3.01 Documentation Page 61 FRONT-END OPERATION ------------------------------------------------------------------------- With many net/echo mailers, such as BinkleyTerm, the mailer will answer the phone and then run the BBS with the caller already connected. With UltraBBS, if the caller is already connected, you should run UltraBBS with the baud rate as the parameter (ie: "UBBS 2400"). If the caller is on local, run UltraBBS with the parameter 'L' (local mode) or 'S' (snoop mode) (ie: "UBBS L"). Batch files for use with these mailers and other BBS software can easily be adapted to UltraBBS operation. When you use a front-end, you should not use UltraBBS's events, as they are triggered at the call waiting screen, which will never come up while using a front-end. Instead, use the front-end's events. If you wish to use UltraBBS's events to limits callers' time on the BBS before the front-end's events, be sure to run UBBS.EXE at the end of your front-end event batch so that UBBS will load at the call waiting screen and immediately exit, thus clearing the event flag. UltraBBS 3.01 Documentation Page 62 U3MANAGE COMMAND LINE PARAMETERS ------------------------------------------------------------------------- There are 6 commands in UltraBBS's U3MANAGE which can be executed from the DOS command line. These are very useful in your event or from other batch files. The following is a list of these commands and their parameters and their [defaults]: /PACKUSERS: packs user file /KILLDELETED: kill deleted users? [Y] /SORT: sort the user file? [Y] /KILLDATE: kill users who haven't called since this date [don't] /KILLBELOW: kill all users below this security level [don't] /PACKFILES: packs filebase file /KILLDELETED: kill deleted files? [Y] /ACTUALKILL: actually remove killed files from hard drive? [Y] /SORT: sort the filebase file? [Y] (actually its ALWAYS sorted) /KILLDATE: kill files uploaded on or before this date [don't] /KILLDATE2: kill files not downloaded since this date [don't] /PACKMSGS: packs a message file /KILLRCVD: kill all received receiver-only messages? [N] /CONFNUM: conference number to pack or (A)ll [0] /KEEPLAST: number of messages below top to keep [keep all] /RENUMBER: message number to begin renumbering at [no renumber] /KILLDAYS: kill messages left before this many days ago [don't] /CREATELIST: creates a master file list /CONFNUM: conference number to generate list from [0] /SECFORLIST: security level's point of view to generate [255] /LISTNAME: name for output file [FILELIST.TXT] /ADDGIFRES: add resolution to all GIF file descriptions /IMPORTTICS: Look for .TIC files and import them into the Filebase. Some examples of command line uses: U3MANAGE /PACKUSERS /KILLDATE:08/10/90 /SORT:N U3MANAGE /ADDGIFRES U3MANAGE /CREATELIST /CONFNUM:1 /SECFORLIST:100 /LISTNAME:LIST.DOC U3MANAGE /PACKFILES /KILLDELETED:N U3MANAGE /PACKMSGS /KILLRCVD:Y /KEEPLAST:300 /RENUMBER:1 U3MANAGE /IMPORTTICS UltraBBS 3.01 Documentation Page 63 FILE FORMATS ------------------------------------------------------------------------- Refer to the file UBBSFMTS.TXT for full information! UltraBBS 3.01 Documentation Page 64 QUESTIONS AND ANSWERS ------------------------------------------------------------------------- Q. I would like new users to be able to leave private messages to me, but I don't want them to be able to leave messages to anyone else before I verify the user. How can I do this? A. There are essentially two security levels for the 'E'nter Message command. The first is the actual security level for entering messages. This is the security level that allows users to send messages publicly or privately to other users. There is also the To-Sysop Message Security level. Set this security level to the security level required to leave messages to the sysop. In other words, you would set the 'E'nter Message command higher than the security level of new users, and you would make the To-Sysop Message Security available for new users. The new user's messages will automatically be directed towards the sysop. Q. I get a 'Cannot Open ...' error from UltraBBS. What is causing this? A. In most cases, a 'Cannot Open ...' (for example, 'Cannot Open Messages File', 'Cannot Open Users File', etc) error from UltraBBS indicates that you have specified a bad path for that file's file name. Either the drive does not exist, or the directory does not exist. Check over all of your paths in SETUP. Also make sure that you have allocated enough FILES in your CONFIG.SYS. Q. I am having trouble with modem communications in my multinode, multitasking environment. What should I do? A. Make sure that your FOSSIL is configured properly to support multiple comm ports. Also, under some configurations (such as shared IRQs) you will need to load the FOSSIL before you load the multitasker. It is highly recommended that you read your FOSSIL docs carefully. For multitasking operation, we recommend the X00 FOSSIL driver. Q. When I log on with a certain name, the BBS says that I am somebody else. What is wrong? A. The index files for your user file are probably incorrect or corrupted. Pack your user file to fix the problem. Q. UltraBBS reports that SHARE is not loaded, even though I have loaded it in UltraBBS's window in my multitasking environment. What's the deal? A. SHARE must be loaded before the multitasker, not in a window. UltraBBS 3.01 Documentation Page 65 UBBSWHO PROGRAM ------------------------------------------------------------------------- UltraBBS UBBSWHO Program (UBBSWHO.EXE) Copyright (c) 1991-1993 Craig Baker, All Rights Reserved. The UBBSWHO.EXE program is used to get a (WH)o's on Other Nodes display from the DOS prompt in a networking or multitasking environment. It also displays whether or not each user is paging the sysop. The command line (displayed when the program is run) is: UBBSWHO NODEINFO.DAT_Path Highest_Node_Number example: UBBSWHO D:\UBBS\FILES\NODEINFO.DAT 10 You may want to create a batch file in your PATH to run this utility without retyping the command line parameters each time. UltraBBS 3.01 Documentation Page 66 FIDOCVT PROGRAM ------------------------------------------------------------------------- UltraBBS FIDOCVT Program (FIDOCVT.EXE) Copyright (c) 1991-1993 Craig Baker, All Rights Reserved. The FIDOCVT.EXE program is used to import and export FIDO (usually used for FIDONet) style messages to/from UltraBBS. It handles echomail AND Netmail messages, both FidoNet and UUCP style. The command line syntax for FIDOCVT is FIDOCVT [/i|/e] UBBS.DAT UltraBBS_Conf# FIDO_Directory [/s] [/n] The /i or /e parameter (use one of them, but not both!) specifies an (i)mport or an (e)xport. The UltraBBS_Conf# parameter is the conference number of the UltraBBS message base that this import/export will affect. The FIDO_Directory is the directory of the FIDO messages that you wish to import (it may or may not end with a \). If the export is to netmail, then this must be the netmail directory as known to QMAIL or other message packer/tosser. The optional /s parameter at the end, if specified, will keep the "SEEN-BY" lines on the echo messages (during an import). Otherwise, they are removed. The optional /n parameter at the end, if specified, will suppress filtering of the hi bit ASCII characters in messages (during an export). Otherwise, they are converted to spaces. If you wish to have an origin line on messages entered from your BBS, create a file named ORIGIN in the directory from which you run FIDOCVT. This should be a one-line, maximum 68 character file which contains your origin line. If you do not create this file, FIDOCVT will not add an origin line to the end of your messages. If you log in to your BBS with a name such as "SYSOP", you may wish to have that name changed to your real name before it is exported out to the FIDONet, and have it changed back to (as an example) "SYSOP" before it is imported. To do this, you should create a file called SYSOP in the directory from which FIDOCVT runs. The first line of this file should be the name which you wish to change, and the second line should be the name which you wish to change it to during an export. The reverse will be done during an import. Any message base which is used with FIDOCVT must be set as "Echo" in the UltraBBS SETUP program. Only messages which users designate as "Echo" will be exported from the message bases. When an (O)ffline Reading packet is imported, all messages posted in "Echo" conferences get their echo flag turned on. UltraBBS 3.01 Documentation Page 67 To use FIDOCVT, it is recommended that you prepare two batch files, one that will export for all of your message bases, and one that will import for all of your message bases. After your mail tosser, you should run an import on all message bases. The import function will import all messages in the FIDO directory, starting at message # 2. It then deletes all messages in the directory (including message # 1). Before your mail scanner, you should run an export on all message bases. The export function will add the new messages in the UltraBBS message base to the end of the messages in the FIDO directory (starting after the last message number currently in that directory). After your mail scanner is done with the FIDO messages, you may wish to do a DEL *.MSG command in each of your FIDO message directories--it is not required, but will save a bit of your disk space. For those interested, the exact specifics of the way FIDOCVT operates follow. Unless you are trying to track down a specific problem, are familiar with the operation of FIDONet, or are just curious, you need not read the rest of this section. FIDOCVT /i The import function first locks the UltraBBS message base, preventing any messages from being saved until the import is done. The import function begins at FIDO message number 2 and imports until it comes to a message number which does not exist in the FIDO directory. If any message which FIDOCVT encounters has the intransit bit turned on, FIDOCVT will skip it. After importing each message, FIDOCVT deletes the message. After the import is finished, FIDOCVT sets the lastfidomsgimported variable in the UltraBBS message base's header to the high message number. FIDOCVT then unlocks the UltraBBS message base. Finally, FIDOCVT deletes the FIDO directory's 1.MSG file. FIDOCVT /e The export function first finds the highest numbered message (# 2 or above) in the FIDO directory, and begins creating messages after that message number. In the UltraBBS message base, FIDOCVT begins exporting at the message numbered lastfidomsgimported + 1. FIDOCVT sets the local and intransit bits on. FIDOCVT will only export messages that have their echo flag turned on, and are not killed. Finally, when there are no messages left to export from the UltraBBS message base, FIDOCVT then sets the lastfidomsgimported variable to the last UltraBBS message number it exported. Examples: FIDOCVT /e UBBS.DAT 1 C:\UBBS\MSGS\001 /s < exports from conference 1 FIDOCVT /i UBBS.DAT 5 C:\UBBS\MSGS\005 /s /n < imports into conference 5 UltraBBS 3.01 Documentation Page 68 HOW ULTRABBS HANDLES NETWORKS AND NETMAIL: ------------------------------------------------------------------------- UltraBBS now has built in support for both FidoNet and UUCP style networks. More may be added as the needs arise. Currently, there are TWO defined network TYPES. Type 1 refers to a Fidonet style network. Type 2 refers to a UUCP-Internet style Network. These are specified on a conference by conference address. In the U3SETUP program, you select YOUR address within these networks. For example, Pinecliffe BBS is 1:104/28 in Fidonet and pinecliffe.com in the internet domain. These are the addresses that are set in the UBBS.DAT files. Different nodes within the BBS may have their own addresses, for example if you have several banks of phone lines with different Fidonet addresses (due to different modems). Both FROM: and TO: fields in netmail can be up to 72 characters. FIDONET: In Fidonet Netmail, the TO: field is checked for an address (something after an '@' sign). If it doesn't see an address it prompts for one. For example you might address mail as follows: TO: Craig Baker @ 1:104/28 <- node address supplied. TO: Craig Baker <- no node address, UltraBBS now asks: FIDONET ADDRESS: 1:104/28 <- valid address supplied. UltraBBS checks its internal nodelist for a valid address. This nodelist is generated by the ADDNODES utility that reads a NODELIST.xxx file and stores the nodes within ULTRABBS.NDX. If you get an invalid address, it means that UltraBBS did not find the target node. Mail would have the SENDERS address in the FROM field as follows: FROM: Keith Baker @ 2:100/10 <- for example. UUCP MAIL: Here, the only rule UltraBBS can check is that the address be welformed - no spaces, with an '@' somewhere in the middle. For example: TO: cdb ADDRESS: pinecliffe.com is the same as: TO: cdb@pinecliffe.com Either form would be accepted and lead to a well-formed address. UltraBBS 3.01 Documentation Page 69 An overview of the Netmail process is as follows: On Pinecliffe, conference 199 is the Fidonet Gateway. Messages for export from the BBS as Fidonet netmail are entered here as usual. When Pinecliffe EXPORTS mail, new messages are written into directory \UBBS\MSGS\MAIL (This is in QM.CFG as the Netmail directory) And they are present as 1.msg, 2.msg, etc. (Unlike a standard conference where the 1.msg is reserved for the High Water Mark message) These are PROPER NETMAIL MESSAGES -- and may be edited with any netmail editor. Then QM.EXE when it is executed sees these messages, packs them into a packet and prepares it to leave the BBS via the Front Door like Binkleyterm. When QM.EXE sees INCOMING netmail packets, it LEAVES these messages in the MAIL directory. FIDOCVT.EXE is then run again and it imports the new netmail messages directly into the message base. Therefore: NETMAIL PROCESSING UltraBBS Message Messages Leaving BBS -> Base: 199MSGS.DAT FIDOCVT /e -- FIDOCVT EXPORT --> UBBS\MSGS\MAIL\*.msg ^ (FIDOCVT /e UBBS.DAT 199 UBBS\MSGS\MAIL) (QMail Netmail Dir) | / \- FIDOCVT /i <---- FIDOCVT IMPORT ----<---/ / | (FIDOCVT /i UBBS.DAT 199 UBBS\MSGS\MAIL) / | / | / | ----->--->-->-->------> | / Messages coming INTO BBS > v ^ | QM | | TOSS ^ v QM SCAN PACK | v Mail .PKTS in INBOUND DIR Mail .PKTs in OUTBOUND DIR Note for FIDO addressing, UltraBBS must have an internal nodelist. This is generated from the most recent NODELIST.xxx file by ADDNODES.EXE. UltraBBS 3.01 Documentation Page 70 CHANGES FROM VERSION 2.09: ------------------------------------------------------------------------- Almost too numerous to mention. But: Complete rework of Z, L, N file search commands. Now use a Btree based search making them MUCH faster!! Rework of U3MANAGE. Much faster pack function, also added .TIC and FILES.BBS file importing. Also CD Rom support will be available shortly -- you will be able to import an ENTIRE CD-rom into the FileBase! Eliminated 200 conference limit. Essentially unlimited now, with the U3SETUP program being used to alter than number. Expanded file descriptions to 10 lines per file. Also added DIZ,SDI support. Many new commands and options. Geared to REMOTE operation by a sysop! Sysop can broadcast messages to all nodes, bring nodes down, and display a BBS Down message to all callers. Many bug fixes from 2.09. Built in Netmail and network support. Recognizes Fidonet and UUCP style addressed. To and From fields now allow 72 characters. Handle support included. Handles provided as an alternate login. UltraBBS now can shell to doors shrinking to only 3k in size! No more out-of-memory errors from Doors. QUOTES and HISTORY support now built in. Encryption of messages (with a cryptologically secure algorithm) is now built into the bbs. It is implemented with the UBBSENC.DAT file, in the same directory as ULTRABBS.NDX. If this file is missing, users will receive a message "Encryption not supported on this BBS" when they try to use this feature. UltraBBS 3.01 Documentation Page 71 CONVERSION FROM ULTRABBS 2.09 to ULTRABBS 3.0x ------------------------------------------------------------------------- Also provided is a new program CVTUBBS.EXE. This program takes a UBBS.DAT (from 2.09) and does the complete conversion to UltraBBS 3.01. It makes an \OLDU209 directory with all the old files as backups. You thus need at least as much FREE SPACE as Ultra files now occupy!. PLEASE VERIFY YOU HAVE SUFFICIENT DISK SPACE AND BACK UP BEFORE CONVERSION. CVTUBBS converts the UBBS.DAT, USERS.DAT, FILEBASE.DAT, CONFDATA.DAT, all message bases, and then calls MYSORT (or QSORT) and MAKENDX to rebuild the indices from the flat files into ULTRABBS.NDX. MAKENDX is a useful program - for much more than just the conversion process. If you have a utility that adds records to the flat file portions of the UltraBBS file structures, even if you can't handle the ULTRABBS.NDX file directly, MAKENDX can 'update' the Btree file with the new portions of information. UltraBBS 3.01 Documentation Page 72 CONTACTING THE AUTHOR ------------------------------------------------------------------------- UltraBBS has several beta test sites where one can obtain help with installation, and obtain the latest available version. Additionally, support is available through echomail in most major networks. Currently, the best way to contact the author with problems/questions/ suggestions is: Craig Baker - Phone# Voice 303-444-7071 or 303-642-7534. On Pinecliffe BBS: 303-642-7463 On the Internet cdb@pinecliffe.com UltraBBS 3.01 Documentation Page 73 REGISTRATION ------------------------------------------------------------------------- For information on registration, please see the accompanying text file, REGISTER.TXT. Registration is highly urged after a reasonable (60 day) trial period. THANKS ------------------------------------------------------------------------- UltraBBS would not be where it is today without the many hours of testing, support, and patience of many people. Some of these people are test sites, others have taken the time to report bugs and assist in tracking them down. Others have taken the time to suggest new features, or complain about shortcomings. A list of some of these people follows (in no specific order). Thanks to everybody who has aided with the development of this massive project! Kevin Carr Jon Hutto Mark Robbins Bill Smith Greg Bowers Arthur Mol Craig Baker Dan Crescent Thomas Ryan The Dorsai Staffers Edward Fenster Michael Walsh -------------------------------- And to the present UltraBBS Support Team: Craig Baker Brian Godette. And - ESPECIALLY to my patient beta testers: Merlin Depeel Erik Harris Anssi Johannson Perry Mertz UltraBBS 3.01 Documentation Page 74 WANT TO GET INVOLVED? ------------------------------------------------------------------------- The UltraBBS team is actively soliciting help in two areas: 1) Third party utilities! Anyone interested in contributing such utilities should contact the author immediately so that you may be listed here. 2) Converters -- to enable sysops to convert from their existing BBS packages to UltraBBS. Several folks are working on them now, but more help WILL be accepted!