SYSOP DOCUMENTATION FOR DOORS for the IBM Personal Computer Version 02-88 and higher by Bob Westcott 7 Dunloggin Drive Merrimack N.H. 03054 Voice (603) 424-6977 Data (603) 424-5497 Feb, 1988 Whats new in this version of Doorware: No longer have to sign on the BBS first to go to local mode. Should work with all versions of RBBS 15.1C and above. Should work with all versions of QuickBBS 2.0 and higher. 1.1 Introduction ---------------- Doorware is the name I have given the type of software that I make to operate on the RBBS type of BBS. I try to make the software as error free as possible but "Murphy" is always there so if you run into errors please call via voice or leave a message on my BBS and I will try to have them fixed on the next version. If you have any software that you think will make a good door I am always looking for that type to convert to Doorware. To do this the code must be in basic SOURCE. I do not release the source code without the authors permission and then only the code as I receive it. Credit for the software is ALWAYS given to the author (if know). Because it is very possible to cause a security problem on the RBBS (people being able to get into your DOS) the door part of the source will not be made available. I will help anyone who is interested in the way you write software to work on the 'Doors'. Also I have been writing code for over 15 years and the first 10 I always release my source code, but as it always went someone would change some code (Really trying to improve it) and blew it and since I always have my name, address, and phone number on my software it always came back with with what a bad program it was and it doesn't work correctlly and I got a bad name. So I no longer give out code. The software is able to handle multi-tasking under Multi-Link and Double Dos, but is limited to 9 nodes. 1.2 Update Conventions ---------------------- Since new versions should no longer be necessary when when either a new version of RBBS or QuickBBS the only updates will be to make improvements and new software. The convention of showing versions shall be as follows: xxxxyyzz.ARC Where xxxx is the first 4 letters of the software. Where yy is the month of release. Where zz is the year of release. The latest version of the Doorware will always be on my BBS and other selected BBS. 2.1 Required files ------------------ You must have a batch file that you are running your RBBS from. The purpose of the files are as follows: 1. filename.EXE The operational software. 2. filename.DOC The file which informs the player who what when and where about this program. 3. filename.SCR This is the daily score board, but it is also the file that holds your system requirements. Not all programs use the score part of this file 4. filename1.SCR This is the monthly score board. Not always used but always created. 5. filename.BAT The batch file that gets you to the doorware from the RBBS. DO NOT USE THE SAME FILENAME AS THE DOORWARE NAME. THIS WILL CAUSE A PROBLEM!!! 5. SYSOP.DOC This file. 6. PRELOG.xxx The same as on the RBBS it allows you to place notices on the system. xxx= the 1st three letter/numbers of the program. 7.filenameG.DOR This file is not required but will allow you to make a graphic picture with sound. ********** NOTE ********** If you are going to use this software with the Door monitor do NOT use the batch files as stated in this record. Use only the batch files as stated in the monitor SYSOP.DOC. 2.0 Setup --------- Because this software reads information from the RBBS files it is very important that the supplied files MUST be placed on the same drive that the DORINFOx.DEF is located. You must make the changes you want on following information in the 1st 8 fields of the filename.SCR file: 1. Field #1 The number of times the user may sign on to filename each day. (This does NOT apply to SYSOP he may sign on as many times as he wishes) 2. Field #2 The foregound color. 3. Field #3 The background color. 4. Field #4 The border color. 5. Field #5 The number of minutes a player is allowed without making a move. 6. Field #6 The total number of minutes allowed on this door. 7. Field #7 This field determines if you are going to use a common file for all games or a single file for each game. See ** for more info about this. 8. Field #8 This field determines if SYSOP score will be used and if there will be sound as follows. 0 Sysop's score posted, No sound. 1 Sysop's score not posted, No sound. 2 Sysop's score posted, With sound. 3 Sysop's score not posted, With sound. ** This field is used as follows if set to '0' it means a file called filename.DAY will be created and will list all the users that has signed on THAT day to THAT program and will be used by field #1 to determine how many times a user has signed on THAT day. If this field is set to a '1' then a file called COMMON.DAY will be created and will have all the users that have signed on to any program that has this field set to '1' to be logged. Example: You are running 3 games, GAME1.EXE, GAME2.EXE, and GAME3.EXE. You have field #6 set to '1' on all programs and field #1 set to '2' in all programs. The user will only be able to sign on to any of the games 2 times (total) each day. If all 3 programs have field #6 set to '0' then the user may sign on to EACH program 2 times each day. Beware this fields may be mixed and will act as listed and mix things up quite well, SO keep it as simple as possible. Remember this feature will only be true if the door software you are using will allow this, all my software EXCEPT CHESSDOR will have this feature. The filename.SCR file will create itself if it can not find one. It will set the all starting scores to 0. If you wish to start at any other score you can use EDLIN to change them, but remember to change them EACH month as they will be reset to 0 with the first user each month. DO NOT TRY TO CREATE THIS YOURSELF AS IT CAN BE MESSED UP AND CAUSE ERRORS. The filename1.SCR file is very simple and will create itself if one can not be found. This files holds the monthly champ information, but will NOT be outputed until the first monthly champ is created. The last entry of the filename.BAT is the file that the RBBS calls to bring up the door program. The following will work for both tasking and NON-tasking systems. ----------------------------------------------------------------- (The filename.BAT file ) WATCHDG1 OFF To allow around program to monitor line (a must!!) filename %1 Call the door program. The door menu file must have the filename in capitals. Do NOT remove the 'WATCHDGx ON' call from the RBBS.BAT files as they are needed when you go to your DOS from remote (7 from the main menu). You may now use the same door menu file for the nodes as RBBS now passes the node information to the batch files. QUICKBBS: Set up to have function 7 call: filename 1 ' for users filename ' for local 2.3 Running the Doorware program -------------------------------- After completing the setup as stated above insure that when running the CONFIG file for the RBBS that you have the doors open and allow the correct access level users to use the doors that you want. Also insure that the RBBS answers on ring 1 or higher. That is all that is needed to make this work in remote. To run in local just be on the drive where the program is located and type the name of the program. While watching the screen when a remote user is on a door you will see the users name is in the lower left corner of the screen, in the middle will be the version # of the Doorware program that you are using and the node that is operating, and on the right side you will have displayed the time the user started using the the program when the program is first loaded (15:23:47) then it will display the number of minutes the user has left in the doors (M.L.= 23:42). Also when the remote users screen does a clear yours will NOT it will just print (CLEAR SCREEN). The purpose of this is to keep the 25 line on your screen and clear to remote users screen. The following two paragraphs are only true when using NO multi tasking or when using Double DOS. Pressing the function #10 key while a remote user is on the system will place you in the chat mode and allow you to talk with the player. To return the player to the game you must press the ESC key this is the same procedure as on the RBBS. The player does NOT have a function on his menu to call you. Pressing the function #8 key allows you to reduce or increase the time the player is allowed to stay on on this one time. You will get a prompt for the number of minutes you wish to let them have then you enter a number and press enter. This will cause a message to be place on the screen to inform the player that the amount of around has changed. So you got a problem!!! ----------------------- If you have a problem installing this program or it bombs on you look for the following data: 1. A printout displayed on your screen telling you the problem. 2. Look on the disk that holds the main DOR program for a file named ERRORS.DOR and print it. This info should be forwarded to me for debuging and correction. In most cases (all I hope) one of the 2 above indications should happen when a error occurs. All errors should be reported to be via phone or RBBS if possible for correction. Good luck and enjoy this software. Bob... Bob Westcott 7 Dunloggin Drive Merrimack N.H 03054 (D)ata 603-424-5497 (V)oice 603-424-6977 ill place you in the chat mode and allow you to talk with the player. To return the player to the game you must press the ESC key this is the same procedure as on the RBBS. The player does NOT have a function on his menu to call you. Pressing the function #8 key allows you to reduce or increase the time the player is allowed to stay on on this one time. You will get a prompt for the number of minutes you wish to let them have then you enter a number and press enter. This will cause a message to be place on the screen to inform the player that the amount of around has changed. So you got a problem!!! ----------------------- If you have a problem installing this program or it bombs on you look for the following data: 1. A printout displayed on your screen telling you the problem. 2. Look on the disk that holds the main DOR program for a file named ERRORS.DOR and print it. This info should be forwarded to me for debuging and correction. In most cases (all I hope) one of the 2 above indications should happen when a error occurs. All errors should be reported to be via phone or RBBS if possible for correction. Good luck and enjoy this software. Bob...