RBBS vers. 3.7 DOCUMENTATION November 23, 1984 by Dennis Recla INTRODUCTION: This is another effort in the line of RBBS programs started several years ago. This NEW version is the next generation of the RBBS35 program which I did in early 1984. It was an improve ment over the RBBS31 program, and included expanded comments as well as additional new features to improve the operation as seen by the user and the SYSOP. It had one problem which I hope to clear up with this new version. The program has gotten so big that the normal L80 linker used with BASCOM would not link the REL file created. Most CP/M 80 systems have a TPA of about 56 K or less, and since L80 uses the system memory for it's operations it would run out of usable space to do the LINK. There are several Linkers which are 'Disk Based' and the various Temp. files are stored on disk instead of in Memory. These linkers such as LD80 and PLINK work very well with large REL files. BUT !! They are not normally found in the library of the average computer user, as MicroSoft does not supply LD80 with the BASCOM MBASIC compiler package. (Perhaps they should) RBBS vers. 3.7 dosen't cure the problem but I hope to reduce the trouble that some SYSOPS have had getting the program to link and be able to use it. So.....the plan was to creat a version of RBBS that could be distributed as a .COM file and still provide the user with a program that would fit most system requirements. In addition an INSTALL program was written to make the installation of the RBBS program on the system even easier. This program creates the password files that are needed to customize the RBBS program to your own requirements. These password files give the RBBS program its name, and identify YOU as the SYSOP as well as letting you decide which disk drives are used to store the various files used and created by RBBS37. The password files are not necessary for the program to operate, so if something happend to one of them it would work, using the default values I entered in the RBBS37 program before it was compiled. These can be found in the RBBS37.ASC file that is supplied with this RBBS37 Package. These defaults can be changed and I will explain later what you can do to the .COM file and where to find these values in the binary code using DDT or a similar program. I have also found that the comments source code RBBS37.ASC has also gotten so large that it will not run correctly under MBASIC as it fills most of the usable TPA left over after MBASIC is loaded on the system. If you want to experiment with the program and have plans to make changes in it then use the RBBS37NC.ASC version. This is an identical copy of RBBS37.ASC, but most all of the comments or remarks have been removed. This version will run under MBASIC. I would reccommend that if you do make changes to the program that you incorporate and comment them in the RBBS37.ASC to make it easier for others to understand how the program works. All of the required utility programs have also been supplied as COM files so that you need not use MBASIC to run them. In each case you will find the ASC or atleast the squeezed version AQC to allow for your own modification if you find it necessary. The program RBBSUTIL is used to maintain the message base and it's associated files. RBBSINST.COM and RBBSINST.HLP are used to create the password files needed. I hope to sometime in the near future create another utility or incorporate in RBBSUTIL a method of maintaining the USERS file created by RBBS37. Maybe if I wait long enough someone will write one for me, as on some systems the USERS file can become very large. That covers most of the basics about this new version of RBBS, I hope that you find it usefull. It was re-written for use primarily as a message system, with a capability of keeping track of callers, and controlling the access by the caller to the CP/M operating system. If you are putting together a simple RBBS-RCP/M system than this program might be just the thing you want. There are several around the country running the older RBBS35 program as well as my own system. If this new version is as popular then It will have been worth the effort. If you as the SYSOP require a program with more 'power' then I suggest that you look into the other RBBS programs such as RBBS4 written in 'C' or MSGSYS20 which runs under CBASIC. In addition the various versions of MINI-RBBS also have their attributes, since in those programs the RBBS has been broken down into an entry program, a message base, and an exit program. NOTE: This is the last revision of RBBS3 that I will make, unless there are found to be some bugs in the code. I think that this program has gotten out of hand and has grown to a point that any other features or additions can be best supported from one of the other RBBS like programs. What is really needed is a version of an RBBS program that is written in 8080 code, this will give it the speed, as well as provide a means of getting a message system on line without the requirement of having a commercial support program. Even the EMX program which is written in assembly language requires that you have M80 instead of the standard version of ASM.COM that is supplied with almost every CP/M based system. Dennis Recla Lost Island RBBS-RCP/M Garland Tx 214 681-4789 Like a Lost Island it is not always there when you look for it !! (Soon to be 24 hours a day) HOW IT ALL WORKS Entering/Leaving RBBS: Once this program is installed on the disk it should be renamed to RBBS and you now let your BYE program link to it. BYE allows you to run a program when a caller makes connection to your system. This should be set up to run RBBS when the caller makes connection with your system. There are a couple of commonly used ways to set up your system. If you plan to have a message system only with no access to the CP/M operating system by the callers except for the SYSOP or a SUPER user then you can put the various RBBS program files in any user area on the disk. In this case put the files all in the user area '0' since you need not protect them from those who enter CP/M. If you are running an RCP/M-RBBS then a common practice is to set up user 15 as the secondary default area to search in NZCPR when the WHEEL is set. Then in user 14 you put the RBBS.COM program and the associated files to run it. When BYE answers the telephone it then links and runs the RBBS file in user 14. You will have set up NZCPR to prevent a user from going to user area 14 with the MAXUSR equate. When RBBS is exited using the 'J' command for JUMP to CP/M it goes in and sets the CP/M operating system equates in low memory from the current user area (14) to user 0 where it dumps you upon exit. If the caller uses the 'G' command to GO then RBBS runs the program BYE. BYE.COM should also be in the same drive/user area as the RBBS program is installed. Having RBBS.COM in user area 14 causes a couple of problems in that if a caller is not allowed to get there then how does he/she re-enter RBBS once they have entered CP/M. Simple..I have also included a program I call RBBS.COM, you use to run RBBS that exists in a user area 14 where the caller is not allowed to go. It will also support the RBBS P re-entry technique to enter RBBS once the caller has gone to CP/M. It only takes up a minimum of space on the system. Be sure to keep it separate from the real RBBS.COM in user 14. It is necessary to have a copy of BYE in user area 14 and one in 0 so that the caller can exit the system, when they type in BYE. That's how you get in and out of the RBBS37 program, just link to it from BYE.COM and let RBBS run BYE.COM when the caller exits the message system. Inside RBBS37: The first thing the caller sees is the Version message that tells the caller the name of your system, it is followed by my own bit of information indicating that this program is from Lillypond Software (software written by FROGS). INFO Next the message file called INFO is show to the caller, this is a file you have created using a text editor and named INFO, be sure to put a few CR's at the beginning and end to keep the texts from packing together as they are printed. The INFO file is there for you to give the caller information about the system he/she has just called. BULLETIN Next the message file called BULLETIN is show to the caller. It follows the INFO file that was just show to the caller. The BULLETIN file is a way of you as the SYSOP to let the caller know about new features, or to give out additional information about the system. NEWCOM This file NEWCOM is only shown to the caller once, it is a bit of information that you have created to let a first time user know what you expect of them or to give them special information that a first time caller will need to use your system. MENURBBS Another new feature in RBBS37 is that a first time caller is shown the MENU of commands that are supported by RBBS37. This will only occur the first time the new user calls, after that they must use the '?' function to see the MENU again. The following is a example of the MENURBBS file which you will need to create or you can use the one supplied with the RBBS37.LBR. sample MENURBBS file Functions supported: by RBBS vers. 3.7 Bulletin File Chat with SYSOP Enter Message * GO 'Leave the system' Feedback for SYSOP News and information Read Message Scan message base Kill Message * Users file (Valid Members) Toggle BELL List last callers * Welcome Message

