ftp.wwiv.com

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

/ ftp.wwiv.com / ftp.wwiv.com.zip / ftp.wwiv.com / pub / BBS / XHOST20S.ZIP / MANUAL.DOC < prev next >

Wrap

Text File | 1992-10-07 | 82KB | 1,944 lines

▒▒▒▒▒▒▄ ▒▒▄ ▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▄ ▒▒▄ ▒▒▒▒▒▒▄ ▒▒▄ ▒▒▄ ▒▒▄ ▒▒▒▒▒▒▄ ▒▒█▀▀▀▀ ▒▒▒▒█ ▒▒█▀▀▀▀ ▒▒█▀▀▀▀ ▒▒█ ▒▒█ ▀▒▒█▀▀ ▒▒█ ▒▒█ ▒▒█ ▒▒█▀▀▀▀ ▒▒▒▒▒▄ ▒▒█ ▒▒▒▒▒▄ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒▄ ▒▒█▀▀▀ ▒▒▒▒▄ ▒▒█▀▀▀ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒▒▒█▀ ▒▒█▀▀▀ ▒▒▒▒▒▒▄ ▒▒█▀▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒█ ▒▒█ ▒▒█ ▒▒█▀ ▒▒▒▒▒▒▄ ▀▀▀▀▀▀ ▀▀ ▀▀ ▀▀▀▀▀▀ ▀▀▀▀▀▀ ▀▀▀▀▀▀ ▀▀ ▀▀ ▀▀ ▀▀▀▀▀▀ ▒▒▄ ▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒█ ▒▒█ ▒▒█▀▒▒█ ▒▒█▀▀▀▀ ▀▒▒█▀▀ ▒▒▒▒▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒▒▄ ▒▒█ ▒▒█▀▒▒█ ▒▒█ ▒▒█ ▀▀▀▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒▒█ ▒▒▒▒▒▒█ ▒▒█ ▀▀ ▀▀ ▀▀▀▀▀▀ ▀▀▀▀▀▀ ▀▀ Executive Host - Premium Host/BBS for Telix Copyright (c) 1992 by Steve Wood All Rights Reserved NOTE: This manual is the documentation for version 1.7. For additional information and documentation please read the file WHATSNEW.TXT. Another fine product from, The Fine Software Products WOODSHED for Intelligent People Steve Wood - Owner, Programmer, Technical Support T A B L E O F C O N T E N T S --------------------------------------------------------------------------- Introduction ......................................................... 1 System Requirements .............................................. 1 External Protocols and other Registered Features ................. 2 Installation ......................................................... 3 Main Menu Options .................................................... 6 SysOp Menu ....................................................... 6 Guest Menu ....................................................... 10 Message Menu ....................................................... 10 SysOp's Function Keys ................................................ 11 Security Levels ...................................................... 11 The Host User File ................................................... 12 The Message Base ..................................................... 12 Private Messages ................................................. 13 Public Messages ................................................. 13 The Message Data File ............................................ 13 Adding Files to the Host ............................................. 13 Installing Filelists (with descriptions) ............................. 14 Installing Bulletins ................................................. 15 Installing Doors ..................................................... 15 Installing Conferences ............................................... 16 Additional Security - Trashcan File .................................. 18 New User Questionnaire ............................................... 18 Event ................................................................ 18 Using the Host Utilities ............................................. 19 Using the Host Filer ................................................. 20 File Transfers ....................................................... 22 Downloading ...................................................... 22 Uploading ........................................................ 22 Important Files to Become Familiar With .............................. 22 Limitations .......................................................... 24 Support .............................................................. 24 APPENDIX A - High Speed and Error-Correcting Modem Setup ............. A1 APPENDIX B - Mail Doors, Offline Readers, Mail Networks, and Frontends. B1 page 1 --------------------------------------------------------------------------- ╒══════════════════════════════════════════════════════════════════════════╕ │ The author makes no warranties, expressed or implied, as to the quality, │ │ performance, or merchantability of this program. The author will not be │ │ held liable for any direct, indirect, incidental or consequential │ │ damages resulting from the use of this program. Your use of this │ │ program and your subsequent registration, constitutes your acceptance │ │ and agreement to this disclaimer and your releasing the author from any │ │ form of warranty, liability or litigation. │ ╘══════════════════════════════════════════════════════════════════════════╛ INTRODUCTION: Executive Host v1.7/2.0 has many new features and improvements over previous versions. Be sure to read the file WHATSNEW.TXT for information about changes and new features. Most of Executive Host is written in the SALT language "Script Application Language for Telix", and version 3.12 of above of the Telix Communications Program must already be installed in order for the host to function properly. Special thanks go to Colin Sampaleanu, author of Telix and the SALT language. Telix is a registered copyright of: Colin Sampaleanu & Exis Inc. P.O. Box 130 West Hill, ON Canada M1E 4R4 Register your copy of Telix today! All Executive Host utilities were written and compiled using the Borland C++ Professional Compiler, and compressed using the PKLITE Professional Executable File Compressor. Borland C++ is a Copyright of Borland International. PkLite Professional is Copyright PkWare, Inc. SYSTEM REQUIREMENTS - 1. 256k of memory and an MS-DOS or compatible operating system. 2. Telix version 3.12 or above already installed. 3. A good text editor that accepts file names on the command line is required. Ted.com, a public domain text editor from PC Magazine is included for those who do not currently have their own editor. Obtaining a more cabable text editor, such as Qedit (shareware) is highly recommended. page 2 --------------------------------------------------------------------------- IF YOU ALREADY HAVE EXECUTIVE HOST INSTALLED: Your registered copy gives you more features and flexibility than your original copy, but will install easily and use your existing setup and data files. If you have a message base generated by version 1.6 or below, run CONVERT.BAT to update your old files to the new format. To install the new software, run INSTALL.EXE and follow the instructions on the screen. Run BOARD.BAT and fill in the new configuration options. Now you are up and running with your personalized copy, Zmodem capabilities, and your existing set-up. Do not unzip any of the example zip files unless you need to use these examples of the menus and data files. Otherwise you may overwrite already existing files. INSTALLING EXTERNAL PROTOCOLS: Your registered version of Executive Host supports all four of the external protocol slots available in Telix version 3.12. The external protocols that you set-up must use the following letter identifiers - (P), (J), (O), (L). Any other letter identifiers will not work with Executive Host. These letters were chosen to try to match as best as possible with the most popular external protocols used today. The Executive Host protocol menu uses the P-Mpt, J-Jmodem, O-Mobyturbo, and L-Zmax protocols, however you may use any protocol you wish and change the menus accordingly. You do not have to set-up these exact protocols, but you do have to use the letter identifiers specified above for any external protocols that you make available. Puma up and download batch files are included on your disk , but must be set-up in Telix as per the Telix manual. Complete set-ups for MobyTurbo are also included. To install external protocols, always follow Telix's and the protocol's instructions. BIMODEM: In addition, you also have Bimodem capabilities built in, which is executed from a batch file called BIMODEM.BAT. If you have already installed Bimodem with your Telix package, then copy the BIMODEM.BAT file into your Telix directory and you are ready to go with Bimodem. If you have Bimodem installed in a different directory than Telix, you will have to modify the bimodem.bat file. You will probably want to run BICONFIG again also, in order to set-up the options for optimal BBS use (i.e. do not write over existing files, do not download out of ALL directories, etc.). Follow the Bimodem Documentation for setting up the protocol for a BBS, and of course if you still have problems or questions, give us a call at any of the support locations, or send me a letter. A Bimodem interface that will add the Bimodem descriptions to your uploads filelist is in the works. As soon as it is completed it will be made available on the our support BBS. page 3 --------------------------------------------------------------------------- CUSTOM MENUS: Another benefit of your having registered is the ability to design and add custom menus to your Host. Custom guest, sysop, message, and protocol menus will now be used instead of the internal menus, if found in the Telix directory. Some example menus have been included in the file MENUS.ZIP on your disk. These files are the correct length to interface perfectly with the program, and should be used as a model in designing your own menus. Have fun in this endeavor, and may I suggest using TheDraw program for your ansi projects. It is the best ansi screen design program available, and can be found on most good boards (TDRAW401.ZIP is the latest version). INSTALLATION: First time installation of Executive Host begins by running INSTALL.EXE. DO NOT copy any Executive Host files into a Telix script directory. If you do not have your text editor configured in Telix, do so now. This is done by running Telix and entering "ALT-O". Then choose "Filenames and Paths" and enter your editor's name under option "h" (If you do not have your own text editor, ted.com will be used automatically, and the Telix editor setup is not necessary). Hit Escape to exit this screen. If you do not have Telix configured to use a status bar on the BOTTOM of the screen, do so now. This is done from the "Terminal Options" setup screen. Save your new setup and exit Telix. If you are using ZIP files, ensure that a copy of pkzip and pkunzip are located in the host directory or somewhere in your system's path. Decide where you want your DOWN and UP directories and create them with the "MD" command. The DOWN directory is the primary download directory where callers may download files from. However, downloading from the UP (uploads) directory is also permitted. One set-up would be: C:\ -- Telix ---down └----up You would create them by typing "MD C:\TELIX\DOWN" and "MD C:\TELIX\UP". page 4 --------------------------------------------------------------------------- *** SPECIAL NOTE - NEW FEATURE!!! Downloading is now permitted from any valid path on your system. Paths are listed in an ascii (text) file named DOWNLOAD.LST. See page 13 for further details. Now run the BOARD.BAT file by typing "BOARD" and pressing the Enter key. The set-up program will start automatically. When prompted for the SysOp's name and password, enter your name and password, or the name and password of the person who will be the System Operator. Next a list of system parameters will be displayed: Executive Host Configuration A: Name of BBS or Host System : (left blank) A: Executive Host Download Directory : C:\Telix\down\ B: Executive Host Uploads Directory : C:\Telix\up\ C: Connection Type : Modem D: Minutes Allowed per Call : 60 E: Hour of day to run event (0-23) : 0 F: Host Access (Public or Private) : Private G: SysOp's Page Turned On/Off : on H: New Caller's security Level : 1 I: Type of Monitor (Color/Mono) : Mono J: Baud Rate Locked (High-Speed Modems) : No K: Auto Answer Mode or Ring Detection : Auto L: Number of Rings to Answer On : 1 M: Protect Doors With Password : Yes N: FrontEnd Mail System is Attached : No Q: Quit without saving any changes X: Exit and save changes to disk. Which option -> Each option should be configured to your individual needs as below, OPTION A: is the full path of where your download files directory will be located. OPTION B: is the full path of where your uploads directory will be located. OPTION C: should be left as "Modem" unless you are connecting two computers directly with a serial cable, in which it should be set at "Direct". OPTION D: Is the total minutes allowed on-line per call. A number between 1 and 60 minutes may be chosen or "0" for no limit. OPTION E: Time that the Host will execute it's event (EVENT.BAT). Event may be run on any hour of the day (0-23), with "0" representing midnight. page 5 --------------------------------------------------------------------------- OPTION F: This setting, if set at "private", will not allow caller's who are not registered to access the host. If set at "public", new callers may access the host at the security level set in option H. OPTION G: This option sets whether the SysOp's page will be turned on or off. OPTION H: This option selects the security level that will be assigned to new, unverified callers prior to their verification and upgrade by the SysOp. Valid levels for this option are: Level 0 - Caller is "locked-out" of the Host and will have no access. Level 1 - Callers may read mail, view bulletins and info screen, page the SysOp, or leave a private message to the SysOp. Level 2 - Same as 1, but may also view filelists and perform a text search on filelists. Level 3 - Same as 2, but may also enter public messages and upload files. Level 4 - Same as 3, but has access to doors and may view files. Level 5 - Caller has full guest privileges including the ability to download files. OPTION I: Is the type of monitor and should be set as "Mono" if you have a monochrome monitor or "Color" if you have a color monitor. OPTION J: This option should be left as "No" unless you are using an error correcting modem, which requires the baud rate to be locked. (i.e. HST or Hayes 9600 baud modems) OPTION K: Auto Answer Mode sets the modem in the answer mode using the Hayes ATS0=x command. This method is satisfactory in most cases. Ring Detection mode waits until a ring is detected before sending at ATA to the modem signalling it to answer. This mode may be preferred by some in order to better interface with other software programs or hardware (such as modem/fax cards). OPTION L: This option sets the number of rings the modem will wait before answering the phone. Values between 1 and 99 may be selected. OPTION M: This option allows the sysop to decide whether password protection is desired each time a caller returns from a door. It is recommended that this option be kept at 'Yes' for optimal security. Password protection coming out of the remote shell is mandatory. OPTION N: This option tells the host system if it is being executed from a FrontEnd mail system, such as the FrontDoor mail program. FrontEnd programs are necessary in order to interface with certain mail networks, such as FidoNet. page 6 --------------------------------------------------------------------------- This completes the initial installation of the host, and this is all that is required to run the host as a remote access program, or as a simple BBS. Help on the Host's menus are available while running the Host by typing "H" from the main, protocol and message menus. More detailed instructions on how to set up multiple doors, bulletins, filelists, etc. come later in this manual. THE MENU OPTIONS: DESCRIPTIONS OF THE SYSOP'S MENU COMMANDS. █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █ Executive Host █░░ █▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█░░ █ SysOp Menu █░░ ░░░░░░░░░░░░░░░░░░░ █▄▄▄▄▄▄▄▄▄▄▄▄▄▄█░░ ░░░░░░░░░░░░░░░ █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █ (D)ownload File █░░ █ (U)pload File █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █ (F)ile Directories █ (M)essage Menu █░░ █ (V)iew File █ (B)ulletins █░░ █ (T)ext Search █ (O)pen Door █░░ █ (S)hell to Dos █ (EDIT) Guest List █░░ █ (J)oin Conference █ (UTIL)ities █░░ █ (Q)uit Conference █ (I)nfo on Host █░░ █ (X)pert Mode █ (C)olor on/off █░░ █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█ (P)age SysOp █░░ ░░░░░░░░░░░░░░░░░░░░░░░░░░█ (H)elp on Menus █░░ █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█░░ (G)oodbye ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ (D)ownload - Sends a file from Executive Host to you. The SysOp may download from anywhere on the system by using a full path. The SysOp may also use wildcards (i.e. *.*) when downloading with batch protocols. (U)pload - Sets Executive Host up to receive a file from you. The SysOp may also upload files to anywhere on the system by using a full path (i.e. C:\LOTUS\BUSINESS.WKS). If you use Zmodem, you will not be able to upload with a full path since the protocol grabs the filename from the remote site. (F)ile Directories - Gives a list of all files available for download, with file names, sizes, dates, and descriptions. After each screen is filled, the display will pause until <Enter> is pressed. If filelists have not been set-up by the SysOp, only names, sizes, dates, and transfer times will be displayed to the caller. (V)iew - The (Z) sub-option will view any Zip file in the main or uploads directory of Executive Host. A guest may also view text files that are compressed inside of the zip file. The (T) sub-option will allow a guest to view any text file that the SysOp has made available. page 7 --------------------------------------------------------------------------- A directory of text files available for view can be found with the (F) option from the main menu, and then the (T) sub-option. The (S)ysOp view sub-option allows the SysOp to view any text file, anywhere on the system. (T)ext Search - This option allows the caller to do a text search of the filelists made available by the SysOp. Searches for specific text, file names, portions of file names, or even dates (in the correct format) are allowed. Wildcards (* or ?) will be searched for literally and should not be used. If the SysOp has not set-up filelists, this option may not be performed. (J)oin Conference - This option allows callers to join (or enter) a conference area. Conference areas may have their own level of security (minimum access level), file areas, and message base, depending on how the SysOp chooses to set them up. (Q)uit Conference - This option returns the caller to the Main conference area (the area all callers are in when they first log on). This command is used by callers when they are wish to return to the Main conference after using the (J)oin command. (X)pert Mode - This will make Executive Host stop displaying the main, protocol, and message menus. (M)essage Menu - This option displays the five message options available for all callers. They are as follows: (E)nter a message (R)ead messages (N)ote to SysOp (J)oin Conference (Q)uit Conference All of the menu choices on the message menu may also be executed from the main menu, even though some are not listed. (B)ulletins - Displays a menu of bulletins callers may view. (O)pen Door - Displays a menu of doors that may be entered. (UTIL) Host Utilities - This option allows the use of four SysOp utilities. These utilities are: (S)hell to DOS - This allows the SysOp to shell to dos from remote. This option may be used when in local mode, but the F2 key is probably a better choice in this case. The remote shell may be executed without using the "UTIL" option by just entering "S" from the main menu. The Host will shell to DOS using one of three methods. First, if the DOORWAY.EXE file is detected in the Telix directory, the Host will create a DOOR.SYS file and drop to DOS using this excellent redirection program. Doorway will allow the SysOp to run any program from remote that does not run in graphics mode. This includes most word-processors, databases, and spreadsheets. Doorway is share-ware, and the latest version is available on most good BBS's as DRWY220.ZIP. page 8 --------------------------------------------------------------------------- If you need support for running graphic programs from remote, you will have to buy a commercial program such as PC-Anywhere, Carbon Copy, or Commute. Any of these programs can be executed successfully from the Executive Host remote shell. Consult the documentation of these programs on how to run them in the carrier detect startup mode. If Doorway is not detected, then the Host will search for the file DROP.BAT. The SysOp may modify this file to use the redirection program/method of his choice (i.e. Gateway, PC-Anywhere, Commute). If this file is found, the Host will run it to perform the remote shell. NEW FEATURE!!! - Beginning with v1.7, Executive Host now swaps completely out of Telix when executing the remote shell. This means that you will have nearly your entire system memory available to run programs from remote. Swapping completely out of Telix requires that the communications port be reset. This is done by running RESET.EXE (an Executive Host utility) in the first line of the DROP.BAT file. In addition, the BOARD.BAT file must be executed in the last line of the DROP.BAT file, in order to reload Executive Host after the remote shell. An example DROP.BAT file is listed below. This example is the default DROP.BAT file that Executive Host creates automatically when DOORWAY.EXE is detected in the Telix directory. RESET.EXE DOORWAY SYS /O:t /L: /G:ON /V:D /B:M /C:Dos C: CD \TELIX BOARD If DOORWAY.EXE and DROP.BAT are both not found, the Host will use the DOS CTTY redirection function to allow the SysOp to shell from remote. The SysOp will not be able to run most programs, but will be able to use DOS programs and commands, pkzip/pkunzip, and other programs that do not write directly to the screen. (R)ead Host Caller's Log - Allows the remote view of the host caller's log, which is a text record of everything that takes place on the host. The caller's log is also where the caller's registration information is stored. (D)OS Command Line - Allows the execution of dos commands without having to drop to DOS. (EDIT) Guest List - The guest list is the file that contains the list of users of the host. This command allows the SysOp to directly modify the security levels of callers, even from remote. The sub-options for this command are: (V)iew Guest List - Allows the SysOp to view the current list of callers along with their current status (security), and their password. (A)dd a new guest to list - This option allows the SysOp to add a new caller's name and password to the guest list. The new caller is given full guest access to the Host (level 5). page 9 --------------------------------------------------------------------------- (C)hange Caller's Security Level - This option will allow the SysOp to change a caller's access level and set it from (1-8). (D)eny a Guest Access to Host - This in effect "locks-out" a caller. In other words, his access level is set to 0, and when he calls and enters his correct password he will be immediately disconnected. (S)uspend Download privileges - This options will suspend all the downloading privileges of a caller by setting his access level to 4. (T)urn off Host - Shuts down the host from remote. When this option is chosen, the SysOp will be prompted to decide which environment the host should quit to (Telix or DOS). By quitting to DOS, the SysOp may return to a batch file process. (I)nfo on Host - Displays the Executive Host information screen. (C)olor On/Off - This will allow the caller to switch between ascii and color menus. (P)age - If the page is turned on, this will page the SYSOP for 20 seconds. (H)elp - Will display a menu command help file. (G)oodbye - This will log you off, and set Executive Host up for another caller. DESCRIPTIONS OF THE GUEST'S MENU COMMANDS: █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █ Executive Host █░░ █▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█░░ █ Guest Menu █░░ ░░░░░░░░░░░░░░░░░░░ █▄▄▄▄▄▄▄▄▄▄▄▄▄▄█░░ ░░░░░░░░░░░░░░░ █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █ (D)ownload File █░░ █ (U)pload File █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █ (F)ile Directories █ (M)essage Menu █░░ █ (V)iew File █ (B)ulletins █░░ █ (T)ext Search █ (O)pen Door █░░ █ (J)oin Conference █ (I)nfo on Host █░░ █ (Q)uit Conference █ (C)olor on/off █░░ █ (X)pert Mode █ (N)ote to Sysop █░░ █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█ (P)age SysOp █░░ ░░░░░░░░░░░░░░░░░░░░░░░░░░█ (H)elp on Menus █░░ █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█░░ (G)oodbye ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ page 10 --------------------------------------------------------------------------- The Guest menu is identical to the SysOp menu except for the substitution of the (N)ote to SysOp command in the place of the SysOp (UTIL)ities command. The (N)ote to SysOp command will allow a caller to leave a message to the sysop, no matter what the caller's security level. If a caller's security level 2 or below, the message is automatically marked as private E-mail. DESCRIPTIONS OF THE MESSAGE MENU COMMANDS: █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █ Executive Host █░░ █ Message Menu █░░ █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█░░ █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█░░ ░░░░░░░░░░░░░░░░░░░ ░░░░░░░░░░░░░░░░░ █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █ █░░ █ (E)nter a Message █░░ █ (R)ead Messages █░░ █ (N)ote to SysOp █░░ █ (J)oin Conference █░░ █ (Q)uit Conference █░░ █ █░░ █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█░░ ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ (H)elp on Message Menu (E)nter Message - Allows callers with access level 3 or above to leave a private or public message. Public messages may be addressed to a specific person, or to "ALL". Callers with access level 2 or below may only leave private mail addressed to the SysOp. (R)ead Messages - Allows callers to read mail addressed to them, and also read all messages in the conference marked as public mail. The (N)ote to SysOp, (J)oin Conference, and (Q)uit Conference commands are identical to those found on the main guest and sysop menus. SYSOP'S FUNCTION KEYS (ON-LINE COMMANDS): The SysOp has eight commands on the function keys that may be executed while a caller is on-line, or while in the local logon mode. The SysOp may toggle the list of commands on the status line by using the up and down arrow keys. F1 Key - Kill User - This function will hang-up on the current caller immediately with no warning or comment. F2 Key - Dos Functions - This function will bring up the Telix Dos functions window where the SysOp may drop to dos, perform a directory, etc. page 11 --------------------------------------------------------------------------- F3 Key - This key will initiate chat with the current caller. F4 Key - This key will allow the SysOp to edit the user file (EXECHOST.USR) file with a text editor, while the caller waits on-line. F5 Key - This key will raise the caller's access level (temporarily) to the SysOp level (level 9). F6 Key - This key will set the caller's access level (temporarily) to access level 5 (full guest access). F7 Key - This key will increase the caller's on-line time in 5-minute increments. F8 Key - This key will decrease the caller's on-line time in 5-minute decrements. F9 Key - This key toggles the page on/off switch. If this switch is on callers will be able to page the SysOp. If it is turned off, the caller will be instructed to leave a message. F10 Key - This key displays the SysOp's full-screen help. It does not interfere with the caller, and the caller cannot see the help message. HOST SECURITY LEVELS: Level 0 - Caller is "locked-out" of the Host and will have no access. Level 1 - Callers may read mail, view bulletins and info screen, page the SysOp, or leave a private message to the SysOp. Level 2 - Same as 1, but may also view filelists and perform a text search on filelists. Level 3 - Same as 2, but may also enter public messages and upload files. Level 4 - Same as 3, but has access to doors and may view files. Level 5 - Caller has full guest privileges including the ability to download files. Level 6 - Same access as 5, but higher conference security. Level 7 - Same access as 5, except for time allowed online. If the SysOp is not giving all callers unlimited time, this level will always be given 60 minutes access. Also higher conference security. Level 8 - Same access as 5, except this caller will always have an unlimited amount of access time. Also higher conference security. Level 9 - SysOp status. Caller has full access to all SysOp functions. page 12 --------------------------------------------------------------------------- Access level 9 may not be assigned via the Guest List Editor. In order to assign this powerful level to a caller other than yourself, you must edit the EXECHOST.USR file with your text editor. It is highly recommended that you not give anyone an access level 9 other than yourself. Access level 9 will give the caller complete access to your system, and disastrous results could occur either by accident or on purpose. EDITING THE EXECHOST.USR FILE: Here is one example of an Executive Host Guest List File (exechost.usr). ⌐----------------- User's Name | ⌐--------- User's Password | | ⌐----- User's Security Level | | | ⌐--- User's Data Number (used in execmail.dat) | | | | | | | | (semicolons used as dividers) | | | | | | | | John Wright;host;9;1 << SysOp >> Edward Williams;dud;5;2 << Guest >> Brent Taft;whipped;5;3 << Guest >> Jay Fuller;guy;5;4 << Guest >> Jack Ripper;nut;5;5 << Guest >> Bob Coffey;pup;5;6 << Guest >> Claude Hammond;smart;5;7 << Guest >> Access Levels may be changed by directly modifying this file with a text editor. This is the only way you will be able to assign access level 9 to a user. In most cases, the easiest way to change access levels is by using the on-line guest list editor. Once logged on either local or from remote, enter "edit" from the main menu. THE MESSAGE BASE AND HOW IT WORKS: The message base combines public messages and private E-mail into one secure message system. Each message base has its own index file for added speed and ease of use. The message base uses the message data numbers assigned to each user in the EXECHOST.USR file. The data numbers are added sequentially to the file EXECMAIL.DAT, where the user's message information is stored. Two important bits of information are stored here. The first is the number of the user's last message read. This is stored in order to give the caller an idea of where he left off from the last time he read messages. The second bit of information is the number of the last public message addressed to the user. When a caller logs on, the Host looks at the message data file, and compares the last message read with the last message sent to the user. This way the Host is able to quickly determine if the user has new mail, without having to scan the entire message base. page 13 --------------------------------------------------------------------------- This quick scan is performed for each conference in which the caller has access (if conferences have been setup), and the caller is notified of which conferences he has mail waiting. Messages written to or from the caller may be deleted by choosing (k)ill at the bottom of the message. The SysOp may delete any public message. Note: This function does not actually delete the message from the message base, but simply marks it as deleted so callers are unable to read it. PACK.EXE must be run to strip these deleted messages from the message base. It is recommended that SysOps run PACK.EXE at least once a week (or in the daily event) in order to trim down the size of the message base and speed up it's operation. Read the file PACK.DOC for more information on PACK.EXE. Example of the EXECMAIL.DAT file: ⌐------- Message Data Number | ⌐--- User's Last Message Read (public message) | | ⌐ Number of Last Message Sent to User (public message) | | | | | | (semicolons user as dividers) 001;000040;000038 002;000039;000012 003;000040;000033 004;000022;000007 005;000035;000004 ADDING FILES TO YOUR HOST SETUP: If you are running the program as a public access BBS, or just as a semi-private host, you will be sure to want to make available certain programs for download. Of course the SysOp may download from anywhere on the system, but guest callers may download from only the upload and download directories. Therefore, in order to make programs available to all callers, they must be copied into one of these directories. The arrangement makes no difference; all files may be in the uploads directory, all files may be in one of the download directories, or any combination is fine and the Host will find them all. ** NEW!! ** Beginning with version 1.6, any valid path on the computer system may be used as a download directory. In order for the Host to recognize them properly they must be listed in a file named DOWNLOAD.LST. i.e. << Beginning of File >> C:\GAMES\ D:\UTILS\ E:\CDROM1\ E:\CDROM2\ etc, etc.... << End of File >> page 14 --------------------------------------------------------------------------- There is no limit to the number of paths that may be used as download directories for your callers. WARNING!! Do not add your Telix directory to this list, since this would compromise your system security. If you are using filelists with descriptions, initially just copy your new files to a download directory. Then use the Host Filer to add these filenames to your filelists (Option A). After your initial set-up it is a good idea to add new programs to the filelists prior to copying them into the download directories. The easiest and most efficient way to do this is to first separate new files into categories represented by your filelists. For example, copy all of your new utility files into a temporary directory. Then use option A to add the new files to your utility filelist. This will allow you to enter a path such as "C:\TEMP\*.ZIP", instead of adding each file individually. All that is left is to copy the files into a valid download directory, delete the original files in the temp directory, and start your new category. INSTALLING DESCRIPTION FILES - Executive Host works fine using only physical (DOS) file directories, however most SysOps who want to run a serious bbs will want to use a series of filelists that will display the filenames, dates, and descriptions. Executive Host has an advanced filer built in, and filelists can be setup easily as follows. 1. Decide how many different filelists you wish to use, and enter their names and numbers in the directory data file DIR.DAT. 2. If you want to use only one big filelist, the DIR.DAT file is not necessary. Just name the filelist MAIN.DIR, and the host will use it. 3. If you use the DIR.DAT file, you must also use the file called DIRLIST. This file is the menu that will be displayed whenever a caller chooses to view the filelists, and should contain the menu of filelists with their corresponding number. An ansi color directory menu file may also be used and must be called DIRLISTG. Ansi colors are automatically added to DIRLIST if this file is not present. 4. A Recent Uploads filelist should also be created and must be called NEW.DIR. This file is where the descriptions of files uploaded by callers will be added. It is recommended that files be rotated out of the Recent Uploads directory after about a week's time, but that is up to the SysOp. 5. Once the data file has been setup and each filelist has been created, the Host Filer (F6) will recognize your setup and allow you to edit and modify these files when necessary. All files must be in the Telix directory. Example files of the DIR.DAT, DIRLIST and DIRLISTG files are included in the file EXAMPLES.ZIP. 6. Ansi colors are added to the filelists automatically, so a separate ansi file is not necessary. page 15 --------------------------------------------------------------------------- INSTALLING BULLETINS - The set-up for bulletins is similar to the setup for filelists and is done as follows: 1. If you wish to use only one bulletin file, name it BULLETIN, and the Host will display it when a caller selects the view bulletins option. An ansi bulletin may also be displayed for callers who choose color. This file must be called BULLTING. 2. If you wish to set-up multiple bulletins, you must use a data file similar to the filelist data file. Enter each bulletin's name and number in the file BULLETIN.DAT. 3. If you are using multiple bulletins, you must modify the file BULLLIST, which is the menu displayed to callers that shows the available bulletins, and their corresponding number The file BULLLIST.G may also be used to display a color bulletin menu. Ansi colors are automatically added if this file is not found. 4. Create each bulletin with your text editor, and put them in the host directory. Ansi is added automatically to the bulletins unless you wish to make separate ansi bulletins. You may do this by adding a "G" to the end of the bulletin file name. For example, the ansi bulletin for the file RULES, should be RULESG. Note that the bulletin name may not be longer than 7 characters long if an ansi version of the bulletin is to be used. 5. Once all of this has been completed, your bulletins, menu, and data file may be modified in the SysOp's Utilities Window (F5) at the waiting for call screen. INSTALLING DOORS - The set-up of doors is also similar to the set-up of bulletins and filelists, and is done as follows: 1. If you wish to have only one door on-line, then create a file called DOOR.BAT that will run the door. DOOR.BAT will be run whenever a caller chooses the (O)pen Door option. 2. If you wish to use multiple doors, modify the file DOOR.DAT with the batch file name and corresponding number of each door. 3. Also modify the door menu file DOORLIST, which is displayed to the caller when the (O)pen Door option is chosen. The file DOORLIST.G may be used to create a color door menu to callers. Ansi colors are automatically added if this file is not found. 4. Create the batch file for each door to be run. FISHING.BAT is an example of a batch file for an RBBS door. 5. Once the above has been accomplished, the door batch files, menu, and data file may be modified from the SysOp's Utilities window (F5) at the waiting for call screen. page 16 --------------------------------------------------------------------------- 6. Two files are created when a door is opened, a GAP BBS compatible DOOR.SYS file which is recognized by Gap door programs and Doorway, and the DORINFO1.DEF file, which is recognized by RBBS compatible doors, and some QBBS doors. 7. IMPORTANT!: Beginning with version 1.7, Executive Host swaps completely out of Telix to execute door programs. For this reason, and in order to reset the computer's communications port, the RESET.EXE program must be run in each door batch file. RESET.EXE should be the first command executed in each door batch file, otherwise the some doors may become confused and. In addition, since Telix is completely swapped out when running doors, in order to reload the host system, the board.bat file must be run as the last line in ALL door batch files. An example door batch file for the Kannons and Katapults door game is listed below. RESET.EXE CD KNK KNK C:\TELIX\DORINFO1.DEF CD \TELIX BOARD.BAT Notice that RESET.EXE is the first command in the batch file, and that BOARD.BAT is the last command. It is very important that all door batch files are setup similarly. INSTALLING CONFERENCES - The setup of conferences in Executive Host was new to version 1.6, and can add much power and flexibility to the host system. Setup of conferences is listed on a step-by-step basis below. There are four main steps. 1. Create the conference subdirectory with the DOS "MD" command. Conference subdirectories are where the conference messages and other data files are stored, and these subdirectories must branch directly off of the Telix directory. For example, to create a subdirectory for the SYSOP conference, you would type "MD SYSOP" from the Telix subdirectory. Although conference subdirectories do not have to be named the same as the conference name, it is probably a good idea to do so. 2. Add the conference setup information to the file CONF.DAT. This is where the conference name, number, and other important information are stored. The format of this file is shown below: 1;SysOp <-- number and name of conference (1) SYSOP\ <-- conference directory (2) C:\TELIX\DOWN\ <-- conference download directory (3) C:\TELIX\UP\ <-- conference upload directory (4) 6 <-- minimum access level for conference (5) Line one contains the conference number and name. Be sure to limit your conference name to less than 30 characters. page 17 --------------------------------------------------------------------------- Line two contains the name of the conference directory that you just created using the DOS "MD" command. Do not use the full path, i.e. "C:\TELIX\SYSOP\". Enter the path in the exact format as shown above. Line three contains the conference download directory. This may be the same or different from the main download directory setup in the Host configuration. Line four contains the conference upload directory. This path may also be the same or different than the main upload directory setup in the Host configuration. Line five contains the minimum access level of callers that will be admitted into the conference. Be sure to end all paths with a "\" backslash, as shown above. More conferences are added to the CONF.DAT file in the same manner, by listing this information below the last conference. An example of the CONF.DAT file with setups for three conferences is included in the file EXAMPLES.ZIP. 3. Next create or edit the CONFMENU and CONFMENU.G files. These are the conference menu files that will be displayed to callers when they select the (J)oin Conference option from the main menu. These files, along with the CONF.DAT file must be present in the Telix directory in order for the Host to recognize that conferences have been setup properly. Examples of both of these files are also included in EXAMPLES.ZIP. 4. Special conference files and menus may now be added to the conference directory. Conference specific setups for bulletins, doors, and filelists may be created for each conference. For example, if the Host found the files DIRLIST/DIRLIST.G and DIR.DAT in a conference directory, it would use this filelist setup when callers are in this conference only. The SysOp can setup bulletins, filelists and doors in each conference, EXACTLY as was done for the Main conference. By limiting the access of callers admitted into conferences, the SysOp can thus create private conferences with their own file areas, doors, bulletins and message bases. In addition, the SysOp may design different menus for each conference, and place them in the conference directory, if so inclined. The following files may be placed in the conference directory as substitutes for the files and menus in the Telix directory: OPEN * OPENG * NEWS * NEWSG * DIR.DAT DIRLIST DIRLISTG DOOR.DAT DOORLIST DOORLIST.G BULLETIN.DAT BULLLIST BULLLIST.G page 18 --------------------------------------------------------------------------- Executive Host v1.7 also supports different menus in each conference. These files, of course, are not necessary, but if you wish to have different menus in each conference, it is now possible. Of course, you must have a registered version of Executive Host to utilize custom menus. Files marked with an asterisk (*) will only be displayed if found in the conference directory. If any of the other files are not found in the conference directory, the identical files in the Telix directory will be used. In other words, the Main conference's filelists, bulletins and doors will always be used as a default if the SysOp has not setup special ones for each conference. No other files of any kind should be copied into the conference directory, as they will not be used and will only waste your hard-drive space. In particular, all filelists (dir files), bulletins, and door batch files should be kept in the Telix directory, and full paths are not necessary in the DIR.DAT, DOOR.DAT, and BULLETIN.DAT files. ADDITIONAL SYSTEM SECURITY - Version 1.7 and above now allows the SysOp to create and update a 'trashcan' file. This file should be called TRASHCAN.TXT and is a list of obscene and/or undesirable names that the SysOp wishes to check new callers' names against, when they are first registering. When a caller first logs in as a new user, his name is checked against the names in the trashcan file. If the new caller's name matches with any of the undesirable names listed in the file, the caller is disconnected immediately. This file can be used to weed out obvious undesirable callers with names such as 'Hacker', and can also be used to prevent a particular person from registering who has proved to be a problem in the past. Both single and full names can be added to this file, and should be listed, one on each line, as shown below (case is insignificant): Hacker Jerk Joe Pest BBS Terrorist etc. CALLER REGISTRATION INFORMATION AND SCRIPTS - Version 1.7 and above now has an external script questionnaire with a list of questions to be asked of new callers. This script questionnaire file is named REGISTER.ASK, and can be modified by the SysOp to change the default questions, or add additional questions. Answers to the new user questionnaire are no longer saved to the EXECHOST.LOG file. Instead, answers to the REGISTER.ASK file are saved to a file named REGISTER.ANS. THE HOST EVENT - Executive Host will execute the EVENT.BAT file daily, at the hour specified in the Host Configuration. The default EVENT.BAT file executes the PACK.EXE message base utility, and then runs the BOARD.BAT file to reload the Host. Additionally, the host deletes the file CALLERS.DAT (internally) immediately after executing the event. page 19 --------------------------------------------------------------------------- This file contains information on how much time each caller has left on the BBS for that particular day. If you are not running your host 24 hours, and the event is not run each day, this file will still need to be deleted, otherwise all active callers will eventually run out of time, and will be unable to login to your system. The EVENT.BAT file is a perfect place to run optional utilities and perform automatic backup procedures on your system. USING THE HOST UTILITIES - By Pressing the F5 key at the waiting for caller screen, the SysOp may enter the Host Utilities area. In this area the SysOp may choose from 10 different utility functions (A-J). If conferences have been setup, the conference menu will be displayed, and the SysOp will be asked to select the conference to work out of. ╔══════════════════════════════════════════════════════════════════╗ ║ ║ ║ ║ ║ Sysop's Host Utilities ║ ║ ║ ║ ║ ║ A> List Caller's Log F> Edit Door List ║ ║ ║ ║ B> Edit UserFile G> Edit Door Batch Files ║ ║ ║ ║ C> Edit Bulletin List H> Edit Door Data File ║ ║ ║ ║ D> Edit Bulletins I> Test-Run Door ║ ║ ║ ║ E> Edit Bulletin Data File J> DOS Command Line ║ ║ ║ ║ ║ ║ Choose a Utility Option? <Enter>=quit -> ║ ║ ║ ║ ║ ╚══════════════════════════════════════════════════════════════════╝ (A) - List Caller's Log. This option will use the LIST.COM file browsing utility to view the Host caller's log. A copy of List.com must be located in the Telix directory. V. Buerg's more advanced list.com may be substituted in the place of the list program distributed with Executive Host. (B) - Edit UserFile. This option will use the text editor defined in Telix to edit the Host's user database. Callers' passwords and security may be manually changed using this option. Be careful to not alter the structure or order of this file, otherwise the host will report an error. (C) - Press C to bring up the bulletin menu file in your text editor. This is the file that shows callers the bulletins available for view. If this file is modified, and you are also using the file BULLLIST.G to display a color menu, you will have to make the necessary changes to it also. page 20 --------------------------------------------------------------------------- (D) - Option D will allow the editing of each bulletin that is set-up in the bulletin data file (BULLETIN.DAT). First you will be displayed the bulletin menu, from which you must select which bulletin to edit. (E) - Option E allows will bring up the bulletin data file in your text editor. This is the file that tells the host, which bulletins to read, and their respective numbers. (F) - Option F will allow the editing of the door menu file DOORLIST. This is the menu of all doors available for callers, and is displayed when a caller enters "O" for open door. If you are using the file DOORLIST.G. (G) - Choosing option G will allow you to edit any of your batch files that execute doors. The Host will display your door menu, in order for you to select the batch file to edit, and will then bring up the batch file you choose in your text editor. (H) - Option H allow you to edit the door data file, which contains the number and name of each door available for callers to use. (I) - This option will test-run any of the doors that you have set-up in the door data file. It will display your door menu, and ask you to select a door to test-run. Once you have done this it will run the door's batch file, and allow you to test your set-up and installation of doors. (J) - DOS Command Line - This option will allow the SysOp to run a specific application without dropping to DOS. A Drop to DOS may be accomplished by pressing the <Enter> or <ESC> key from the DOS command Line. USING THE HOST FILER - By pressing the F6 key at the waiting for caller screen, the SysOp may enter the Host Filer area. In this area the SysOp may choose from 10 different Filer options also (A-J). If conferences have been setup, the conference menu will be displayed, and the SysOp will be asked to select the conference to work out of. ╔══════════════════════════════════════════════════════════════════╗ ║ ║ ║ Executive Host Filer ║ ║ ║ ║ A> Add New Files to Filelist F> Verify Filelist ║ ║ ║ ║ B> Auto-Describe Filelist G> Sort Filelist ║ ║ ║ ║ C> Edit Filelist Menu H> Run Editor ║ ║ ║ ║ D> Edit Filelist I> Run List.com ║ ║ ║ ║ E> Edit Filelist Data File J> DOS Command Line ║ ║ ║ ║ ║ ║ Choose a Filer Option? <Enter>=quit -> ║ ║ ║ ╚══════════════════════════════════════════════════════════════════╝ page 21 --------------------------------------------------------------------------- (A) - The "Add New Files to Filelist" option allows the SysOp to add one or more new files that he has acquired to a filelist. The SysOp will be asked for the path of the new programs first. For example "A:*.ZIP" may be entered. Then the SysOp will be asked which filelist to add the new programs to. The file adder will add these programs to the filelist and allow the manual entry of descriptions by the SysOp. Also remember to sort the filelist after the new files have been added (Option G). The new files must of course be copied into the main or uploads directory in order to be available for downloading. (B) - The "Auto-Describe Filelist" option will add descriptions to your filelist from an existing list. In other words, if you have just used option (A) to add new files to an Executive Host filelist, and you do not want to add all of the descriptions manually, you have another alternative. You can download or capture a filelist from another BBS, and use this source file to transfer the descriptions to your Host filelist. This is the purpose of option (B). The source file may be in any popular bbs format i.e. PCB, RBBS, dBBS, etc. The SysOp will be asked for the name of the filelist that needs descriptions added. Next, the name of the source file to be searched must be entered. Both files must be sorted alphabetically prior to using this option. A .bak file of the filelist is created in case something goes wrong. All files must be in the Telix (Host) directory. (C-E) - Allows the editing of filelists, the directory menu file, and the directory data file. (F) - Verify Filelist - This option will verify that all the files in a filelist really exist in either the upload or download directories. If you have a dir file with 75 files, a successful verification result would look like this: 75 files processed. 0 files NOT Found. (G) - Sort Filelist - This option will sort a filelist using the program SORTIT.EXE. This program sorts filelists alphabetically, while ignoring (not sorting) any filelist information header that may be present. Filelists may not be larger than 64k in size. A custom sort program, such as V. Buerg's SORTF.COM may be implemented to sort files larger than 64k. This is done by deleting the file SORTIT.EXE and creating a batch file named SORTIT.BAT to run the program. It is a good idea to always keep filelists sorted in order to give callers an orderly display of files available for download. Also, filelists must be sorted prior to using the "Auto-Describe Filelist" option in the Host Filer. To sort a file from the dos prompt, simply type "SORTIT [name of filelist]". (H) - Run Editor - This option simply runs the editor defined in Telix without a file name. Ted.com is run by default if an editor is not defined in Telix. (I) - Run List - This option will run the LIST.COM file browsing utility if it is present in the Telix directory. (J) - DOS command Line - This option is identical to option "J" in the Host Utilities area. You may enter a DOS command to be executed, or press <Enter> or <Esc> to drop to DOS. page 22 --------------------------------------------------------------------------- DOWNLOADING - Downloading may take place from either upload or download directories, and all files in any of these directories are always available for download by all callers with access to the conference. The SysOp may of course enter a full path and download from anywhere on the system. Remember that the file DOWNLOAD.LST may be used to make any path on the system a valid Executive Host download directory. UPLOADING - Files uploaded by all callers will be sent to the uploads directory. In addition the UPLOADS.BAT file will be run if it exists. This batch file could perform various virus checking functions, and integrity checks on the uploaded file(s). The SysOp may include a full path when uploading, and the file can be sent anywhere on the system. IMPORTANT FILES TO BECOME FAMILIAR WITH - The following files are used in the day to day operation of the Host and their structure and format should be studied by the SysOp. If they should ever become corrupted or deleted, your knowledge of their structure will ensure that you will be back on-line quickly. System and Message Base Files: exechost.usr - the Host UserFile containing the name, password, and security levels of all callers. exechost.cnf - the Host configuration data file execmail.dat - the message base data file. message.txt - the message base text. message.dat - the message base pointers data file. message.ndx - the message base index file Executive Host External Menu Files: * guest.men - main menu displayed to all callers except sysop * guestg.men - ansi version of guest.men * sysop.men - main menu displayed to the sysop only * sysopg.men - ansi version of sysop.men * message.men - message system menu * messageg.men - ansi version of message.men * protocol.men - protocol selection menu * protcolg.men - ansi version of protocol.men * util.men - sysop utilities menu * utilg.men - ansi version of util.men * edit.men - sysop's edit guest list menu * editg.men - ansi version of edit.men [*] - these files are not supported in the UNREGISTERED version. page 23 --------------------------------------------------------------------------- Other important files: exechost.log - host usage log - contains a log of caller activities on your host bbs system. register.ask - the script file questionnaire which contains questions asked of all new callers. register.ans - the answer file containing each new caller's answers to the questions in the register.ask script file. trashcan.txt - text file containing any obscene or undesirable names you wish to check new callers' names against before granting registration. sortit.exe - program that sorts filelists. reset.exe - resets communications port before remote shell & doors. pack.exe - removes deleted mail from each message base and updates the message index file. list.com - text file browse utility. drop.bat - batch file used for remote shell to DOS. upload.bat - batch file executed whenever a caller uploads a file. event.bat - batch file run as an "event" at a certain hour each day. board.bat - runs Executive Host. bimodem.bat - runs the optional Bimodem protocol program. logon.bat - executed immediately prior to the open/openg files being displayed to a caller (if found). logoff.bat - executed immediately after each caller logs off the host system (if found). dir.dat - data file of filelists. door.dat - data file of door batch files. bulletin.dat - data file of bulletin files available for view. callers.dat - data file recording on-line time used by callers. conf.dat - data file with conference information. bulllist - bulletin menu file displayed to callers. bullist.g - ansi version of bulllist. dirlist - directory file menu displayed to callers. dirlistg - ansi version of dirlist. doorlist - door menu file displayed to callers. doorlist.g - ansi version of doorlist. open - ascii file displayed when caller first logs on. openg - ansi version of open file. news - news file that is displayed immediately following open/openg. newsg - ansi version of news file. vip - file displayed to callers with access level 6 or 7 immediately after the news file. vipg - ansi version of vip file. info - file displayed when caller chooses (I)nfo on Host. infog - ansi version of info file. goodbye - file displayed when caller logs off. goodbyeg - ansi version of goodbye. newuser - file displayed after a new caller registers. newuserg - ansi version of newuser file. uptest - file that is displayed immediately after an upload. uptestg - ansi version of uptest file. page 24 --------------------------------------------------------------------------- LIMITS - The following limits are built into all versions of Executive Host. 9,999 Registered Callers. 999 Conferences, each with its own message base. 99 Filelists per conference (9,801 total). 99 Bulletins per conference (9,801 total). 99 Doors per conference (9,801 total). 999,999 Messages in each conference message base (98,999,901 total). Of course disk space is a limiting factor in many cases. SUPPORT - Support for Executive Host is available exclusively at the BBS listed below. Support is available 24 hours a day. Main Support Board - The WOODSHED, (404) 279-8923 (14400bps,N,8,1). We will always be operating with the latest version of Executive Host Software (sometimes Beta), and a v.32.bis modem. The author (Steve Wood) is active in the Telix conference on the RIME international mail network, if you wish to contact him there. Support is also available on the following BBS Systems: Trying Hard BBS . . . . . 404-509-7464 Priority of support will always go to Registered users of Executive Host. Thank you and enjoy Executive Host. page A1 --------------------------------------------------------------------------- APPENDIX A - HIGH SPEED AND ERROR CORRECTING MODEM SETUP The US Robotics and other high speed or error correcting modems require special settings in order to work properly with Telix and Executive Host. You have two choices that will allow you to connect with all callers. But first, make sure that you have a copy of Executive Host 1.3 or above. Support for these modems was not included with earlier versions. OPTION 1: Set the Executive Host configuration "Lock Baud Rates" to "YES". Then go into Telix configuration and ensure that the two screens below are set as indicated. The most important settings for Executive Host have been marked with the "(*)" sign. These settings MUST be set as shown to have the Host perform correctly. The Baud rate shown below should be set at 4800 or 9600 for 2400cps modems, or 19200 or 38400 for high speed (9600 baud) modems, such as the USRobotics HST dual standard. ╒═╡ Terminal options ╞═════════════════════════════════════════════════╕ │ │ │ A - Baud 19200 Parity None Data length 8 Stop bits 1 (*) │ │ B - COM2 or COM1 │ │ │ │ C - Default terminal type ........... ANSI-BBS (*) │ │ D - Status line ..................... Bottom (*) │ │ E - Local echo ...................... Off │ │ F - Add Line Feeds after CRs ........ Off │ │ G - Strip high bit (incoming data) .. Off │ │ H - Received Backspace destructive .. On │ │ I - XON/XOFF software flow control .. On (*) │ │ J - CTS/RTS hardware flow control ... On (*) │ │ K - DSR/DTR hardware flow control ... Off (*) │ │ L - Compuserve Quick B transfers .... On │ │ M - Zmodem auto-downloads ........... On │ │ N - Answerback string (ENQ) ......... │ │ │ │ │ │ Change which setting? (Return or Esc to exit) │ ╘══════════════════════════════════════════════════════════════════════╛ page A2 --------------------------------------------------------------------------- ╒═╡ Modem and dialing parameter setup ╞════════════════════════════════╕ │ │ │ A - Init string ......... ~~~+++~~~AT&B1&H1&I0&R2V1X4^M (*) │ │ B - Dialing prefix 1 .... ATDP (NOTE: Be sure to save the above │ │ C - Dialing prefix 2 .... ATDP string into your NVRAM "AT&W"). │ │ D - Dialing prefix 3 .... ATDP │ │ E - Dialing suffix ...... ^M │ │ F - Connect string ...... CONNECT │ │ G - No connect strings .. NO CARRIER BUSY │ │ VOICE NO DIAL TONE │ │ H - Hang-up string ...... ~~~+++~~~ATH0^M │ │ I - Auto answer string .. ~~~+++~~~ATS0=1^M │ │ J - Dial cancel string .. ^M │ │ │ │ K - Dial time ........... 50 │ │ L - Redial pause ........ 10 │ │ M - Auto baud detect .... Off (*) │ │ N - Drop DTR to hangup .. On (*) │ │ │ │ │ │ Change which setting? (Return or Esc to exit) │ ╘══════════════════════════════════════════════════════════════════════╛ The new Telix modem configuration program (included with v3.15 of Telix), will setup your modem and Telix in a similar manner. However, you must ensure that both CTS/RTS and Xon/Xoff flow control are enabled. The Executive Host configuration option "Lock Baud Rates?" must be set to "Yes". Additional help for the setup of high speed and error correcting modems under Executive Host is available on our support BBS, 24 hours a day. page B1 --------------------------------------------------------------------------- APPENDIX B - MAIL DOORS, OFFLINE READERS, MAIL NETWORKS, AND FRONTENDS UNIVERSAL TEXT INTERFACE (UTI) - Executive Host UTI conversion utilities already exist to link the Executive Host message base with many external mail programs and networks. The latest version of these drivers will always be made available on the bbs systems listed below. THE WOODSHED BBS - (602) 841-7881 sysop, Steve Wood Trying Hard BBS - (404) 509-7464 sysop, Karl Ulrich The UTI utilities allow the sysop to use the following programs in conjunction with Executive Host. 1. PCrelay Software - written by Kip Compton. This software allows Executive Host systems to be linked with the Relaynet (RIMES) international mail network, and other mail networks that run under PCrelay software. PCrelay can also be used to link BBS's together (outside of a network), in order to share message bases. 2. MegaDoor Offline Mail Door - written by Kip Compton. This software is setup as a door under Executive Host, and allows callers to download mail, read and reply offline, and upload new mail into the Executive Host system later. 3. MegaReader Offline Mail Reader - written by Kip Compton. The MegaReader program is used by callers to read and reply offline to messages downloaded from the MegaDoor. 4. Any other MegaMail compatible program or door available now or in the future. The latest version and technical support for all of the products listed above can be obtained directly from Kip Compton on his support bbs, 24 hours a day: - (703) 690-7361. FRONTEND PROGRAMS: Additionally, Executive Host now has sufficient support to be run from a frontend mail program. Frontend Mail programs actually answer incoming calls, and then pass the necessary information on to the bbs software so that the caller can be logged in normally. Many people prefer to run BBS software from a frontend program such as FrontDoor, because of its consistent interface and also because of the many additional features available to the sysop while waiting for incoming calls. Primarily however, frontend programs were designed for linking message base systems with other bbs systems and mail networks. It is possible that the existing UTI drivers for Executive Host can be modified to allow the message base to be linked to networks via a frontend program. page B2 --------------------------------------------------------------------------- The same is true for linking the Executive Host message base with mail networks that require a frontend, such as the FidoNet international mail network. However, at the time this manual was written, it has never been done, so further information is not currently available. In order to obtain the current caller information from the frontend program, Executive Host will read a file named FRONTEND.USR. This file must contain three pieces of information, normally passed as command line parameters from frontend programs: baud rate port minutes left before next event This file can be built automatically by the batch file that calls Executive Host. The FrontDoor mail program passes the baud, port, and minutes until next event information as %1, %2, and %3 command line variables. An example of the EXEBBS.BAT file used by FrontDoor is listed below: ECHO %1 > FRONTEND.USR ; copies the baud info to the new file ECHO %2 >> FRONTEND.USR ; appends the port info to the file ECHO %3 >> FRONTEND.USR ; appends the minutes left info BOARD.BAT ; runs Executive Host Please call the Executive Host support BBS (WOODSHED) for further information on setting up frontend programs.