ProfitPress Mega CDROM2 Shareware Freeware (MSDOS)(1992)(Eng)

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

/ ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng) / ProfitPress-MegaCDROM2.B6I / BBS / DOORS / CAMP10.ZIP / INSTALL.DOC < prev next >

Wrap

Text File | 1991-05-29 | 15.0 KB | 384 lines

Install.doc for use with Camptown Races ver 1.0 by Kent Ogle The BULK of this file is directly from BBS Onliner Interface. Since I am using the BOI, I thought it would be best for the author of this very useful tool to explain the biggest part of it's many features. If you have designs to write doors, I suggest you seriously consider Mr. Mead's BOI. It is mainly out of respect to him, (and by his permission) that I include this file, to illustrate its versatility, not out of my own laziness in the area of documentation. QUICK INSTALLATION: Some have complained about my documentation writing for previous versions of this door, so I am adding this quick start section. There are 5 easy steps to take before you finish installation. 1. Make sure all files listed in camptown.doc are in the same subdirectory. 2. Know what type of BBS software you are running. 3. Be certain which comport you are running on. 4. Edit camptown.ctl with any ascii file editor to reflect the data for you and your BBS. 5. Read the balance of this document to determine your command- line parameters. This document is effective 12/10/90 {/// BOI \\\} BBSNOTES BBS Onliner Interface version 1.20 Copyright (C) 1990 Andrew J. Mead All Rights Reserved. Contact: Andrew J. Mead POB 1155 Chapel Hill, NC 27514-1155. or #98 @9968 WWIVnet 1:151/223 FidoNet Sections (in order of appearance) General info - what this file is Command Line Directives - what options to use /n Name switch /q Quiet mode switch /z Time Limit switch /i IRQ/PortAddress Customization switch /l Force Local Mode switch /c Communication Port Override switch /b Locked Baud Rate RTS/CTS switch /k Carrier Detect Override switch SysOp Control - who's playing this game anyway Current User Line F-10 SysOp Abort Key F-9 Line Noise Disconnect Key Specific BBS Installation 2 A.M. BBS Notes - /2 Jumper.Dat installation Auntie BBS Notes - /7 Auntie.Sys installation Force, GAP Notes - /S Door.Sys (long) installation Forum Notes - /F UserInfo.Txt installation Genesis Notes - /G CallInfo.BBS installation GT, DoorWay Notes - /D Door.Sys (short) installation ModuleX Notes - /M Number.Txt installation Opus-CBCS 1.13 Notes - /3 LastUser.BBS installation Opus-CBCS 1.14 Notes - /O LastUsXX.Dat installation PCBoard 12.x Notes - /1 PCBoard.Sys installation PCBoard 14.x Notes - /P PCBoard.Sys installation Phoenix Notes - /H Info.BBS installation RyBBS Notes - /5 CurrUser.BBS installation Sapphire Notes - /8 Sapphire.Dat installation Search Light Notes - /9 Search Light installation Spitfire Notes - /6 SFDoors.Dat installation WildCat Notes - /W CallInfo.BBS installation WWIV Notes - /4 Chain.Txt installation DoorInfo Notes - /R# DorInfo#.Def Installation: EIS-PC, FoReM, OLEcom, QuickBBS, RBBS, Remote Access, TAG, TP-Board - General Info - This file includes specific notes and examples for most BBS systems that this game runs under. A few basic recomendations: - Command Line Directives - /n this switch is only necessary for use with the /9 SearchLight switch or other BBS systems that run the game with command line directives instead of using drop files. It also can be used if you run the game locally from DOS. /q will keep the game from beeping on the host computer. This enables the SysOp to get a good nights sleep. /z sets a maximum time limit. Normally the game will allow the player as much time as he has left to play. This allows the SysOp to encourage players not to fall asleep during games. The game will execute an inactivity time-out at approximately 2 minutes. It will beep at the halfway point and then again when it returns control to the BBS. The game will auto-detect local play, so you can safely play the same door locally that the remote users play. /i allows for customization of your serial communications. If you are using a PS/2 on Com3 or above, or if you are using any non-standard IRQ/port address set-up, this option will allow you to get the game playing. This option will not interfere with the game auto-detecting local play. This option (or the /c or /l options) should not be used unless absolutely necessary. NOTE : If you think the game is being forced into local play, check the following. If a remote user is playing the game, the bottom line of the host computer will say 'Current User : User's Name or Alias here'. If the line is there, then the game is not locked into local mode. In local mode, the game never displays the 'Current User' line. /b - Locked BAUD Rate : These programs use RTS handshaking. If you are using a modem with the baud rate locked, then you will want to use this switch. '/B' implements RTS/CTS handshaking, and prevents the game from overrunning the modems internal buffer. /k turns of the games carrier detect routines. This option is a 'last resort' option. If your modem does not properly maintain a Carrier Detect' signal, the game will automatically abort. This option supresses this activity. If the user does drop carrier, the game will still do an inactivity timeout after 2 minutes. If you are forced to use this option, you probably are having hardware problems with the modem or RS-232 connector (bad pin or broken wire). - SysOp Control - Current User Line - The bottom line (line 25) on the BBSs monitor will display the name of the player currently logged on. This will not display if the game is being played locally. F-10 - SysOp abort. Pressing this key on the host keyboard will abort the game in progress, and return control to the batch file, or BBS. The user will be notified that the SysOp has terminated the session. F-9 - Line Noise. Pressing this key on the host keyboard will simulate line noise, then hang up the phone. It will appear to the user as if the connection was trashed. - 2 A.M. BBS Notes - - The /2 option reads a 'Jumper.Dat' file. For actual installation, follow the WWIV example. - Auntie BBS Notes - - This option is currently in the BETA stage. - The /7 option reads a 'Auntie.Sys' file. You will need to include the /c or /i directive with this set-up. Auntie.Sys does not tell which communications port is being used. For actual installation, follow the WWIV example. If you have documentation on this file, or possibly other files that Auntie BBS creates, please let me know. - Force, Gap Notes - - The /S option reads a 'Door.Sys' file. This is the new proposed standard for doors. This format is currently used by Force and GAP. For actual installation, follow the WWIV example. - Forum Notes - - The /F option reads a 'UserInfo.Txt' file. For actual installation, follow the WWIV example. - Genesis Notes - - The /G option does not currently work. I do not have sufficient information on Genesis' CallInfo.BBS. It seems to match WildCat's upto line 28. Line 29 should contain communication port information. If it does, use the /W directive instead. I would really appreciate some more complete documentation on Genesis. - GT, DoorWay Notes - - The /D option reads a 'Door.Sys' file. This is the same Door.Sys that is used by Marshall Dudley's DoorWay to Unlimited Doors Program. For actual installation, follow the WWIV example. - ModuleX Notes - - The /M option reads a 'Number.Txt' file. For actual installation, follow the WWIV example. - OPUS-CBCS 1.13 Notes - - This option does not currently work. - The /3 option reads a 'LastUser.BBS' file. For actual installation, follow the WWIV example. If you have documentation on this file, please let me (Andrew J. Mead, address below) know. - OPUS-CBCS 1.14 Notes - - The /OXX option reads a 'LastUsXX.Dat' file. The 'XX' is the OPUS task number; if it is absent the program will attempt to read a file called 'LastUser.Dat'. an example with a task number (hexadecimal) of 'e' would be Camptown /o0e:c:\opus\ ... the c:\opus\ tells it to look for 'LastUs0E.Dat' in the C:\OPUS\ directory. The '...' is the other command line options (check the WWIV example for a more thorough example). - PCBoard 12.x Notes - - This option is currently in the BETA stage.. - The /1 option reads a 'PCBoard.Sys' file. For actual installation, follow the WWIV example. If you have documentation on this file, please send it to me. - PCBoard 14.x Notes - - The /P option reads a 'PCBoard.Sys' file. For actual installation, follow the WWIV example. - Phoenix Notes - - The /H option reads a 'Info.BBS' file. For actual installation, follow the WWIV example. - RyBBS Notes - - The /5 option reads a 'CurrUser.BBS' file. For actual installation, follow the WWIV example. - Sapphire Notes - - This option does not currently work. - The /8 option reads a 'Sapphire.Dat' file. For actual installation, follow the WWIV example. If you have documentation on this file, or possibly other files that Sapphire BBS creates, please let me know. - Search Light Notes - - The /9 option is the reverse of the rest of these BBS switches. Since the program is being run directly by SLBBS instead of from a batch file, the current directory is the same as the BBS's directory. /9 will tell the game to get the path from the command line. c:\slbbs\games\stars\starsbbs /9 This will tell the game to get 'c:\slbbs\games\stars\' from memory. You will need to pass more information to make the game run. I have added a /n switch to read the users name. You should use the %U switch so that SearchLight passes the complete name like Andy_Mead. It should look something like /n:%U or /n%U. The next switch you should use is the /z directive to get the user's time remaining. I believe the SL switch is %M, so you should have /z:%M or optionally you can set a specific time limit (i.e. /z:20). The final piece of information need is communication port. My games use /c and SL uses %P. Therefore /c:%P should fit the bill. A final example (check elsewhere for description of /q ) would be c:\slbbs\games\mad\madness /9 /n:%U /c:%P /z:%M /q The spaces between switches is mandatory! - Spitfire Notes - - The /6 option reads a 'SFDoors.Dat' file. For actual installation, follow the WWIV example. - WWIV Notes - - sample WWIV installation WWIV,chain.txt directory - C:\WWIV batch file - camp.bat stars.bat directory - C:\WWIV\GAMES starsbbs.exe directory - C:\WWIV\GAMES\CAMP camp.bat listing echo off cd c:\wwiv\games\camp camptown /4:c:\wwiv\ /q /z:20 cd c:\wwiv chainedit setting file - c:\wwiv\games\camp.bat dos interrupts - off, this game handles it's own communications shrink - doesn't matter - recommend NO ansi - required allow 300 bps users - recommend NO - If you are NOT using WWIV then substitute your BBSs switch for '/4'. - In WWIV mode, the current user line will also display user's number and real name. - DoorInfo Notes - - EIS-PC, FoReM, Professional OLEcom, QuickBBS, RBBS, Remote Access, TAG, and TP-Board. - If you use RBBS (or another DorInfo generating BBS), you will need to let the program know what node the program is on. If you use /R by itself, the program will look for a file called DoorInfo.Def. /R1 will look for DorInfo1.Def, /R2 will look for DorInfo2.Def, etc... A sample command line for node 1 would be: camptown /r1:c:\rbbs\ /z:35 /q where the program looks for DorInfo1.Def in c:\rbbs. {/// I suggest copying the drop file to the camptown subdirectory, and then deleting it at the end of the game. I have had mixed reports with setting the search path in the command line, although I know of several boards being able to utilize it, it CAN BE a difficult process to implement. If you have trouble getting Camptown up and running, try this. K Ogle \\\} BBS Onliner Interface Copyright (C) 1990 Andrew J. Mead - All Rights Reserved. The Mad Programmer - Brown & Mead Consulting POB 1155 Chapel Hill, NC 27514-1155 Camptown Races Copyright (C) 1991 by Kent D. Ogle 909 West 1st Webb City, Mo 64870 Support Board : The PC-Depot, Scott Stuart, sysop fidonet 1:286/777 (417)624-3815 HST Dual Standard (please register!)