Password Change Jump to CP/M X'pert User Help (some comments about things can also be given as show below) * Special function requirements Verified users only Repeated Ctrl-K's abort, Ctrl-S pauses Messages are Private unless addressed to ALL For Sequential retrieval (not scanning), use '+' after message #. For example, R;10+ reads message #10 and all that follow, a Ctrl K can be used to 'SKIP' to the next message in this mode. The above sample of MENURBBS lets the caller see all the functions that are supported by the RBBS37 Program. Depending upon how you set up the passwording files, you can prevent the new caller from leaving messages or seeing some of the various files. They can also be limited in their access to CP/M using the 'J' command. SYSOP functions: The SYSOP has a few extra commands that are available to he/she only. They are not listed on the MENU or are they shown on the command line. First is the 'Z' command, this lets you view the COMMENTS file that has been left by the callers in eedback or upon exiting the RBBS program. You can also have comments in this file that are created by the EXITRBBS program. This command allows you to view the XMODEM.LOG file if you have created one from the XMODEM program. This command helps to let you know who has been uploading or downloading files from your system and as a way to provide audit capabilities without having to enter CP/M. You might use this if you run your system from home and have a Modem at work to call and 'see how things are'.

This PASSWORD command is available to all users in that they can modify their own password anytime they like. When the SYSOP calls up the 'P' command you will get an expanded version of password change. This is where you as the SYSOP set up the validation of the callers. You can set up any caller from the validation command to either a alidated user, a wit, or a uper user. If you don't want to make any changes to the validation then just hit the again until you get the command line prompt back. This is not a restricted command that only the SYSOP can use, but one that is normally not told to the callers. When a caller uses the command to view the USERS file he/she will only see the names of those users that have been validated. This limit on the viewing of the USERS file helps to eliminate those callers who enjoy logging in with some obscene name and then run the users list to see it come up on the screen. In the same way when a new user comes on the system they are not allowed to view the CALLERS file which gives a list of the past users in chronological order. Although if the UALL command is used, then the caller can view all the users on the system in the USERS file. EXITING THE PROGRAM o Command: The easiest is the 'G' command that first allows the caller to leave a message for the SYSOP then exits the RBBS program. It does this exit by running the BYE.COM program that you have on the disk. In RBBS35 the exit was done by 'POKEing' the UART control port to drop the DTR line. This is probably a better way, but one that cannot be made universal to all computer systems. ump Command: Depending upon the password setup you are using with CP/M entry you may or may not be asking the caller a question that requires a proper answer. Once the question or password has been entered correctly then like in the 'G' command the caller is give a chance to leave a message for the SYSOP. Following the comments request the file called ENTERCPM is show to the caller. This file is used to give information to the caller about how you have your RCP/M set up or about any special commands that are to be used by the caller. DISK DRIVES USED DSK$ - DSK2$ and DSK3$ files: Since some CP/M systems have small disk drives like the Osborne and the Heath H89 you can be limited by the number of users or number of messages left on your system. As a way of helping this problem, I have set up the RBBS37 program to allow the use of as many as three disk drives to store and run the various files needed from. DSK$ is the default drive, and it is A: on this drive are stored the RBBS37.COM program, BOOTPWD, DATETIME.DAT, ENTERCPM, INFO, HELP and HELP(x) files, NEWS and NEWS(x) files, BULLETIN, and NEWCOM. DSK2$ contains the files, pwds, COUNTERS, SUMMARY, MESSAGES, and COMMENTS. These files are ones that grow the fastest on the system. DSK3$ contains the files, LASTCALR, CALLERS, and USERS. Remember..these can all be the same drive or just two such as using A: for DSK$ and B: for DSK2$ and DSK3$. RBBS37 Installation using RBBSINST.COM RBBSINST was written to provide a very simple way to create the various password files used by the RBBS37 program. In addition to the RBBSINST.COM file there is another file called RBBSINST.HLP which contains the HELP information that you can ask for when using the RBBSINST program. To install the RBBS37 program you must put the RBBSINST program and the RBBSINST.HLP file in the user area on A: drive that you will be running the RBBS37 program from. If you choose to use other disk drives for some of the other files created by RBBS37, you must have those disk installed in the system. If because of the size of the Install program you don't have enough room, then leave off the RBBS37.COM program for now and put it back in after the RBBSINST program has been run, and the password files created. Once they have been created, the RBBSINST files can then be deleted. You are now ready to type in RBBSINST to start the install program. If you have the files BOOTPWD and pwds previously installed on the system then you will be shown a menu of what the password files have been set up for. If this is a first time installation then you will enter right into the installation program. After the first bit of information you are asked the first question about your system, and that is what drive to put the DSK2$ files on. You need only to enter the letter of the drive to be used. If you enter a '?' at this point, you will be shown the HELP file. Once you have gone past the first question whenever you enter a '-' you will be returned to the previous question prompt. This allows you to correct your entry if after you have entered an answer you change your mind or noticed that it was incorrect. If you hit a "+" at this time you will enter the menu portion of the install program. This gives you a quick way to see what you have done so far. If this is a first time installation then be sure to return to the point that you left off and continue entering the password file information. The menu of password data allows you to modify a single parameter and save and exit your new changes to the two password files in a system that had already been configured. Here are the questions you will be asked by the program: 1. What drive should be used for DSK2$ files ? The value for DSK$ is pre-assigned in the program to Drive A: on this drive are the following files: BOOTPWD, BULLETIN, INFO, HELP, NEWS, ENTERCPM, MENURBBS, and DATETIME.DAT. These are the files having the minimum of security required. As the SYSOP you can select which drive contains other files created and used by RBBS37. Remember they can all be on the same disk drive, the idea behind breaking up the files was to allow this program to be used on systems having small disk density (90K etc.) You are now being asked to select the DSK2$ drive. On this drive are contained the files PWDS, COUNTERS, SUMMARY, MESSAGES, and COMMENTS. These are the files which will grow the fastest as messages and comments are left by the callers. You will also note that the file called PWDS is written in lowercase to provide additional protection from being viewed by someone who may have entered the system. 2. What drive shoudl be used for DSK3$ files ?? Like DSK2$ there are additional files stored on drive DSK3$. These are the files LASTCALR, CALLERS, and USERS. The USERS file is one of the files that should be protected as it will contain all the passwords of all your system users. Now you can select the drive that the DSK2$ files will be stored on. -Remember- that all the files will be located in the same user area, but on different drives, or you can use drive A: for all drives. A default is written into the program and this is the A: drive, if any of the password files are not found, the system will default to the pre-programmed default values. 3. Enter your FIRST name ?? When ever you log on as the SYSOP, you might also want to be notified if there are any other messages for you directed to your REAL name. So enter in this your FIRST name that you will be using on this RBBS system. This creates the value for SYS1$ 4. Enter your LAST name ?? This is the LASTNAME you as the SYSOP will be using on the system. The last value and this one are used to flag you when logged in as the SYSOP that there are messages for you directed to your REAL name. This creates the value for SYS2$ 5. What is the name of your RBBS37 System ?? This value in the password files is used to provide the name of your RBBS37 system. It can be in Upper/lower case characters of any discription as long as it is on one single line. This is the VERS1$ value and is printed on entry to your RBBS system. 6. What is the Direct to CP/M Entry password ?? This value called P1$ is the password for direct entry to CP/M thru the RBBS system. When asked for your first name upon system entry you use this password, you will skip over the RBBS message system and be allowed direct entry to CP/M. This password should probably be the most complicated of all your passwords. If it is found out, you have no way of keeping that caller out of your operating system, other then protections that you might be using provided to the system by NZCPR, ZCMD, or ZCPR2. Select this password carefully, use a combination of letters and numbers to provide additional difficulty of guessing it. 7. What is the LAST NAME password for SYSOP entry ?? This is the P2$ password, it is the LASTNAME you use when you use the firstname of SYSOP to enter the RBBS program as the SYSOP. It is another important password, and should be selected with care, so that it will be difficult for someone to guess. A combination of letters, and numbers will help to provide additio nal difficulty in guessing the password. 8. What is the VALIDATION password you will use ?? This is the Validation password VAP$, it is a special password that is requested whenever you validate a new user. If there are more than one SYSOP on the system, this provides a way for the main SYSOP to be the only one allowed to validate new users to the system. Like all other passwords select it with care !! 9.What question will be asked caller before allowed entry to CP/M This is a question that a caller is asked before allowed entry to CP/M using the J command from RBBS37. This question is not needed if you are allowing entry to CP/M without a password, or not allowing any entry to CP/M. It was originally used as a way of keeping non CP/M users from entering the system. Questions relating to CP/M would usually be asked, and you could assume that anyone knowing the answer would have some knowledge of CP/M. This is the PC$ entry. 10.What is the answer to the CP/M entry question ?? This is the answer to the question in the previous menu, it is the answer you must enter to get into the CP/M system. IF you don't want to require a password for CP/M entry than use an answer in this file of NOPASS, using that will delete the need for a CP/M entry password or answer to the PC$ question. This is the value for P3$. 11. Will there be more than one SYSOP using the system Some RBBS systems may want to have more than one SYSOP on the board, if this is what you would like then enter the proper answer. When there are more then one SYSOP, then folllowing the correct entry of SYSOP (First name) and lastname, the SYSOP will be questioned as to which SYSOP he/she is. This will allow the SYSOP to leave messages on the message system that have a more personal identification of the SYSOP instead of the name SYSOP. You could be SYSOP DENNIS or SYSOP NR1, whatever you enter in the Which SYSOP question will be tagged on the SYSOP name. This is the setup of MSYS. 12. What should the BELL delay value be ?? Here is your chance to set up the timing loop used by the RBBS program when the SYSOP is paged for CHAT. This is a value that is between 1 and 32000, when in the Compiled mode, you need to choose a value in excess of 10000, while in the MBASIC mode you can pick a value of less then 500 or so to see how it works. This is the value for BEEP. 13. What will be the allowed line length of messages. ?? You can control the number of lines in messages that are entered on the message system. This is the SIZE value in the program, andyou can enter the number of lines you want to limit the cal lers to leave on the message system. A good starting value is 20. 14. How many NEWS files will there be to read ?? This value is for the number of NEWS files that are on the system. These are files which you create using a word processor that provide information about various topics. If you enter a value of 0 then the program will know that there is only 1 NEWS file, and it will contain whatever information you want. If the value is 1 or greater, then the NEWS file should contain a menu of the other NEWS files you have put on the system. The additio nal news files are named NEWS1, NEWS2, etc. depending upon the number you have selected with this entry. This is the value for NNUM. 15.How many HELP file will there be to read ?? This value is for the number of HELP files that are on the system. These are files which you create using a word processor that provide information or help on various topics. If you enter a value of 0 then the program will know that there is only 1 HELP file, and it contain whatever information you want. If the value is 1 or greater, then the HELP file should contain a menu of the other HELP files you have put on the system. The additional HELP files are named HELP1, HELP2, etc. depending upon the number you have selected with this entry. This is the value for HNUM. 16. Do you want to SKIP the 'Last message nr' Message ?? Upon entry to the RBBS system the caller can be notified which was the last message he read. This does require that whenever you do a purge of the message base using RBBSUTIL.COM you do not renumber the messages. If the messages are renumbered each time than this information stored in the users file is of no use. If you plan on making use of the 'Last Message read' message then enter the correct answer to the question. This is the value for SKIP. 17. Do you want TWITS to not have entry to the RBBS Well this won't keep them out of the system unless you tag the caller as a TWIT. If you select to keep TWITS off the system then whenever the TWIT calls using the name you have TWITED from the password validation portion of the RBBS program he will be hung up on. The TWIT is given a chance to leave you a COMMENT before being droped off the system. This may make for some interesting comments from the person, but it does provide a way for them to appologise or let you know his opinions too. The drawback is that he can call in using a new name and start all over again. An alternative to TWITING is to change the password of an unwanted caller instead. This also will keep them off the system. The other advantage of setting a caller to TWIT is that he/she will not be allowed access to any functions. If you select to keep them off or just limit their abilities you can do it with this function. This is the value for TWIT$ 18. Do you want ANY caller to be able to post a MESSAGE The system can be protected from those folks who like to leave nasty or obscene messages. You can set up the system to allow only validated users to leave messages on the public board, or with this menu you can select to let anyone leave messages on the public board. You may want to allow them to CP/M but you may not want to take a chance of letting a new caller leave a public message. This is the value for LMSG. 19. Do you want veryone to have passworded entry to CP/M or just the alidated users or o one except the SYSOP or a SUPER user. Here is your chance to determine who will have access to the CP/Moperating system. Using a combination of this menu and the menu for password entry to CP/M you can create a number of va rious ways to allow or not allow entry to CP/M. E> will allow everyone to enter CP/M except a TWIT, if you have decided to require a password, then one will be required. V> will allow only validated users to enter CP/M, a password may or may not be required depending upon how you set up the CP/M entry password requirements earlier in this program. N> Will allow No One to enter CP/M at all, except for the SYSOP or a SUPER user of the system. This is the value for GOCPM. 20. Do you have a DATE/TIME file to be read by RBBS As a way of providing a Date/time function for the RBBS program, there is a section of the code that will go out and read a file from DSK$ called DATETIME.DAT. You can manually enter date and time information into this file or let the system do it each time the BYE program answers the phone. This is an awkward way to do this, but one that can be made universal from the compiled ver sion of RBBS37. If you don't have a file to be read then so indicate, and the program will work in the same old fashion as it has in the past. This is the value for DATIM$. 21. Do you want validated users to be able to SCAN and see private messages. Sometimes callers wonder why the message count is larger than what they can see on the board, or the report says there are more messages than they are able to read. In these cases the messages they are trying to read are private and they are not allowed to read them. One way to fix this is to set SCAN to YES, and this will allow validated callers to see the private messages whenever they do a SCAN of the message base. They cannot read any of them, but just see that there really is a messge with that num ber. This is the value for SCAN$. PASSWORD FILES a Discription The first password file loaded is BOOTPWD and is located on DSK$ it contains the format of Strings and variables in the following order and used by RBBS37. DSK2$, DSK3$, SYS1$, SYS2$, VERS1$, TWIT$, DATIM$ The second password file loaded is PWDS and is located on DSK2$ as described in BOOTPWD. You will also note that this file is in lower case on your system. This prevents anyone from typing this file. To view it you will need to use SWEEP or NSWP. If you have somehow managed to make it return to UPPER case, and the RBBS37 program can't find it, then use DU.COM (Disk Utility) to modify the Directory entry and revert it back to lower case. The DSK2$ file contains the following Strings and Variable descriptions in the following order. P1$, P2$, P3$, PC$, VAP$, SCAN$, BEEP, SIZE, MSYS, NNUM, HNUM, SKIP, LMSG, GOCPM LASTCALR file changes The LASTCALR file created from RBBS37 has an additional field added to the original format found in the earlier versions of RBBS. It consists of FIRSTNAME,LASTNAME,DATE/TIME information. The Date/time information may not appear if you have no way of creating the DATETIME.DAT file required by the program. RBBS35 Compatability No problem, all the files you have created from RBBS35 are compatable with the new version RBBS37. You can replace RBBS35 with RBBS37, and no one will be the wiser. Just replace the old PWDS file and run the RBBSINST, and you are ready to go. RBBS37 uses the same format for the MESSAGES and USERS files as RBBS35. JUST A FEW OF THE FILES USERS FILE: With RBBS37 you can create several levels of USERS on the system. By leaving the users unvalidated, you now have the first kind of user on your system. A non-validated user, has very limited capabilities and cannot leave messages on the board, unless you allow everyone the ability to leave messages. Next is a Validated user, this user can now leave messages, and look at other files and may or may not be allowed access to CP/M. Then there is a SUPER user, this is almost a SYSOP, but not quite, he/she can go to CP/M whenever they use the 'J' command without having to answer any question or provide a password for entry. This user when using the 'S' scan command will see Private messages on the system. They cannot read them, but will be able to see them even when the validated user cannot. In addition when a super user enters he is automatically in the Xpert mode on the command line. The last type of user is a TWIT, this user does not have any capabilities except to read messages or leave a comment to the SYSOP. Here is an example of the USER file. 6 ;Number of Users # DENNIS;RECLA;GARLAND,TX;SINNED; 2 ;SUPER user/last msg =2 ! ROBERT;HUFF;DALLAS,TX;BOBHUFF; 0 ;Verified user MIKE;MOORE;IRVING,TX;DISKDRIVE;3 ;new user/last msg=3 ! STEVE;SANDER;IRVING,TX;SUPERGUY; 4 ;Verified user/last msg =4 * BIG;JOHN;GARLAND,TX;BADGUY; 0 ;Bad Guy use * to keep out NEW;USER;ANYWHERE,TX;HELLOTHERE; 0 ;new user not verified yet REMEMBER.. If you find it necessary to modify the USERS file, be sure to correct the 'count' at the beginning of the file, and to erase the entire line. The program looks for a line length of 65 characters and if this changes the USERS file will be corrupted and in some cases made useless. HELP/NEWS FILES These files are an added feature of the program, the original RBBS35 allowed for only a NEWS file. In this expanded version you can have as many NEWS and HELP files as you want. These are set up in the RBBSINST program. In the installation you need to indicate the number of files there will be for HELP and NEWS. If you put a 0 then then RBBS37 will know that there is only one file called NEWS or HELP. In the case of a single file, the HELP or NEWS file will contain the information you want to give the caller. When it is finished typing to the screen, the caller is returned to the command line prompt. If a value larger than 0 is entered for NEWS or HELP file numbers, then the files called HELP and NEWS are the MENU for the additional files. A number request is made from that file asking the caller what file number they want to read. With only one expansion NEWS or HELP file it is a little awkward, but with two or more it works quite well. Each of the additional files are named NEWS1, NEWS2, NEWS3, etc. and it is the same for the various HELP files. A typical menu might appear as follows: --- HELP Files Available 1> Using RBBS 2> Leaving a Message 3> Using CHAT 4> Going to CP/M --- Each time the caller selects a number and that file is viewed, he will be returned to the file menu for the next selection. To exit the menu file enter a number 1 greater than the highest message number. A prompt line will indicate this whenever the value entered in NNUM and HNUM from the installation program is greater than 0. --> PARTING COMMENTS <-- As I said before this program has grown in size and linking it has become a formidable task. If you really feel that you need to modify the .ASC file and are unable to link it then send the file to my system using the XMODEM RP command and I will link it for you. Call back in a couple of days, and you should be able to download your COM file. Lost Island RBBS-RCP/M (214) 681-4789 or send the file on an 8" SSSD disk in a re-usable shipping container and $$ or postage for return mailing. Before mailing be sure to contact me via 'voice' (214) 270-1834 to get the mailing address.