Fido's Complete Operating Manual Page INSTALL-1 Table of Contents Introduction to Fido ___________________________ Page 2 Getting it all together ________________________ Page 4 Step 1: Setting Up Message and File Areas ______ Page 5 Step 2: The Environment ________________________ Page 7 Step 3: Starting Fido __________________________ Page 10 Step 4: Setting Up Areas _______________________ Page 11 Completing Installation ________________________ Page 14 System Messages and Bulletins __________________ Page 15 Making a Public System _________________________ Page 16 Semi-Private (Restricted) Public System ________ Page 18 Making Fido a Private System ___________________ Page 19 Changing Command Privilege Levels ______________ Page 21 Hints and Tips _________________________________ Page 22 Files Section Organization _____________________ Page 24 Command Line Switches and Setting Time Limits __ Page 27 HELP Files _____________________________________ Page 30 Installing the Modem ___________________________ Page 31 Commanding the modem: FIDOMDM.BBS ______________ Page 34 Specific Computers and Modems __________________ Page 35 Specific Modems ________________________________ Page 36 Modem Problem Determination ____________________ Page 39 Install Index __________________________________ Page 40 Fido's Complete Operating Manual Page INSTALL-2 Introduction to Fido If you are really lucky, this manual will help you create and customize a Fido Bulletin Board system to your liking. If you are not lucky, you will become hopelessly lost and confused. This manual covers installing and operating the software itself. If you are attempting to become part of the world wide FidoNet, please contact a FidoNet sysop who is currently in the net. The problem is that since it's inception in May 1984, the basic net organization has changed radically, every few months, and all attempts at putting down information in a such slowly changing text such as this is hopelessly outdated by the time it reaches your hands. To get information on the current FidoNet, contact Fido 125/1 (formerly known as Fido #1) and look for the latest Fido History document, or other related files. As an example of the problems involved, when the Third Edition of this manual was distributed in November 1984, there were 50 or so FidoNet nodes in the US, in a simple amorphous network; today (Aug 85) there are over 350 systems in the US, Canada, England, Sweden, Holland and France, in a multitiered tree shaped network. So much for putting dynamic information is a static place as this. Fido is a software system, not just a single program. Besides the program itself, Fido requires a number of disk files, subdirectories or other disks to hold messages and downloadable files, and obviously a modem and cable. While Fido requires many disk files to run properly, almost all of them are created and maintained by Fido itself. The exceptions are the batch file to actually run Fido, the welcome messages and other text messages that Fido can display, and various other lists and messages. These are covered in detail later, and are simple to create manually, if need be, with an ordinary text editor. You can think of Fido as having an inside and an outside. The inside is what you can change and see by running the Fido program. These are things such as setting up message and file areas, privilege levels for the various commands, scheduled events such as FidoNet, and the like. These are all accessed by Fido commands. The outside consists of the disks used, the modem and cable, the MSDOS batch file, subdirectories for the message and file areas, signon and welcome messages that the system operator creates, and so on. While these are of course used by Fido (messages are displayed, modem is used to answer and dial, etc) they cannot be created or modified Fido's Complete Operating Manual Page INSTALL-3 Introduction to Fido from within Fido. Simply put, there are four stages to follow to get Fido properly installed. These are: (1) The Environment: Making subdirectories, formatting blank diskettes if necessary, determining how many and where to put the message and file areas. (2) Inside: Running Fido from the local keyboard (instead of the modem) in order to set up Fido to match the environment you created. Fido must be told about each message and file area subdirectory or diskette set up earlier. (3) Outside: Customizing the batch file to run Fido from; this contains the command line parameters for users time limits, and other operating details. (4) Hardware: Making the modem go. Up to this point, the modem is not needed at all, and can be ignored. If you have a modem already connected and running with a communications program, then this step is easy. Fido's Complete Operating Manual Page INSTALL-4 Getting it all together This part wasn't mentioned above, and really should be done before you even start. Ask yourself some very basic questions: do you have a machine that is capable of running Fido? (MSDOS version 2 or later, a supported machine or IBM clone, enough memory, etc)? Do you have all the files? A supported modem, or reason to believe yours will work? Most people will not have trouble with this, but be warned that things are not always what the computer store salesman said they were. "Hayes Compatibility" means more than just executes AT commands. It implies things about the signals on the rear panel connecter (Mainly Data Terminal Ready and Carrier Detect) and other not so obvious capabilities. A good test here is: does it run SMARTCOM from Hayes? Standard PCTALK? If you are running "vanilla" hardware, such as an IBM XT, DOS 2.1, a Hayes 1200 and a ribbon cable, you won't have any problem. Those of you with less popular hardware should be very careful. Points to Check MSDOS 2 or higher A supported machine A serial port 192K or more memory A usable modem A usable cable Lots of diskettes All the files you need Fido's Complete Operating Manual Page INSTALL-5 Step 1: Setting Up Message and File Areas The first step is to figure out what you want your system to look like. This depends on your needs, your hardware (mainly, how much disk space do you have) and the needs of your users. It is not possible to cover all the combinations that Fido can be configured in, and the one you end up with will probably change as your needs change. Therefore, this manual will cover a single simple configuration; others are set up in the same way, and once it is understood, is fairly straightforward. Fido's Complete Operating Manual Page INSTALL-6 Step 1: Setting Up Message and File Areas If you follow this installation guide exactly, you will end up with a Fido Bulletin Board system that has the following characteristics: - A public access system - Two independent Message Areas - Two independent File Areas - An additional, special Message Area where users can find special messages from the system operator. - Ready to be used with a DC Hayes SmartModem 1200 Any and all of this can be modified, either now (if you are confident) or later, after you get this example one running. While this manual is arranged in the order covered in the introduction, you may actually perform any steps in any order; however, this order has been found, by trial and error, to be the simplest and easiest to follow.YOu can of course do anything you want! Fido's Complete Operating Manual Page INSTALL-7 Step 2: The Environment You will note that Fido uses MSDOS subdirectories in huge quantities. If it's a subject you aren't comfortable with, please learn to use them before tackling Fido. Subdirectories aren't as hard as Microsoft makes you think with their terrible manuals. HINT: All of the Fido documentation assumes you have a working knowledge of MSDOS paths. If you don't understand what they do and how they work, you probably won't be able to get through this manual, nor be able to maintain your system if you do. Paths are just not that hard, and are very handy even if you aren't intersted in Fido. There isn't really any difference, as far as Fido is concerned, between hard disks and floppy disks. However, Fido loves to consume disk space, and floppies aren't that generous. Before we start, some general notes on hard disks and floppies. HINT: If you are new to subdirectories and all that, you can make your life easier if oyu set your system prompt to tell you where you are: PROMPT ($P) $S Execute this manually, or put it in AUTOEXEC.BAT. Installation on a Hard Disk System The easiest thing to do is start at the root, and create a new subdirectory just for Fido: CD \ log into the root MD FIDO make a FIDO directory CD FIDO enter the FIDO directory Do the above, and you will be in the newly created subdirectory. You can then ignore ALL drive letters shown in the examples below. (B:, etc) Installation on Floppy Systems You are going to need all the space you can get. You should format two new diskettes, and make one bootable (format it with /S, to install the system on it). This will become your A: diskette. On it, put the minimum tools you will need: some sort of editor or word processor (for making Fido's Complete Operating Manual Page INSTALL-8 Step 2: The Environment welcome messages, etc) and the fido .EXE files. Put the other formatted diskette in B:. YOu may have to do a lot of disk swapping to get everything created right. If your drives aren't called A: and B:, then just substitute the letters that you want. For all systems, you should set the number of BUFFERS in CONFIG.SYS on the booted diskette. The performance increase will be enormous. If you do NOT do this, then your Fido system will run very slowly, and annoy all of your users, and generally drive you crazy. If you know how to use CONFIG.SYS, then just do it. If not, then on your boot disk do the following: A: CD \ log into the root COPY CON CONFIG.SYS copy keyboard to CONFIG.SYS BUFFERS = 50 type this exactly, FILES = 20 this too ^Z Enter Control-Z, then return Copied 1 file(s) Message from MSDOS Next time you boot, MSDOS will read CONFIG.SYS and set the number of buffers to 50. (It will not do it until then.) Anyways ... Before even thinking about running any programs, the subdirectories and such need to be created. As mentioned above, we will end up with two message areas and two file areas. Message areas: GENERAL Msg area #1 TECH Msg area #2 File Areas: IBMPC File area #1 CPM80 File Area #2 Special Areas: ANSWERS Special Msg area Please remember that the names of the subdirectories are totally arbitrary; you can make them anything you want. If the names reflect what's in them, though, it's much easier a few months from now. Fido's Complete Operating Manual Page INSTALL-9 Step 2: The Environment First, create these subdirectories using the MD or MKDIR command: B: on drive B: ... MD GENERAL MD TECH MD IBMPC MD CPM80 MD ANSWERS Now the subdirectories exist on your disk. These are where Fido will put messages and files that can be accessed by users. (Of course, there areen't any messages or files yet, so don't worry about it.) Now for a tedious part. Now you must log into each area, and make a file called DIR.BBS. This is a very small file, and contains a one line description of what the subdirectory is for. (No, Fido cannot read; this small description is merely displayed to a user when they log into an area.) HINT: Make these good descriptions, as they are what the user sees, and is all they have to tell what is in there. Normally, Fido will display the actual subdirectory name; an option lets you hide it, and display the DIR.BBS contents only. This is the /Y command line switch. makinbg DIR.BBS can be done with your word processor, or more simply with the COPY command. CD GENERAL enter the GENERAL subdir COPY CON DIR.BBS make DIR.BBS General Interest Messages one line descrption ^Z Control-Z, then ENTER 1 File(s) Copied MSDOS message to you CD \FIDO log into previous subdir Repeat this for each area, entering the description for each, instead of the "General Interest Messages" in the example above. At this point, you have made all the basic subdirectories for Fido. Changes or additions can be made later, following the same basic steps. Fido's Complete Operating Manual Page INSTALL-10 Step 3: Starting Fido Now that the basic subdirectories have been made, you must run Fido and tell it where to find them. There is one last step before you do this; it is to make sure that Fido has the minimum files it needs to run. While they are not absolutely necessary to run Fido, the HELP files are handy, since you probably havent memorized all the Fido commands yet. All that needs to be done is to copy them into the main Fido directory. While logged into the main Fido directory, or the root for floppy systems, put the Fido distribution diskette into B:, and: COPY B:*.HLP You also need as a minimum the initial user list, USER.BBS, and the initial system file, SYSTEM.BBS. You will also need the Fido program, of course. Copy these from the distribution diskette, to the Fido subdirectory. HINT: If you can't figure out why you are having problems with the user list, USER.BBS, or can't remember the password, etc, refer to the SYSOP.EXE program in the Table of Contents. COPY B:USER.BBS COPY B:SYSTEM.BBS COPY B:FIDO_IBM.EXE (or _DEC for DEC, etc) Now, Fido has all it needs to be run. Fido has many command line options, which are covered in a later section. Here, you need only one: /T Test Mode FIDO_IBM /T (or _DEC for DEC, etc) After a few seconds, you will see the signon message, and a prompt for your name. You will NOT see any nice welcome messages and so on; these are created later. At the prompt for your name, fill in as follows: Your FIRST Name: SYSOP Your LAST Name: Wait ... Password: WHAT When you enter the password, it will be displayed as dots, so sthat someone looking over your shoulder can't see your password. After some messages from Fido, you will be at the MAIN Command prompt. Fido's Complete Operating Manual Page INSTALL-11 Step 4: Setting Up Areas There are a number of commands that do NOT show up in the prompt. These are the sysop commands, and are the digits 1 to 9. Only a user with SYSOP privileges may use them. (The initial user list contains one user, named SYSOP, whose privilege level is also SYSOP. That's what you entered at the example above.) The sysop-only commands are covered in detail in elsewhere; however the minimum needed information will be provided here. HINT: One point to remember about the numeric sysop only commands; you can get help with most of them by entering: n ? Where n is the command number. Fido keeps track of message and file subdirectories by storing them in small lists kept in diskfiles named SYSTEMx.BBS. Each list contains one Message Area subdirectory, one File Area subdirectory, and one HELP subdirectory (not used here). There can be up to 99 lists. When a user chooses a message or file area, they are really choosing one of these lists. You must now store the names of the subdirectories in these lists, so that Fido will know where to find them, and so that users can select them. The "1" command is used to maintain these lists. The lists are numbered 0 to 99; you select one by: 1 Where is a number 0 - 99 First we set area #1, using the subdirectory names chosen before. (Only what you enter is shown here; Fido will display the Main Command prompt and other messages also.) 1 ? Get HELP! 1 1 Select list 1 1 B:\GENERAL\M Set Message Area name 1 B:\IBMPC\F Set File Download Area name 1 B:\IBMPC\U Set File Upload Area 1 S Save the changes The first set of areas is now set. You can view your changes by entering "1" by itself. Now repeat this process for the second set of areas. 1 2 Select list 2 1 B:\TECH\M Set Message Area Fido's Complete Operating Manual Page INSTALL-12 Step 4: Setting Up Areas 1 B:\CPM80\F Set File Download Area 1 B:\CPM80\U Set File Upload Area 1 S Save changes The third list will contain only the ANSWERS message area, there is no corresponding File Area. This is set in the same way as the other areas. 1 3 Select list 3 1 B:\ANSWERS\M Set Message Area 1 F Set BLANK File Area 1 U Set BLANK Upload area 1 S Save the changes The last list to set is the "special" list, number 0. Only the Message Area is used from this list. This area is where comments to the sysop go, using the G (GoodBye) command. Usually (and in this example) this area will be the same as one of the regular areas; ANSWERS in this instance. This is so that the sysop can reply to messages left at GoodBye, and users can read them by choosing the ANSWER area. 1 0 Select list 0 1 B:\ANSWERS\M Set message area 1 F Blank areas, as above 1 U 1 S HINT: If you leave the message path for area #0 BLANK, then Fido will not ask "Leave a message to the sysop? (y,n)" at the G)oodbye command, but merely disconnect. At this point Fido is more or less usable in Test Mode (/T). You can now go into the various areas, enter messages and operate most of the commands. There will not be any files available yet, nor any messages. You should go through each area and make sure it is set up as you think it is. Message Areas From the MAIN Command prompt, use M to enter the Message Section. The A)rea command displays the message areas available, and lets you choose one. You should see three areas, and the small descriptions you entered previously. If not, something is wrong; go back over the previous steps and check. Probably just an incorrectly entered name. If all is well, pick one of the areas, for example "1" for area #1, GENERAL. HINT: Use the E command to enter a sample message. After saving it, it should say "Saving your message". If it does Fido's Complete Operating Manual Page INSTALL-13 Step 4: Setting Up Areas not, but says "DISK FULL: Cannot save your message" it is either that you disk is really full (not likely at this point!) or the subdirectory name you entered is incorrect. You must manually create, with the MSDOS MKDIR command, the subdirectories where Fido expects to find them. Return to the MAIN Command prompt, then enter the Files Section, and check the areas there, using the A command as before. You should see the area descriptions. Note however, that there will not be any files for downloading. Fido's Complete Operating Manual Page INSTALL-14 Completing Installation The software portion of Fido/FidoNet is more or less ready to be used. At this point, there are a number of options. The sections you need are listed below; be sure to browse through the others for ideas and tips. ALL SYSTEMS: Fido Message Files How to customize the welcome messages, bulletins, etc., in common with all Fido configurations. Hints and Tips Tips on speed, problems to watch out for, and ways to improve overall performance. Some things you can do and shouldnt do. PICK ONE: Public System How to make a public access bulletin board, so that new users can log in for themselves, and how to handle special cases. Semi-Public System How to make a semi-private system, where new users can log themselves in, but have restricted privileges. Private System Where new users are not allowed; the sysop has to manually enter new users. How to keep security absolute. ALL SYSTEMS: Modem Installation Installing and configuring the modem. Many modems are listed as installed in actual installations. Tips on how to fix problems. AND THEN ... FidoNet Installation Setting up your Fido as a node in the public domain electronic mail network, and what this means. Fido's Complete Operating Manual Page INSTALL-15 System Messages and Bulletins There are a number of text files that Fido will display at various points; welcome messages, the initial signon, the bulletins and so forth. You will need to customize them to your taste, or delete them if they areen't needed. Fido does not require the presence of any of these, though you should probably use most of them. These are the ones in common with all Fido setups. There is a section for each configuration: public access, private, and semiprivate. WELCOME1.BBS This is the first text that a user sees, after determining baud rate by hitting the CR or ENTER key. Most of the public Fidos use the "doggie", already provided on the distribution diskette. WELCOME2.BBS Presented after a user enters their name and password. Just a chance to give logged in users news or other information. Many systems run without WELCOME2.BBS. BULLETIN.BBS Usually where frequently changing information is posted, for all user to see. This bulletin can also be read with the B (Bulletin) command from the MAIN Command prompt. EDTORIAL.BBS Similar to BULLETIN.BBS, except Fido does not display it automatically. It can be accessed by the E command from the Main Section. (Note that the name is missing the "i"; EDTORIAL not EDiTORIAL. YELL.BBS This file is displayed to the user if they attempt a Y)ell command and yelling is not scheduled. You can use this to inform them what the Y)ell schedules are. IF you do not have this file, then Fido displays "Yelling at the sysop isn't allowed right now.". Fido's Complete Operating Manual Page INSTALL-16 Making a Public System When set up as in the previous sections, Fido is by default a public access system. However, there are special files that you can use to make life easier for you and your users. NEWUSER1.BBS This is displayed once for new users, just before Fido requests their city and state, and to choose a password. It should probably explain the need for a password, etc. NEWUSER2.BBS This is displayed right after a new user enters their city, state, and password. Usually, a simple tutorial of the system, what to expect, where to find things. If a previously logged in user forgets their password, after three attempts at entering a password, and no match is found, then there are a few options. The presence or absence of QNOPWD.BBS, a special questionaire, determines how Fido treats new users. OPTION 1: LEAVE A MESSAGE TO THE SYSOP Make sure that you do not have a file named QNOPWD.BBS; if it exists, then Option 2 will be used. NOPWD.BBS is displayed, then they get to leave a message to the sysop, identical to when a logged in user uses the "G" command to leave a comment. After leaving a comment, they are logged off. They have 10 minutes (or the specified /S value) to complete the message. OPTION 2: FILL OUT A QUESTIONAIRE OPTION 3: MESSAGE THEN LOG OFF For these two options, QNOPWD.BBS is used. This is a special file, a questionnaire. Briefly, a questionaire causes Fido to ask the user questions contained in it, and records the answers (in this case) in ANOPWD.BBS. If used, you should look at this file daily to check for new users. You can delete it whenever necessary, Fido will create a new one. Alternatively, QNOPWD.BBS can contain only text to be displayed, and no questions at all. Usually, this is the easiest thing to do; just tell them to log on again, but use a new name and password. Fido's Complete Operating Manual Page INSTALL-17 Making a Public System If QNOPWD.BBS exists, the user gets to fill it out (or not) and is then logged off; they do not get to leave a message to the sysop as in Option 1. Fido's Complete Operating Manual Page INSTALL-18 Semi-Private (Restricted) Public System If you want to run a public board, but restrict new users, this can be easily done. COMMAND LINE SWITCH: /P New Users get DISGRACE privilege When new users log on, they are assigned DISGRACE privilege. Then, by using the "3" command to set the privilege level for the Fido commands, you can restrict the commands available to new users. For instance, they can read messages, but not enter any, not be able to change their name or password, access the file area or the message area, or any other Fido command. If you use this method, then new users have to be upgraded manually, using the SYSOP utility program. Other than the new users privilege level, the is identical to a public system. You can accomplish the same thing by leaving new users' privilege as NORMAL, and useing the 3 command to change the privilege levels of the commands themselves to limit thier use. Fido's Complete Operating Manual Page INSTALL-19 Making Fido a Private System After following the previous steps to get Fido up as a public system, follow these to make it a private system. A private system is one where only already existing callers can log on; new callers are prevented from entering the system. You can let new callers leave a message to the sysop, fill out a questionaire, or merely log them off, with or without a messaeg as to why. When running a private system, callers must be entered manually, using the SYSOP utility program. Operation of SYSOP is covered elsewhere. The presence or absence of QNOPWD.BBS, a special questionaire, determines how Fido treats new users. COMMAND LINE SWITCH: /M Private System Add this switch to the command line in RUNBBS.BAT. It prevents new users from being added to the user list. OPTION 1: NEW USERS CAN LEAVE A MESSAGE TO THE SYSOP Make sure that you do not have a file named QNOPWD.BBS; if it exists, then Option 2 will be used. This is one way in which you can make new users request entry to your system; NOPWD.BBS is displayed, then they get to leave a message to the sysop, identical to when a logged in user uses the "G" command to leave a comment. After leaving a comment, they are logged off. They have 10 minutes (or the specified /S value) to complete the message. NOPWD.BBS is just a text file, that is displayed to new users, or users that forgot their password. In it, you can explain that this is a private system, and request that they enter whatever information you require. OPTION 2: NEW USERS FILL OUT A QUESTIONAIRE OPTION 3: NEW USERS GET LOGGED OFF IMMEDIATELY For these two options, QNOPWD.BBS is used. This is a special file, a questionnaire. Briefly, a questionaire causes Fido to ask the user questions contained in it, and records the answers (in this case) in ANOPWD.BBS. You should look at this file daily to check for new users. You can delete it whenever necessary, Fido will create a new one. Alternatively, QNOPWD.BBS can contain only text to be displayed, and no questions at all. This is frequently Fido's Complete Operating Manual Page INSTALL-20 Making Fido a Private System used to tell users that the system is totally private, and access to it cannot be had. If QNOPWD.BBS exists, the user gets to fill it out (or not) and is then logged off; they do not get to leave a message to the sysop as in Option 1. Fido's Complete Operating Manual Page INSTALL-21 Changing Command Privilege Levels To further customize Fido, you can change the privilege level needed to operate each of the commands. This is done with the 3 command (covered in detail in Fido's Operating Manual). Entering 3 by itself lists the current settings. Each command area has it's own privilege tables: Main Section, MAINPRIV.BBS Message Sections, MSGPRIV.BBS Mail Sections, MAILPRIV.BBS File Sections, FILEPRIV.BBS Read Command Prompt READPRIV.BBS CHANGE Command Prompt CHGPRIV.BBS For example, you can change the Raw-Display command in the file areas to be NORMAL, and let everyone use it, or you can make the EnterMessage command in the Message areas privil, so that new callers (first time callers) cannot enter messages until you up their privilege level with the SYSOP.EXE program. (They can always leave Messages to the Sysop at G)oodbye.) Briefly, to change a command privilege, enter: 3 Where: Is the command letter, as entered normally to Fido. (E for E)nter message, K for K)ill, etc.) Is one of the Fido privilege levels below. You MUST spell it out fully. TWIT Lowest DISGRACE NORMAL PRIVEL EXTRA SYSOP Highest Fido's Complete Operating Manual Page INSTALL-22 Hints and Tips There are a number of things you can do that make Fido faster. If you have enough memory for a memory disk, put the messages in it. This will speed things up by a factor of ten or so. Dont worry about the .BBS files or .HLP files; they are small and infrequently accessed. The downloadable files are generally too large, and again, areent accessed in a way that they speed up from a memory disk. Also, you should use a large number of FILES and BUFFERS in CONFIG.SYS. This is probably the limiting speed factor in most systems without memory disks. Use the maximum FILES = 20, (each "file" takes only 36 bytes, so dont worry about that) and lots of buffers. The following is an example: FILES = 20 BUFFERS = 50 More than 70 buffers or so starts to actually slow the system down, as DOS spends all of its time fiddling around with the buffers instead of the data inside them. If you run out of memory, then lower the number of buffers. Buffers are 512 (1/2 K) bytes each on IBM PC type machines. HINT: MSDOS is not too smart about checking for enough memory when you use BUFFERS = . The actual buffers arent allocated until they are needed; if at that time there isnt enough memory, then you get the message: "Insufficient Memory" And the system halts, making you reboot. Make sure you have enough memory. 40 to 50 buffers is plenty, and will work fine with 256K of memory. Use GOOD diskettes. If you get a disk error, the user will just see the system hung, and the "... error" "Retry Ignore Abort" message on the local console. Not good. Initially, use the RUNBBS.BAT batch file from the distribution set of files. Modify it to include any switches needed. Later on, you can include other things for system maintenance, using the scheduler. See the scheduler section for that. When Fido terminates to DOS, it returns an ERRORLEVEL, that can be detected from within RUNBBS.BAT. Some of the ERRORLEVEL values are built into Fido; others can be set by Fido's Complete Operating Manual Page INSTALL-23 Hints and Tips the sysop. The fixed ones are: 0 No errors or special conditions 1 Control-C from console or stack overflow 2 Fido Disk File error 3 Other fatal errors If there is some fatal error, you'd probably like to see it, and in any case there's not any sense in running again. Also, you have to type Control-C on the local console to terminate Fido (for maintainance, etc) and this causes it to terminate the batch file. The Fido software is not prone to crashing. Most troubles will be hardware ones, or power failures and brownouts. The system cannot be crashed by callers hanging up at random points, and there is no way in which debuggers can be run, etc. WARNING: Beware of other programs such as NEWKEY, pop up alarm clocks, SIDE KICK, automatic screen blank programs, and anything like them. None of them are compatible with any program that makes extensive use of interrupts, such as Fido. Most of the programs do illegal things with the hardware, and will bomb Fido, and other systems. You may never have problems; probably you will, but it may take hours or days to show up. One symptom is that the system just "stops". If in doubt, start the system up again; if it happens again, reboot again, this time leaving out any such program, and see if that cures it. It may take several days to discover. It is recommended that you do not use such programs while running Fido. Fido is very friendly to multitasking programs such as Multilink, and has a command line option, /I, to acocmodate them. Please refer to the Command Line Switch section for details. Fido's Complete Operating Manual Page INSTALL-24 Files Section Organization There are a number of ways you can run your Files Section, if you have one at all. You can of course combine the features any way you want, but here are some common ones: OPTION 1: FREE ACCESS UPLOAD AND DOWNLOAD Users can upload and download files at will. New files are uploaded into the same area and added to the files list, so that they are available immediately. OPTION 2: FREE ACCESS DOWNLOAD, UPLOAD BY SUBMISSION Users can download any file, but newly uploaded files cannot be downloaded until the sysop allows it. There are two ways to do this. These are accomplished with three things: File Download Path In the list of areas File Upload Path In the list of areas FILES.BBS The files list The upload and download paths are accessed by the "1" command, as mentioned before. FILES.BBS is a special file in each file area, that contains the list of available files. Before describing the Options above, here is some information: FILES.BBS is the list in each Files area of the files available for downloading. You must create the first one, but it can be automatically updated in a number of ways later. FILES.BBS is basically just a text file, that contains the names and a description. Fido puts in the file size, and aligns the columns neatly. For instance: (Sample Files display) AFILE.EXE 4545 Just a sample file. PROG.BIN 323432434 A very large file FOO.FIZ MISSING Another sample (The actual FILES.BBS contents) AFILE.EXE Just a sample file. PROG.BIN A very large file FOO.FIZ Another sample. You must enter the names as shown; the DOS DIR format (FILE EXT) will not work, it must be (FILE.EXT). Fido's Complete Operating Manual Page INSTALL-25 Files Section Organization Note that if a file is really missing (not in the directory) the file size will say MISSING instead. There are special lines within FILES.BBS, that control how it is listed by the various commands. The special lines are determined by the first character. They are: - This is a comment only line So is this (starts with a space) @ This is the "end" of the files list. The first two are merely comments; you can use them for whatever you wish. The third is a special marker, and tells Fido to not list anything after this line, including this line. When a file is uploaded, Fido asks for a one line description for that file. The filename and description is added to the END of the files list, above. If there is a line beginning with @, then the new files are added after it. Since nothing is listed beyond this point, these files are not listed, and are esentially unavailable until the sysop edits FILES.BBS and deletes the line containing the @, or moves it past the last file in the list. This lets the sysop check out uploaded files before making them available. Uploading and Downloading As mentioned before, Fido has an upload and a download path. The F)iles command lists the files in the download path, using the FILES.BBS list there. Uploaded files go into the upload path, and their names and descriptions are added to the FILES.BBS list in the upload path. If the upload and download paths are the SAME, then Fido will not let an uploaded file replace (or destroy ...) an already existing downloadable file. This prevents good files from accidentally being destroyed or changed. If the upload and download paths are DIFFERENT, then Fido will let existing files be overwritten. Usually this means there is a seperate upload area, not accessible to users. You can use the above characteristics to your advantage. Instead of trying to describe them all, here are three examples. OPTION 1: FREE ACCESS UPLOAD AND DOWNLOAD Fido's Complete Operating Manual Page INSTALL-26 Files Section Organization Users can upload and download files at will. New files are uploaded into the same area and added to the files list, so that they are available immediately. Make the upload and download paths the same. New files go into the download area. Make sure there is no @ line in FILES.BBS; when a new file is uploaded, it's name and description is added to the end of the files list, where it is immediately available for downloading. OPTION 2: FREE ACCESS DOWNLOAD, UPLOAD BY SUBMISSION Users can download any file, but newly uploaded files cannot be downloaded until the sysop allows it. There are two ways to do this. VARIATION A: As in Option 1, make the paths the same, but put a line beginning with @ in FILES.BBS. When a file is uploaded, it is added to the download directory, but it's name and description will not be displayed with the "F" command. This is the easiest to maintain way to do things; to make new files available, all you have to do is delete the line beginning with @, or move it to the end of the list. The disadvantage is that the file really is accessible; it just does not show. If a user knows it's there, it can be downloaded. VARIATION B: Make the upload and download paths different, where the upload path is a disk or directory not available as a File Area. It doesnt matter if there is an @ line in FILES.BBS. Since new files are uploaded into a totally seperate area, they cannot be accessed by users. (You can put the path in a separate file area, with SYSOP privilege level, so that you can get in there to look.) The disadvantage is that in order to make these files available, you must use the DOS COPY command, and update the FILES.BBS in the download area manually. This is the most secure method, is is reccomended only you require absolute security on uploaded files. Fido's Complete Operating Manual Page INSTALL-27 Command Line Switches and Setting Time Limits There are many command line options that control Fido operation. You will have to edit these into the batchfile that runs Fido. The switches are: /J Set Modem Type Selects the type of modem you are using. is a number that specifies the modem type: 1/J Hayes 2/J DEC DF03 3/J Racal Vadic VA212 4/J Novation/ IBM PC Junior 5/J US Robotics 7/J Prentice POPCOM 8/J IBM PC Junior 9/J Ventel MD212 with WECO option 10/J GDC modem 11/J Hayes 2400 12/J US Robotics Courier See the section on modems for details. /Y Don't display pathnames Causes Fido to NOT display the subdirectory name when listing file ans message areas with the A)rea command. Normally, Fido displays the pathname as set with the "1" command, followed by the contents of the DIR.BBS file. Adding /Y to the command line causes Fido to display the DIR.BBS contents only. /I Set multi-task environment This does only two simple things: it changes the names used for the log files, and affects the way messages are created. The names for the logs will incorporate the task ID number; ie. if you specify 9/I the log files will be: SYSOP9.LOG MAILER9.LOG You cannot use 0 as a number. The other effect of setting a task ID is to force Fido to recount the messages before saving a new message. This hopefully prevents duplicate message numbers making a mess of things, or at least minimizes it. It has the unfortunate side effect of greatly slowing down saving messages. Fido's Complete Operating Manual Page INSTALL-28 Command Line Switches and Setting Time Limits If you use /I in test mode, you will not be able to see anything. Do not use /I with /T. /T Test Mode Test mode. Described early in this manual, not used for a remote Fido system. Not a good thing to put into the batch file. /M Private System Private message system. Please read the chapter on private systems. /P Low Default User Privilege Set the default privilege level for new users to DISGRACE. See the chapter on semiprivate systems for details. (number)/S Log On Time Limit Set the time limit for logging on. This limit starts as soon as carrier is detected, and stops after a valid password is entered. At that point, the normal user or first time user time limit starts. The minimum is 5 minutes; the default is 10. (number)/L Normal User Time Limit Set the time limit per call to (number), where (number) is the number of minutes. 0 means unlimited use, i.e. no time limit. Must be 0 - 65535. Read a later section on time limits. If not specified, then the limit defaults to 60 minutes. (number)/F First Time Users Time Limit Set the time limit for new users. The default here is 60 minutes also. You can give first time callers a low limit. (number)/D Daily Time Limit Set the total time limit for a 24 hour period. This is usually 4 or 5 times the /L limit. This is the maximum number of minutes a caller is allowed in a 24 hour period, and prevents long term hogging, and keeps them from hanging up and calling right back when the per-connect limit is Fido's Complete Operating Manual Page INSTALL-29 Command Line Switches and Setting Time Limits reached. The default is 300 minutes. (number)/K K byte Download Limit Limit the number of K bytes a caller can download in a 24 hr. period. Along with /F, /L, and /D, allows full control over call-in-once-download-everything and-never-call-back type users. /V Carrier Detect Mask Bit Define the bit used to determine the state of the Carrier Detect signal from the modem. The default is CTS, or 16. For most machines, use 128/V. See the modem section in this manual for details. /U No File Transfer Display Disables the file transfer information displayed when a file upload or download is happening. Normally, Fido will display status messages about each block being transferred, and all errors that happen. This is very useful when a caller is having trouble. Enter /U to disable this display. /G Set FidoNet Attempts with Connect Sets the number of attempts with connect for FidoNet. The default is one. This is the number of times that Fido/FidoNet will call a particular number, if the modems connect but no mail is transferred. /1 Set COM1 /2 Set COM2 Select which physical IO device to use. The default is /1, COM1 on the IBM PC. /2 Selects COM2. Not used on machines other than the IBM PC, unless otherwise noted. These switches are entered thusly: Fido 90/l 30/f 200/k 180/d 90 minute time limit per call (normal users) 30 minute time limit (first time callers) 200K bytes/48 hrs download limit 180 minutes time limit per user per 48 hrs Fido's Complete Operating Manual Page INSTALL-30 HELP Files Fido has a number of HELP files, that are displayed by entering "?" at almost any point within Fido. There is a help file for each place ? can be entered. The HELP path is used to find the file needed. The standard Fido setup is a single subdirectory called HELP, which contains all the help files. All the help files have the extention .HLP without exception. These are: 1.HLP Sysop 1 command 2.HLP Sysop 2 command 3.HLP Sysop 3 command 5.HLP Sysop 5 command 6.HLP Sysop 6 command 8.HLP Sysop 8 command MAIN.HLP Main Section command prompt C.HLP Within the C command, Main Section MSG.HLP Message Section command prompt MQUERY.HLP Within the R command, Message, Mail Section ENTERCMD.HLP Within the E command, Message Section MAIL.HLP FidoNet Mail Area command prompt FILES.HLP File Section command prompt XFERTYPE.HLP Within the D and U commands, File Section NODES.HLP At the "Fido to send to" prompt, entering a FidoNet message. You can customize these if necessary, but at least initially don't worry about them. Fido's Complete Operating Manual Page INSTALL-31 Installing the Modem The modem should be installed ONLY after the software is ready for it. There is no need for a modem while configuring the software. In order to test Fido and the modem, you will need a second computer and modem. This may be difficult, but is the only way by which to test the modem. Any modem and computer or terminal may be used; all you require is some sort of communications program to call your Fido with. For IBM PC versions, you can use a command line switch to select either COM1 or COM2. The default is COM1. If you need to use COM2, add to your command line in RUNBBS.BAT: /2 COM2 If you remember to set the modem type (/J) right, Fido will initialize the modem for you; you need not set any switches, except as mentioned below. If you have a modem that is not listed, then you are on your own; if it is a Hayes compatible, by all means try that. Please check that you modem is not on the list of problem modems, further below. It is entirely possible you will have to modify your modem cable or replace it; even if you have a modem/comm/ program combination that works, it may not have all the lines needed to operate a bulletin board. The extra lines are Carrier Detect (CD) and Data Terminal Ready (DTR). These two are not normally needed by most communications programs; they are however needed by Bulletin Boards, since they need to be able to detect incoming calls and to force them to disconnect. USING A STANDARD CABLE You can change the RS232 pin that Fido uses to determine the state of the Carrier Detect signal. This is done with the /V switch; see the section on Command Line Switches, and the section on Specific Computers, next. No /V switch at all is the same as entering: 16/V default Which is NOT what is needed by most machines. Refer to the Specific Computers section for /V values. Legal values for /V are: 1, 2, 4, 8, 16, 32, 64, 128. Testing the Modem When Fido ir first run, after initializing itself, it will say: Fido's Complete Operating Manual Page INSTALL-32 Installing the Modem - Waiting for a Call or Event This means that Fido finished initializing the modem, there is no incoming call, and that it is aiting for an incoming call. This is the normal standby state of Fido. When a call comes in, the modem (not Fido) answers the call. (You can see the modem light the OH, Offhook, lamp.) When the modem has completed the connection process, it informs Fido of this with the Carrier Detect (CD) signal (The modem lights the Carrier Detect (CD) lamp.) The /V value is a bit mask used to isolate the CD signal from the others. When Carrier Detect is true, signaling an incoming call, Fido displays: - Incoming call - Determining baud rate At this point, Fido is waiting for the caller to hit CR and/or space bar to determine the baud rate. When the caller disconnects, the modem drops it's CD signal, and Fido lowers Data Terminal Ready (DTR) momentarily, raises it again, and goes back to the original display: - Waiting for a call or event You must get Fido to perform this exact sequence of events. If it does not, please refer to the Modem Problem Determination section. Custom Cabling The idea here is to connect the cable such that you can not only communicate to the modem, but also get to the Carrier Detect and Data Terminal Ready signals to and from it. If you already have MINITEL, PC-TALK, etc working with the modem, thats a good start, but not enough. The Carrier Detect line is not needed by programs such as MINITEL and PC-TALK; Fido needs it to tell when a caller has made a connection, or when they have hung up. Just because PC-TALK or MINITEL work with the modem doesnt mean that Fido will. The following are the pins that must be wired to an IBM Async Card. You will have to determine how to connect other computers using this as an example. IBM PC SMARTMODEM USE 1 1 Ground, 2 2 Data, modem to PC Fido's Complete Operating Manual Page INSTALL-33 Installing the Modem 3 3 Data, PC to modem, 6 6 Carrier Detect 20 20 Data Terminal Ready The other pins are not needed by Fido, though may be needed by other comm. programs, and in any case can be left in. Carrier Detect: CD CD is generated by the modem, and tells the computer (Fido) that a call came in, and a connection made. Conversly, Fido can tell when a caller hangs up or loses connection, and knows to log that user off. Data Terminal Ready: DTR Fido uses this to disconnect users that have gone over their limit, and to prevent incoming calls while Fido is performing internal processing that may take a few minutes. DTR is also of extreme importance for FidoNet for placing outgoing calls. Fido will not run properly if DTR is not connected and working properly. Fido's Complete Operating Manual Page INSTALL-34 Commanding the modem: FIDOMDM.BBS FIDOMDM.BBS is a special, optional, file that Fido uses to command the modem. If it does not exist, then it is not used. You need to use this file only if you have special requirements. Fido will automatically initialize the modem for you. If FIDOMDM.BBS exists, the contents of it are output line by line to the modem. The contents of the file are not checked in any way; it is sent blindly. After sending one line, Fido will wait up to three seconds for and responses from the modem; these responses, if any, are thrown away. The purpose is to avoid sending commands to fast. If there is no response, Fido waits three seconds and goes on to the next line. FIDOMDM.BBS is processed after Fido initializes the modem itself; this lets you override or modify the default settings. For example, if you wanted to leave the loudspeaker on, and have the modem answer on the second ring instead of the first, for a Hayes type modem use: ATS0=2 ATM1 Fido's Complete Operating Manual Page INSTALL-35 Specific Computers and Modems These are some notes on specific installations. If your machine combination is not here, you will ahve to play with the various settings of /V, /J and FIDOMDM.BBS mentioned earlier. Fido has only been tested on the machines listed inside the front cover; it may or may not work on other machines. IBM Jr, PC, XT, AT and ALL CLONES Use 128/V for all modem types. A 1 to 1 cable will work with all modems. DEC RAINBOW: ALL MODELS SANYO 555 USe 16/V for all most types. I have very little personal experience with these machines. VICTOR 9000 Use 8/V. OTRONA ATTACHE Use 16/V. You will need to use the special Attache MODEM cable; the PRINTER cable will not work without modifications. Fido's Complete Operating Manual Page INSTALL-36 Specific Modems The /J values are listed below. Please check for notes on certain modem types. 1/J Hayes 2/J DEC DF03 3/J Racal Vadic VA212 4/J Novation/ IBM PC Junior 5/J US Robotics 7/J Prentice POPCOM 8/J IBM PC Junior 9/J Ventel MD212 with WECO option 10/J GDC modem 11/J Hayes 2400 12/J US Robotics Courier HINT: The following is opinion only; it is not "fact". I have had the chance to play with many modems while working with Fido, so I'd thought I'd share some opinions. This is the only plug you will find anywhere in this manual for specific hardware. The differences in quality between modems is great, and not always apparent to the buyer. "Hayes compatibility" is a misnomer, there are very few that truly are. Even some of Hayes' own products are not "Hayes compatible". For a 1200/300 baud modems, the Hayes is still by far the best. It is expensive, but you cannot possibly go wrong; it performs flawlessly, there is obviously lots of software for it, and they are plentiful. Some of the clones I have worked with personally, or have suffecient second hand information to rely on. Hayes clones: Prentice POPCOM, General Data Corp modems are fine modems, though they are "supersets" of the Hayes; you need to set further commands to make them compatible. Once done, they seem to be fine. The US Robotics 212A and Password are fairly good; they have some bugs/side effects problems, but Fido has software to compensate for them. Fairly minor bugs, somewhat of an annoyance for BBS use, but it is very inexpensive. All Racal Vadic modems seem to be quite good. Only one is compatible with Fido. They tend to have very wordy "menus", which are nice for use with dumb terminals but terrible for use with computer programs. The DEC DF03 is a terrible modem, mostly because it is a very ancient design. It dials only pulse. It is not a smart modem. Ventel seems to be a popular modem with the "minicomputer" crowd, but it does not provide a Carrier Detect signal, making it about as useful as a telephone Fido's Complete Operating Manual Page INSTALL-37 Specific Modems without a ringer. For 2400 baud, at this writing there seems to be mainly Hayes, US Robotics, and Multitech. I have not used the Multitech, but it is supposedly a good modem. I do have both a Hayes and the US Robotics Courier; the USR unit is *far* superior to the Hayes. The Hayes is not "Hayes compatible", the USR is. The USR outsurpasses the Hayes 2400 in all aspects. Except the cabinet is flimsy plastic, oh well. I more or less reviewed the USR in FidoNews (FidoNet Users' Newsletter) and will not repeat it here. No contest, as far as I'm concerned; the supposed handy features of the Hayes 2400 turn out to be useless frills. Please keep in mind that these are merely my opinions (of which I have more than my share) and not recommendations. If you are dissatisfied it is your own fault. Hayes SmartModem 1200 Modem Type: 1/J Switch Settings (External Modem) 1 Up Support DTR Lead 2 Down Digit Result Codes 3 Down Result codes sent 5 Up Autoanswer first ring 6 Up Supports Carrier Detect lead 8 Down Recognize commands Others as needed Anchor Automation Signalman Fido will not work with the Anchor Automation, as it does not support the DTR control line. Fido cannot cause a caller to hang up, nor can it disconnect during FidoNet mail transfers. Since FidoNet would be unable to disconnect after placing a call, with a remote possibility of an extremely high phone bill, the decision has been made not to support this modem. Bizcomp Modem This so called "Hayes compatible" is one of the poorest modems ever made; it is barely compatible, and unfortunately, cannot be used for Fido, nor many other comm. type programs. It will work OK at 1200 baud, but not at 300. For some unknown reason, the modem transmits all characters at 1200 baud, even when connected at 300. While it sounds like it simplifies things, by not having to switch baud rates, it Fido's Complete Operating Manual Page INSTALL-38 Specific Modems also means that you must "throttle" data sent to it; you cannot just send data at 1200 baud to the modem, when it is leaving the modem at only 300 baud. This has so many basic flaws that no attempt will be made at making Fido accomodate it. Qubie 1200 Modem Another "Hayes compatible"that does not work. This has many serious but subtle problems. The Carrier Detect signal is "faked", and does not work. Other problems were reported. It probably will not work with Fido, unless Basic Time revises the firmware. US Robotics Modem Modem Type: 5/J Switch Settings: RNG: Off 8HI: On BAL: Off DTR: On The 212A and Password have a strange side effect: if a partial command, or just garbage, is sent to the modem, it will not answer the phone. The modem expects a CR after each line, and will sit and wait until it gets one. Fido fixes this by issueing commands to clear the modem, hence it is not a problem. Make sure you select 5/J. Ventel MD212A All of the Ventel modems do not normally supply Carrier Detect; this makes them absolutely useless for Bulletin Board use. The MD212A, however, has an optional ROM called "WECO" (dont ask me) that supplies the missing signal. You will need to contact the factory for this option. Fido's Complete Operating Manual Page INSTALL-39 Modem Problem Determination SYMPTOM: Fido says "Waiting for a call or event" but will not answer the phone. The modem is not in autoanswer mode. Did you use the right /J setting? Is the modem on? Plugged in? SYMPTOM: Fido says "Waiting for a call or event", immediately followed by "Incoming call, determining baud rate" when there is no incoming call. You have the modem installed incorrectly. The problem is that Fido thinks that there is Carrier Detected when there isnt. There are a number of possibilities. You may have the /V value wrong. If the one recommended one does not work, try the others. There are eight possible values; 1,2,4,8,16,32,64,128. You may have switch settings wrong: you must set any switches needed to make the Carrier Detect and Data Terminal Ready signals active. Fido cannot do this. You may have a cable that does not have all the signals needed; replace the cable. SYMPTOM: After a caller logs off, Fido rings the bell continuously, displaying the message "CANNOT DISCONNECT THE MODEM!". Fido requires that it be able to cause a disconnect by using the DTR line. The Anchor Automation modem does not support DTR, and therefore cannot be used with Fido. For modems with options switches, it may be merely a switch setting to enable the use of the DTR line. This can also be caused by a modem cable that does not have all the connections made. If you see this message, you can type Control-C to abort it. You should also make sure the modem is disconnected until you can repair this situation. Fido's Complete Operating Manual Page INSTALL-40 Install Index "1" command............................. 11 -....................................... 25 /1 Set COM1............................. 29 /2 Set COM2............................. 29 /D Daily Time Limit..................... 28 /F First Time Users Time Limit.......... 28 /G Set FidoNet Attempts with Connect.... 29 /I Set multi-task environment........... 27,23 /J...................................... 39,27 /K K byte Download Limit................ 29 /L Normal User Time Limit............... 28 /M Private System....................... 28,19 /P Low Default User Privilege........... 28,18 /S Log On Time Limit.................... 28 /T Test Mode............................ 28,10 /U No File Transfer Display............. 29 /V Carrier Detect Mask Bit.............. 29,31 /Y Don't display pathnames.............. 27 1 command............................... 30 1.HLP................................... 30 128/V................................... 29 2 command............................... 30 2.HLP................................... 30 3 command............................... 30,21,18 3.HLP................................... 30 5 command............................... 30 5.HLP................................... 30 6 command............................... 30 6.HLP................................... 30 8 command............................... 30 8.HLP................................... 30 @....................................... 25,26 ANSWERS message area.................... 12 Basic subdirectories.................... 10 Batchfile............................... 27 BUFFERS = 50............................ 8,22 BULLETIN.BBS............................ 15 Bulletins............................... 15 C.HLP................................... 30 Carrier Detect.......................... 29,39,31,32 CD...................................... 31 CHGPRIV.BBS............................. 21 COM1.................................... 29 Fido's Complete Operating Manual Page INSTALL-41 Install Index COM2.................................... 29 Command line options.................... 27 Command Line Switch..................... 23 CONFIG.SYS.............................. 22,8 Control-C............................... 23 Custom Cabling.......................... 32 Data Terminal Ready..................... 32,39 Digits 1 to 9........................... 11 DIR.BBS................................. 9,27 DISGRACE................................ 18,21 Disk File error......................... 23 DISK FULL............................... 12 Diskettes............................... 22 Distribution diskette................... 10 Download................................ 24,22 DTR..................................... 32,31 EDTORIAL.BBS............................ 15 ENTERCMD.HLP............................ 30 ERRORLEVEL.............................. 22 EXTRA................................... 21 Fatal errors............................ 23 File Areas.............................. 6 File transfer information............... 29 FILEPRIV.BBS............................ 21 FILES = 20.............................. 22 Files Section........................... 24 FILES.BBS............................... 25,24 FILES.HLP............................... 30 First time callers...................... 28 G)oodbye................................ 12 HELP files.............................. 30 HELP path............................... 30 HINT:................................... 11,7,22,12,36,12,10 HINT:................................... 7,9 Insufficient Memory..................... 22 Interrupts.............................. 23 MAIL.HLP................................ 30 MAILPRIV.BBS............................ 21 MAIN.HLP................................ 30 MAINPRIV.BBS............................ 21 Memory disk............................. 22 Message and file areas.................. 2 Message Areas........................... 6 MKDIR................................... 8 Modem Problem Determination............. 32 Modem type.............................. 27 MQUERY.HLP.............................. 30 MSG.HLP................................. 30 MSGPRIV.BBS............................. 21 Fido's Complete Operating Manual Page INSTALL-42 Install Index New users............................... 28 NEWKEY.................................. 23 NEWUSER1.BBS............................ 16 NEWUSER2.BBS............................ 16 No time limit........................... 28 NODES.HLP............................... 30 NOPWD.BBS............................... 16,19 NORMAL.................................. 21 Offhook................................. 32 Other programs.......................... 23 Out of memory........................... 22 Password:............................... 10 Private message system.................. 28 Private system.......................... 19 PRIVEL.................................. 21 Privilege level......................... 28 Public access system.................... 16 Public system........................... 18 QNOPWD.BBS.............................. 16,19 Questionnaire........................... 19,16 READPRIV.BBS............................ 21 RUNBBS.BAT.............................. 22,19 Scheduler............................... 22 Screen blank programs................... 23 Seperate upload area.................... 25 Set File Download Area.................. 11 Set File Upload Area.................... 11 Set Message Area........................ 11 SIDE KICK............................... 23 Signon message.......................... 10 Subdirectories.......................... 2 SYSOP................................... 21,11 SYSTEM.BBS.............................. 10 Test mode............................... 28,10 Time limit per call..................... 28,28 TWIT.................................... 21 Upload and download..................... 24 USER.BBS................................ 10 Welcome messages........................ 10,2,15 WELCOME1.BBS............................ 15 WELCOME2.BBS............................ 15 XFERTYPE.HLP............................ 30 Y)ell................................... 15 YELL.BBS................................ 15 Your FIRST Name:........................ 10 Fido's Complete Operating Manual Page INSTALL-43 Install Index Your LAST Name:......................... 10