OS/2 Shareware BBS: 2 BBS

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

/ OS/2 Shareware BBS: 2 BBS / 02-BBS.zip / dp004b4.zip / SYSOP.DOC < prev next >

Wrap

Text File | 1997-08-13 | 22KB | 435 lines

This document and all other documents are out of date but still include the correct installation procedures etc. The file list is also out of date. They have both been outdated since version 0.02. Good luck! ** NOTE ** If you are upgrading from version 0.01, see the UPGRADE.DOC file --- You must now run DP.BAT instead of DATAPAGE.EXE DataPage Beta 4 (version 0.04 -- Program & Design by Michael Burke DISCLAIMER The author has taken every precaution to insure that no harm or damage will occur on computer systems operating this package. Nevertheless, the author shall NOT be held liable for whatever may happen on your computer system or to any computer systems which connects to your own as a result of operating this package. The user assumes full responsibility for the correct operation of this software package, whether harm or damage results from software error, hardware malfunction, or operator error. NO warranties are offered, expressly stated or implied, including without limitation or restriction any warranties of operation for a particular purpose and/or merchantability. If you do not agree with this then do NOT use this program. A major portion of this software comes from the DDPlus Door Driver Package. The DDPlus Doordriver kit has been used for the communications, interrupt handling and some utility functions and that part of the software remains copyrighted by the authors of the DDplus Package. This game is distributed under the Shareware concept. You are allowed to operate this game for as long as you want, as long as you can find a way to work around the limitations. INTRODUCTION: ------------ This door is a BBS equivalent of WWW pages. It is not quite as versatile; however, it does allow users to maintain their own personal "DataPage", which is a directory on your hard drive containing files they upload (to a kb limit that you decide). REQUIREMENTS: ------------ At this point in time the only requirements are FILES=10 (or more) in your config.sys file and ANSI.SYS. SHARE should also be loaded IF you intend to use the game in a multi-node environment OR under DesqView. The game is RIP aware but NOT a RIP Game at this time. A FOSSIL is NOT required to run the game, although one will be supported if it exists. Automatic time slicing support is provided to most common multi-taskers as well. Files Included -------------- Below is a listing of all files for the this Game. If you are missing ANY of these files (except for the DOC and FRM files), the game will NOT function. Feel free to give out copies of the ENTIRE archive package of this game but please make sure all the files below are in that package: README.1ST - The text file you are reading. B4UASK.DOC - Self help checklist provided for sysops to ensure that they have done everything you require in order to run your door on their BBS. SYSOP.DOC - THE most important document in your distribution package! Explains how to set up and operate your door on their BBS's. BUGRPT.FRM - A standard bug report form for use by sysops. REGISTER.FRM - Tells sysops how to register your product and the procedures to be followed. SETUP.EXE - The FIRST thing you should run when you unzip it. It'll let you set up miscellaneous options. DATAPAGE.EXE - The main module! You should run this locally after editing DOOR.CTL by typing DATAPAGE /L to initialize the user data file. When it is initialized, to modify user defaults you can run: USEREDIT.EXE - The user editor/user defaults editor. CEXYZ.EXE - Default Transfer protocol. X,Y,Z.BAT - Batch Files for downloading files. X,Y,ZUP.BAT - Batch Files for uploading files. DPHELP.ANS - DataPage Help ANSI done by Nathan Fraser DPHELP.TXT - DataPage help file. DIRLIST.ZIP - Directory Lister plug-in. To install it, unzip it into your DataPage directory. DIRLIST.TXT must exist when you run DataPage but is not included with the package. Installation ------------ 1. Decompress the DataPage archive into a new directory; ie. C:\DOORS\DATAPAGE 2. Run SETUP.EXE to set miscellaneous options. 3. Edit the DOOR.CTL file with an ASCII text editor to set BBS options. The file is well documented. 4. Edit the DIRLIST.TXT file to set directories for users to use. Think of them as categories. Include NO slashes, backslashes, etc in the file, just one directory per line, up to 20 directories. Make sure the directories exist as subdirectories of DataPage. ie. the file could be just: SAMPLE EXAMPLE and you could have a C:\DATAPAGE\SAMPLE and C:\DATAPAGE\EXAMPLE directory to go with them. 5. Run DATAPAGE.EXE /L to initialize the user data file. 6. Run USEREDIT.EXE to set the new user defaults. 7. Set it up on your BBS. The commandline should be something resembling: DP /PC:\BBS /N1 (where c:\bbs is the location of the dropfile and /N1 is the node number, ie node 2 would be /N2) NOTE: This door is *NOT* yet multinode. It will work with multiple concurrent users, but only one node may transfer files (always node 1, or 2, etc... depending on what comport you set in SETUP.EXE) 8. In order to run the game program online the following parameters may be used. "/Bxxxxx" This tells DataPage to lock its baud rate at xxxxx. In order to get the most efficiency out of a high speed error correcting modem (9600 baud or above), you may lock the baud rate to a speed higher than what the caller is actually using. By locking the baud to say 38,400, the modem can compress text data that is being sent and achieve a baud rate much higher than the actual transmission rate. This will lock the baud rate at the same value for all nodes that use this command line. If you perfer a more selective way to lock baud use 'LOCKBAUD' command in the DOOR.CTL file. "/Cx" (where x is 1..4) This specifies a comport number. Some bbs software does not create door information files (dropfiles) that contain the comport number. If your bbs does have a comport listed in the dropfile then there is no need for this parameter. The default is comport 0, local mode. "/E" - Expanded Memory Specification If your machine has over one megabyte of memory, then you may have some available. DataPage can utilize EMS to improve game performance and reduce conventional memory requirements. This command will tell DataPage to use EMS memory to hold its overlay buffer. Otherwise disc area may be used to hold this buffer. This needs a memory manager and when enabled and is compatible with DESQview. Default is NOT to use available EMS. "/L" This tells DataPage to load up in LOCAL mode. This is good for testing or when a sysop just wants to "try out" the door without messing with his BBS setup. The "/L" mode will ask the user for his name and run the door in local mode. "/Nx" (where x is 1..9) This specifies a "node number". Some bbs software support multinode environments in which you must know the node number of the drop file to use. For example, RBBS-PC uses DORINFOx.DEF. If you specified "/N2" then DataPage would use DORINFO2.DEF. "/Mx" (where x is up to 2 filename acceptable characters) Used to specify one of Multiple control files. If you have created more than one DOOR.CTL file (DOOR1.CTL, DOOR2.CTL, etc.) for each node or network PC then you can select the one you want by using the /M parm. Example: "/M2" will force DataPage to use door2.ctl. "/Pyyy" This specifies the path to the drop files. For example, "/PC:\BBS" would tell DataPage to look for the drop file in C:\BBS. If this is left out the program assumes the drop file is in the current directory. "/R" To force local RIP for the sysop. Used only if the program has RipLink built in and the door supports RIP. Use AFTER the /L parameter if you are using the door in local mode. "/V" This command will tell DataPage not to show any display on the local screen. Only a colored screen and a message will be displayed. The cursor will not move as it will be turned off. Saves a little processing on multi-tasking systems. "/W" This flags the program that a network is present even though no multitaskers are detected. This is useful if the door is run on a network such as Novell that doesn't use multitaskers. COMMON ERRORS 003 File path not found. Check to make sure the game directory is correctly named as GAMEDIR. 201 Files not found. Check to make sure that all required games files are in the GAMEDIR directory. Sample Batch File ----------------- CD \DOORS\DATAPAGE DATAPAGE /PC:\SBBS\NODEx <-=- NODE number !!DO NOT USE "x"!! CD \SBBS\NODEx --> Please note that you replace the "x" with the appropriate node number. Ex: Dorinfo1.def ; Dorinfo2.def ; etc... RESTRICTIONS ON THE UNREGISTERED GAME ------------------------------------- Until the door is registered the following restrictions are in effect: a. There will be a slight delay experienced by users at the beginning of the game. b. You cannot let a user have more than 256 kb total for their DataPage directory space. c. Once you are registered any future updates can be obtained free through my BBS and my upgrades are ALWAYS easy to implement! WHAT TO DO IF THERE ARE PROBLEMS -------------------------------- Every effort is made to ensure that the door runs correctly before it leaves my BBS as Shareware. If you are experiencing problems please do the following BEFORE calling me: 1. Read ALL the SYSOP.DOC to ensure you have setup the program and have met all the program requirements. 2. Use the B4UASK.DOC as a checklist to ensure that you have not done anything wrong. Multinode use ------------- This door is *NOT* yet multinode. It will work with multiple concurrent users, but only one node may transfer files (always node 1, or 2, etc... depending on what comport you set in SETUP.EXE) Common Problems (Locked Bauds, High Speed modems, etc) ------------------------------------------------------ 1. The door does NOT require a fossil driver to run. 2. If you are running a high speed modem (9600 baud or above), then I suggest you run your bbs/mailer/doors at a locked baud rate. On high speed error correcting modems, locking the baud rate will have a noticeable increase on the speed of text that is sent. It's beyond the scope of this document to discuss configuring your BBS and mailer for a locked baud rate; you may wish to consult those docs for information on that. Here are a few things to keep in mind when setting up DataPage with a locked baud rate: a. When using a locked baud rate, I highly recommend using a FOSSIL driver. This door will work at high speeds without one though. BNU is a good fossil driver which can even be loaded and unloaded before and after you run this game. b. If you are using a fossil, then make sure to tell the fossil that the port is locked. For BNU, to lock com1: at 38,400, you would use something like "L0=38400" on BNU's command line. c. If you lock the baud for one program, it must be locked for everything. You can't lock the baud for just this door, but not your BBS/mailer. d. You may need to use the /B switch on the datapage.exe Command line to specify the locked baud rate. For 19,200 this would be "/B19200" and for 38,400 this would be "/B38400". Please note there is no space between the "/B" and the baud rate. 3. What follows is some information on possible strange situations that may occur: a. Low speed users can use the door, but high speed users get garbage. - If you are not using the DORINFOx.DEF or DOOR.SYS drop file then you may wish to find a converter program to convert whatever drop file your BBS produces to the DORINFOx.DEF or DOOR.SYS format and tell datapage.exe to use that. Several converter programs are readily available on most BBS systems. CallDoor is a good one if you can find it. I have it on my BBS for download if you need it. b. DataPage hangs up when a user enters the door. - Sounds like the door is getting the wrong baud rate somehow. Try switching over to the DOOR.SYS drop file method if possible. c. Text and screens are getting cut off. - If you are running with a locked baud, then this could be caused by some sort of FLOW CONTROL problem. Try using a fossil if you aren't already. d. If you're using something other than the DOOR.SYS drop file, then I always suggest trying to use DOOR.SYS if possible. It is the most reliable method and has had the most testing. If that is not possible try DORINFOx.DEF as an alternative. e. A door locks up node 1. This can happen with fossils or the internal communications routines because it uses the default comport of 1 when NONE is found in the dropfile or door.ctl file. To correct this make sure the right port is shown in the dropfile OR door.ctl file. f. ANSI is reflected correctly on the local screen but the user is getting garbage. Assuming the user has ANSI installed then most likely the problem is at your end. First make sure you have configured the door.ctl file to show the correct locked port rate. Second make sure the dropfile is passing the locked port rate INSTEAD of the actual conncet rate. If it is not passing the locked port rate then you may need to use a different dropfile format OR use a dropfile converter program to change the line to show the locked port rate INSTEAD of the actual connect rate. "Corrupted" data files ---------------------- It is possible that something could happen to your door data file. A power outage, door crash, or other event could damage the data files. If you get one of these messages, then the best thing to do is reinstall. CREDITS: -------- This relatively small section is just to recognize the GOOD people who have made this door a possibility. The DDPlus Team - Thanks to Scott Baker, Steve Lorenz, Bob Dalton, Andy Stewart, Tom Morgan and other contributors for that great turbo pascal door kit. If you ever want to make a door product for use with BBS's then this is the kit to get! DESQview is a registered trademark of Quarterdeck Office Systems. Doordriver kit is proprietary software by Scott Baker. Ripscript & Ripterm are registered trademarks of TeleGrafix Communications. Where to reach me ----------------- I can usually be reached at my BBS system, which should be listed in the section entitled "registration" which is below. I can also be reached via e-mail. Registration ------------ If you or your users enjoy this door, then please register it. Information on price and how to register is shown on the enclosed REGISTER.FRM. Registration will disable the delay, allow additional options and entitle you to life time support through my BBS. BBS Support includes unlimited free updates and upgrades (not like some door door authors who charge for major upgrades/updates!) through my BBS. To register this game just print out the registration form (REGISTER.FRM) file included with the door and send it with your check or money order to: Michael R. Burke 81 Walthen Drive Charlottetown, PE C1A 4T7 Canada More information is in the register.frm file. HOW TO REACH ME BY MODEM --------------------------- The Realm (Canada) (902) 892-3395 (2400 to 14400 baud) Fidonet 1:255/304 email: mburkepei@hotmail.com Reminder: You will be mailed a LETTER with your registration code. Just allow an appropriate amount of time (a week or two) after dropping your check in the mail for it to arrive to me and the code to be sent by mail back to you. If you need it sooner log onto my BBS, leave me a message telling me you mailed the registration and when I receive your check or money order I will post a private message on the BBS giving you the key code. If you do it this way please allow at least a week from the time you mail it to the time you call and get your code. If you go the BBS route you may or may not receive a key code by mail. If you prefer you can ask for the codes via email. REMINDER: No disks are sent, if you need the most current version you must call OR freq my BBS for it. Bug Reports/Comments/Suggestions -------------------------------- I have made every attempt to make sure the game is free of bugs, BUT the possibility always exists that one may have been missed by me or the playtesters. If you find a bug, or have a suggestion or comment to make which would make future versions better please print out the BUGRPT.FRM and mailer, fill it out, and send it to me. I read ALL of them and those people that lead me to find a bug or generate a better game will receive credit in the game documentation. PLEASE DO NOT NOTIFY ME OF PROBLEMS AND EXPECT ME TO FIX THEM IF YOU HAVE FAILED TO PROVIDE ME WITH THE BUGRPT.FRM AND OTHER INFORMATION I REQUIRE AS STATED IN THE B4UASK.DOC. Thank you for scanning or reading this documentation. Michael Burke, Author.