H H BBBBBBBBBB BBBBBBBBBB SSSSSSSSS H H B B B B S H H B B B B S HHHHHHHHHH BBBBBBBBB BBBBBBBBB SSSSSSSSS H H B B B B S H H B B B B S H H BBBBBBBBBB BBBBBBBBBB SSSSSSSSS REMOTE BULLETIN BOARD SYSTEM Help Guide prepared by Irv Hoff PRACSA Sysop RCPM (415) 948-2513 300-1200-2400-9600 baud 17 April 1988 Page 1 HBBS, based on PBBS by Irv Hoff, W6FFC 17 April 1988 ------------- INTRODUCTION: ------------ HBBS is a CP/M Bulletin Board System. It requires a Z80 processor and a computer with a time clock. It uses BYE5 to answer the telephone and match the computer to the incoming caller's modem speed. If users are allowed into the operating system to upload/download files, another program such as ZCMD or ZCPR3 is needed to provide flow path control, to allow the Sysop full access via the 'wheel byte' and to provide prompts showing the current user area. HBBS works well with KMD.COM if allow- ing CP/M file transfers. It permits separate areas for CP/M and MS-DOS uploads, if desired. HBBS is likely the most automatic BBS in existance. It is also one if the most friendly, requiring almost no knowledge of how to use the system. There are virtually no hidden or secret commands, "what you see is what you get". It automatically erases messages which have been read (after 'xx' days, set currently to 30) and can automatically change new users to a higher level, on a daily basis, until they reach normal user status. HISTORY: -------- My first involvement in BBS systems was in 1964. Radio was used, rather than telephone lines. Keith Petersen, Vic Poor and myself were among those initially involved. In 1968 we started a BBS on a Hewlett- Packard 2000A, using normal phone lines at 300 baud. It was written by Harry Pyle who later wrote the instruction set for 8008 which preceeded the 8080 as the first micropcomputer chip. About 1978, Ward Christensen developed the CBBS bulletin board system, in assembly level code. Also about that time he wrote a program he called MODEM, so he could transmit programs to Randy Suess across Chicago. This became an immediate hit with computer hackers as it was "the only game in town". This program later blossomed into such clones as MODEM7 and SMODEM7, which in turn led the way to MDM7 and later to IMP and MEX. About 1979, Keith modified Ward's MODEM program and called his new program XMODEM, for operation by a remote user. The world's initial RCPM system became available in Royal Oak, Michigan. Somehwere about 1980, RBBS was written in MBASIC. Unlike Ward's program which was being sold commercially, RBBS was free. All sorts of clones were developed, a majority of which either fell by the wayside or the original authors are no longer supporting. Most were offered free, some were commercial with the user obtaining them directly from the author. Shareware was not in use in the early and mid-80's. (Keith went on to become a leading Sysop for GEnie and I am currently a CP/M Sysop for CompuServe in addition to helping on a number of other RCPM systems around the country.) HBBS.DOC 17 April 1988 Page 2 Programs with names such as RBBS, OxGate, Oracle, MBBS, QBBS, ZBBS, DBBS, TBBS, CBBS, METAL, ZMSG and several others I thought I would still remember, have been used by CP/M enthusiasts since that time. During the 1983 Xmas holidays, Simon Ewins of Toronto wrote EMX, a Z80 BBS assembly level program. Dennis Recla (who has been guardian of the most recent versions of RBBS38) told Russ Pencin about EMX when Russ was looking for another program to improve his own BBS in Dallas. PBBS resulted. A number of people have contributed heavily to help improve the earlier versions. The assembly level program has recieved a lot of interest and many people have contributed to the current version, with Russ acting as a collection point of ideas. I was giving him new routines so rapidly that around Xmas time 1986, Russ said enough already yet, develop your own version. HBBS resulted. It has been nearly two years in development and does represent some major philosophical differences with regard to PBBS. On the other hand, there are so many similarities, comparing the two might be similar to looking at features of two General Motors autos such as a Buick and an Oldsmobile. Some of these similarities are due to routines I originally contributed to PBBS. There are enough differences between HBBS and PBBS however, to give the user an excellent choice. In early 1988, Russ turned PBBS completely over to Ian Cottrell (who also makes the monthly list of RCPM systems available.) Ian is planning to fully support PBBS and act as a central control point for future up- dates. ACKNOWLEDGEMENTS: ----------------- To Keith Petersen, Victor Poor and Harry Pyle for interest in radio message systems. To Ward Christensen and Paul Traina for establishing some of the original BBS systems around the USA. To Keith for modifying Ward's MODEM program to the well-known XMODEM file transfer program. To Simon Ewins who wrote EMX. To Russ Pencin for devloping that into PBBS and to Ian Cottrell for writing the .DOC file for PBBS. Also to Wayne Masters for support and assistance in developing routines for BYE5, KMD, ZCMD2x and early versions of PBBS. To Norman Beeler, Bucky Carr, Bob Dean, Peter Essl, Werner Gumpert, Adam Heath, Ted Logan, Al Mehr, Chuck Metz and Clay Walker for using the program during the past year or so, while assisting in its development. Particular thanks to Paul Foote for his interest, encouragement and proof-reading, plus his many phone conversations with other Sysops about our progress. Thanks to Ian Cottrell and Russ Pencin for adopting ideas and routines I submitted for earlier versions of their PBBS program. HBBS.DOC 17 April 1988 Page 3 STATEMENT: ---------- HBBS was originally deveopled for use with the PRACSA Sysop RCPM. It was made available to a small group of PRACSA Sysop members who had expressed particular interest in some of its features. Now that Ian and Russ have both encouraged me to make it available, I am releasing it for general use. There are always MANY features any program such as this COULD have. We have attempted to include the most important ones as well as make it the most "Sysop friendly" BBS in existence. Anybody already familiar with other BBS programs will quickly notice some features they will like and as quickly decide it's missing some they have grown to like on other systems. If your first inclination is to start adding things, please do what Russ encouraged me to do. (Stop modifying his version and write one of my own.) Rather than attempt to update HBBS with your mods and then put your name on it for general distribution, please pick another name and release your version with the new name. That would allow both of us to make whatever additions seemed apprporiate to our own versions, without upsetting the other person by changing some of his pet routines. COMPARISON WITH PBBS: --------------------- There are oodles of tiny differences with PBBS and several cases of major design differences. No attempt at a complete list will be made. Some of the primary differences involve: 1) HBBS has all the commands on one line with one menu. PBBS alternates between two different menus and two lines of commands. 2) HBBS has fully automatic daily message backup. 3) HBBS has an 'Again' repeat of the current message. of general interest so they aren't deleted. 4) HBBS has fully automatic, daily maintenance after a a specified hour. 5) HBBS has a line-numbered editor to let the writer pace his messsage length. 6) HBBS includes the time the message was entered, when using the 'H' option for message headers. 7) HBBS shows all new messages since last time on, by just hitting CR twice. 8) HBBS offers a TAG feature allowing the Sysop to save messages to reread when he has more time to re-read and answer the message in detail. HBBS.DOC 17 April 1988 Page 4 9) HBBS has a lovely "Modify" command, to delete, unde- vate (or vice versa), change to "were read" or "not read", change to a more appropriate area, redirect to a different reader, etc. (Shown only to the Sysop or Ass't Sysop.) 10) HBBS marks "To: ALL" messages as having been read, so they will be automatically deleted at a later date. The Sysop can mark messages of general interest so they aren't deleted. 11) Written to encourage public messages, not private. PBBS is forever asking: "Ok to delete your messages, now?" NOTE: There is currently a lawsuit in Indiana re- ----- lative to the Invasion of Privacy law passed by Congress. A Sysop allowed people to see some messages the sender had marked private. Give serious consideration to not allowing any private messages - this also makes a lot more messages available for general reading, which in turn attracts more users, more com- ments, etc. It gives technical boards more importance as more people will call to learn things from these additional messages. (Also consider not allowing users to erase mes- sages or these interesting discussions will not be available to those who can't make it on the system before they are deleted. HBBS automatically deletes them later in the month which gives any active user an opportunity to read anything of interest. HBBS.DOC 17 April 1988 Page 5 MAJOR FEATURES: --------------- A list of primary features would be lengthy and time consuming. An overview might instead be more informative. Keep in mind the word PBBS could be substutited in most cases where HBBS is used. The differences between the two programs have for the most part already been mentioned. PBBS is a more private system than HBBS, and the person reading his own messages is frequently asked "ok to erase your messages, now?" HBBS on the other hand was written to encourage public messages and the Sysop is urged to keep the distributed options intact, with private messages not even allowed. (Messages left by first time users do go directly to the Sysop, however and are private. He can make them public if he thinks it would be appropriate. This gives him an opportunity to intercept filthy and obscene messages that "twits" and "nerds" occasionally leave on some systems. HBBS uses a customized version of BYE510 (called BYE510HC) to auto- matically do maintenance updates at a specificed hour after a new date. (West coast users often set that to 9 AM, east coast users so far have preferred 5 AM.) This not only backs up all the message activity of the previous day, but also drops off messages that have been read and are over 'xx' days old. (Most have been setting that to 30 days, which allows users to read nearly all messages even if they only can call in occasionally.) The messages are then renumbered and each user "highest message last read" automatically updated. With PBBS, the Sysop tries to get each user to delete his own messages when read (not allowed for HBBS by most Sysops) else PBBS has no way to automatically eliminate the ones that have already been read. There are 9 different user levels available. Very few Sysops need this many: 0 - Inactive user, slot can be used by a new caller, if needed 1 - twit, this name will be ignored if used again 2 - normal first-time new user 3 - (set as desired) 4 - (set as desired) 5 - often a normal user with 90 days to call back, 1 hour time 6 - usually a special user of some sort 7 - super-special user, maybe a visitin Sysop or board member 8 - assistant Sysop, helper 9 - Sysop himself The privileges for each user level can be varied by the Sysop, including the follow- ing 5 items: 1) How many drives he can access, new users usually limited 2) How many user areas he can use, advanced users given more 3) How long he can stay on each calendar day, or unlimited 4) How many days of inactivity permitted before being dropped 5) What ratio of uploads to downloads permitted, or none needed HBBS.DOC 17 April 1988 Page 6 PROGRAMS INCLUDED: ------------------ HBBS includes two major library files: HBBS-1.LBR <<-- main files used for assembly HBBS-1SU.LBR <<-- supplementary support files The first has all the major files needed to install the actual HBBS program itself. The second has all the supplementary files needed, few of which need to be assembled. Several of those in the second file are included as an example and the user will wish to replace or heavily edit them for his own use. Don't get alarmed and immediately decide it's too complicated or takes too much room. Any BBS is a lot more complex than most potential Sysops would expect. If you have any experience at all with editing files and using a Z80 assembler, you should find it reasonably simple to install the program and have it running in perhaps even an hour or two. INSTALLATION: ------------- Where to start? It really doesn't matter a whole lot. Perhaps the most logical place would be to get BYE510HC.AZM from HBBS-1SU.LBR and edit the options you need. Add the appropriate BYE5 clock and hardware inserts needed for your computer. Assemble the program and then rename to BYE.COM and place on A0: Take the same clock insert and change the TIME: label to TIMER: and then use XIZ.COM (included in the supplementary library) to convert it to Z80 code for use with HBBS. Rename this new Z80 version BYERTC.INC. Extract and uncrunch all the files from HBBS-SU1.LBR and put them into A14: or whatever area you plan to use for storing the messages and user files, etc. Good idea to plan on A14: initially at least. It will be helpful to make a minimum of changes until the program is first work- ing and then you can play around as much as you like. It would be very difficult to help you over the telephone or via an exchange of messages if you make unexpected changes and then seek assistance where the other person has no idea what you have altered. Run the HINSTAL.COM program on A14: This makes a number of files, including the USERS.BBS file with which you can get started. It asks how many users you have selected - answer 500 at this time. (You can change that later, if some other number is preferred.) It will then ask for a name, city/state, phone number and password. This person then becomes the Sysop with a level 9 assignment. HBBS.DOC 17 April 1988 Page 7 Then extract, and uncrunch all the files in HBBS-1.LBR. Edit the HBBSHDR.INC file. This has all the things that are needed to be set for your partiuclar instllation, your preferences, etc. At this time resist making any changes other than the PDT at the very beginning. Then look for the "SYSOP:" label. This currently says "YOUR NAME". Put your own name in this area, making sure it is all upper case. We suggest you quit at this point, merely to bring up the program with minimum changes. After it is working properly, you can branch out and make changes. The program is currently set for four disk drives. After you have it going, you will want to edit the ACC2: through ACC9: table for number of drives each user can access, etc. (This is shown toward the end of this file.) Edit the HSAVE.Z80 program. It will ask what drive and user area you wish the backup files to be stored on. That will only take a short time to answer. You are ready to assemble the program. There are two HBBSxxx.SUB files. One is for use with M80/L80, the other for SLR's Z80ASM assem- bler: A14>EX HBBS-M80 <-- uses HBBS-M80.SUB A14>EX HBBS-SLR <-- uses HBBS-SLR.SUB It will take perhaps 18-20 minutes to automatically assemble all of the files. When finished, distribute the .COM files as follows: HBBS.COM <-- rename to BBS.COM and put on A0: HBYE.COM <-- leave on A14: HBBSMNT.COM <-- rename to MAINT.COM and leave on A14: HNOTE.COM <-- rename to NOTE.COM and put on A0: HCHAT.COM <-- rename to CHAT.COM and put on A0: HSAVE.COM <-- leave on A14: HMNT.COM <-- leave on A14: WHAT ELSE IS NEEDED: -------------------- If you plan to allow normal users into the CP/M operating section, you will want to have something like ZCMD29 or ZCPR3 to replace the CCP portion of your CP/M system. This will prevent remote users from using commands like "REN", "ERA", "SAVE", etc. It will also allow an external "DIR" file (normally SDxxx.COM, renamed to DIR.COM) and will show normal drive/user areas to be displayed. HBBS.DOC 17 April 1988 Page 8 USING THE PROGRAM: ----------------- If all has gone well up to here, you are all set to start using the program. If you have two telephone lines, you could use the second line to call the BBS system. The more common method would be to just call up BYE5 in the following manner: A>BYE E This will activate the BYE510HC program (which you renamed BYE.COM) and activate the BBS as though you were a remote caller. When it asks for your name you can say SYSOP or type the same name you entered when using HINSTAL.COM originally. When you get to the command line, you can use "E" to enter the ini- tial message on the system. When ready to quit, type "G" for "GOODBYE", then "Y" for yes. You will likely get an error at that time, since there is no Callers file (as yet) to display. Ignore this error, the first remote caller (other than the Sysop whose name is not added to the last caller file) will open this file. After that you will not see any error message. HBBS normally shows the last 10-12 callers, when the current caller is finished. You are on your way. There are probably pages and pages that could be added to these instructions. These additional comments would include information on what each file does, how to use it, special features such as typing '@' sign to activate the 'YAK' mode if you wish to chat on the keyboard with the current user, possible error messages, etc. Check further pages then, for more specific details. Some people will have nearly all the information they need already. Other users who may have less experience with such systems will want/need to read more. ------------------------------------------------------------------------ HBBS.DOC 17 April 1988 Page 9 OTHER FILES: ------------ Files that are NOT included in either library that will probably be useful/necessary on a BBS with file transfer capabilityes would be: CHEK15 - renamed CHEK.COM KMD23 - renamed KMD.COM LDIR-B - renamed LDIR.COM LT24 - renamed TYPE.COM LUX77B - renamed LUX.COM SD130 - renamed DIR.COM UNARC16 - renamed UNARC.COM ZFILE5 - renamed FILE.COM These would all be placed on the A0: area so they could be called from any location the user can access. Some of these programs give the Sysop additional capability if the wheel byte is on. As an example, KMD will allow the Sysop to upload and download files to any user area, with no request for a file description and no indication in the KMD.LOG file. SD130 and ZFILE5 will allow him to look at all user areas, including his private files (usually on A15:, etc.) LT24 will permit the Sysop to ex- tract files from a .LBR and automatically uncrunch or unsqueeze them, if needed. It will also uncrunch or unsqueeze a normal file, with if the wheel byte is set for the Sysop - a MOST USEFUL program. ------------------------------------------------------------------------ LIBRARY CONTENTS: ----------------- (1) Library File = HBBS-1.LBR ------------------------- name length method original name ============ === ==== ======== ================= -17APR88. 0 0k -- 1) EX .CZM 18 3k Crunched --> EX.COM 2) HBBS .ZZ0 620 78k Crunched --> HBBS.Z80 3) HBBS-M80.SUB 3 1k -- 4) HBBS-SLR.SUB 2 1k -- 5) HBBSHDR .IZC 121 16k Crunched --> HBBSHDR.INC 6) HBBSMNT .ZZ0 242 31k Crunched --> HBBSMNT.Z80 7) HBBSUBS .IZC 74 10k Crunched --> HBBSUBS.INC 8) HBYE .ZZ0 162 21k Crunched --> HBYE.Z80 9) HCHAT .ZZ0 46 6k Crunched --> HCHAT.Z80 10) HDOSHDR .IZC 9 2k Crunched --> HDOSHDR.INC 11) HINSTAL .CZM 35 5k Crunched --> HINSTAL.COM 12) HMNT .ZZ0 147 19k Crunched --> HMNT.Z80 13) HNOTE .ZZ0 117 15k Crunched --> HNOTE.Z80 14) HSAVE .ZZ0 37 5k Crunched --> HSAVE.Z80 15) WHEEL .ZZ0 46 6k Crunched --> WHEEL.Z80 16) XIZ .CZM 36 5k Crunched --> XIZ.COM HBBS.DOC 17 April 1988 Page 10 (2) Library File = HBBS-1SU.LBR --------------------------- name length method original name ============ === ==== ======== ================= -17APR88. 0 0k -- a) BBSMENU .BZS 4 1k Crunched --> BBSMENU.BBS b) BULLETIN.BZS 2 1k Crunched --> BULLETIN.BBS c) BYE510HC.AZM 256 32k Crunched --> BYE510HC.ASM d) CALLERS .COM 6 1k -- e) CP/M .BBS 2 1k -- f) FOR .CZM 10 2k Crunched --> FOR.COM g) HASHALL .CZM 196 25k Crunched --> HASHALL.COM h) HBBS .DZC 156 20k Crunched --> HBBS.DOC i) INFO . 1 1k -- j) INFOA .ZZZ 9 2k Crunched --> INFOA. k) INFOB .ZZZ 7 1k Crunched --> INFOB. l) INFOERR .BBS 1 1k -- m) KFOR .CZM 11 2k Crunched --> KFOR.COM n) KMDEL .CZM 11 2k Crunched --> KMDEL.COM o) KNEW .CZM 11 2k Crunched --> KNEW.COM p) NEW .CZM 10 2k Crunched --> NEW.COM q) WELCOM2 .BBS 4 1k -- r) WELCOM3 .BBS 2 1k -- s) WELCOM4 .BBS 2 1k -- t) WELCOM5 .BBS 2 1k -- u) WELCOM6 .BBS 2 1k -- v) WELCOM7 .BBS 2 1k -- w) WELCOME .BBS 8 1k -- BRIEF DESCRIPTION OF FILES: --------------------------- 1) EX.COM - Actually EX15.COM. Used with either of the submit files to assemble the .Z80 HBBS files with mini- mum operator fuss. 2) HBBS.Z80 - Main HBBS program. When assembled, rename BBS.COM and place on A0: It's called up by BYE.COM when the modem receives a new call. 3) HBBS-M80.SUB - For use with EX.COM and the M80/L80 assembler and linker. Minimizes hand typing numerous commands to generate the .COM files needed. 4) HBBS-SLR.SUB - For use with EX.COM and the SLR Z80ASM assembler. No linker needed, as that program generates .COM files directly. 5) HBBSHDR.INC - Has all the options for settting up the HBBS pro- gram. Is assembled as part of the various .Z80 files so they may be used independently. This program contains nearly everything you would al- ter to customize the BBS to your own preference. HBBS.DOC 17 April 1988 Page 11 6) HBBSMNT.Z80 - Maintence program for manually entering new names into the USERS file, for changing user access level (locking out twits, etc.) and general up- dating of the system. Also can update messages, renumber them, etc. Many of these features are automatically handled by HMNT. After assembly, rename to MAINT.COM (for easier typing) and put on A14: 7) HBBSUBS.INC - File containing most of the routines common to the various other files, so they only need by typed once. (If altered or modified, minimizes work required and insures all modules then have the new updated version.) 8) HBYE.Z80 - The "exit file" when a person signs off. Updates his parameters such as highest message read, the last time on the system, how long he was on, the number of uploads and downloads he now has, etc. Says "Goodbye, thanks for callling", etc. 9) HCHAT.Z80 - Rename to CHAT.COM when assembled and place on A0: Allows the remote user to summon the Sysop, if available, for a keyboard chat. If not, asks if he would like to leave a note to the Sysop. 10) HDOSHDR.INC - The "get time" routine to pick off the current time and convert it into an ASCII display. Included in nearly all the .Z80 files during assembly. 11) HINSTAL.COM - Used to enter the Sysop's name, password, etc. It also makes the initial message files needed to accept the first message. Will ask for the num- ber of users requested in HBBSHDR.INC (500 with the original, distributed copy. Only the very busiest systems might find this restrictive.) 12) HMNT.Z80 - Special HBBS program for the "midnight maintenance" after a new date and the time selected in BYE5. After HSAVE.COM does the back, this kicks in and updates the message base, dropping messages that have been read and are over 'xx' days old. (30 is normally used unless the system is unusually busy.) In addition, waits until at least 'xx' (usually 20) messages will be deleted as it is advantageous to only do this occasionally. HBBS.DOC 17 April 1988 Page 12 13) HNOTE - If the Sysop is not available, and the user is in the CP/M section, he can leave a note to the Sysop. It can be either private or public. It gives the user the capability of leaving private messages to the Sysop, without otherwise making private messages generally available. Thus the door hasn't been closed, but it makes it harder for people to just mark ALL their Sysop messages private - most of which likely should be public, so other people can read them and perhaps offer answers, simplifying the Sysop's work. 14) HSAVE.Z80 - Special HBBS program to back up the message base on another drive/user area prior to any mainte- nance activity. Can be called manually, but is normally called automatically by BYE510HC after a new date and the first user after a preselect- ed time, has disconnected. 15) WHEEL.Z80 - Permits the Sysop to activate the wheel byte with all user areas, when some remote user is on the system. You can rename it, if desired. It also requests a secret password that is not shown to the remote user. Also permits you to access the floppy drives which you may have told HBBS not to allow - some systems lock up if running DIR, etc., without diskettes in the floppy drives. Edit to select a desired password, assemble and hide on A0: as a .SYS file (via STAT or NSWP.) 16) XIZ.COM - Translates 8080 source code to Z80 source code. Used to change the BYE5 hardware insert for your computer, to Z80 code so it can be assemble with other Z80 code in the HBBSMNT file. --------------------- a) BBSMENU.BBS - Menu of HBBS command line choices. Shown to all new users and available to anybody by typing ? b) BULLETIN.BBS - Allows the Sysop to use special bulletins if/when needed. (Not part of the "welcome" message that is shown at signon - is diplayed after he has logged in with his name and password.) Perhaps your club has a meeting this coming week, etc. If not needed, replace with a file that has only a "CR-LF", else an error message will be shown indicating no file can be found. HBBS.DOC 17 April 1988 Page 13 c) BYE510HC.AZM - A special version of BYE510.ASM, for use with HBBS. Most of the superfluous equates needed for other BBS have been removed. This has several special routines added for backing up the system after a new date, then updating the message base if/when enough messages are ready for deletion to bother taking the time needed. Also renumbers the re- maining messages and resets each user's "highest message last read" number. d) CALLERS.COM - Shows the previous 20 callers on the system. This works when in CP/M and is similar to command "P" if in the message base. Put it on A0: Handy to see how to spell some recent caller's name while in CP/M section and updating him to normal user. e) CP/M.BBS - Little display shown when going from the HBBS mes- sage system to CP/M. Change to suit your needs. f) FOR.COM - Updated file for A0: normally from the KMD23.LBR, but this (and the others mentioned below) may be newer than what you have now. 0103h Drive for CP/M KMD.LOG probably A: 0104h User area for KMD.LOG, usually 14: 0105h FF - yes separate 16-bit area 00 - no, just one upload area 0106h Drive for 16-bit uploads 0107h Drive for MSDOS KMD.LOG, probably A: 0108h User area for MSDOS KDM.LOG, usually 13: Note: same arrangement for: NEW.COM KMDEL.COM KFOR.COM KNEW.COM g) HASHALL.COM - Packs, then alphabetizes the USERS.BBS file. Often used to change the number of users if 500 is not desired. Run this program and answer the query with current number of users, then rerun it for the new number you want. Change the MAXU equate in HBBSHDR.INC, reassemble and place those files where they should go. Then use MAINT.COM option 9 to unpack and redistribute the user's names. h) HBBS.DOC - This .DOC file you are now reading i) INFO - Index of information files available. Change with with your favorite editor when you add or remove such files. Such information files can become a most important asset to your system, if current. Supports up to 26 such files, A-Z. HBBS.DOC 17 April 1988 Page 14 j) INFOA - Example of an information file, which is called by selecting INFO choice A. k) INFOB - A second example of an information file, called by selecting INFO choice B. l) INFOERR - Backup file for error purposes. It says there are are no information files to show. m) KFOR.COM - Allows the Sysop to manually insert a description into the FOR file. Will be rarely used. Needed at times if somebody uploads a file to your pri- vate area which you later make public, but has no description. (See FOR.COM above, to set the proper drive/user values.) n) KMDEL.COM - Very useful program, erases all download entries from your KMD.LOG file, retaining all upload en- tries. Keeps your KMD.LOG to a manageable size. (See FOR.COM above, to set the proper drive/user values.) o) KNEW.COM - Lets the Sysop manually insert an entry into the KMD.LOG. He may have uploaded a file with the wheel byte on, which does not put anything into the KMD.LOG. (See FOR.COM above, to set proper drive/user values.) p) NEW.COM - Displays most recent file uploads, time they were uploaded, by whom, their length, baud rate, etc. (See FOR.COM above, to set the proper drive/user values.) q,r,s,t,u,v - Examples of welcome files for each access level. You will want to change these to suit your own system. They can add a little personal touch. w) WELCOME.BBS - Shown when your modem answers the phone, and remote user has typed "any key", to start things going. ------------------------------------------------------------------------ HBBS.DOC 17 April 1988 Page 15 APPENDIX A: ----------- (This is the BBSMENU.BBS, it is shown to all new users or by typing '?') commands are: A - Choose new Area (from menu) M - Read all messages to me B - Bulletins (if any are current) N - New files recently uploaded C - Go to CP/M (file transfer area) P - Previous caller list F - For descriptions of new files R - Read public (and your new) mail E - Enter message S - See system/your statistics G - Goodbye (sign off) T - Toggles [more] pause on/off H - Header scan of messages U - Users list I - Information/help/news (if any) Y - Yak with Sysop (if available) L - Read all messages left by me ? - Display this command list ------------------------------------------------------------------------ APPENDIX B: ----------- Each access level from 2 through 9, can have separate capability. This shows how the HBBSHDR.INC file is currently set for distribution. Alter whatever you wish for your system, particularly the number of drives, in the first column of each user level. Days to deletion would be 255 max- imum, with 0 used for "never delete". ; Access table byte order is: Max drive, max user, minutes online, days ; to deletion (0=no autodelete), KMD D/L ratio allowed. ; ;NOTE: Drive A=1, B=2, C=3, etc. Users are 0-15. ; ACC2: DEFB 2,1,30,10,10 ; Drive, user, time on system, ACC3: DEFB 5,9,45,60,20 ; days to delete, KMD ratio ACC4: DEFB 6,9,60,75,20 ; New user (almost normal) ACC5: DEFB 6,10,60,90,30 ; Normal user ACC6: DEFB 6,11,60,180,30 ; Club members ACC7: DEFB 6,12,90,240,40 ; Special Users, unlimited time ACC8: DEFB 6,15,0,0,0 ; Co-SYSOP, unlimited time ACC9: DEFB 6,15,0,0,0 ; SYSOP, unlimited time ; ------------------------------------------------------------------------ HBBS.DOC 17 April 1988 Page 16 ERROR STATEMENTS: ----------------- You will occasionally get an error of the: BDOS Function 33, Error Code 01 01 reading unwritten data 02 (not returned in random mode) 03 cannot close current extent 04 seek to unwritten extent 05 (not returned in read mode) 06 seek past physical end of disk Function 33 is associated with "random record reads". Error code 01 and 04 occur when a random read operation accesses a data block which has not been previously written or an extent which has not been created, which are equivalent conditions. Error 03 does not normally occur under proper system operation, but can be cleared by simply re-reading, or re- opening extent zero as long as the disk is not physically write protect- ed. Error code 06 occurs whenever btye r2 is non-zero under the current 2.2 release. Normally, non-zero return codes can be treated as missing data with zero return codes indicating operation complete. ------------------------------------------------------------------------ SETTING MESSAGE AREAS (option in HBBSHDR.INC): ---------------------------------------------- The primary advantage of having different areas is to enable the Sysop to leave messages in the 'Special' or 'Private' area. He need not mark them "private" in addition, but may do so. When/if answered, the answer will automatically be stored in that same area making the answer private, even though the Sysop likely does not allow users to originate private messages. He can use the 'Special area' to leave messages for level 8 (assistant Sysop) users, and keep the 'Private area' for his own personal use. HBBS offers tremendous flexibility, without needing pri- vate messages or allowing users to delete their own messages. Selecting areas also helps keep discussions of CP/M and MS-DOS com- puters separated. This is often advantageous, as people may otherwise not give enough information for those reading the message to realize the computer being discussed, or to answer the message with useful and help- ful information. If you want to let people send private messages to each other, and delete any messages to-from them, please consider using PBBS which seems to be designed with privacy in mind. HBBS was designed as an "open" BBS where users would not be allowed to originate private messages (except to the Sysop, when in the CP/M area and after selecting "NOTE.COM".) It also is designed to not allow users to erase their own messages, which are automatically erased after 'xx' days (30 by default unless changed) after the message has been read. an (X) on the message header informs both the Sysop and the sender that the message has been received by the person to which it was addressed. HBBS.DOC 17 April 1988 Page 17 You CAN allow private messages to the Sysop, you CAN allow private messages between users and you CAN allow anybody to erase their messages but we hope you don't. Most Sysops find a high percentage of private messages are addessed only to them. This greatly increases their amount of work to support the system, and limits the assistance others can give in helping to answer technical questions. If allowing deletions, some excellent, highly informative messages might be erased before hardly any other users might see them. This is a disservice to those users who may also be in a position to add further comments. Note: Bob Freed wrote UNARC16. He tells the story of leaving a legnthy, technical message about file compression on a particular BBS. After he quit, he remembered something he meant to include. He called back as soon as he could get onto the BBS again. Guess what? The person who was keeping him from immediately accessing the system turned out to be the recipient of Bob's message and he had ALREADY erased the lengthy and very informa- tive message. Bob was "not pleased". Obviously he doesn't leave such messages on that BSS these days, not knowing how long they might remain for others to see. (I enjoy reading anything he may write, myself, and suspect you would, as well.) PBSS .DOC FILE -------------- Ian Cottrell wrote the PBBS .DOC file. It is very comprehensive and many of the comments it contains are applicable to HBBS. If you wish to delve into some of these topics further, you may find your question has been covered in that file, intended to be read/printed via WordStar. SUMMARY: -------- Trying to tell somebody how to install a BBS is perhaps comparable to trying to teach geometry or calculus. The math teacher has to assume the student already has a good background in arithmetic and algebra. If the CP/M user wishing to install HBBS does not have at least some know- ledge of editors and assemblers, it may be more difficult for him to get the system running. If you have difficulty, call some BBS and leave a message "To: ALL" asking for assistance. One of the purposes of the PRACSA Sysop RCPM is to help new Sysops get such information as well as act as a collection point for new programs and ideas about operating BBS. I will try to help but voice phone calls can be expensive and time- consuming. Start out by trying to install the program with no changes, except those mentioned. Once working, you can then consider altering a few equates while you "shoot for effect". - Irv Hoff Sysop PRACSA Sysop RCPM (415) 948-2513 (415) 948-2166 voice