Beijing Paradise BBS Backup

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

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / 2AM3_1A.ZIP / 2AMSYS3.DOC next >

Wrap

Text File | 1988-11-02 | 185.7 KB | 5,615 lines

2AM-BBS, Version 3.0 Sysop's Manual (c) Copyright 1986,1987,1988 by: Chris Gorman Neil Clarke Tom Vogl 2AM Associates May 8, 1988 Table Of Contents Chapter 1 Introduction 1.1 The 2AM-BBS Documentation Set.................................1-1 1.2 System requirements...........................................1-1 1.3 Setup.........................................................1-1 1.4 Sub-Directories...............................................1-2 1.5 Your AUTOEXEC.BAT File........................................1-3 1.6 Technical Support.............................................1-4 1.7 Networks......................................................1-5 Chapter 2 Keyboard Functions 2.1 Logging In From The Console...................................2-1 2.2 Stopping & Restarting The BBS.................................2-1 2.3 Help Key......................................................2-1 2.4 Input/Output In 2AM-BBS.......................................2-1 2.4.1 The Printer..............................................2-1 2.4.2 Output To Disk...........................................2-2 2.5 View/Edit Current User........................................2-2 2.6 Reserving The Terminal........................................2-2 2.7 Bell Toggle...................................................2-2 2.8 Jumping To DOS................................................2-2 Chapter 3 Further Setup and Customization 3.1 Menus.........................................................3-1 3.2 Text Files....................................................3-2 Chapter 4 The User Validator 4.1 Files.........................................................4-1 4.1.1 USERLOG.DAT..............................................4-1 4.1.2 User Application File....................................4-2 4.1.3 System Logs..............................................4-2 4.1.4 Lookup Files.............................................4-3 4.1.5 ACCESS.DAT...............................................4-3 4.2 Privilege Bits For New Users..................................4-3 4.3 Validator Commands............................................4-3 4.4 The Sweeper...................................................4-5 4.5 Privileges For The Validator..................................4-8 Chapter 5 User Logins 5.1 New User Logins...............................................5-1 5.2 The Standard Login ...........................................5-2 5.3 NEWUSER.DAT...................................................5-3 5.4 .DEF Files....................................................5-3 5.5 Special Login Messages........................................5-4 5.6 Rejects.Dat...................................................5-4 Chapter 6 The Editor 6.1 Privileged Options ...........................................6-1 6.2 Privilege Bits Used...........................................6-1 i Chapter 7 Message Bases 7.1 File Formats (BASEINFO).......................................7-1 7.2 Base Maintenance .............................................7-4 7.3 Privilege Bits Used...........................................7-6 7.4 Base Cleanups ...............................................7-6 Chapter 8 Email Utility 8.1 Email Commands................................................8-1 8.2 Special Options During Read Incoming..........................8-1 8.3 Maintenance Commands..........................................8-2 8.4 Files.........................................................8-2 8.5 Privilege Bits and Mail Quotas................................8-3 Chapter 9 Files Section 9.1 File Credits and Times........................................9-1 9.2 File Formats..................................................9-1 9.2.1 Download Files ..........................................9-1 9.2.2 Upload Files.............................................9-3 9.2.3 External Protocols.......................................9-3 9.3 The Maint Utility.............................................9-4 9.3.1 From A File Library......................................9-4 9.3.2 From The Upload Library..................................9-5 9.4 Privilege Bits Used...........................................9-5 Chapter 10 BBS Lister Utility 10.1 File Formats................................................10-1 10.2 Maintenance Commands........................................10-1 10.3 Privilege Bits Used.........................................10-1 Chapter 11 JumpDoors 11.1 File Formats................................................11-1 11.1.1 PASSAGES.DAT...........................................11-1 11.1.2 JUMPER.DAT.............................................11-2 11.2 The Maint Utility...........................................11-2 11.3 Notes On Writting Jumpdoors.................................11-3 11.4 Privilege Bits Used.........................................11-3 Chapter 12 Trivia 12.1 File Formats................................................12-1 12.2 Maintenance Section.........................................12-2 12.3 Privilege Bits Used.........................................12-3 Chapter 13 Voter 13.1 File Format.................................................13-1 13.2 Maintenance Commands........................................13-1 13.3 Privilege Bits Used.........................................13-1 Chapter 14 Chat Utility 14.1 Request Chat................................................14-1 14.2 Accept/Deny Chat............................................14-1 14.3 Leaving Chat................................................14-1 14.4 Chat Files..................................................14-1 ii Chapter 15 Other Main Menu Options... 15.1 Configure...................................................15-1 15.2 Feedback....................................................15-1 15.3 System Info.................................................15-1 15.4 Off.........................................................15-1 15.5 Daily Log...................................................15-1 15.6 Login Notes.................................................15-2 15.7 User Application............................................15-2 15.8 Error! ....................................................15-2 Chapter 16 Main Menu Maintenance Chapter 17 Miscellaneous Options 17.1 Loggin In From The Console..................................17-1 17.2 Timeouts....................................................17-1 17.3 Carrier Drops...............................................17-1 17.4 The Scheduler...............................................17-1 17.5 A Note About Backups........................................17-2 Chapter 18 Utilities 18.1 BASEEDIT.EXE................................................18-1 18.2 BSMAINT.EXE.................................................18-3 18.3 DAYVIEW.EXE.................................................18-4 18.4 DBMAINT.EXE.................................................18-4 18.5 DIRSORT.EXE.................................................18-5 18.6 DRIVER.EXE..................................................18-6 18.7 HLPMAINT.EXE................................................18-6 18.8 LOOKER.EXE..................................................18-7 18.9 MAKEVOTE.EXE................................................18-7 Appendix 1 Privilege Bits 1.1 By Number............................................Appendix 1-1 1.2 By Use...............................................Appendix 1-2 Appendix 2 2AM File Map Appendix 3 Multiuser Setup and Commands Appendix 4 Bit Encoded Responses Appendix 5 The DRIVE.DAT File 5.1 System Specifics.....................................Appendix 5-1 5.2 Drive Paths..........................................Appendix 5-1 5.3 Prompts..............................................Appendix 5-1 5.4 Headers And Messages.................................Appendix 5-2 5.5 Modem And Port Information...........................Appendix 5-2 Appendix 6 ANSI Color Commands Appendix 7 Trouble Shooting Index iii 2AM BBS Sysop's Manual Introduction _________________________________________________________________________ Introduction Chapter 1 1.1 THE 2AM-BBS DOCUMENT SET The documentation for this Bulletin Board System is divided into two manuals. Each is tailored for a certain kind of user. The first manual is the 2AM-BBS User's Manual. It contains all the information that one of your users needs to use every public feature of this board. In purchasing this product, you are given full rights to copy the user's manual, and we encourage you to do so. Also, you will find the user's manual helpful for yourself in learning simple principles behind the board's operation. This manual, the second manual, is the 2AM-BBS Sysop's Manual. It is a reference manual and contains notes on sysop sections as well as file formats for all the utilities and any other information you might need to operate the board. 1.2 SYSTEM REQUIREMENTS 2AM-BBS will run on any IBM-PC or IBM compatible computer with at least 256K of memory running under the MS-DOS or PC-DOS operating system. You need DOS 2.1 or higher, a hard drive and a Hayes compatible modem. 1.3 SETUP Setup is simple. You should have 2 or more disks labeled 2AM-BBS disk #1, 2AM-BBS disk #2, etc. Place the first disk into drive A: of your computer and make sure you are at an "A>" prompt, and type INSTALL at the DOS prompt. This program will copy all the files from the distribution disks onto the drive you want to keep the BBS files on. By default, it would like to put all files on Drive C (probably some kind of hard disk) in a subdirectory c:\bbs. If you do not want to use this configuration, you will have the opportunity to change all of these parameters during installation. After you have completed the install procedure, log onto the drive and subdirectory where the system files are (sys_disk in the installation procedure) using the DOS command: CD \BBS . Make sure your modem is turned on, and type: BBS . You are now up and running. Note, if you are planning on running a multiport system, please refer to the multiuser section of this documentation. To log in locally (not through the modem), hit the ESCAPE key. An account has already been setup for you. Account number 1 is the sysop account. Its password is 2AM-BBS. We strongly suggest that you change the password as soon as you log in since this default account exists on all 2AM-BBS's and people know the number and password for it. At this point, you are running 2AM-BBS with the default files that we gave you. Nothing is customized to your tastes and you will obviously 1-1 2AM BBS Sysop's Manual Introduction _________________________________________________________________________ want to make a lot of changes. In order to do so, you will need two things: An ASCII editor and this manual. Many of the files 2AM uses can be modified with an ASCII editor. An ASCII editor is any editor that does NOT but special characters in the file. DOS's EDLIN program is an ASCII editor. If you are not sure if an editor is ASCII or not, try TYPEing a file that it wrote from DOS. If the file lists exactly how it looked in the editor, the editor is probably an ASCII editor. If you do not have an ASCII editor - do not panic, you can use 2AM's editor to modify most of these files. You will need this manual for reference purposes since many files have a specific format that they must be in. Please keep this manual in a convenient location since you will probably refer to it often during your initial setup. 1.4 SUB-DIRECTORIES 2AM-BBS uses many different files to operate. These files are neatly grouped into subdirectories. Two notes about these subdirectories: 1. There is a file in with the program files called DRIVEx.DAT. The "x" can be a number (1, 2, 3 etc..) or it could be non-existent. If the BBS is to be run as a single user system, DRIVE.DAT is all you will need. If you plan to run more than one line, then please refer to the multiuser section of this manual. For the sake of clarity, we will refer to this file simply as DRIVE.DAT. DRIVE.DAT is a text files and contains, among other things, a list of all the subdirectories that have been created for the board. It must exist on the system disk or the BBS will not be able to start. When the system runs, it reads this file to find out where to go to get things. If you want to move files, you can create different subdirectories and modify DRIVE.DAT to look at these new subdirectories. For example, if you wanted to move the help files from "c:\bbs\help\" to "b:\help\", mkdir b:\help, copy the files to that directory, and edit DRIVE.DAT. Now use the utility DRIVER.EXE (supplied with 2AM-BBS) to edit this file. DRIVER can be used to edit any DRIVE.DAT file and is recommend over the use of a standard text editor. 2. Since people are really fond of moving subdirectories around in this manner, we can't just say things like "change directory to c:\bbs\help". Some people might not have their help files there. As a result, we have come up with logical name for each subdirectory. For example, the logical name for the subdirectory with the help files in it is help disk. You will see these names used constantly in this manual. Now, let us give you a listing of all the subdirectories with there logical names and a brief statement of what sort of files are in each: 1-2 2AM BBS Sysop's Manual Introduction _________________________________________________________________________ Base_disk Message bases reside here. BBS_disk Contains the database files for the BBS lister. Chat_disk Contains all the CHAT text files. Dload_disk Contains library files for the download section Help_disk Contains the system HELP files. Jump_disk Contains files for the JumpDoors Utility Log_disk Contains all the daily logs. Look_disk Contains user lookup tables. DO NOT ALTER THESE FILES! If you have a problem with these files, refer to the LOOKER utility supplied with 2AM-BBS. Mail_disk All EMAIL will reside here. Menu_disk Contains the system MENUS. Sem_disk Directory for internal use by 2AM-BBS. Sys_disk Contains 2AM-BBS itself and some key system files. Text_disk Contains TEXT files such as login notes and bulletins. Trivia_disk Contains all the files for trivia. Uload_disk Contains the uploads and the files that handle them. Vote_disk Contains files for the voting booth. 1.5 YOUR AUTOEXEC.BAT FILE When your computer boots up, it reads the file autoexec.bat. So that the BBS will re-boot if power goes out, put lines to change directory to sys_disk and execute BBS in this file. For example: C: CD \BBS BBS 1.6 TECHNICAL SUPPORT The authors of this software are just as excited about seeing your board in operation as you are. We are happy to help you out if you should get stuck. However, we also would like you to be able to solve problems on 1-3 2AM BBS Sysop's Manual Introduction _________________________________________________________________________ your own (since there are many little things to keep track of). We really do not anticipate too much worry; everything has been tested thoroughly before it was shipped to you by our beta test sites. However, if anything goes wrong, or you need help, here are steps you can take: 1. Check the manual first PLEASE!. Some setups are tricky, and you might have to do a little file debugging to get everything working. Most problems can be fixed if you are careful to compare the files you have setup against the samples in this manual. 2. All registered owners of this program have access to special bases at the DREW Underground, 201-377-8245, 201-377-8193, 201-377-7861, 201- 377-6810 or 201-377-4538 (yes - it is a 5 line 2AM-BBS). Any questions left in these bases will be answered promptly. If you are an experienced sysop, we encourage you to help out others through these bases. Also, discussions on improvements for the board are very much encouraged. This is your best approach to getting answers. We would appreciate it if you would try to reach us via The Underground before calling us voice. 3. If you have access to BITNET, you can contact us via the following accounts: Neil : NCLARKE@DREW Chris : CGORMAN@CITCHEM 4. Above we mentioned that all registered users of this program have special access at the Drew Underground. Since this is a demonstration copy of 2AM-BBS, you do not have to register your copy with us. If you find you have problems, you can still call the Underground (numbers above) and leave feedback. The authors will get in touch with you as soon as possible. Should you decide to purchase a full copy of 2AM-BBS, you will receive the home phone numbers of all the 2AM Associates. If you encounter a problem or have any questions with a full 2AM-BBS system, you can call us direct and get immediate assistance from us. 1.7 NETWORKS Currently, there is a version of 2AM-BBS available for the BI-TECH network. If you are interested in obtaining a version of 2AM-BBS for any other network system, contact 2AM Associates. We will be happy to develop a version of 2AM-BBS for any network for which you can provide us specifications. 1-4 2AM BBS Sysop's Manual Keyboard Functions _________________________________________________________________________ Keyboard Functions Chapter 2 2.1 LOGGING IN FROM THE CONSOLE If a user has privilege bit #72, he can access the BBS from the terminal (local mode). This privilege bit prevents anyone from walking up to your terminal and logging in. It is especially useful when the terminal is easily accessed by many people that you don't want logging in locally. To log on in local mode, hit the ESCAPE key. 2.2 STOPPING AND RE-STARTING 2AM-BBS When running 2AM-BBS from the terminal (not via the modem), remember the following keys: 1. Shift-F10 stops the program and returns you to DOS. 2. Shift-F9 will halt the system and re-start it. Using either of these function keys while a user is online will drop the user from the board. 2.3 HELP KEY F1 is the help function key. A window appears at the top of the screen with all of the function keys and their definitions displayed alongside. 2.4 INPUT/OUTPUT IN 2AM-BBS 2.4.1 THE PRINTER If you have a printer and wish calls to be logged to it, create the file sys disk:pon.cnf. 2AM-BBS just checks to see if it exists before logging calls to the printer - the file need not contain anything. In addition to logging calls, the printer can be used with the following keys: 1. F3 will send everything that appears on the screen to the printer. Hitting F3 again will turn the printer off. When this is in use, the letter P will appear in the status line at the top of your screen. Note that this option may not be used while file save (F5) is active. 2. F4 will dump whatever is currently on the screen to the printer. 2.4.2 OUTPUT TO DISK F5 sends everything that appears on the screen to a disk file. The system will pause and you will be prompted for a file name when you hit 2-1 2AM BBS Sysop's Manual Keyboard Functions _________________________________________________________________________ this key. Hitting F5 again will stop sending output to a file. When this is in use, the letter F will appear in the status line at the top of your screen. Note that this option cannot be used while output to printer (F4) is active. 2.5 VIEW/EDIT CURRENT USER 1. F7 allows the sysop to view the user currently online. A window appears on the top of the screen with information about the user such as the user's name, number, time limit, time remaining, file credits, e-mail limit, e-mail sent, etc. 2. F8 allows the sysop to edit the user online. A definition file may be used, or the sysop may edit the user manually. Options include adjusting the user's time remaining, adding or subtracting privilege bits, changing the e-mail limits, file credits, etc. Note: if security mode is ACTIVE (set in the Validator), this function is disabled. 2.6 RESERVING THE TERMINAL F6 reserves the next available login for the sysop. When the current user logs out, the board takes itself offline and sounds an alarm to notify you that the board is available. The letter R will appear in the status line at the top of the screen when this function is in use. 2.7 BELL TOGGLE F2 toggles the bell on and off. Default is bells on. Resetting the board with Shift-F9 will not turn the bell toggle off, but a system reboot will return the toggle to its default mode. The letter B will appear in the status line at the top of the screen when the bell toggle is on. 2.8 JUMPING TO DOS Hitting ALT-J from almost anywhere in the system (when a user is logged in) will take you into DOS if you are running 2AM-BBS locally (from the terminal). Any user on-line when you jump to DOS will have his/her screen "freeze". They will not see what you are doing in DOS. Type EXIT at a DOS prompt to return to 2AM-BBS. NOTE: You cannot jump to DOS when a user is in the editor. 2-2 2AM BBS Sysop's Manual Further Setup and Customization _________________________________________________________________________ Further Setup and Customization Chapter 3 2AM-BBS uses many text files that the sysop can configure to his or her tastes, and this chapter covers some general principles for modifying these files. 3.1 MENUS Menus are pre-created but can be changed to suit your tastes. If you intend to customize your system, this is a good place to start. As they stand now, menus display all options open to a new user. Privileged options are not displayed. As a rule of thumb, we do not generally show a user anything that he does not have access to. 2AM-BBS supports 40 and 80 columns as well as standard ANSI color commands. If the menu contains IBM extended graphics characters and the user cannot display them, then these characters are displayed as periods. Menu names have three different formats. Below are examples for 2AM's Main menu: 1. If the file main80x.mnu exists and the user has responded that he or she can display ANSI graphics, this file will be output. If you have an ANSI editor and want to make ANSI menus, put the addition "80x" on the menu name to create files of the form "abcd80x.mnu" where "abcd" is the menu name shown below. 2. If the ANSI menu does not exist OR if the user cannot display ANSI, but has an 80 column screen, the file main80.mnu will be output if it exists. When writing 80 column menus, create files of the form "abcd80.mnu" where "abcd" is the menu name shown below. 3. If both cases 1 and 2 fail (either only one menu is set up OR the user cannot display ANSI or 80 columns) then the file main.mnu will be output. If you do not wish to have more than one menu for a section, use menus without the "80" or "80x" additions to the name. The menus are as follows (just the "abcd" part here, you add the "80" or "80x" additions as appropriate: 1. base : Menu for the message bases 2. bbsls: Menu for the BBS Lister 3. bmain: Menu for base maintenance 4. conf : Menu for the configure section 5. door : Menu for the jumpdoors section 6. edcom: Menu for the editor 7. email: Menu for Email 8. files: Menu for the FILES section 3-1 2AM BBS Sysop's Manual Further Setup and Customization _________________________________________________________________________ 9. main : Main menu 10. maint: Menu for the main maintenance section 11. triv : Menu for the trivia section 12. valid: Menu for the user validator 13. voter: Menu for the voter section NOTE: All of these files are straight ASCII with one exception. If the character ASCII 250 is embedded in the file as the first character on a line, it will be intercepted and the message: Hit RETURN to continue will be output. Different editors will allow you to put ASCII 250's in files in different ways, but the most standard way is to hold down the ALT key, and, holding it down, type "250" on the numeric keypad on the right of the keyboard. This feature allows both you and us to paginate various text files. You can make use of this special ASCII character in any text file that the BBS outputs. 3.2 TEXT FILES These files are in text_disk and also may be customized. Specifics for introduction and information files in text_disk will have to be filled in. All of the features (the "80" and "80x" additions, the Ascii 250, etc.) that existed for the menus exist for text and information files as well. If the first character in a text file is a "w", (note: lower case) the text file will be displayed in either 40 or 80 columns depending on the user's configuration. Please examine the help files supplied with 2AM-BBS for examples of files using the "w" format. For best effect, "w" format files should be created with a word processor that supports hard and soft carriage returns. 3-2 2AM BBS Sysop's Manual User Validator _________________________________________________________________________ The User Validator Chapter 4 The validator is the section of the BBS that allows the sysop to edit, view, and maintain all user accounts. You enter the validator by typing "@" at the main menu. Please note: if you do not have the privlege bit required for the validator, you will receive an "Invalid Command" message when typing "@" here. 4.1 FILES This section describes all the files used by the validator section of 2AM-BBS. 4.1.1 USERLOG.DAT The userlog file is sys disk:userlog.dat. It contains all nonpersonal data about the users. The following information is stored: 1. Username. The name the person uses on the board, not necessarily a real name. 2. Password. 3. Date of first login. 4. Date of most recent login. 5. Total time on system (hours : minutes). 6. Total number of calls ever made by the person. 7. Time limit on system. The maximum time allowed is 1439 minutes per day (23 hours, 59 minutes). 8. File credits (stored in terms of kilobytes) that the user can download. This number is governed by the upload/download ratio you have set in Drive.dat (see Utilities section for more information). 9. User privs. A list of the privilege bits and their functions is contained in the file sys disk:access.dat. 10. Number of logfails. If a person gives an account number but the wrong password for that account, a logfail will be recorded in that account. When the real owner of that account logs in, if the number is three or more, the message: XX LOGFAILS SINCE LAST SUCCESSFUL LOGIN will appear. XX is the number of times an incorrect password was given for the account number. This number is reset to zero after a successful login. If the logfails are high (5 and up), someone may be attempting to break into this account, or the user has forgotten his password. 11. Daily E-mail limit. Setting this to zero allows the user to send an unlimited amount of mail. Valid limits are 1 through 255. 12. Other information that the different sections of the BBS may need (whether the user voted on a topic, what the person's last post 4-1 2AM BBS Sysop's Manual User Validator _________________________________________________________________________ number was (to tell if a message was posted before or after the last time a person called in), whether the user needs linefeeds, has an 80 column screen, can display ANSI graphics, etc.) The first user on the system (probably you) will be account number (record number) one. Record zero is reserved for the 2AM-BBS authors so that they can go in and do maintenance or upload utilities or updates when necessary. The userlog will then contain one record for each user. 4.1.2 USER APPLICATION FILE This file contains personal information. It is collected during the user application procedure when a user logs in for the first time. The following information is stored: 1. Person's last name 2. Person's first name 3. Person's street address 4. Person's city 5. Person's state (2 letter abbreviation) 6. Person's zip code 7. Person's voice phone number (area code mandatory) 8. Person's modem phone number 9. Person's age 10. A one line statement from the person as to where they heard about the board. 11. Does the person want this information kept confidential (Y/N). 12. Bit encoded answers to up to three questions that you can pose during the user application. Bit encoding is explained its own chapter in this manual. 4.1.3 SYSTEM LOGS The logs, sys disk:sys.log, sys disk:chat.log, sys disk:files.log, sys disk:handle.log, and sys disk:gen.log are kept by the system. Syslog (sys.log) keeps information about new users, system errors, BBS Lister entries, and other information that you might need to know. Chat.log keeps a record of all chat requests. Files.log keeps a record of all files uploaded and downloaded through the Files section and the users who transferred the files. Handle.log records all users who use the /name command in the editor. Gen.log records logfails, carrier drops, and system startup times. To read, copy, or delete these logs, use the [S] command in the validator. 4.1.4 LOOKUP FILES The directory look disk contains a set of user lookup tables. When someone refers to a user by name (e.g. sending Email), these files are 4-2 2AM BBS Sysop's Manual User Validator _________________________________________________________________________ consulted to find the person's usernumber. The lookup files are just there to make access to the userlog quicker. They do not need to be changed, and must always be present when the BBS is running. If there are ever problems with them, you can delete all the files in look disk and run the utility LOOKER.EXE (refer to the Utilities chapter of this manual). It will regenerate the lookup tables by reading from the userlog. 4.1.5 ACCESS.DAT sys disk:access.dat contains descriptions of all the privilege bits. The descriptions for each privlege bit are used when a user uses the [Y]our status command off the main menu. You may view and edit the privlege bits descriptions in the file with the [A] command in the validator. Some privilege bits are reserved by the software; some are for you to use. You may assign users privilege bits when you make up message bases and protect files in and around the BBS. 4.2 PRIVILEGE BITS FOR NEW USERS When a user logs in as new, he or she ONLY gets privlege bit 1 unless the sysop has created the file NEWUSER.DAT in sys disk. (See the chapter on new users for more information.) The rest (Email, FILES access, etc.), may be given through the edit functions in the validator. 4.3 VALIDATOR COMMANDS [E] - Edit User [V] - View User [D] - Delete user [A] - Access list [S] - Show a log [!] - View User applic. [N] - New user validator [L] - Load Sweeper [Q] - Quick scan users [R] - Range edit users [W] - Wipe users [T] - Toggle security mode [M] - Main Menu The [E], [D], [V], [!], and [N] options all support either the username or user number as parameters. Example: VALIDATOR > D203 Or: VALIDATOR > D DEAD ED If you put the option without the argument, you will be prompted for more information: 4-3 2AM BBS Sysop's Manual User Validator _________________________________________________________________________ Validator > D Username/number to delete > 203 1. [V]iew username or number. Displays the information in the user's userlog record. 2. [!] username or number. Displays the information in the user's user application record. 3. [E] username or number. Displays each field in the user's record to you one field at a time and then stops and prompts you. Users may be edited manually or with a definition (.DEF) file. If you hit return here, the information will not be changed. If you type in new information at this prompt, the information you just typed will replace the old information. If you change a user's name, the validator will ask you if the user lookup tables should be modified. If the name change is not temporary, change the user lookup tables. The user's record cannot be found (when sending email to the person, etc) if the lookup tables are not modified. When changing usernames, CHECK to make sure you don't assign two users the same username. Both will be able to read each other's mail and the user lookup tables may not function correctly. When it comes to the user privilege bits, all the user privilege bits are shown and you are prompted to add or delete privilege bits. You can specify ranges of privilege bits here. Placing a minus sign (-) at the beginning of the line will delete those privilege bits from the user. Hit RETURN when you are finished adding or deleting privileges. 4. [N]ew user. Validates username, number, or return. (This option is a shortcut for [!]username or number then [E]username or number.) If a name or number is not supplied, the system gives you all the new users in the SYS.LOG to be edited. It is recommended that you do not clear the SYS.LOG until after this command has been used. First the user application record is displayed. Then you are prompted to edit the userlog fields. 5. [D]elete username or number. Will delete the user viewing the user record and asking you to confirm. 6. [Q]uickscan users. This feature outputs a two line summary of the user record for a range of users. Full range parsing is available. Q* means quickscan all users. (NOTE: To see what the last active record in the userlog is, use q9999. The last active record will be displayed.) 7. [A]ccess allows you to maintain sys disk:access.dat. You may choose to [E]dit a description for a privilege bit (normally done when you assign it to something), [L]ist privlege bits (give a range of bits to list or "*" to list all of them), or [S]can through the file looking 4-4 2AM BBS Sysop's Manual User Validator _________________________________________________________________________ for a bit. When you scan, you will be asked for some characters to match against. If you are trying to find the privlege bit to use /load in the editor, for instance, give the characters "/load". 8. [S]how log allows you to look at a log. After the log is displayed, you will be prompted to [m]ove, [p]rint, [e]rase, [c]opy, or [q]uit. Copying a log will create a file with the number 1 appended to the file name (i.e. SYS1.LOG). The [e]rase command will clear and restart the log. The [m]ove command will first copy, then erase the log. NOTE: Log files are just text files. 9. [R]ange editor allows you to change file credits, mail and time limits, and privilege bits on a range of users. When prompted for one of the first three items, you will have the option to change these, relative to what they are already set for, by placing a plus (+) or a minus (-) before this number. For example, using +5 for e-mail on a user who has a 10 message e-mail limit will give that user a total of 15 e-mail messages. If a plus or minus is not supplied, the range sets it exactly to the number given. NOTE: The range editor is a powerful supplement to the sweeper. 10. [W]ipe users is a quick method of deleting a range of users. Use this with the sweeper when purging users. 11. [T]oggle security mode. When security mode is activated, you can no longer jump to DOS and privacy mode will be turned on. Privacy mode blanks the screen when a user enters e-mail and for selected message bases. When security mode is on, an S appears in the status bar at the top of the screen. 12. [L]oad Sweeper. This is a feature of 2AM that allows you to select users by almost any criteria you can think of. The sweeper is explained below. 4.4 THE SWEEPER The sweeper is enabled by selecting option "L" from the validator ([L]oad Sweeper). It allows the sysop to select a group of users based on various criteria. The sysop can then edit or view those users in a number of ways. Once in the sweeper, a question mark [?] will display the sweeper menu. The sweeper is automatically cleared when you enter the sweeper or exit the validator. The following options can be used in the Sweeper: A - Abort: Cancels and clears the sweeper, returning you to the validator. C - Call dates ( [F]irst and [L]ast ): Allows you to select users by first or last call dates. Once a date is chosen, you are then asked if you want the calls compared to calls made before, after, or on that date . 4-5 2AM BBS Sysop's Manual User Validator _________________________________________________________________________ E - E-mail limit: Allows you to select users based on their e-mail limits F - File credits: Allows you to select users based on total file credits H - Handles - [A]dd or [R]emove a specific handle: Allows you to add or remove a specific handle to the sweeper at any time. I - Input to sweeper from text file: Retrieves a file stored with the [O]utput command. Enter a file name without any extension. Files must be on sys_disk and have a .SWE extension (see "O" below). M - Return to validator with data (Done): Brings you back to the validator prompt. If the sweeper is loaded, you will see the message "Sweeper is loaded". The next validator command that directly affects users (i.e., range edit, quickscan) will effect that command for ALL users in the sweeper list. After the sweeper list has been used, it is cleared. If you wish to do more than one ranged function, output the sweeper list to a text file (see below). O - Output sweeper to text file: Outputs the current sweeper list into a text file. Supply a file name only (no extenstion). 2AM will put all text files created by the sweeper in the sys_disk with the extension .SWE. P - Privs: Allows you to create a sweeper list from a specific privilege bit. R - Range: Allows you to add users to the sweeper list via a range of user numbers. S - Show sweeper list: Outputs to the screen the list of users in the sweeper. T - Time allowed each day: Allows you to add users by time allowed. Note: File credits, time, and e-mail limits all give you the option of selecting a value greater than, less than, or equal to the value you enter. After entering a criteria into the sweeper using one of the above options, you must select a sub-command. Sub-commands determine what is to be done with users that match the criteria you entered. You can add and remove users to the sweeper list via the various sub-commands. The following sub-commands apply when adding/subtracting users to the sweeper list: [1] Add matches and remove non-matches [2] Add non matches and remove matches [3] Add matches only [4] Add non matches only [5] Remove matches only [6] Remove non matches only 4-6 2AM BBS Sysop's Manual User Validator _________________________________________________________________________ Example 1: Below is an example of the purging users with [C]all date option. Users who have not called since 1-23-88 are selected, then deleted using the [W]ipe command. Sweeper is empty Sweeper >c Which call? [F]irst, [L]ast, [Q]uit >L Enter date to check against Last call date (xx-xx-xx) >01-23-88 Select users whose Last call is BEFORE/AFTER/ON this date? <B/A/O> >B Selection option [1-6],[?] >3 Working.. Completed. Users in Sweeper: 35 Sweeper >m Sweeper Loaded Validator >w 4 : CHRIS 01-17-87 -- 07-18-87 Delete this user ([Y]/n/q) > (We cut out the other 34 users in the interests of brevity.) Example 2: Below is an example of using the [P]riv bit option. We selected all users who have privlege bit 101, then removed all users who had privlege bit 65. Sweeper is empty Sweeper >p Enter the Priv to Check: 101 Selection option [1-6],[?] >3 Working... Completed. Users in Sweeper: 53 Sweeper >p Enter the Priv to Check: 65 Selection option [1-6],[?] >5 Working... Completed. Users in Sweeper: 47 4-7 2AM BBS Sysop's Manual User Validator _________________________________________________________________________ 4.5 PRIVILEGE BITS FOR THE VALIDATOR The following privilege bits are reserved for the validator: 1. #89: User may enter the validator 2. #90: User may view user applications in the validator. 3. #91: User may view passwords when reading user records. 4. #92: RESERVED for future validator expansion 5. #93: User may edit user records in the validator. 6. #94: User may delete user records in the validator. You can give limited validator access by giving out privilege bit #89, bits #89 and #90 or privilege bits #89, #90 and #91. These combinations allow partial viewing of user records. 4-8 2AM BBS Sysop's Manual User Logins _________________________________________________________________________ User Logins Chapter 5 This chapter will describe the login process from the sysop's point of view and point out some of the changes you can make to the new user process. 5.1 NEW USER LOGINS When first logging in, a user will get the Board Name, communications parameters, and a <HIT RETURN> prompt. After hitting return, the file text disk:start.txt is output. Most BBSes use this as an introduction to the board. NOTE: this file, like most other files MUST exist or users logging in will get "file not found" messages on their screens. If you do not wish text to output in certain places (such as here), just create a blank file. The user will then answer some questions that will be used to set up his or her account. Details of these questions are in the user's manual. All the information that is entered here is stored in sys disk:userlog.dat. Next the file text disk:userapp.txt will be output. This marks the beginning of the user application procedure. The user will then be asked for real name, address, etc. This information is stored in sys disk:userapp.dat. Most questions are pre-configured, but a few can be modified by the sysop. There are three multiple choice questions that can be asked in the user application process. Each question can have up to 8 choices for answers. If you want to ask these questions, create any of the following files: text disk:appq1.txt text disk:appq2.txt text disk:appq3.txt List the choices in the file with numbers next to each choice. This file will be output and the user will be instructed: Input all choices that apply Input one choice per line Hit RETURN on a blank line when done Responses to these questions will be stored as three bit encoded numbers. Bit encoding is discussed in its own chapter in this manual. Each BBS has a policy for releasing information, and your policy should be written up and saved in the file text disk:privacy.txt. A standard statement usually goes something like: 5-1 2AM BBS Sysop's Manual User Logins _________________________________________________________________________ Do you mind if the sysop releases your account name to users of similar interest? Under NO condition will your user information be released without your permission. This statement is followed by the text: Do you agree to the above terms [Y/N] > If the person answers NO, his or her user application will contain the words "Information marked Confidential!" Now, closing comments for the user application are output (text disk:append.txt). The user is assigned an account number and is then tested to make sure he has written it down and remembered it. Now the file text disk:nuser.txt (or nuser80.txt or nuser80x.txt) is output. This file contains comments to the new user (board policy, any special features or functions of the board, etc.). After hitting return, the new user is placed where an old user would first come into the board. The file text disk:notes.txt is output. NOTE: this file is the file output for the "read bulletin" option (the [+] option on the main menu). 5.2 THE STANDARD LOGIN Any user can login with either his or her account number OR by typing his or her user name at the first prompt. NOTE: if a user supplies an illegal account name/password combination, the account with the incorrect password will be marked as having a logfail on it. After 3 logfails, the board will drop carrier on a user and will continue to drop carrier on anyone who gives an incorrect name or password for that account. Once the user has logged in, a check on their daily time limit is made. If they have used all their time for the day, they are notified that they have exceeded their daily time limit and the board resets. If the user is attempting to log in from local mode and does not have privilege bit 72, they are given the message "Insufficient access to enter local mode" and the board resets. When a user successfully logs in, the file text disk:notes.txt will be output. Then some of the following lines will appear: Welcome USERNAME You are caller number 44, 21 for today Last caller was LAST USER 4 Logfails since last login You have 3 new Email messages New voting topics have been created New trivia questions have been created 5-2 2AM BBS Sysop's Manual User Logins _________________________________________________________________________ The caller number and name of the last caller is stored in the file sys disk:last. This file is specially formatted, and it should not be changed. If there were more than two logfails on the account, a notice of the form above will be output. Also, if there is new Email for the user, the user will be notified upon login as above. Note also that when new trivia/voting topics are created, the user will get the last two lines in the example. 5.3 NEWUSER.DAT Newuser.dat allows you to alter the default configurations for new users. The example below will use these defaults. The file sys disk:newuser.dat can contain the configurations shown below, or any variation you wish to grant a new user. Each line contains a number to be assigned, followed by a description of what that number is used for. The file must contain these items in the following order: 100 - File credits (in kilobytes) a new user can download before uploading 0 - E-mail limit (0 equals no limit on e-mail messages per day) 35 - Time limit for a new user 1 - Privilege bit to give to new user These quotas and privileges will automatically be given to all new users on their first call. NOTE: Additional privileges can be added, one per line, after the last line in this example. The descriptions after the numbers are not necessary but help guide modification of the file. Please note: Do NOT give out important privilege bits to new users. 2AM- BBS will not allow you to grant bits 81 through 100 with this file. It is recommended that sysops give out privilege bit 1. This bit is not used by the program, but it is convenient to use for message base access and it is the default bit to assign to all files, voting, and trivia sections. 5.4 .DEF FILES .DEF files are a fast method for sysops to edit users' accounts. The format is identical to the format of NEWUSER.DAT above. If Time Limit, E-Mail Limit of File Credits are 0 in a .DEF file, the users' current values will not be altered. .DEF files allows a sysop to create lists of standard privs that are given to validated users. Using .DEF files insures that you give the same privilege bits to users when you are doing some kind of standard account editing (ie: validating a new user). 5-3 2AM BBS Sysop's Manual User Logins _________________________________________________________________________ 5.5 SPECIAL LOGIN MESSAGES There are three special login messages that can be displayed when a user logs in. Each is triggered by a privilege bit. If privilege bit #75 is on, the file text disk:splogin1.txt is output. If privilege bit #76 is on, the file text disk:splogin2.txt is output. If privilege bit #77 is on, two things happen. The file text disk:splogin3.txt is output, and the user is forced to fill out another new user application. Set privilege bit #77 when a user supplies false information in the user application. Then set up file splogin3.txt with some message indicating that you rejected the application. The file will be output, and the user will be taken to the user application section. Privilege bit #77 is reserved for this purpose, but you are free to use the other two bits as you see fit. NOTE: All three special login messages are non-abortable. 5.6 REJECTS.DAT The file REJECTS.DAT in SYS_DISK can be used as a means of disabling certain handles from being used by new users on your BBS. Pattern matching is also available. This is an example of the REJECTS.DAT file: NEIL *LARK -*SYSOP The above set of lines show all three possible modes selected in the rejection list. The first line is an example of a direct pattern match. If a user tried to create an account called NEIL then they would get the message that that name is reserved or restricted on this bbs. The second line would do the same thing, but restrict any handle containing LARK (ie CLARKE, LARK BARK, LARKING). The final example performs the same as the previous examples except that the "-" at the beginning of the line tells it to let the person fill out an application before telling them the name is bad. This option is there just in case you are really sick of people using foul handles, and you want to make then suffer through the application before they find out they can't use that handle. The system puts them through the entire application procedure, but does not save their information anywhere. 5-4 2AM BBS Sysop's Manual The Editor _________________________________________________________________________ The Editor Chapter 6 The board has one editor, and it is called whenever you post a message on a message base, in feedback, in Email, and in the BBS Lister. If you wish, you can use the editor to edit text files as well using the /LOAD and /SVE commands described below. 6.1 PRIVILEGED OPTIONS All commands are explained in the user's manual except for three privileged commands: 1. /LOAD will prompt you for a text file name, and will load that text file into the editor. You will be placed right after the last line of the file you have loaded in. You can then edit this file. REMEMBER: the editor will only allow at most 100 lines, so if your file is larger than 100 lines, it will be truncated. 2. /SVE will prompt you for a file name and will then save the contents of the editor into that file. Using this feature, you can "/load" in files and edit them and then "/sve" them. If you are editing a file for the bbs or something like that, just "/a" (abort) out of the editor after you are done editing (otherwise, the file will be saved as a message). Note: You can overwrite files using "/sve". If the file already exists, you will be prompted as to whether or not you wish to overwrite it. 3. /NAME this command allows the user to change to name appearing in the heading of a message. The name used must be a name that is not currently in the user log. This prevents people from "impersonating" other users. /NAME can NOT be used in email. Also /NAME can not be used in certain types of message bases. Please refer to the Message Base section of this manual for more information. 6.2 PRIVILEGE BITS USED Privilege bits can be assigned to give users privilege to enter longer messages into the editor. If you do not give any privilege bit out, the user will have a 40 line editor. If you wish a user to be able to type in more than 40 lines, you may use the following bits: 1. #78 - Gives a user a 60 line editor 2. #79 - Gives a user a 100 line editor In addition, the following other privilege bits pertain to the editor: 1. #81 - /LOAD command in the editor 2. #82 - /SVE command in the editor 3. #87 - Allows change of handle (/NAME) 4. #80 - Allows ANSI color escapes sequences in the editor 6-1 2AM BBS Sysop's Manual The Editor _________________________________________________________________________ 6-2 2AM BBS Sysop's Manual Message Bases _________________________________________________________________________ Message Bases Chapter 7 7.1 FILE FORMATS There are three files to each message base. These files are baseXX.ptr, baseXX.dat, and baseinfo in the base_disk directory. (XX equals base number.) Baseinfo is a directory of what bases are available. The file contains all of the information necessary for accessing, describing, and maintaining the bases. A base cannot be accessed unless there is a line in baseinfo that refers to that base. BASEINFO STRUCTURE The following is the format for a line in baseinfo: (| = one blank space) base_number | read_priv | write_priv | maint_priv | base_window | base_selection | base_name OR 0 | priv to view comment | 0 | 0 | 0 | 0 | comment 1. Base_number is the number for the base. NOTE: it is not necessarily the base number that every user sees. For instance, when a user goes to base 3 the user will be taken to the third base in the baseinfo file that he has access to. This may be any base number, not necessarily physical base number three. The base number a user sees is called the logical base number and will be dependent upon the user's access level. The physical base number is the number you assign the base in baseinfo. For example, a line in baseinfo containing a base number of 3 will refer to files base3.ptr and base3.dat. If this base is at the end of the baseinfo file, it may have a logical number of 10 if it is the tenth base the user can access. For the most part, you do not have to be concerned by logical base numbers. They are automatically determined by 2AM according to the order you list information in the baseinfo file. The physical base numbers are used to determine what files will hold the message for a specific base. In addition, the physical base numbers also are used to select different base types. The following base numbers give the sysop several options: 1-199 Normal bases 200-299 No /NAME allowed unless user has privilege bit 99 (system access) 300-399 Anonymous posting is automatic 400-499 Real names are used automatically 500-699 Normal bases/privacy mode on 700-799 No /NAME without privilege bit 99/privacy mode on 800-899 Anonymous posting is automatic/privacy mode on 900-999 Real names are used/privacy mode on 7-1 2AM BBS Sysop's Manual Message Bases _________________________________________________________________________ Normal bases are bases in which there are no added restrictions or features. Handle change (/NAME) is allowed on all bases from 1-199 and 500-699 if the user has the /NAME privilege bit. Anonymous posts are messages in which the time is left blank and the poster's name is changed to ANONYMOUS. This is an automatic feature and cannot be overridden with /NAME. Real name bases are bases that will change the user's handle to the name that they supplied in their user application. This is an automatic feature and cannot be overridden with /NAME. Privacy mode will cause the screen to blank when a user enters this base whenever security mode is enabled (see validator T command). NOTE: Privacy mode will NOT go into effect during a local mode login. 2. Read_priv is the privilege bit necessary to read in this base. A user will not know a base exists without read access to the base. 3. Write_priv is the privilege bit necessary to write in this base. You may give a user read_priv for the base without write_priv if you wish. If a user does not have the write privilege for the base, an asterisk will appear next to the base name in the [S]how bases option. 4. Maintenance_priv is the privilege bit necessary to do maintenance in this base. By giving each base a different maintenance privilege bit, you can allow individual users to govern particular bases. With maintenance privileges, a user can delete or edit any message on the base. The user can also access base maintenance while on the base. It is not necessary to give all bases different maintenance bits. If you do not wish to give users maintenance access, assign it one of the system bits such as 99. 5. Base_window allows you to set a finite amount of messages per base that you wish to remain visible. Messages outside of this window will not automatically be deleted. Messages may be retrieved if they scroll off the window by altering the window size or by deleting newer messages. Messages may be deleted by using the BSMaint Utility (see Utilities chapter for more information.) A window of zero allows for unlimited messages on that base. 6. Base_selection is one of the "invisible" privilege bits or zero. The number assigned must be between 213 and 252 if you want to allow the users to de-select this base. This option is used for the Read Selected command. NOTE: whenever you create a new base, it would be a good idea to grant all users the access bit you have assigned for this field. If you assign this field a zero, a user cannot de-select the base. 7. Base_name is the name of the base. Examples: "Public", "System News", "IBM computer user's forum". The name can be up to 35 characters and can contain any legitimate ASCII characters or ANSI color sequences. 7-2 2AM BBS Sysop's Manual Message Bases _________________________________________________________________________ The following is an example baseinfo line: 12 1 4 45 100 215 Public Base 12: The messages for "Public Base" are in base disk:base12.ptr and base disk:base12.dat. 1: Anyone with privilege bit 1 can read messages in this base. If a user does not have privilege bit 1, he or she will not even know that this base exists. 4: Anyone with privilege bit 4 can post messages on this base if they have privilege bit 1 as well. 45: Anyone with privilege bit 45 can do maintenance on this base if they have privilege bit 1 as well. 100: is the maximum number of messages visible on this base. 215: is the privilege bit used for selection purposes. An example baseinfo file: 1) 1 65 65 99 0 0 Feedback 2) 0 1 0 0 0 0 3) 0 1 0 0 0 0 System Boards 4) 0 1 0 0 0 0 ::::::::::::: 5) 16 1 1 12 200 215 Public Base 6) 3 1 99 99 0 0 System News The numbers in boldface are NOT part of the baseinfo file. They are for referencing purposes only. Also, please note the spacing in the sample. Please make your baseinfo file easy to read. 1. Feedback messages are in base 1 (ie. base1.dat and base1.ptr), and feedback will appear as base 1 to any user with privilege bit 65. You must have feedback as the FIRST base in the list, and you must have privilege bit 65 in both the read and write fields. Users are temporarily given privilege bit 65 whenever they leave feedback. If you put ANY other number down, people will not be able to send you feedback. Instead, feedback will go to the first base that they have access to. If you want to make feedback public, this is a good way to do it. 2. Comment line. This causes a blank line to be printed in the [S]how bases command provided the user has privilege bit 1. 3. Comment line. This prints out the words "System Boards" to be printed in the [S]how bases command provided the user has privilege bit 1. 7-3 2AM BBS Sysop's Manual Message Bases _________________________________________________________________________ 4. Comment line. This prints out the underscore in the [S]how bases command provided the user has privilege bit 1. 5. Public Base. Read access is privilege bit 1, write access is privilege bit 1, maintenance access is privilege bit 12, window size is 100, and selection is allowed with privilege bit 215. 6. System News. Read access is privilege bit 1, write access is privilege bit 99, maintenance access is privilege bit 99, window size is unlimited, and de-selection is not allowed. The baseinfo file may be edited with any text editor, or you may use the baseedit utility described in the utilities chapter. We highly recommend you use the baseedit program provided with 2AM-BBS since it will reduce the possibility of making errors when editing the baseinfo file. .PTR AND .DAT FILES 2AM-BBS comes with a few of these files. Keep one baseXX.ptr and one baseXX.dat file for feedback and assign the rest to user bases. You can create more base files with the [X] option in maintenance (see below) or with the BASEEDIT program covered in the utilities section of this manual. 7.2 BASE MAINTENANCE A user can do maintenance on a base if he or she has the master base maintenance privilege bit (86) or the privilege bit to do maintenance on that particular base. Base maintenance allows the following: 1. In a [S]how bases command, a dash '-' will appear next to any base that a user has base maintenance privileges for. 2. Users with base maintenance privileges can read deleted messages and undelete messages (from the maintenance section). 3. Users with base maintenance privilege bits have the option to compact deleted messages. A compacted message cannot be undeleted. If you choose to compact a deleted message, any number from 1 to the size of the base (ie., 200) is valid. NOTE: The closer to the beginning of the base, the longer it takes. Compacting from message one causes the compaction to run through the entire base. It is recommended that you compact from the message previous to the one being deleted. 4. Users with base maintenance can delete or edit any message on the base, or delete a range of messages. 7-4 2AM BBS Sysop's Manual Message Bases _________________________________________________________________________ Typing "maint" from any base prompt puts you into the base maintenance section. Typing "m" will get you back to the main base prompt. The following options are available: 1. [X] Base Create. This option allows a user to generate new baseXX.dat and baseXX.ptr files. Bases cannot be seen by the public until there is a line for the base in baseinfo. When creating a base, you will be prompted for the physical base number of the base (the number that corresponds to the XX in the baseXX.ptr and baseXX.dat files). Don't confuse this physical base number with the logical base number. If you try to create a base and it already exists, you will be prompted as to whether or not you want to overwrite the existing files. If you choose yes, the messages will be erased and a new base will be generated. A user needs privilege bit 85 to create bases. 2. [U]ndelete messages. Any message that is marked deleted can be undeleted here. NOTE: compacted messages are lost forever. Only messages marked "Deleted" in their header may be undeleted. 3. [C]opy Message. Allows a user to copy a message to another base. You may copy either by the logical base number or by the base name. (Example: in copying a message to the feedback base, you can enter "Feedback" or any significant string of characters from that base name.) A user needs privilege bit 83 to copy messages. 4. [G]rant access. Allows a base-op to grant users read and write access to a base. Users may be entered by handle only. 5. [R]emove access. Allows a base-op to remove users' read and write access to a base. Users may be entered by handle only. NOTE: If you use the same privilege bit to read or write on more than one base, and a baseop removes a user's privilege for one of those bases, the user loses access to ALL bases containing the same read/write privilege bit. 6. [L]ist users. This prints out a list of all users with read, write, and maintenance access to a base. Asterisks appear in the appropriate category for each user. 7. [W]ho command. This shows the actual handle of users who posted a message or range of messages. It is used as a quick way of determining who changed handles in a message base. It may also be used on bases that are restricted to anonymous or real name posting. 8. [I]nformation command. This allows a base-op to create the base information (the message that is displayed via the "I" command in the bases). When you type "I" from base maintenance, you are put into the editor of the current base information message. If base information does not exist, just input what you want the message to contain. If the base information already exists, you will be placed at the last line of the current base information message. You must restart or 7-5 2AM BBS Sysop's Manual Message Bases _________________________________________________________________________ delete the current message if you want to change the information completely. 7.3 PRIVILEGE BITS USED 1. You may reserve whatever unused privilege bits you want to give a user read access, write access, and maintenance access to a base. You specify the privilege to read and/or write to a base in the file base disk:baseinfo (described above). Use the access list in the validator to see which bits are currently unused. When you reserve a privilege bit, add it to your access list so that you have an accurate record of what bits you used. 2. Privilege bit #65 allows a user to read/write in feedback. 3. Privilege bit #83 allows a user to copy messages. 4. Privilege bit #85 allows a user to create bases. 5. Privilege bit #86 gives the user master base maintenance privileges 7.4 BASE CLEANUPS When messages are deleted or edited, excess data collects in the base files. Running the utility BSMAINT (see Utilities chapter for complete information) cleans out the excess data and compresses the message bases. NOTE: if you want to completely wipe a base, just use the base create option in maint. It will delete the old base files and generate new, empty ones. 7-6 2AM BBS Sysop's Manual Email _________________________________________________________________________ Email Chapter 8 8.1 EMAIL COMMANDS The following commands can be issued by any user who has access to the email section of 2AM-BBS: 1. [M] - Return to main menu. 2. [P] - Post. Send an email message to a user. If you would like to send the same message to several people, enter all their account names separated by a comma. For example: E-mail > P CAT, LARRY E., CHRIS,TV will send the message to users: CAT, LARRY E., CHRIS and TV all at once. 3. [R] - Read email. You will be asked if you would like to read your incoming or outgoing mail. You could enter [RI] or [RO] to read you mail thus avoiding the prompt 2AM displays if you enter only an [R]. 4. [L] - List all your email messages that are still outgoing. 5. [U] - User lookup. This is identical to the [U] option on the main menu. 6. [H] - Identical to every menu in 2AM-BBS, option [H] calls the help system. During a Read Incoming, a user has the ability to: 1. [A] - Answer the message 2. [F] - Forward the message to another user. 3. [N] - Go to the next message. Note - this option will DELETE the currently displayed message. 4. [R] - Re-Read the currently displayed message. 8.2 SPECIAL OPTIONS DURING READ INCOMING There are two extra options in the Email read incoming command that the sysop has control over. The first is the option to [D]isksave a message, and the second is to [S]kip a message. These functions need individual privilege bits (listed at the end of the chapter). [D]isksave prompts you for a file name (to be stored in MAIL_DISK), and then saves the message. [S]kip message allows the reader to pass by this message without deleting it. A skipped message will remain in the user's mail file. It will appear every time the user reads incoming mail until it is deleted with the [N]ext message command. 8-1 2AM BBS Sysop's Manual Email _________________________________________________________________________ 8.3 MAINTENANCE COMMANDS There are two maintenance commands in the Email section. These commands are used to view mail and print a list of a user's outgoing mail. They both require the Email maintenance privilege bit. By adding a username to the [L] command, one may get the outgoing list for that username. For example E-Mail > L MADD HATTER will give the outgoing mail listing for the user named MADD HATTER, instead of your own list. The second maintenance command is SPY. [SPY] allows you to view a user's incoming and outgoing mail as if you were that user. All the prompts will be the same and have the same effect as if that user executed them. In other words, using the Answer option in a SPY on a user's incoming mail will allow you to answer as that particular user. It will in no way state that you, and not the user, answered that mail. It is not expected that this option will be used, as it is rather unethical. NOTE: This option automatically gives you access to skip Email messages. NOTE: In SPYing on a user's incoming mail, the [N]ext message command will delete the message. Use skip to go onto the next letter. Example: E-Mail > SPY MADD HATTER will prompt you as to whether you wish to read incoming, outgoing, or both, and then read MADD HATTER's mail as if you were him. 8.4 FILES All files pertaining to Email are stored in MAIL_DISK. The files are as follows: (XX = usernumber) minXX.dat Incoming mail data file for user XX. minXX.ptr Incoming mail pointer file for user XX. moutXX. Outgoing mail pointers for user XX. Each mail file is self-maintaining. When a user is deleted, so are all their mail files, but not their outgoing messages. NOTE: Once a user is deleted, you will be unable to list their outgoing messages. NOTE: The message "Message count for this user incorrect" may appear if a user has had outgoing mail to a user who has since been deleted. All mail files are referenced by usernumber. Thus, changing a user's handle will have no effect on their incoming mail, but other users will 8-2 2AM BBS Sysop's Manual Email _________________________________________________________________________ not be able to list outgoing messages to a user whose handle you have changed. Also, if you changed a user's handle, they will not be able to read their outgoing mail written with their old handle. 8.5 PRIVILEGE BITS AND MAIL QUOTAS 2 - Access to Email 60 - Skip messages in RI 62 - Email Maintenance 63 - Disksave messages in RI Email quotas may be set on individual users. It is often used on multiuser boards to prevent people from having online conversations via Email. The quota may be set at any number from 1 to 254. Setting the mail limit to 0 allows a user unlimited Email messages. 8-3 2AM BBS Sysop's Manual Files _________________________________________________________________________ FILES Section Chapter 9 9.1 FILE CREDITS AND TIMES In your DRIVE.DAT file there are three fields that control parts of the files section. The first allows you to set a file credit system based on the number of Kilobytes (K) a user uploads. This number is multiplied by the amount in K that the user uploads, and then added to the users file credits. The other two fields control the opening and closing times for the files section. (This is overridden if the user has privilege bit 64). Setting these two times to equal values leaves the Files Section open 24 hours a day. However, setting these to two different values will allow you to open and close your Files Section during certain parts of the day. If you wish to change these settings at any time, use the utility DRIVER (for more information, see the chapter on Utilities). 9.2 FILE FORMATS There are several files you will use in managing uploads and downloads. You will note that there are two directories for the FILES utility, one for uploads (uload_disk) and one for downloads (dload_disk). 9.2.1. DOWNLOAD FILES There are two sets of files for downloads. The first file is dload_disk:library.dat. It holds the titles of all the libraries available, and you will create it yourself with a text editor. The format for each line is as follows: (| = one space) privilege bit to access | library number | library name OR 0 | privilege bit to read comment | comment Below is a sample library.dat for two sets of libraries, one accessed by privilege bit #22 and one accessed by privilege bit #23: 9-1 2AM BBS Sysop's Manual Files _________________________________________________________________________ 0 22 0 22 Normal libraries for priv #22 users 0 22 ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::: 0 22 22 8 Games 22 7 Utilities 0 23 0 23 Libraries for priv #23 users 0 23 ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 0 23 23 4 Pascal programs 23 6 Cobol programs 71 0 Upload directory 0 1 Please note that the upload directory has a file number of 0 and a privilege number of 71. This entry must be in library.dat or you will not be able to process uploads. Also noticed that the files do not have to be in numerical order. The user will view the files sections in numerical order. In the above example, a user with privilege bit 22 will see the Games directory as directory 1, even though it is physically directory 8. If a user does not have access to any files sections, he will not be allowed into the files area. The other set of files are dload disk:dirX.dat. They are the directories of files for library section X. Each has the following format: (| = one blank space) Privilege bit to access | Entry type | Disk file name Filename to display | Number of bytes | Date | Description OR Privilege bit to access | 0 Comment line There are four entry types, numbering from one to four. 1 - Non-readable 2 - Readable 3 - Free Non-readable 4 - Free and readable 9-2 2AM BBS Sysop's Manual Files _________________________________________________________________________ A free file is one that may be downloaded with the loss of any download credits. A readable file is a text file in the downloader. A non- readable file is a program or archive. Example: 1 0 # Filename Bytes Date Description 1 0 ---------------------------------------------------- 1 1 C:\PROG1.COM PROG1.COM 21888 11-15-87 PROGRAM TO TIE SHOES 4 3 C:\FW\BBS\UMAN\OUTPUT\2AMUSER.ARC 2AMUSER.ARC 36944 11-15-87 2AM USER'S MANUAL (FREE DOWNLOAD) 1 0 THIS IS A COMMENT -- NOTE THE ZERO IN THE COMMENT FIELD 1 2 C:\BBS\DLOAD\THINKER.DOC THINKER.DOC 1031 11-15-87 COMPUTER THOUGHT (READ ME) 9.2.2. UPLOAD FILES 1. The uploaded files themselves are called uload disk:up-XX.YY where XX is the upload number and YY is the port number (if the system is running more than one). 2. uload disk:lastu.dat contains the number of the last upload. It will be created automatically when an upload is made if it does not exist. 3. text disk:uplod.txt is a non-abortable text file that will be output when a user requests an upload. It is normally used to explain system rules concerning uploads. 9.2.3. EXTERNAL PROTOCOLS This option allows the sysop to add additional file transfer protocols. There are three variables that may be passed to these programs. BAUDRATE (note uppercase), COMPORT, and NAME. BAUDRATE is the buad rate the user is calling at. COMPORT is the COM port the user is on. NAME is the filename to send/receive. All but NAME are optional. 1. dload disk:protocol.dat contains the necessary information for calling external download protocols. 2. uload disk:protocol.dat contains the necessary information for calling external upload protocols. The format for these files, is two lines for each protocol. The first line contains the protocol and necessary information. The second line contains the name of the protocol that you wish to display in the list. Example: 9-3 2AM BBS Sysop's Manual Files _________________________________________________________________________ %C:\PROTOCOL\DSZ.COM port COMPORT speed BAUDRATE D sz NAME Zmodem %C:\PROTOCOL\DSZ.COM port COMPORT speed BAUDRATE D sb -k NAME Ymodem 1K (True Ymodem) %C:\PROTOCOL\DSZ.COM port COMPORT speed BAUDRATE D sx -k NAME Xmodem 1K The above example shows you how to use Omen Technologies DSZ external protocol program for downloads. This file would reside in DLOAD_DISK. NOTE: There are percent signs at the beginning of each program line to let the BBS know that these are .COM/.EXE files. They follow the same format used by JUMPDOORs. 9.3 THE MAINTENANCE UTILITY This utility in the FILES section is accessed by typing "maint" at one of the FILES prompts. You will need privilege bit #64 to access this maintenance section. There are different maintenace options depending on whether you are in the upload library or one of the files libraries. 9.3.1 FROM A FILE LIBRARY When calling MAINTENANCE from any library (except the upload library), you have several options: 1. Add [C]omment. You are asked for the comment to add and the privilege to view it. It is placed at the end of the library listing. 2. Add [F]ile. You are asked for: 1) Privilege bit to read the file (default is 1) 2) Full Filename on Disk (include drive name and path) 3) Description (up to 40 characters) for the file. 4) File type (1 through 4) The MAINTENANCE utility will stamp the date and size into the entry and add it to the end of the library list. 3. [U]pdate dir. All files in the directory will be checked to see if they exist. If a file is not found on the disk, but is listed in the library, it will be listed and you will be asked if you want to keep it in the directory. An answer of [Y] will write the word 'OFFLINE' as the size of the file, but leave the directory entry. An answer of [N] will remove the file entry from the library directory. If you want to put comments in the middle of the list, move files around, or do any other fancy stuff, you will have to edit the dirX.dat file, taking care to stick to the proper format. 9-4 2AM BBS Sysop's Manual Files _________________________________________________________________________ 9.3.2 FROM THE UPLOAD LIBRARY If you are in the upload library and type MAINTENANCE you will get two options: Would you like to move files to their proper directories ([Y],n) File movement will show you each upload listing in reverse order (from the end of the library list to the beginning) and ask questions pertaining to what should be done with the file: Do you wish to keep this file [Y]/N/Save 1. Hitting N erases the file and entry and skips the rest of the questions. 2. Hitting S asks for a new name for the file. The file cannot be moved out of the uload_disk directory with this command, so DO NOT put a drive name or path name in the file name. Use the Save command for files that you wish to keep for yourself and not put in file libraries. 3. Hitting Y (or return) continues. New disk filename for file >. Give the filename that you wish the upload to be renamed to. Include drive and path! Privilege bit to download DEF=1. Give the privilege bit necessary to download the file. Which library to add to. Give the library number you wish to add the upload to. Hit "?" if you forget the list and the list of libraries will be output. Can this file be read online y/[N]? This is to differentiate text files from program or archived files. Process next file [Y]/N. Hit Y or RETURN to keep going, N to stop. At the end, the message: No uploads online at this time will appear. All uploads have been moved into libraries, deleted or renamed. 9.4 PRIVILEGE BITS USED 1. The user must have user privilege bit #7 on to download at 300 baud. 2. The user must have privilege bit #8 to download at 1200 or 2400 baud. 3. When downloading, a user is not allowed to go seriously over his or her time limit. The time limit is checked before the transfer is 9-5 2AM BBS Sysop's Manual Files _________________________________________________________________________ started. A transfer is never aborted halfway through. If you wish to allow users to exceed their time limits for a download by any amount (some may not be able to download a large file in the time allotted them), give them privilege bit #9. 4. Privilege bits to download each individual file are stored in the library files. 5. Privilege bit to access the maintenance utility is 64. 6. Privilege bit to access the upload library is 71. More about the upload library in the section on upload files. 7. If an upload is marked for the sysop only ('/' as first character of the description), it will have privilege bit 99 to access it. 9-6 2AM BBS Sysop's Manual BBS Lister _________________________________________________________________________ BBS Lister Chapter 10 This utility will keep statistics on other BBSes and will allow you to compile lists of boards based on several criteria. 10.1 FILE FORMATS Three files are used: bbs disk:bbslist.dat, bbs disk:bbslist.ptr and bbs disk:bbslist.sr1. They are all random access and thus cannot be typed out or edited. Each will be automatically created when the first entry is made for it. 10.2 MAINTENANCE COMMANDS In maintenance, the following commands are available: 1. [D]elete board. You will be asked for the entry number and the board listing will be removed from the database. 2. [E]dit board. You will be asked to re-enter the entire BBS description. 3. [U]ndelete board. You will be asked for the entry number and the board listing will be reinstated to the database. 10.3 PRIVILEGE BITS USED 1. Privilege bit #69 allows a user to add one board to the list. After the board is added, this privilege bit is automatically revoked. 2. Privilege bit #70 allows a user to add any number of boards. This bit is not taken away after adding a board. 3. Privilege bit #61 allows a user to access the maintenance commands for this module. 10-1 2AM BBS Sysop's Manual Jumpdoor _________________________________________________________________________ JumpDoors Chapter 11 This allows you to offer programs that the other users can run. These programs can be anything that fits in memory and can communicate through the serial (modem) port. If the sysop wishes to run programs in local mode only, then serial port support is not required. 11.1 FILE FORMATS Two files are used by JumpDoors: jump disk:Passages.dat and jump disk:Jumper.dat. 11.1.1 JUMP_DISK:PASSAGES.DAT This is the library of available JumpDoors. This file is not required to operate the BBS. It is only necessary if you wish to make jumpdoors available. Each entry in the file takes two lines and has the format: (| = one blank space). Priv | local | full file name and command line Description Or: 0 Comment Priv is the privilege required to use the jumpdoor. Any user with this privilege set will be able to see and use this jumpdoor. Local is 1 if the program can only be used from the console, otherwise it should be 0. File or command name is the full file name and command line. The command line is optional. NOTE: People running multi-user versions of 2AM-BBS may wish to pass the port number to a jumpdoor. To do this, place PORTNUM (please note uppercase) in the command line. When the BBS executes this door, it will translate PORTNUM to the actual port number. .COM and .EXE programs should have a % sign in front of them to identify them as such. Otherwise, a " /c " (single space before and after /c) must be used. These conditions are automatically added if the door is installed via the maintenance section. Description is the title of the jumpdoor output in the [S]how command. Example: 0 0 Jumpdoors Available 0 0 ::::::::::::::::::::::::: 11-1 2AM BBS Sysop's Manual Jumpdoor _________________________________________________________________________ 0 0 99 0 %C:\2AM\UTILS\BSMAINT.EXE C:\BBS\BASES\ N BASEINFO.ALT Compress bases with Alternate Baseinfo and BSMAINT 1 0 /c c:\bbs\jump\chess.bat PORTNUM Play Chess The above example shows three types of entries: comments, exe/com file, and other file types. Note the placement of the percent and the " /c" in the above example. 11.1.2 JUMP_DISK:JUMPER.DAT This is a file that the BBS writes before it sends a user through a door. It contains some information about the user that any jumpdoor program can make use of if it wishes. The file is a text file and contains the following (each item on a separate line): 1. System Name 2. System Owner 3. Username 4. Usernumber (i.e. account number) 5. User's first name (from application) 6. User's last name (from application) 7. User's City, State 8. Time Remaining 9. Communications port (1 or 2). 10. Baud rate ('300','1200','2400') 11. Number of nulls needed (an integer from 0 to 15). 12. Linefeeds? 'TRUE' if user needs linefeeds. Otherwise: 'FALSE'. 13. Upper Case only? 'TRUE' or 'FALSE'. 14. 80 columns? 'TRUE' or 'FALSE'. 15. IBM Graphics? 'TRUE' or 'FALSE' 16. Ansi menus? 'TRUE' if the user can display ANSI, otherwise 'FALSE'. 17. Bell? 'TRUE' or 'FALSE'. Current setting of the system bell. 11.2 THE MAINTENANCE UTILITY Maintenance is accessed by typing MAINT at the jumpdoors prompt. Users need privilege bit #100 to use jumpdoors maint. It will add jumpdoors or comments to jump disk:passages.dat. It will automatically create this file if it does not exist. If you select add [C]omment, you will be prompted for a comment to add to jump disk:passages.dat. If you select add [J]umpdoor, you will be asked the following: 1. Priv bit to use [DEF=1]. Give the privilege bit that a user must have to use this jumpdoor. 11-2 2AM BBS Sysop's Manual Jumpdoor _________________________________________________________________________ 2. Local mode only Y/N. If the jumpdoor cannot communicate through the serial port, select NO here. 3. Full name of program or command. Give the full name of the program to be executed, including drive and path and extension. Also include the command line (ie. c:\myprogs\vroom.com 1 PORTNUM). 4. Is this a COM or EXE file? Answer yes or no. (Is the extension of this program .COM or .EXE?) 5. Description. This is what will be displayed in the [S]how jumpdoors command. 11.3 NOTES ON WRITING JUMPDOORS The jumpdoor must send its output to the screen and serial port to be useful to users who call through the modem port. 2AM-BBS de-installs all its serial input and output routines when it exits to a jumpdoor, so it will not interfere with modem communications. You may install jumpdoors for programs that do not access the serial port, but users who call in cannot use them. Be sure to mark these programs as LOCAL only (as shown above) so users do not get stuck in them. Any program that uses the serial port should run as a jumpdoor. Please ensure, however, that it does NOT: 1. Reset or change anything in the modem. 2. Change the baudrate, parity, etc. You may disconnect the user with these actions. 3. Permanently alter any interrupts or interfere with memory used by the bbs. 2AM-BBS is in memory along with the door and will not work if you write all over it, obviously. Jumpdoors can be written in any language (C, Pascal, Basic, etc, or even assembly language). Libraries of serial input/output procedures are readily available both commercially and in the public domain. If you write a jumpdoor, the 2AM Associates would be most interested in seeing it and, if it does anything reasonable, will be glad to distribute it with the BBS package if you wish. 11.4 PRIVILEGE BITS USED Users must have privilege bit #100 to do jumpdoors maintenance. Privileges to access each individual jumpdoor is kept in the jumpdoors files. 11-3 2AM BBS Sysop's Manual Trivia _________________________________________________________________________ Trivia Chapter 12 This section lets you create sets of trivia questions for your users to answer. Scores must be manually tallied by the sysop or a user with trivia maintenance. 12.1 FILE FORMATS For all sections below, X refers to the physical trivia section number. As in the message bases, the physical numbers may not always be the same as the logical numbers. For instance, the prompt may tell you that you are in Trivia Section 3, but may actually be in any physical section 1 through 20. 1. trivia.lvl - This is a text file that you must create or modify. Each entry in this file consists of two numbers followed by a title. The first number is the privilege bit to access the section or library. If this value is set to 0 then the text is considered a comment field. The second number is the physical file number except in comment lines. In comment lines, the second number is the privilege bit needed to view the comment. This number is used to associate the section with a set of corresponding files. The numbers used in this field must be between 1 and 20. Note: This is the same layout used for the LIBRARY.DAT file in the FILES section. Example: (| = one space) 0 | 1 | 0 | 1 | Trivia Sections Available 0 | 1 | :::::::::::::::::::::::::::::::::::::::::::::::::: 1 | 3 | General Trivia 20 | 8 | Star Trek Trivia 20 | 2 | Computer Trivia 0 | 1 | In the above example, users with privilege bit 1 will see only General Trivia and all the comment lines. Users who also have privilege bit 20 will see all three sections. 2. trivqX.dat - These files are created with the [C] option in maint. It holds between 1 and 10 trivia questions that are currently available in trivia section X. If you are in trivia section X and this file does not exist, when you try to answer the questions, the message: 'No Questions Available in this group' will appear. 3. trivaX.dat - These files contain the questions and answers for the last trivia set if one exists. If you are in trivia section X and this file does not exist, when you ask for last week's answers, the message 'No answers available' will appear. 12-1 2AM BBS Sysop's Manual Trivia _________________________________________________________________________ 4. tscorcX.dat - These files contain the current scores for section X, sorted according to percentage. This file is automatically restarted when you create new questions. If this file does not exist or is empty, the message 'No scores compiled' will appear if you ask for the scores option. 5. tscorlX.dat - These files contain the last set of scores for section X, sorted according to percentage. This file is automatically generated when you create new questions. If this file does not exist or is empty, the message 'No scores compiled' will appear if you ask for the scores option. 6. tansX.dat - These files contain answers to questions for trivia section X that have not been graded yet. When you view and correct these responses, these files will be altered. If this file does not exist, there are no uncorrected trivia answers. 12.2 MAINTENANCE SECTION The "MAINT" command allows you to create question files, correct answers, and allow certain users to retake trivia. A user with privileges to maintain a trivia section will see a "-" before the section name when listing the available sections. With this section, you can have users correct trivia scores. This command may be accessed if you have either master trivia maintenance or trivia maintenance for that physical section. Privileges for each physical section are bits 193 through 212 and are in sequential order for each section. The following commands are available: 1. [C]reate question set - The first thing this does is check to see if a question set already exists. If there is an active question set, you are forced to answer each question. These answers are then used to create the trivax.dat file (described above). You then can input a new set of up to 10 questions. Each question may take up to five lines. If you do not use all five lines, just leave it blank by hitting return. The old and new score files are then created. All user accounts with the appropriate privilege bits are then granted the ability to take these questions and are notified that new questions have been created. 2. [A]nswer correct - If there are answers that have not been corrected, they are output here for grading. If there are no new answers, you will be told so. The trivia questions and users' answers will be displayed one at a time. You have the option of giving full or partial credit for each answer. If you only wish to see the answers, select [D] and the questions will no longer be displayed. Hitting [D] again will re-display the questions. If you see the word 'quit' for any answer, you know the person has aborted the question set. After you correct the questions for a user, you will be prompted as to 12-2 2AM BBS Sysop's Manual Trivia _________________________________________________________________________ whether or not you wish to adjust the score. After this you will be prompted to either save and go on to the next user, save and quit, skip this score and go on to the next user, or skip this score and quit from grading. 3. [M]odify taker. A person is only allowed to answer trivia questions once. If you wish to allow a user to retake a set of trivia questions, use this option. You will be asked for the name of the user. If that person exists, he will then be allowed to re-answer the questions. Note for multi-user systems: If the person is online while you are modifying his account, it will have no effect. 12.3 PRIVILEGE BITS USED Privilege bits to do maintenance in a trivia section range from 193 to 212 for trivia sections 1 to 20 respectively. Master trivia maintenance is privilege bit 67. 12-3 2AM BBS Sysop's Manual Voter _________________________________________________________________________ Voter Chapter 13 In the 2AM-BBS voter, you can create up to 24 topics with between 2 and 10 choices for each topic. 13.1 FILE FORMAT The only file for this section is vote disk:voter.dat. All topics, descriptions and votes are kept here. Use the utility MAKEVOTE.EXE to create or reset this file if necessary. 13.2 MAINTENANCE COMMANDS The maintenance section is accessible to anyone with privilege bit 68 and contains the following commands: 1. [C]reate vote topic allows you to create a topic. All topics are in sequential order according to the date they were created. Users with the correct privilege bits will be notified when a new voting topic is created. When you make up a voting topic, you will be prompted for the following information: 1) Vote priv: Privilege to view and use this topic 2) Topic Title: This is what is displayed with the [S]how topics command. 3) A three-line description of the topic. 4) Between 2 and 10 answers of no more than 35 characters each. 2. [D]elete vote topic. You are prompted for the topic to delete. 13.3 PRIVILEGE BITS USED Privilege bit 68 is the maintenance bit for the voter. Privileges for individual voting topics are determined by the sysop when creating a voting topic. 13-1 2AM BBS Sysop's Manual Chat _________________________________________________________________________ Chat Chapter 14 Chat is used to speak directly to a user. Everything you type will appear on your screen as well as the on the user's screen. 14.1 REQUEST CHAT When a user types "chat" from the main menu, he will be prompted for a reason (in 80 characters or less). The chat page is a series of nine bells. If the sysop does not answer by the last bell, the user is put back at main menu. A "C" will be placed in the status line at the top of the screen that will stay there for the rest of the user's login or until the sysop answers chat. The reason for the chat request remains stored in memory. 14.2 ACCEPT/DENY CHAT The sysop can accept/deny chat by hitting the ESCAPE key. You are prompted for the following: [A]ccept, [D]eny, [C]ustom, [N]o Message. All but the last option outputs a text file (see below). The sysop can initiate chat anywhere but at a single-character input prompt and during a file transfer. If the user has already requested chat, the reason will be displayed when you hit the escape key. After you accept chat, the "C" will disappear from the status line. 14.3 LEAVING CHAT To leave chat, hit the ESCAPE key again. You are prompted for the following: [R]eturn user, [D]ump file. The [D]ump file option will allow you to dump an ASCII text file from your computer to the user's screen. You cannot dump a program to the screen. It is strongly recommended that you only dump ASCII text files, as other files may have unpredictable results on yours or your users' screens. 14.4 CHAT FILES Chat uses the following files: 1. chat disk:chat.req: This file is output when a user requests chat. It is usually on the order of, "Why do you request chat?" 2. chat disk:chat.acc: This file is output if you accept a user's request. 3. chat disk:chat.abt: This file is output if the user hits the return key at the reason prompt. 4. chat disk:chat.ext: This file is output when you leave chat. 14-1 2AM BBS Sysop's Manual Chat _________________________________________________________________________ 5. chat disk:chat.den: This file is output if you do not get back to the user requesting chat. It basically says "could not find sysop". 6. chat disk:chat.dni: This file is output if you select to deny chat. 7. chat disk:chat.2nd: This file is output if the user tries to call chat a second time without the sysop having accepted the first call. A log of chat requests is kept in memory. For more information, see the validator section. 14-2 2AM BBS Sysop's Manual Other Main Menu Options _________________________________________________________________________ Other Main Menu Options... Chapter 15 15.1 CONFIGURE The Configure Utility allows a user to configure the BBS to his computer and terminal program, as well as to his own likings. All of this information is kept in sys disk:userlog.dat, but can only be changed by the user. There are no sysop options here. All the options are covered in the user's manual. 15.2 FEEDBACK This option is available during logoff or if you hit "F" at the main menu. Feedback is a way for users to communicate quickly with the sysop(s). The privilege bit for feedback is 65. For more information on feedback, there is a section on it in the message base chapter. 15.3 SYSTEM INFO This command is invoked by typing "I" at the main menu. System info outputs the text file text disk:sysin.txt. Appending an '80' or '80x' to the filename will output an 80 column or ANSI version of the file if these files exist. This file normally contains: 1. Computer Type 2. Memory and Storage 3. Peripherals on system (printer/modem/etc.) 4. Serial number of 2AM-BBS you are running 5. Any other system specific information. However, you may put any information in it that you wish. 15.4 OFF The file text disk:offnotes.txt is output when a user logs off. Many sysops use the logoff notes to list other BBSes that they are affiliated with. 15.5 DAILY LOG The caller's log for the current day is stored as log disk:mm-dd-yy.log where mm is current month, dd is current day and yy is current year. All the old logs for any past days will be here as well (in log_disk). You may keep as many logs around as you wish. When you need space, delete some old logs. If a user tries to read a deleted log, he will be 15-1 2AM BBS Sysop's Manual Other Main Menu Options _________________________________________________________________________ notified that the log for that day is unavailable. DAYVIEW (see the chapter on utilities) allows the sysop to read and delete log entries. 15.6 LOGIN NOTES If you hit "+" at the main menu, the file text disk:notes.txt will be output. If 'notes80.txt' or 'notes80x.txt' exist, they will be output as appropriate. This is the same file that is displayed when a user logs in. 15.7 USER APPLICATION If a user is online and you would like him to refile his user application, give him privilege bit 77 and type "!" at main menu. (See the chapter on Keyboard Functions for more information on editing users online.) It is used primarily to force people who have filed false information to refile correctly. 15.8 ERROR! If 2AM-BBS encounters an error that it does not know how to deal with, it will give the following message: Error encountered... system shutdown initiated. The system will be back up in 1 minute. Disconnecting.... A message will also be written in the syslog. Check the files you have created for the section where the error occurred. If you are positive your files are in order, and if the error repeats itself, please get in touch with 2AM Associates. We need the EXACT line from the syslog and as much additional information as you can provide. We will either fix the error or point out the error on your side. All fixes of this nature are bug fixes and are free, so please do speak up if something strange crops up. 15-2 2AM BBS Sysop's Manual Main Menu Maintenance _________________________________________________________________________ Main Menu Maintenance Chapter 16 This allows you to manipulate files on the disk and requires user privilege bit #66 to access. Type [MAINT] at the main menu prompt to enter main menu maint. The menu is (menu disk:maint.mnu) and offers the following commands: 1. [A]dd directory mimics the DOS mkdir command. You will be asked for the name of the directory to add. 2. [C]opy file will ask for a file to copy from and a filename to copy to. It works exactly as the DOS copy command with the exception that it will NOT copy groups of files (ie. copy *.dat *.old). 3. [D]irectory will ask for a path, and output a directory in the form that DOS 'dir /w' does. Two things here: put a '\' at the end of the path name or directory will not work. Also, sub directories will not appear. 4. [E]rase a file asks for a filename and then deletes that file. It works exactly as the DOS erase or delete commands do, with the exception that you cannot delete more than one file at a time (ie. erase *.dat). 5. [F]orce login notes goes through the entire userlog and sets everyone's forced login notes read flag to true. Every user will have to read the login notes in their entirety once, after which theis login flag will be turned off. 6. [R]emove directory will ask for a directory name and remove that directory. It works exactly as the DOS rmdir command works. 7. [V]iew text file will ask for a text file name and then will output that file. 8. [X]-fer files allows a remote user to send/receive a file. The user is asked whether the file should be sent to the BBS or received, and then for the filename (give full filename including drive letter and path) on disk. Note: this option does not make an entry in the FILES.LOG. 9. [S]top port (available only in multi-user mode) will notify and then log out the user on the port specified. 16-1 2AM BBS Sysop's Manual Miscellaneous Options _________________________________________________________________________ Miscellaneous Options Chapter 17 17.1 LOGGING IN FROM THE CONSOLE If a user has privilege bit #72, he can access the bbs from the terminal (local mode). This privilege bit prevents anyone from walking up to your terminal and logging in. It is especially useful when the terminal is easily accessed by many people that you don't want logging in locally. To log on in local mode, hit the ESCAPE key. 17.2 TIMEOUTS The system will not just sit forever waiting for a user to do something. So that no one is able to log in and hold the system forever, all prompts are set to timeout after a certain time. Timeouts run as follows: 1. A user has 5 minutes to get a valid username and password entered from the "account number" prompt. 2. If the user is a new user, 35 minutes are allotted for filling out the new user application. 3. Once the user is inside the board, a user's time limit is governed by the time limit set in the user record. New users get 35 minutes online by default. NOTE: This may be altered by creating or editing the Newuser.dat file. 4. If a user is at one of the many single-character prompts, the user has 5 minutes to pick an option before a default option is picked for the user. For example: Leave feedback? (y,[N]) > If a user times out, he will automatically default to the [N] option and continues to the next prompt. 17.3 CARRIER DROPS If the user drops carrier, the bbs will restart. Users lose two minutes each time they drop carrier unless they have the two minute time penalty disable (privilege bit number #73). If a user has call waiting, you may want to give him or her this privilege bit. 17.4 THE SCHEDULER The scheduler allows the sysop to run other programs at prescheduled times. Such programs might be used to run utilities or place your board offhook at certain times of the day. Scheduler data is stored in a the file: sys_disk:schedulX.dat where X is the port number to be run. The file is in the following format. 17-1 2AM BBS Sysop's Manual Miscellaneous Options _________________________________________________________________________ (| equals one space). Hour (0 through 23) | minutes (0 through 59) | 0 or 1 | Command to pass to DOS The third field (0 or 1) is used to signal a priority shutdown. If this is set to 1, the board will shut down at that time no matter what is being done by the user. If it is set to 0, the user's time limit will be truncated but they will not be forced offline at the exact time of the scheduled shutdown. For instance, if a user is leaving feedback, he will be allowed to finish it before the board takes itself offline. Example: 4 30 0 /c C:\BBS\SCHEDULE\BACKUP.BAT 6 25 1 /c C:\BBS\UTIL\BSMAINT.EXE C:\BBS\BASES\ Y BASEINFO.ALT At 4:30 AM, the board will shut down (non-priority) and execute the BACKUP.BAT program. Note the extra space before the /c as well as the /c itself. This is identical to the system used for jumpdoors. At 6:25 AM, the board will shut down (priority) and compress the bases listed in BASEINFO.ALT. The Y indicates that it will compress messages outside the window limit (See utilities chapter for more info). NOTE: All tasks are expected to be in order of execution. In other words, a task to be executed at 3 AM should be before a task to be executed at 4 AM. If a task runs over time into the next task, the second task will not be executed. When the scheduler is active, the main screen will notify you with the message "Shutdown time scheduled". 17.5 A NOTE ABOUT BACKUPS Since it is likely that you will be producing backups via the scheduler, this note is placed here. Many commercial back-up program have an interesting quirk to them. If for some reason you have to restore your system from a backup you made, they usually do not recreate "empty" subdirectories. The sem_disk used by 2AM will normally be empty when there are no users on line. If this directory does not exist, 2AM will NOT run properly in multiuser mode. When restoring from any backup program, make certain that ALL directories are in place since some many not have had anything in them when the backup was made. 17-2 2AM BBS Sysop's Manual Utilities _________________________________________________________________________ Utilities Chapter 18 A utility is a stand-alone program that must be run from outside the BBS. Each of the following utilities must be run from DOS. To run any of the utilities, input the program name at the DOS prompt. 18.1 BASEEDIT.EXE This program is designed to assist the 2AM sysop in creating his/her message base "BASEINFO" file. It provides a simple to use editor that will eliminate the possibility of confusing access bits while creating the file. It also provides the option to view the baseinfo file as it would be output by 2AM-BBS. This output can be the entire file or limited to certain access bits to see exactly what user with a given access bit would see. Please note: Previous version of this program were called EZ-BI. To run the program type: BASEEDIT It is strongly suggested that you take the BBS off-line when using BASE EDIT. The title screen appears. Press ENTER at this screen to continue. BASE EDIT now asks for the path to the BASEINFO file. If you installed 2AM-BBS using the default directories, just press <Enter> here. If the file is in another location, enter the directory. Be sure to include the drive and the ending "\". If BASE EDIT does not find a file named BASEINFO in the directory it will offer to create one. Once the file is found, BASE EDIT loads it and enters the command mode. This mode consists of a three part screen. Part 1 is the biggest section. It occupies the top left half of the screen. In this location, BASE EDIT will display the contents of the BASEINFO file along with line numbers for your reference. Up and down arrows, Page Up and Page Down keys scroll this display. HOME will take you to the first line. END will take you to the last line. These are only for display purposes. You do NOT have to be on a given line to enact a command on it. Part 2 is in the upper right hand corner of the screen. This is the menu of commands that you can call from the command mode. Part 3 is the command window. It is the bottom of the screen. It is here that you enter your commands and BASE EDIT tells you what is going on. 18-1 2AM BBS Sysop's Manual Utilities _________________________________________________________________________ Explanation of Command Mode Options: ------------------------------------ ? - HELP: Summary of all the commands available from BASE EDIT. A - Access.Dat: This option will allow you to edit the information in the access.dat file for a privilege bit. This way when you assign a bit to a base, you can edit the message for that bit from BASE EDIT. D - Delete Line: This option will remove a line from the file. It will also check to see if that base exists. If so, it will offer to delete it for you. If you receive this prompt and answer YES then THAT BASE WILL BE TOTALLY REMOVED FROM YOUR BBS! All messages on it will be deleted. E - Edit a line: BASE EDIT will display the old data for the line number you provide and ask you for new inputs. A valid line number must be given. F - File and Exit: This command will first save you BASEINFO file and exit the BASE EDIT program in a single step. I - Insert line: This will add a line to the file. If the line number you provide is within the file already, BASE EDIT will insert a new line at that point and prompt you for the data input. If you provide a line number of 0, BASE EDIT will append a new line to the end of the file and ask for the appropriate data. M - Move a line to another location: This command will allow you to move one line to another location in the file. The syntax is: line-to- move, where-to-move-it-to. This comes in handy for modifying an existing BASEINFO file. Both the line numbers must be valid lines. Q - Quit WITHOUT save: This option exits BASE EDIT. You will be asked to verify it since the file you are working with is NOT saved automatically. S - Save: This option will save your file. The original file will have its named changed to BASEINFO.OLD for backup purposes. NOTE: If you save a work file more than once in a session, your original file is lost! PLEASE make a back-up of your BASEINFO file before running this program just to be on the safe side. T - Toggle Display: This option changes the primary display mode. It allows you to tell what lines in your baseinfo file are comments and what type of bases they are in a single glance. V - View: This option lets you view how the BASEINFO will appear through 2AM-BBS. There are two types of View commands. View ALL lists the entire file regardless of access bits. This is helpful to get an 18-2 2AM BBS Sysop's Manual Utilities _________________________________________________________________________ overall evaluation of your work. View Privilege will ask you for a list of access bits. The BASEINFO file will then be listed as it would appear to someone with those access bits, including read-only and maintenance markers. If the View command takes up more than one screen - BASE EDIT will pause after it draws the first screen. You can then Scroll the file line by line using the UP and DOWN arrow keys. In the View screen - Press 'Q' to return to the command mode. The View Privilege screen does not take into account the TAG bits. It only reflects the READ, WRITE and MAINT bit settings. 18.2 BSMAINT.EXE This utility is used to compress message bases. This is a complete compression as compared to the partial compression (pointer file compression) that the BBS prompts you for when you delete messages. It removes all deleted messages, and optionally removes messages outside your base window limits. BSMAINT may be run in two different ways. In the first method, you are prompted for the location of BASE_DISK and whether or not you want to delete messages that are outside any window limits you have set. The second method involves using the command line, and was included so that you could run this program via the scheduler (see scheduler in the Miscellaneous chapter). Instead of typing BSMAINT at the DOS prompt, additional information must be entered in the following format: C> BSMAINT BASE_DISK YN ALTERNATE_BASEINFO Where: Base_disk is the name of the directory where your message bases reside (same format as used in drive.dat) YN is either a Y or an N--not both. Y signifies that BSMAINT should delete all messages outside any set base windows. Alternate_baseinfo is not required. If you leave this blank it will assume that you want to compress ALL your bases. An alternate baseinfo is a file which is of the same format as your baseinfo, but without some of your bases. This is included basically to save time during the base compression. You may have bases with no window assigments that are thousands of messages long. If you don't want them to go through the compression process, don't include them in your alternate baseinfo list. It must be in BASE_DISK, and may be any name you desire. Examples of the second method: BSMAINT c:\bbs\bases\ Y baseinfo.alt (total compression of bases listed in baseinfo.alt) BSMAINT d:\bases\ N (compress only delete messages in all bases) 18-3 2AM BBS Sysop's Manual Utilities _________________________________________________________________________ 18.3 DAYVIEW.EXE DAYVIEW allows you to view a user's call-by-call statistics, and also allows you to delete entries in your daily logs. The first thing DAYVIEW will prompt you for is the location of LOG_DISK. If you hit return it will assume that LOG_DISK is the installation default of C:\BBS\LOG\. Next it will ask you for the date of the log to display. After you choose a date, DAYVIEW shows you each log entry for that day, one at a time. You have the option to go forward or backward one user at a time, delete a specific entry, or quit the date. The entries include the user's name, length of call, number of posts made, number of e-mail messages sent, whether or not the user is new, baud rate, port number, and uploads/downloads made. After reading all the entries for a day, DAYVIEW will prompt you for another date to view. Hitting return will abort the utility. NOTE: NEVER delete entries in the current day's log when someone is logged into the BBS! This includes jumping to DOS from the BBS. You will cause errors to occur if you do this! 18.4 DBMAINT.EXE This utility is used to compress the help and BBSlister files. It removes deleted entries, and restructures these files to try to increase their access speeds. DBMAINT may be run in two different ways. The first method requires you to run the program and supply the name of the files you wish compressed. The second involves using the command line, and was included so that you could run this program via the scheduler. (See scheduler in the Miscellaneous chapter). Instead of typing DBMAINT at the DOS prompt, additional information must be entered in the following format: C> DBMAINT INFO_DISK\FILENAME Where: info_disk\filename is the name of the directory and the type of files you will compress. Examples DBMAINT c:\bbs\bbslist\bbslist (compression of BBSlister files) DBMAINT c:\bbs\help\help (compression of help files) 18-4 2AM BBS Sysop's Manual Utilities _________________________________________________________________________ Note that the help files should only be compressed if you have been adding and removing help topics via the HLPMAINT utility. 18.5 DIRSORT.EXE DirSort sorts the DIRx.DAT files used in the files section of 2AM-BBS. This sort is numeric by access bit then alphabetically by file name or numeric by date. Comments will remain with the files they relate to. To call DIRSORT from a DOS prompt, type: DIRSORT If you are running in more than one port on the BBS and it is possible that one of the other ports is in use, type: DIRSORT M This will activate all the necessary record locking for a multiuser BBS. The first screen appears and asks for the path name for the LIBRARY.DAT file that 2AM-BBS uses. If you installed 2AM by using the installation program that came with it and did not change any of the directories, just hit return. To quit here, enter a Q. To specify any other directory, type it here. If you enabled the Multiuser mode a special screen will now appear here. It will ask for the location of the SEM_DISK. You must enter the path name, for example: c:\bbs\sem\ You must include the ending "\". Dirsort can not check to make sure you entered the correct path so please make sure you do it correctly!! DirSort will then ask if you want to see all the file loads as they occur. You can answer Yes if you need to view the files as they are loaded so you can determine the way comments are contained in the file. If you answer no - the file load will be faster. The LIBRARY.DAT file will be displayed to you as the MAIN MENU. From this menu you will be asked to select the DIRx file to be sorted. Selecting a Q will quit this program. Selecting an A will cause DirSort to sort ALL the DIR files using one set of sort parameters. Once a directory is selected, DirSort will ask for the sort parameter. It can sort by FILENAME or by DATE. Enter an F or D for your selection. To obtain an alphabetical listing by date - enter option B. This will sort the file first by Filename then Date. 18-5 2AM BBS Sysop's Manual Utilities _________________________________________________________________________ Once the file has been loaded, DirSort will ask how comments are placed in this file. The two choices are: [A]bove the file, or [B]elow the file they refer to. DirSort does two sorts. The first sort is a numeric sort by access bit (1 first, 252 last). Once this is completed, DirSort then sorts by filename (or date) within the access bit. The original file is renamed to have a '.OLD' extension. DirSort also creates a temporary file named TEMPSORT.OUT in the same directory as the DIRx.DAT files. If a file already exists by that name, it is erased. 18.6 DRIVER.EXE This utility allows you to change various system configurations that are stored in the DRIVEx.DAT file. It is completely menu driven, and may only be run from DOS. DRIVER will prompt you for the path and name of your DRIVEx.DAT file. If you hit return, it assumes that you mean DRIVE.DAT in the current directory. In a single user version, the filename should be something like c:\bbs\drive.dat. In the multiuser version, you must indicate which drive.dat you wish to edit. Example, c:\bbs\drive1.dat.). NOTE: Multiuser systems will have to run this program on each of the DRIVEx.DAT files in order to effect all nodes. If the file you supplied does not exist, it will question you as to whether or not you wish to create a new file or quit. After DRIVER has loaded or created the necessary information, it places windows on the screen. To select an item the use arrow keys and hit RETURN when the item you wish to change is in reverse mode. 18.7 HLPMAINT.EXE HLPMAINT allows the sysop to add or remove help topics from the help library. This is generally useful if you wish to remove help topics on sections of the BBS that you do not plan to use, or if you want to add help topics that are more specific to your bbs. When you run HLPMAINT, it will prompt you to enter the current help directory. Hitting return at this prompt will go to the system default directory (c:\bbs\help.) Next it will prompt you to Add or Remove help files. Enter either an A or an R. Q will quit the utility. If you choose to add a help topic, it will prompt you for three items: help topic name, privilege to read this topic, and the name of the help file you will use. All help files must be kept in HELP_DISK. If you remove a help file, it will prompt you for the 18-6 2AM BBS Sysop's Manual Utilities _________________________________________________________________________ name of the topic to be removed. NOTE: When you remove a topic it does NOT compress the help system files, or erase the help file used by that name. To compress the help files, see DBMAINT. 18.8 LOOKER.EXE LOOKER creates/recreates the lookup tables that are used by the BBS to locate users by their names/handles. It can be run by typing LOOKER from the DOS prompt. Before running LOOKER, you must delete all files from the LOOK_DISK. After you run LOOKER it will ask you for both the locations of SYS_DISK and LOOK_DISK. After this information is supplied, LOOKER will proceed to rebuild the tables based upon your userlog. If you cannot send e-mail to a user, or cannot edit them by name, your lookup tables may be damaged and you should run this program. 18.9 MAKEVOTE.EXE MAKEVOTE is used to create a blank voter file. It should only be used if VOTER.DAT does not exist, or if you wish to delete all your current voting topics. 18-7 2AM BBS Sysop's Manual Utilities _________________________________________________________________________ Appendix 1-8 2AM BBS Sysop's Manual Priv Bits _________________________________________________________________________ Privilege Bits Appendix 1 This section lists all the privalige bits used by 2AM-BBS. If any bits are not listed here, they are free for you to assign as you see fit. 1.1 BY NUMBER Bit Purpose 2 Use Email 7 Download at 300 Baud 8 Download at 1200/2400 Baud 9 Go over time limit on downloads 60 May skip messages in Email 61 MAINT commands for BBS Lister 62 MAINT commands for Email 63 File messages in Email ([D]) 64 MAINT section for Files 65 Feedback Access 66 MAINT section for Main Menu 67 MAINT section for Trivia Master 68 MAINT commands for Voter 69 May add one BBS to BBS Lister 70 Permanent BBS Lister Access 71 Access Uploads in Files 72 Local Mode Access 73 Two Minute Time Penalty Disable 75 Special Login Message #1 76 Special Login Message #2 77 Refile User Application/Special Login Message #3 78 60 Line editor 79 100 Line editor 80 ANSI in editor 81 /LOAD in editor 82 /SVE in editor 83 May copy messages 85 May create bases 86 MAINT: Master bases 87 /NAME in editor 88 RESERVED for future expansion 89 Access Validator 90 May View user applications in validator 91 May View user passwords in validator 92 RESERVED for future validator use 93 May Edit users in validator 94 May Delete users in validator 95 Protect User from deletion 96-98 RESERVED for future expansion 99 System Access 100 MAINT: Jumpdoors Appendix 1-1 2AM BBS Sysop's Manual Priv Bits _________________________________________________________________________ 193 TRIVIA Section 1 194 TRIVIA Section 2 195 TRIVIA Section 3 ... ..... 211 TRIVIA Section 19 212 TRIVIA Section 20 213-255 "INVISIBLE" bits. Used for base selection by user. 1.2 BY USE BBS Lister: 61 MAINT commands for BBS Lister 69 May add one BBS to BBS Lister 70 Permanent BBS Lister Access Email: 2 Use Email 60 May skip messages in Email 62 MAINT commands in Email 63 File messages in Email during Read Incomming ([D]) Editor: 78 60 Line editor 79 100 Line editor 80 ANSI in editor 81 /LOAD in editor 82 /SVE in editor 87 /NAME in editor Files: 7 Download at 300 Baud 8 Download at 1200/2400 Baud 9 Go over time limit on downloads 64 MAINT section for Files 71 Access Uploads in Files Jumpdoors: 100 MAINT section for Jumpdoors Message Bases: 83 May copy messages 85 May create bases 86 MAINT: Master bases 213-255 "INVISIBLE". May be used for base selection bits. Appendix 1-2 2AM BBS Sysop's Manual Priv Bits _________________________________________________________________________ Maint: 61 MAINT commands in BBS Lister 62 MAINT commands in Email 64 MAINT section for Files 66 MAINT section for Main Menu 67 MAINT section for Trivia Master 68 MAINT commands in Voter 86 MAINT section for Master bases 100 MAINT section for Jumpdoors Trivia: 67 MAINT: Trivia Master 193 TRIVIA Section 1 194 TRIVIA Section 2 195 TRIVIA Section 3 ... ..... 211 TRIVIA Section 19 212 TRIVIA Section 20 Validator: 89 Access Validator 90 May View user applications in validator 91 May View user passwords in validator 92 RESERVED for future validator use 93 May Edit users in validator 94 May Delete users in validator Voter: 68 MAINT section for Voter Miscel. 65 Feedback Access 66 MAINT section for Main Menu 72 Local Mode Access 73 Two Minute Time Penalty Disable 75 Special Login Message #1 76 Special Login Message #2 77 Refile User Application/Special Login Message #3 95 Protect User from Deletion 99 System Access Reserved: 88 RESERVED for future expansion 92 RESERVED for future validator use 96-98 RESERVED for future expansion Appendix 1-3 2AM BBS Sysop's Manual 2AM File Map _________________________________________________________________________ 2AM File Map Appendix 2 Key + = text files $ = sysop created files % = supplied with system X, XX, YY = number Base_disk $% baseXX.dat Data file for message base $% baseXX.ptr Pointer file for message base +$% baseinfo. Master Base file % newmsg.dat New Message counter. Do NOT tamper with this. +$ [alternate baseinfo] Optional baseinfo for BSMAINT BBS_disk bbslist.dat BBSlist data file bbslist.ptr BBSlist pointer file bbslist.sr1 BBSlist sort file Chat_disk + % chat.2nd Chat message for second request + % chat.abt Chat message for aborting + % chat.acc Chat message for accepting + % chat.den Chat message for timeout + % chat.dni Chat message for denial + % chat.ext Chat message for exit + % chat.req Chat message for initial request Dload_disk + % dirX.dat Section library +$% library.dat Master files library +$ protocol.dat Download external protocol list Help_disk + % *.hlp Text for help system % help.dat Data file for help system % help.ptr Pointer file for help system % help.sr1 Sort file for help system Appendix 2-1 2AM BBS Sysop's Manual 2AM File Map _________________________________________________________________________ Jump_disk + jumperX.dat User information for jumpdoor +$ passages.dat Jumpdoor directory Log_disk XX-XX-XX.log Daily log for date XX-XX-XX Look_disk % lookXX User lookup tables Mail_disk minXX.dat Incoming mail data minXX.ptr Incoming mail pointer moutXX. Outgoing mail flag file Menu_disk + % base[80x].mnu Message base menu + % bbsls[80x].mnu BBSList menu + % bmain[80x].mnu Base Maint menu + % conf[80x].mnu Configure menu + % door[80x].mnu Jumpdoors menu + % edcom[80x].mnu Editor menu + % email[80x].mnu Email menu + % files[80x].mnu Files menu + % main[80x].mnu Main menu + % maint[80x].mnu Main menu Maint menu + % triv[80x].mnu Trivia menu + % valid[80x].mnu Validator menu + % voter[80x].mnu Voter menu Sem_disk + *.sem Temporary sem file (multiuser only) + mboxX. Temporary mailbox file (multiuser only) us#XX. User lock, flags user online (erase files if present & no one logged in) Appendix 2-2 2AM BBS Sysop's Manual 2AM File Map _________________________________________________________________________ Sys_disk +$ *.def Validator definition files + % *.log System logs for validator +$ *.swe Sweeper output files % bbs.* 2AM-BBS executable program +$% drive[x].dat System configuration file % last Special format last caller file +$ newuser.dat New user configuration file +$ pon.cnf Existance causes logging to printer +$ rejects.dat Handles not allowed on system +$ schedul[x].dat Scheduler time schedule % userapp.dat User Application file, contains personal info % userlog.dat Userlog, contains all account information Text_disk + % append.txt Application closing comments + % appq1.txt Applications questions file 1 + % appq2.txt " " 2 + % appq3.txt " " 3 + % notes[80x].txt Login notes + % nuser.txt New user notes + % offnotes.txt Logout notes + % privacy.txt User information policy + % splogin1.txt Special Login message 1 + % splogin2.txt " " 2 + % splogin3.txt " " 3, refile application + % start.txt System introduction message + % sysin[80x].txt System information + uplod[80x].txt Notice for uploads + % userapp.txt Userapplication introduction Trivia_disk + tansX.dat Trivia last Q&A file trivaX.dat Trivia answers +$% trivia.lvl Master trivia directory + % trivqX.dat Trivia questions tscorcX.dat Trivia current scores tscorlX.dat Trivia last scores Appendix 2-3 2AM BBS Sysop's Manual 2AM File Map _________________________________________________________________________ Uload_disk + lastu.dat Last upload number +$ protocol.dat Upload external protocol list up-XX.YY Uploaded programs Vote_disk $ voter.dat Voter data file Appendix 2-4 2AM BBS Sysop's Manual Multiuser Setup and Commands _________________________________________________________________________ Multiuser Setup and Commands Appendix 3 3.1 CHANGES TO DRIVE.DAT When using the multiuser configuration, the name of DRIVE.DAT changes to either DRIVE1.DAT or DRIVE2.DAT depending on the port you are using. You are responsible for creating these files. NOTE: Make sure that you set the value for the COM port to two different values in these files. 3.2 CHANGES TO BBS PARAMETERS The first parameter when running the bbs is now controlling the port number of the bbs that will run. Example: C> BBS 1 Will execute the BBS, using DRIVE1.DAT, and run port 1. The second parameter controls whether or not the bell can be heard. Example: C> BBS 0 1 Will run the BBS in single user mode with the bells off. Never pass more than two parameters to the BBS. The third parameter is reserved for the system. Do NOT use it. 3.3 SEM DISK AND EXECUTION Always erase any files from sem disk before running the BBS. NOTE: Be sure that none of these files are in use by the other port if a user is online. Each file contains the port number of who is using it. Never run only one line in the multiuser setting unless the other line has executed at least once. There are memory locks, and each port is responsible for clearing those locks when it starts up. If you run one line, the system may end up waiting for the other line to unlock that memory. There is a single user mode, use it if you are running one line. 3.4 ADDITIONAL COMMANDS IN MULTIUSER MODE The WHO command is available from the main menu ([W]) when in multiuser mode. This will display the other users and what they are doing. In main menu MAINT there is a command [S] that can be used to STOP the other line. This will toss the user on the other line off the board at Appendix 3-1 2AM BBS Sysop's Manual Multiuser Setup and Commands _________________________________________________________________________ the first chance it gets. As a safety feature of this option, you must supply the port number with the S command. Example: MAINT > S2 Will through the user off port two. 3.5 EMAIL NOTIFICATION If a user is online when mail is sent to them, they will receive a message to inform them that they have new mail from user ABCD, where ABCD is the user who sent the mail. Appendix 3-2 2AM BBS Sysop's Manual Bit Encoded Responses _________________________________________________________________________ Bit Encoded Responses Appendix 4 This chapter will cover the bit encoding method used for the three optional questions asked a user during his/her application. When you make up a question for the user application, you can have up to 8 possible answers for that question. A user can potentially select more than one answer from the list. Now, a user could select just one choice (example, choice 8), or a user could select many choices (say, 1,3,4). The bit-encoded method allows you to store all the choices in one integer (actually a byte). Each user application has room for 3 bit encoded response questions. Ask these questions by creating the files text disk:appq1.txt, text disk:appq2.txt, and text disk:appq3.txt respectively. If any of these files do not exist, the question corresponding to that file will be skipped, and the user response for that question will be 0. The following table describes how to convert the data (stored in encoded form) back to the responses the user gave. Appendix 4-1 2AM BBS Sysop's Manual Bit Encoded Responses _________________________________________________________________________ ---------------------------------------------------------- code choices code choices code choices ---------------------------------------------------------- 0 none 43 1 2 4 6 86 2 3 5 7 1 1 44 3 4 6 87 1 2 3 5 7 2 2 45 1 3 4 6 88 4 5 7 3 1 2 46 2 3 4 6 89 1 4 5 7 4 3 47 1 2 3 4 6 90 2 4 5 7 5 1 3 48 5 6 91 1 2 4 5 7 6 2 3 49 1 5 6 92 3 4 5 7 7 1 2 3 50 2 5 6 93 1 3 4 5 7 8 4 51 1 2 5 6 94 2 3 4 5 7 9 1 4 52 3 5 6 95 1 2 3 4 5 7 10 2 4 53 1 3 5 6 96 6 7 11 1 2 4 54 2 3 5 6 97 1 6 7 12 3 4 55 1 2 3 5 6 98 2 6 7 13 1 3 4 56 4 5 6 99 1 2 6 7 14 2 3 4 57 1 4 5 6 100 3 6 7 15 1 2 3 4 58 2 4 5 6 101 1 3 6 7 16 5 59 1 2 4 5 6 102 2 3 6 7 17 1 5 60 3 4 5 6 103 1 2 3 6 7 18 2 5 61 1 3 4 5 6 104 4 6 7 19 1 2 5 62 2 3 4 5 6 105 1 4 6 7 20 3 5 63 1 2 3 4 5 6 106 2 4 6 7 21 1 3 5 64 7 107 1 2 4 6 7 22 2 3 5 65 1 7 108 3 4 6 7 23 1 2 3 5 66 2 7 109 1 3 4 6 7 24 4 5 67 1 2 7 110 2 3 4 6 7 25 1 4 5 68 3 7 111 1 2 3 4 6 7 26 2 4 5 69 1 3 7 112 5 6 7 27 1 2 4 5 70 2 3 7 113 1 5 6 7 28 3 4 5 71 1 2 3 7 114 2 5 6 7 29 1 3 4 5 72 4 7 115 1 2 5 6 7 30 2 3 4 5 73 1 4 7 116 3 5 6 7 31 1 2 3 4 5 74 2 4 7 117 1 3 5 6 7 32 6 75 1 2 4 7 118 2 3 5 6 7 33 1 6 76 3 4 7 119 1 2 3 5 6 7 34 2 6 77 1 3 4 7 120 4 5 6 7 35 1 2 6 78 2 3 4 7 121 1 4 5 6 7 36 3 6 79 1 2 3 4 7 122 2 4 5 6 7 37 1 3 6 80 5 7 123 1 2 4 5 6 7 38 2 3 6 81 1 5 7 124 3 4 5 6 7 39 1 2 3 6 82 2 5 7 125 1 3 4 5 6 7 40 4 6 83 1 2 5 7 126 2 3 4 5 6 7 41 1 4 6 84 3 5 7 127 1 2 3 4 5 6 7 42 2 4 6 85 1 3 5 7 128 8 If the code is over 128, subtract 128 from the code and look up the result. The choices will be 8 (from the 128 subtracted off) plus the choices you just looked up. Appendix 4-2 2AM BBS Sysop's Manual DRIVE.DAT _________________________________________________________________________ The Drive.Dat File Appendix 5 Here is a list of all the items in sys disk:driveX.dat. Each item should be on a separate line. 5.1 SYSTEM SPECIFICS [Lines 1-5] 1. System Name (up to 80 characters) 2. Maximum Baudrate system can handle (300, 1200, 2400 - one number) 3. Upload/download ratio file credits on a per K basis. 4. Opening time for the Files section 5 Closing time for the files section. If this line is identical to line 4, the Files section is open 24 hours a day. 5.2 DRIVE PATHS [6-21] 6. sys_disk 7. base_disk 8. help_disk 9. mail_disk 10. trivia_disk 11. dload_disk 12. bbs_disk 13. log_disk 14. menu_disk 15. text_disk 16. vote_disk 17. uload_disk 18. chat_disk 19. sem_disk 20. look_disk 21. jump_disk 5.3 PROMPTS [22 - 34] When installation is done, default prompts are written in. Any may be changed by editing this file. 22. Prompt extension (EX: '>') 23. Prompt for BBSLister 24. Prompt for Email 25. Prompt for FILES 26. Prompt for Help 27. Prompt for Config 28. Prompt for Main 29. Prompt for Maintenance (from Main Menu) Appendix 5-1 2AM BBS Sysop's Manual DRIVE.DAT _________________________________________________________________________ 30. Prompt for Message Bases 31. Prompt for Trivia 32. Prompt for Validator 33. Prompt for Voter 34. Prompt for JumpDoors 5.4 HEADERS AND MESSAGES [35 - 45] Various section headers and messages are on these lines. If you do not like a phrase that the board outputs somewhere, go to this file and see if you can find that phrase. If you can, edit this file and change the phrase. Not all phrases are here; just the ones that got changed most from our experiences. If you find a phrase that you don't like, contact us and in a future version, we may make it a line here. NOTE: 2AM Associates will resist changing error or informational messages to avoid ambiguity in user or sysop documentation. 5.5 MODEM AND PORT INFORMATION [lines 46 - 51] 46. DOS COM port for this line. (0 = Local mode only, 1=COM1, 2=COM2) 47. Initialization string for the modem. ATE0M0V1X1F1S2=128S7=10S10=20S0=1 Please note that this is ALL UPPER CASE. Owners may wish to set X0 for 300 only, X1 for 1200 baud and X4 for 2400 baud modems. 48. Pause between characters during initalization. 50 seems to work fine. You may wish to increase it if the modem does not respond correctly. 49. Pause between initization commands. We use 250, but if the modem does not respond correctly, increase it. 50. Priv needed to log into this port. Can be 0, which allows everyone. 51. The name of this port of the BBS. (blank line on a single user system) Appendix 5-2 2AM BBS Sysop's Manual ANSI Codes _________________________________________________________________________ Appendix 6 ANSI Color Commands 2AM-BBS supports ANSI color in many places. Prompts, text file, menus, email messages and message base posts may all contain ANSI color commands. Below is a list of color commands recognized as standard ANSI commands. All ANSI color commands begin with a ESCAPE character, a "[" and end with a LOWER CASE "m". ( ^ = ESCAPE character) Code Meaning ^[0m Reset Attributes. Return to normal colors. ^[1m Foreground color will be bold until reset. ^[5m Foreground color will blink until reset. ^[30m Black Foreground ^[31m Red Foreground ^[32m Green Foreground ^[33m Yellow Foreground ^[34m Blue Foreground ^[35m Magenta Foreground ^[36m Cyan Foreground ^[37m White Foreground ^[40m Black Background ^[41m Red Background ^[42m Green Background ^[43m Yellow Background ^[44m Blue Background ^[45m Magenta Background ^[46m Cyan Background ^[47m White Background Notes: 1) Yellow will appear to be BROWN unless BOLD is on. 2) Due to limitations of Turbo Pascal, some colors may not appear to be correct on the local terminal (SYSOP'S screen). Be assured that they appear correct to the user. 3) It may be helpful to point out that Background colors are the same as foreground colors plus 10. 4) ^[0m and ^[m are identical to each other. (The 0 is optional). 5) Commands may be nested with semi-colons (;). For example: ^[33;1;44m will turn on yellow foreground, make it bold and make the background blue. Appendix 6-1 2AM BBS Sysop's Manual Trouble Shooting _________________________________________________________________________ Appendix 7 Trouble Shooting If you have a problem with 2AM-BBS, please read through this appendix. It contains several of the more common problems we receive from other sysops. Problem: The "Waiting for Connect" message does not come up when I start my BBS. Solution: There are a few problems that could cause this. They are all related to your modem. 1. If you are using an external modem, make sure it is turned on and plugged in. 2. Check DRIVEx.DAT and make sure that you have it configured for the correct COM port (1 or 2), and the correct baud rate (300, 1200, or 2400). 3. Make sure that your modem supports all the commands in your initialization string. 4. Adjust the Modem EOLN Pause and Modem Init Nulls in DRIVEx.DAT to a number about 20-40 higher. This slows down the initialization string. Restart the board, and see if this works. 5. If all else fails test it with a terminal program and see if modem works. Problem: My modem does not detect a carrier drop. Solution: Some modems require an extra command in the modem initialization string, or a specific dip switch setting. Consult your modem manual and alter the initialization string in DRIVEx.DAT accordingly. (You will want the CD line to follow the line, and not always be "high".) Problem: My modem does not hangup on people when they log out. Solution: Some modems require an extra command in the modem initialization string, or a specific dip switch setting. Consult your modem manual and alter the initialization string in DRIVEx.DAT accordingly. (You will want the DTR line to follow the line, and not always be "high".) Appendix 7-1 2AM BBS Sysop's Manual Trouble Shooting _________________________________________________________________________ Problem: I get an ERROR 16 "Owner Generated Error in File Format". Solution: Check the data files in the section in which this occurred. Generally this will happen if there is blank line at the end of one of the data files, or a line in the file that does not follow the format we describe in this manual. If you recently changed any system files, you should go back and look at them. Problem: The system crashes everytime I try to log into the BBS in multiuser mode. Solution: Check that SEM_DISK exists. Problem: My userlog is a 2 meg file! Solution: This shouldn't happen unless you are using a multitasker and a program that does direct disk writing, or you are using a version of DOS older than version 2.1. Being that not everyone is so careful to watch these things, we have a utility that will help you restore the file to its former glory, or as close to it as possible. It will be made available on request. Problem: My message counters are all wrong. Solution: This can happen when you delete the file NEWMSG.DAT in BASE_DISK. It will attempt to fix itself, by resetting itself to the next callers new post number. If this happens to be a new user or someone who hasn't called in a while, you might want to delete the file again and post a message from your account. Problem: There is a username in the [U]serlog list that I cannot send mail to or edit by name in the validator. Appendix 7-2 2AM BBS Sysop's Manual Trouble Shooting _________________________________________________________________________ Solution: You should erase the files in LOOK_DISK and run the utility LOOKER. This happens when you either delete a file in LOOK_DISK or change someones handle and answer no to the "Change Lookup Tables?" question in the validator. Problem: My users complain that they are recieving "garbage" characters on their screen. Solution: 1. They are not calling at 8-N-1. 2. They are calling at the wrong baud rate. 3. Their terminal is configured for a graphics mode they don't support. 4. They are getting "Line Noise". If this happens to most/all of your users, you might want to have your phone line checked. This is not a software problem. Problem: I get DOS ERROR 8 whenever I try to Jump to Dos, Use a Jumpdoor, Use the Scheduler, or Use an External Protocol. Solution: You are out of memory. Either remove some memory resident programs or add more memory to your computer. Problem: The BBS is in multiuser mode and and appears to be frozen, but it checks the disk every now and then. Solution: From the other port, erase all .sem files from SEM_DISK. Problem: I am in multiuser mode, and the output on my screen seems jerky. Solution: This is a side effect of multitasking. The user shouldn't see any pauses in the output, but you will. The faster your computer is, the less likely this is to be noticed. Appendix 7-3 2AM BBS Sysop's Manual Index _________________________________________________________________________ Index A Access................................................................4-3 Access List...........................................................7-6 ACCESS.DAT......................................................4-1, 18-2 Account 0.............................................................4-2 ANSI...............................................11-2, 15-1, Appendix 6 ANSI Menus............................................................3-1 ASCII.................................................................7-2 250.................................................................3-2 B BASEEDIT.EXE.........................................................18-1 BaseInfo..............................................................7-1 Bit Encoding.....................................................4-2, 5-1 Board Id........................................................5-1, 15-1 BSMAINT.EXE..........................................................18-3 C Caller Number.........................................................4-2 Carrier Drop.........................................................17-1 Carrier Drops........................................................17-1 Chat.................................................................13-1 Files..............................................................14-1 Chat Bell............................................................14-1 Compaction In BBSLister.......................................................18-4 In Help Files......................................................18-4 In Message Bases....................................................7-6 D Daily Time Limit......................................................5-2 DAYVIEW.EXE..........................................................18-4 DBMAINT.EXE..........................................................18-4 DEF Files........................................................4-4, 5-3 Definition File.........................................................2 DIRSORT.EXE..........................................................18-5 DOS Copy...............................................................16-1 Delete.............................................................16-1 Dir................................................................16-1 Erase..............................................................16-1 MkDir..............................................................16-1 RmDir..............................................................16-1 Drive.Dat.................................9-1, Appendix 3-1, Appendix 5-1 Index-1 2AM BBS Sysop's Manual Index _________________________________________________________________________ DRIVER.EXE...........................................................18-6 E Editor Commands /LOAD...............................................................6-1 /NAME...............................................................6-1 /SVE................................................................6-1 Email.................................................................7-1 Message Counter.....................................................4-2 Email Limit...........................................................4-6 Error................................................................15-2 ESCAPE key................................................2-1, 14-1, 17-1 F Feedback........................................................7-3, 15-1 File Map.....................................................Appendix 2-1 Files BaseInfo............................................................7-1 BBSLIST.DAT........................................................10-1 BBSLIST.PTR........................................................10-1 BBSLIST.SR1........................................................10-1 DirX.dat............................................................9-2 Drive.dat...............................9-1, Appendix 3-1, Appendix 5-1 In Chat............................................................14-1 In Files............................................................9-1 In Message Bases....................................................7-1 In Validator........................................................4-1 Jumper.dat.........................................................11-1 Lastu.dat...........................................................9-3 Library.dat.........................................................9-1 Main80.mnu..........................................................3-1 Main80x.mnu.........................................................3-1 Menus...............................................................3-1 NEWUSER.DAT...................................................5-3, 17-1 Passages.dat.......................................................11-1 Pon.cnf.............................................................2-1 Protocol.dat........................................................9-3 Up-XX.YY............................................................9-3 uplod.txt...........................................................9-3 x.DEF...............................................................5-3 Files Section.........................................................8-1 Rejects.dat...........................................................5-4 H HLPMAINT.EXE.........................................................18-6 L Index-2 2AM BBS Sysop's Manual Index _________________________________________________________________________ Local Mode...........................................................17-1 Log Fails.............................................................4-2 Logical Base..........................................................7-1 Login Messages........................................................5-4 LOOKER.EXE...........................................................18-7 M Main Menu Maint......................................................15-1 Maint...........................................................7-5, 15-1 In BBS Lister......................................................10-1 In Files Section....................................................9-4 In Message Bases....................................................7-2 In Trivia..........................................................12-2 In Voter...........................................................13-1 MAKEVOTE.EXE.........................................................18-7 Menu Files............................................................3-1 Modem........................................................Appendix 5-2 Multiuser....................................................Appendix 3-1 N NEWUSER.DAT................................................4-3, 5-3, 17-1 P Password..............................................................4-2 Pattern matching......................................................4-5 Physical Base.........................................................7-1 Priv Bits Changing............................................................4-4 Description.........................................................4-1 For Local Login...............................................2-1, 17-1 In BBS Lister......................................................10-1 In Editor...........................................................6-1 In Files Section....................................................9-5 In Message Bases....................................................7-6 In Trivia..........................................................12-3 In Validator........................................................4-8 In Voter...........................................................13-1 List................................................................4-3 User Applix........................................................15-2 Privacy Mode..........................................................7-2 R Ranges................................................................4-4 Rejects.dat...........................................................5-4 S Index-3 2AM BBS Sysop's Manual Index _________________________________________________________________________ Scheduler................................................17-1, 18-3, 18-4 Sweeper...............................................................4-5 SYS.LOG...............................................................4-4 Syslog..........................................................4-2, 15-2 T Text Files............................................................3-2 Time Penalties.......................................................17-1 Timeout..............................................................17-1 Timeouts.............................................................17-1 Trivia...............................................................12-1 Trouble Shooting.............................................Appendix 7-1 U User App..............................................................4-2 Userlog...............................................................4-1 Utilities Utilities............................................................17-1 BSMAINT.............................................................7-2 DAYVIEW............................................................15-2 Driver..............................................................9-1 V Validator.............................................................3-1 Files...............................................................4-1 Voter................................................................13-1 Index-4