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 / RBBS_PC / RBBSDOCS.ZIP / RBBSDOCS.2 < prev next >

Wrap

Text File | 1990-11-05 | 32.6 KB | 650 lines

INSTALLING RBBS-PC 2-1 2. INSTALLING RBBS-PC --------------------- RBBS-PC is a powerful application that may take months to master fully, but gives those who stick with it a practically ever expanding power as their knowledge and needs grow. But it is not necessary to understand everything or take advantage of all its power, before it can be set up initially, or used. This section is intended to provide a step-by-step approach to setting up RBBS-PC. Follow the steps thoughtfully! Do not proceed to subsequent steps until you understand all the previous steps. Our goal with persons getting started with RBBS-PC for the first time is to get them off to a fast start by (a) bringing up the software to see how it runs, and (b) getting the software to be able to answer an incoming telephone call. A BBS strongly reflects the interests and personality of it's SysOp, and RBBS-PC is one of the most flexible and customizable of the BBS's. However, for those who are NOT familiar with electronic bulletin board systems in general, a good introduction to installing RBBS-PC is contained in the book "Electronic Bulletin Board Starter Kit" by Charles Bowen and David Peyton, published by Bantam Books. The book does in 436 pages what the next few pages attempt to do. It is a superb guide for someone who has never setup a bulletin board system or is not knowledgeable about PC or asynchronous communications. The book comes complete with an extensive index as well as a copy of RBBS-PC Version 15.1C and, of course, the associated source code. Since all versions of RBBS-PC are upward compatible, this book serves equally well as a guide for the uninitiated to all subsequent versions of RBBS-PC. This book guides the potential SysOp in easy stages from unwrapping the two diskettes that are included with the book to operating the more advance features of RBBS-PC. The book was published by Bantam Books in August of 1988, ISBN 0-553-34552-4, and can be found in most technical book and computer stores. It addresses the topic of installing an electronic bulletin board system in a far better way than this "Technical Reference Guide" does. Because RBBS-PC attempts to provide SysOps the maximum flexibility, it is perfectly possible for those setting RBBS-PC up for the first time to shoot themselves in the foot. Be patient with yourself. Remember that things worth achieving usually are not obtainable without effort. 2.1 First Time Installation --------------------------- Do not try to do everything at once. Keep things simple and proceed patiently, a step at a time, putting only one thing in place. The files you need are the executables (RBBS-EXE.ZIP) and system text files (RBBS-TXT.ZIP). RBBS-PC comes completely set up, ready to run. To take advantage of this set up, you must do the following: 1. Create a new subdirectory on the hard drive of your computer. "RBBS" is a suggested name but any can be used. The DOS command to make the directory is "MD \RBBS". 2. Copy the zipped files into the subdirectory. You must have at least RBBS-EXE.ZIP and RBBS-TXT.ZIP. The DOS command to copy is "COPY <from> <to>", e.g. "COPY A:*.ZIP C:\RBBS". 3. Make the subdirectory you created your current one ("CD \RBBS"). RBBS-PC 17.3A TECHNICAL REFERENCE MANUAL 2-2 4. Unzip the files using the command "PKUNZIP -d *". You need to obtain a copy of the program "PKUNZIP.EXE" to do this. Subdirectories will be created off the current directory. 5. Enter the command: INSTALL. This program will check the directory structure, and inform you if any files are missing or misplaced. It also makes sure the RBBS-PC configuration matches your system. The file INSTALL.LOG will contain information about files the install procedure could not find, or had to move. While many of the files are OPTIONAL, consult this log if you later encounter problems running RBBS-PC. You are now ready to run RBBS-PC! RBBS-PC comes with a sample configuration file, and small but empty users and messages file. To bring up RBBS-PC, at the DOS prompt, type RBBS[Enter] where "[Enter]" means to press the "Enter" key. RBBS is a batch file that runs RBBS-PC, and also controls certain RBBS-PC maintenance functions (see section 13 for details). In this first run, RBBS-PC does not to wait for a telephone call to establish communications through a serial port, but just runs as a local application, communicating with you through the screen and keyboard. You should see a copyright notice first, then a "WELCOME TO RBBS-PC", a short message about a "prelog", and then be asked "What is your First Name?" What you see on your screen beginning with the "WELCOME" is exactly the same as a remote caller on the telephone line would see. Instead of your real name, enter SECRET NAME[ENTER]. This is the "secret SysOp name" for the sample system. Next, answer the questions RBBS-PC asks you and look around. Your only goal at this point is to make sure that the software runs on your computer. The next goal is to get RBBS-PC to answer an incoming call. This requires a functioning communications port, modem, and telephone line, as well as more configuration information in RBBS-PC. There are five things you must normally do in preparation: (1) Set the RBBS-PC modem commands properly for your modem, especially the modem initialization string and firmware initialization string (See CONFIG parameter 225). (2) Set the hardware switches on the modem properly, but some modems, especially "internal" modems, may have no hardware switches. (3) Set the communications port to what the modem is using (see CONFIG parameter 221). (4) Initialize the modem's firmware. This makes permanent the settings that RBBS-PC needs (see CONFIG parameter 231). In the best of all worlds, the factory settings of the modem are what RBBS-PC wants and RBBS-PC's default settings work, so that nothing at all must be changed. This is normally the case for the USR Courier 2400 modem. Your key to setting everything up is the RBBS-PC configuration program called "CONFIG.EXE". CONFIG is your guide to configuring RBBS-PC for your preferences and environment, and basically is just a smart editor for INSTALLING RBBS-PC 2-3 setting up RBBS-PC. RBBS-PC stores its configuration parameters in a file called "RBBS-PC.DEF". To edit configuration file RBBS-PC.DEF, just type CONFIG RBBS-PC.DEF[Enter] You will see a copyright notice, CONFIG will read in the current values, and then you will see a table of contents for the many pages of parameters you can set. There are over 300 parameters you can set in RBBS-PC, which can be extremely complex. Most you will never change, but RBBS-PC has tremendous power and flexibility if and when you do need it. You can just press the page down key "PgDn" to see the many screens of parameters, if you want to browse. Do not be intimidated. RBBS-PC, as shipped, has nearly all of these parameters set for you. For more information, read section 10. Once you have set the modem parameters in CONFIG, and saved your changes, you are ready to make sure that RBBS-PC will answer incoming calls. Be sure you have your modem connected and on. Then type RBBS[Enter] You should see a copyright screen. RBBS-PC will draw a screen with boxes. The modem lights should flash, and RBBS-PC should display "Ready for Calls" in a box. Four lights on an external modem will normally be on: High Speed (HS), Auto Answer (AA), Modem Ready (MR), and Terminal Ready (TR). Ideally, you have a second computer beside the first with a modem and telephone line that you can use to call the BBS. Otherwise, have a friend with a computer call it. You need to call with a modem to make sure that the two modems will talk. When the call comes in, the Ring Indicator (RI) should blink. Then the Off Hook (OH) and Carrier Detect (CD) lights should come on as the modems link. And RBBS-PC should chip in with its opening "WELCOME TO" line, and the send (SD) and receive (RD) lights should blink periodically. If the lights blink but you see nothing, you may need to turn on "snoop" so you can see the session on your local terminal. Press F9. If that doesn't do anything, press it again. After the caller says "Goodbye", RBBS-PC should recycle, the CD and OH lights go off, and the box reappear that finally says it is again ready for calls. Once you have RBBS-PC answering calls, you are ready to begin customizing the board, setting it up the way you want, and adding features. You need two primary tools: CONFIG.EXE (part of the RBBS-PC package), and a full screen editor (which you must supply). You need what is called a "programmer's" editor versus a word processor - one that only puts in what you type and never inserts any hidden or special characters - what is sometimes called as straight "ASCII" editor. Here we will walk you through what is behind what the caller sees on logon. The first message is "WELCOME TO " followed by the name of the board, as specified in CONFIG parameter 12. Next the file PRELOG is displayed. This file need not be present, and generally should be brief, as it is displayed on every call. Callers are then asked to identify themselves, by answering the question "What is your FIRST name?" The text after "your" can be set up with CONFIG parameter 45, though most SysOps do not change it (e.g. "What is your ACCOUNT ID?"). The next question is "What is your LAST name?", which can be set in parameter 46. RBBS-PC 17.3A TECHNICAL REFERENCE MANUAL 2-4 If the caller is not in the user's file, which normally means that this is a new, first time caller, then RBBS-PC displays the text file called NEWUSER. Here you should explain the board and the rules you have for people to follow. Callers next see a welcome specific to their security level, called a "logon level greeting file". These files take the form LGnn.DEF, where "nn" is their security level (e.g. level 10 callers would see the file LG10.DEF, if it is present in the default directory). Then, a general "welcome" file is displayed. The general welcome file shown to the caller can be changed "on the fly" by RBBS-PC, dependent on what sort of Graphics option the caller has selected. SysOps often use this for an ANSI log-in screen. There are many other things in RBBS-PC you will want to set up, such as bulletins, news, and conferences. Just remember to take your time. RBBS-PC almost always runs the FIRST time. Make one change at a time and then test it so you don't break something that once worked. 2.2 What's New In 17.3A? ------------------------ 17.3A is a maintenance release for 17.3. Over 100 changes were made to the code. The most significant are: (a) increased reliability, eliminating the following problems: - occasional constant recycling with "connect timeout" - overflow error when modem not working right - untrapped errors, when FMS directory wrong and when trashcan file not set up properly - possible infinite loop in FMS search - possible incorrect modem initialization in CONFIG - problems with execution of external events after 9pm. (b) autodownload now works properly (c) problems with macros were fixed, including repeat of prompts, double execution of a macro, assigns sometimes getting wrong values, problem with block print, problem with PUI's, and macros associated with a protocol not being executed. (d) problems fixed with doors include individuation not restored, doors need not be listed on the menu if in DOORS.DEF, the registration door will respect DOORS.DEF, and bytes downloaded is now right dooring to external protocols. (e) problems fixed with messages/conferences include mail waiting in a conference view works properly for the conference you are in, message display can be paused and interrupted, searches on subject work right if subject not in upper case, TABS works in message entry, person with SysOp status does have mail to SysOp listed in mail scan, public name of SysOp recognized as SysOp, no longer says receiver will be notified of new mail when not in user's file, join to main works in conference view function, support added to allow names to have a netmail address ("@ <node>" on end), and subject prompted for in message entry after a canceled comment to SysOp. INSTALLING RBBS-PC 2-5 (f) problems fixed with the callers log include time logged on is not right when join conferences, and more information is included for local users. (g) Features were added to the Fast File Search to better support macro processing (see section 12.9). (h) The documentation was also rewritten in 17.3A. Many new examples and explanations of features were added. (i) The conference V)iew command now resumes any listing after the last conference listed, rather than restarting at the top each time." Previously, version 17.3 of RBBS-PC added the following enhancements: (a) Search for a file's existence on upload and download has been vastly speeded up. Based on an indexed binary search of a sorted list of file names. (b) Data base function to forward search (jump to a line containing a particular string and continue from there) was added for all file and text displays (c) NEWS facility that automatically displays news since last on to callers (d) Callers can now stack commands to virtually any depth, and stacking is consistently supported everywhere. (e) Modem commands can be selected based on modem model. (f) Users may now FORWARD their mail to another user. SysOps or users having sufficient security to edit a message can forward it to anyone as well as change anything in the message header. (g) The MSG header Security change now allows the SysOp to change ANY field in the header. (h) When reading mail, the SysOp can instantly edit the USER record of the message sender, then return to reading. The specific enhancements added include: (1) When you have insufficient time to download all the files requested, RBBS-PC will inform you of the files omitted but try to download what there is time for instead of canceling the entire download request. (2) Timelock message now shows minutes & seconds left in time lock. (3) Command stacking now supported consistently and to virtually any depth. (4) Autopage message less stiff and formal when caller notified that SysOp wanted to know caller logged on. (5) Chat time given back when SysOp initiates chat and no longer counts against session time. (6) Conference name added to message header. RBBS-PC 17.3A TECHNICAL REFERENCE MANUAL 2-6 (7) Support for new ZIP imploded compression. (8) NEWS facility added. Special bulletin displayed automatically on logon when updated since user last on. (9) Message quoting first gives the edit command prompt but tells how to continue adding to a reply. (10) Default extension automatically added to uploads and downloads when no extension is specified (11) Forward search added to all directory displays and text file displays (12) Delays and embedded returns can be put into modem control strings. (13) Caller shown on welcome line if connection is reliable (14) SmartText can control whether substituted value is inserted or overlaid (15) SmartText can control whether substituted value is trimmed of leading and trailing spaces first (16) Caller is informed when session time is shortened because of an external net mail event. (17) Can use "s" for since last listed on file N)ew command (e.g. "n s u" for list new files since last on in upload directory). (18) When replying to a message, will automatically continue if person sending mail to is not in the user's file, rather than asking the user whether wants to re-enter name or continue. (19) Macro questions can have edits forcing answer to be one of a list or between two values. (20) Protocols to be used to download and upload can be specified anywhere in stacked command line rather than just on end. (21) File searches on up and downloads have been vastly speeded up. Makes a huge different on slow devices like CD-ROMs. Also, have ability to trigger OFF LINE processing for files elsewhere. (22) CONFIG gives option to set modem commands based on modem model. Uses external file MODEMS.SET in default drive/path. Makes RBBS-PC much easier to set up. (23) SysOps can now track UL/DL's and have a "free download" period. (24) SysOps can now explain exactly what a REGISTRATION EXPIRES means. The HELP file RGXPIRE.HLP is seen when a user is warned, and RGXPIRD.HLP is seen when RBBS-PC reduces a caller's access. (25) Support for 38,400 bps, but only through Fossil drivers. (26) Can have multiple extensions searched when trying to detect duplicate on upload (new CONFIG parm 169). INSTALLING RBBS-PC 2-7 2.3 Upgrading To 17.3A ---------------------- 17.3A is virtually "plug compatible" with 17.3. You need only: - replace RBBS-PC.EXE and CONFIG.EXE with the new versions - add the new help file "HELP07" to your other help files - in parameter 225 of CONFIG, add "AT" in front of your firmware write command - replace your MODEMS.SET with the new one - replace MENU5C, for doors, with the new one (edit in your door names), unless yours is not based on the standard one When upgrading from a version PRIOR to 17.3, follow these steps: 1. Do not destroy or overwrite your old files. You may run into difficulties and have to fall back to the old version. Especially keep a backup of your current USERS, MESSAGES, configuration "DEF" files, and your RBBS-PC.EXE and CONFIG.EXE files. 2. Start by trying to get the new version just to run equivalently to the old without implementing new features. Implement new features one at a time. Do not try to implement everything new at once. 3. The file that almost always changes between non-maintenance versions is a configuration "DEF" file. A utility program called RECONFIG.EXE is provided that converts all versions from 14.1D on to the latest. This will save you the trouble of manually re-entering the parameters. If you do not have RECONFIG you should print out all the options you selected on your current RBBS?PC.DEF file. 4. CONFIG.EXE has an option to review the parameters changed since the last version. You should always run this to see what is new and possibly change the values. If you do not have RECONFIG, you generally need to delete your current RBBS?PC.DEF file and manually enter the parameters. Sometimes, however, the same parameters will be in a different place in the new configuration. If you are upgrading from several versions back, there is no simple way of knowing what all is new. 5. The MESSAGES and USERS files are the two that are most important to continue to be able to use. RBBS-PC 17.3 is compatible on both accounts with files at least back through version 14. However, there is a critical parameter to set in CONFIG: the minimum security to auto-add a user to a conference. This applies to conferences not sub-boards, i.e. that have no configuration DEF file. Go into CONFIG, conference mode, and then check this value. No one will be able to join the conference if their security is below this number, even the SysOp. Reset this value so that the desired callers can join the conference. 6. RBBS-PC is written to be upward compatible, preserving all the functions of earlier versions. However, you may have to make changes to the new configuration to make it run equivalently. If upgrading from 17.2x, you need to consider the following: (a) replace RBBS-PC.EXE and CONFIG.EXE RBBS-PC 17.3A TECHNICAL REFERENCE MANUAL 2-8 (b) If you want file a)ll to list multiple physical directory files (as opposed to say just the FMS master file), then you must set up RBBS-PC differently (see CONFIG parameter 218). (c) If you turned on "enforce ratios", but exempted all security levels (this tells RBBS-PC to track, but not restrict, downloads), you must change the ratio (parameter 9 in PASSWRDS) to -1 in order for the code to work equivalently. Similarly, a ratio of 0 will not even COUNT the downloads. (This allows "free" periods of downloading to be specified.) 7. If upgrading from 17.1, you need especially to consider: (a) the minimum security to read and kill all messages. If this is set to 0, everybody can read everyone else's mail! (b) RBBS-PC formerly supported the "arc" format exclusively. Now "zip" is its default, but it can be set up for any. Review the parameters for default extension and archiving command. (c) Your personal directory may not work unless you include a drive/path. Re-enter the parameter value in CONFIG. 6. If you are upgrading from a version prior to 17.1, consider the possibility that the PASSWRDS file may have a different format, that external protocols are controlled by an external table (PROTO.DEF), that the doors interface may be different, and the control for an timed even may be different. See section 10 for information on these CONFIG parameters. 9. Use the new text files, especially the menus and help files. If you have customized versions of these, start with the distributed files and change them. 10. Review the documentation on the major areas of enhancements. Section 26 on the history of RBBS-PC briefly reviews the enhancements in each version of RBBS-PC. Some specific things that you want to take advantage of include: (a) Macros and SmartText have been significantly improved in 17.3. You no longer need to include a "{ST" at the end of macros and will probably want to omit it. You may want to enhance your menus as well. See the revised sections on SmartText and Macros. (b) You may want to make file searches faster and reduce the wear on your hard disk by installing the fast file search system. See section 12.9. (c) You may want to create a new category of system bulletins - a NEWS facility (see section 7.13). The major changes in 17.2A were: (a) use of shelling triggered by the presence of BAT files to test uploads for integrity, convert uploads to a different format, and support viewing of text files inside ZIP files, and verbose list any compressed format, INSTALLING RBBS-PC 2-9 (b) greatly enhanced macros and questionnaires, including new data base functions, (c) enhanced doors interface, including an external control file for doors (DOORS.DEF) as well as the ability of a door to request that RBBS-PC change the user record (DOUTx.DEF), pass any information via command line or a file to a door, and for a door to return information to be displayed to the caller (d) the message files can be configured to have minimum size to hold the messages and let grow in size as new messages are added, (e) conferences and sub-boards can be configured to automatically change the user's security to match the logon security, (f) message quoting, allowing the option to type in be the same on different submenus and be a single keystroke, speech synthesizer support for visually impaired SysOps, making uploads immediately shareable on Novell networks, an easy way to give a conference moderator access to all mail without having to make them SysOps, chained FMS directories, and more. PLEASE NOTE!!!!! ---- 17.3 does NOT change the structure of the user, message, or DEF files from that in 17.2. 2.4 Common Problems Encountered Installing RBBS-PC -------------------------------------------------- IT CONTINUALLY RECYCLES! This can have several causes. RBBS-PC requires that a modem be attached to your communications port. Therefore: - check what communication port is being used. - verify that this communications port exists. - verify that your modem is attached to it. - verify that your modem is powered up. - verify that your modem is configured properly. - verify that CONFIG knows what kind of modem you're using. - verify that the modem cable supports all ten signals required by RBBS-PC (see Appendix F). - verify that DTR (Data Terminal Ready) and CD (Carrier Detect) are set to "normal" rather than always "on" (sometimes called "true" and "forced" instead). - verify that each DOS subdirectory referred to in CONFIG exists. - verify that RBBS-PC runs properly when set up to use COM0 (i.e. a local workstation). If, after all of the above has been attempted, the problem still persists, try deleting your MESSAGES and USERS files and re-run CONFIG to create new ones. Finally, having exhausted all the above remedies, the system continues to continually re-cycle, you may have an incompatible "clone" PC, incompatible DOS, incompatible modem, and/or a bad copy of RBBS-PC.EXE. IT WON'T ANSWER THE PHONE! This also can be caused by one of the following things: - Phone line is not plugged into the modem. - Modem is not powered on. RBBS-PC 17.3A TECHNICAL REFERENCE MANUAL 2-10 - Modem is not connected to the communications port that RBBS-PC was told to use. - Your modem switches or firmware is not set (see CONFIG parameter 231). - Your modem is not "Hayes compatible" enough to handle the modem commands described in section 11. - Your modem cable does not have Pin 22 connected. There are two conditions under which RBBS-PC does not require Pin 22 in the RS-232 cable to reflect the status of "ring". RBBS-PC does not require Pin 22 to be hooked up on the RS-232 cable (that's the cable which runs between the modem and the computer, by the way), if you specify in CONFIG that RBBS-PC is to answer the phone on zero rings, and that it is not a "RING-BACK" system. In this setting RBBS-PC will initialize the modem so that the modem AUTOMATICALLY answers the phone. RBBS-PC also does not require Pin 22 to reflect the status of ring when your modem returns the result code "RING" as the phone is ringing. The default setting for RBBS-PC is that it depends on either Pin 22, or the modem result code "RING", to know when the phone is ringing. This is because RBBS-PC, and NOT the modem, answers the phone. When RBBS-PC is informed by the modem that the phone is ringing, it counts the rings by issuing the "ATS1?" command. When the number of rings has reached the number you told CONFIG you wanted to answer after, RBBS-PC sends the "ATA" command to tell the modem to answer the phone (see section 11). If your modem does NOT send the characters "RING" each time the phone rings, you will need a cable with Pin 22 connected. Some computers (such as the PCjr's external RS-232 interface) and some modem cables don't have a "ring-indicator" signal. Pin 22 is the ring indicator coming from the modem going to the computer. And just because you bought an RS-232 cable, don't assume that it has Pin 22 connected. This is often not the case. IT LOCKS UP MY SYSTEM! This may be caused by one of the following things: - The .EXE file generated by the BASIC compiler is incompatible with either the DOS that you are running (i.e. it isn't IBM's PC-DOS), or other software you load into the system prior to running RBBS-PC (such as a device driver loaded in CONFIG.SYS, or a TSR program loaded in your AUTOEXEC.BAT file). Remove all non-essential memory resident software. - You indicated in CONFIG that you were running one of the supported networks (i.e. CORVUS, MultiLink, Orchid, etc.), but you aren't. - You are running on a COMPAQ DeskPro, or using an add-on board that uses the unused IBM DOS interrupt 7F hex, and should have used CONFIG parameter 29 to indicate you are using a COMPAQ PC. - Your modem isn't set up correctly, probably not supplying us with "true" carrier detect (i.e. the modem tells us that a caller is connected when that's not true). Try selecting "Hayes 2400 compatible" as the modem type in CONFIG, and use parameter 231 to re-program the modem's firmware. - RBBS-PC is trying to log to a printer that does not exist or is not turned on, or out of paper, and no error condition is ever being returned back to RBBS. In CONFIG, tell RBBS-PC to turn the printer off after each recycle (parameter 52). INSTALLING RBBS-PC 2-11 - Your system does not support standard DOS system calls for screen writes. Try setting CONFIG parameter 39 to use BASIC for screen writes. - Your system is not as PC compatible as it should be and may use strange interrupts. Try turning assembler routines off (parameter 38).