****** ****** * * ***** ***** ***** ***** * * * * * * * * * * * * **** * ******* * * * * * * ****** * * * * * * * * * * * * * * * * * * * * * * * * ****** ****** * * ***** ***** ***** * * EchoDor version 3.11 Original Program By Scott Baker Modifications by Robert McCullough Documentation by Jonathan Woods If you should happen to find this program useful, Please send a contribution to: Robert McCullough P.O. Box 101095 Nashville, TN 37224 Voice Phone 615 256-2444 For the latest version of EchoDor, you may call The NEW WorkBench BBS (9600/Hst) BBS Phone 615 256-2211 FidoNet Node 1:116/1000.0 RBBS Net 8:967/1.0 File Requestable as ECHODOR EchoDor Version 3.11 3/16/92 Introduction 1 Installation 2 DoorDriv.Ctl parameter file 5 Multiple DoorDriv.Ctl files 5 Parameters 6 Color Table 12 Special instructions 13 PC Board 14 13 PC Board 12 13 Opus 1.7x 13 GT PowerComm 13 Genesis Deluxe 13 LINE-A operation 13 LINE-B operation 14 ECHODOR.CTL parameter file 15 Display file naming 15 Parameters 16 Color Table 32 SYSOP setup 33 Pack Mail / Compress / Download Setup 34 Basic Setup 34 Compressing Mail 35 Downloading Mail 36 Multiple Node Setup 38 The Common Directory Method 39 Multiple Directory Method 42 Multiple Net Setup 45 Purging & Renumbering Areas 47 The Three Step Method 47 EDorPurg 49 Setup 49 EDorPurg Parameters 51 Operation 53 Recovery Method 54 FastLink 55 Parameters 55 Operation 57 Page i EchoDor Version 3.11 3/16/92 EchoDor Operation 59 Menu Commands 59 Reading messages 60 Entering messages 62 Line Editor 62 Full Screen Editor 64 Insert Mode versus Over type Mode 66 Keyboard emulation 66 Visual Quote 67 Using EchoDor Locally 68 Special local keys 69 Message Header Description 70 How do file-requests work? 72 File-attaches 74 Auto Messages 76 General information 77 EchoUser Program 78 User File Records 78 Default User & Maintenance Record 78 User Records 79 Remote Operation 80 Using SCANMRG 81 The EchoDor Nodelist compiler 82 How it works 82 The Control file 82 Running EchoNLCP 83 EchoNLRD node list reader 84 Opus 1.1x Converter (OPUSCNVT) 85 Support for EchoDor 86 Revision History 87 3.11 revisions 87 Page ii EchoDor Version 3.11 3/16/92 3.10a revisions (we didn't release a 3.10): 90 3.09 revisions: 92 3.08 revisions: 95 Run Time Errors 97 Plans for next version 103 Registration 104 Disclaimer 105 Guarantee 106 Page iii EchoDor Version 3.11 3/16/92 Introduction EchoDor is a full featured echo mail conference processor that incorporates features found in many door programs, and bulletin board systems. The Echo mail community has for some time been lacking a really good echo mail door. It is due to this lack that EchoDor was created. EchoDor may be used on several BBS systems. It is configurable to run under RBBS-PC Ver CPC 15.1 through 17.2, PCBOARD 14.1, and Quickbbs. The difference between these BBS systems is the way they handle passing information to a Door program. RBBS 15.1 puts the information in the first record of the message file. RBBS 16.1+ creates a small text file called DORINFOx.DEF. (the 'x' being the node number that called the door program). PCBOARD creates a random access file called PCBOARD.SYS. Quick BBS passes all the parameters on the command line that calls the door. The information that is passed includes the Users Name, the Communications Port, the baud rate, the graphics type selected, the time remaining, and the sysop name. This information is used by EchoDor to monitor the carrier of the appropriate port, and to control various other functions of EchoDor. If you don't have echo mail currently operating, you probably don't have a need for this program. If you are adding echo mail to your system, and haven't completed installing it yet, STOP. Go back to the echo mail programs, and get that working FIRST! You should set up echo mail to work in a set of subdirectories like FIDO, OPUS, and the rest of the net mail bulletin boards. If you are using RBBS, DO NOT USE RBBSMAIL! RBBSMAIL puts the echo mail messages in your RBBS conference files! EchoDor can't support this feature! If you are using PC Board or QuickBBS, the installation procedures are the same as for RBBS. Thus far PCBOARD does not support a net mail front end processor due to the fact that it does not allow parameters to be passed on the command line. To support echo mail using PCBOARD, BinkleyTerm has to be run in the "MAIL" mode as an event from PCBOARD each evening. Due to this, PCBOARD sysops cannot support Crash mail. Also, PCBOARD does not provide EchoDor will security levels; therefor, security level access control will not work. EchoDor provides a "default" security for all users of 50 when running with PCBOARD. Page 1 EchoDor Version 3.11 3/16/92 Installation If you already have net mail running, the installation will be very simple. If you don't run net mail, some explanation is in order. EchoDor uses FIDO type messages. IE: each message is a separate file (1.MSG, 2.MSG etc..). The messages in each area (Conference/Forum) are stored in their own Subdirectory. EG: C:\------ BBS | +--- MAIL ------- PRIVATE | +--- BAD_MSGS | +--- HUMOR | +--- RBBS-PC | +--- CHATTER | +--- POLITICS You need to get echo mail processor to move all your incoming messages to subdirectories like these. Examples of programs that do this are ConfMail, QM (or QMail), or TossScan. Set up this subdirectory structure BEFORE proceeding to the next section! You must also set up a fossil for EchoDor to use to communicate with the modem. A number of fossil programs are available including X00, BNU, or OPUS!COM. Get one of these if your not already using one and get it installed. Then: Create a directory to hold all the files in the EchoDor archive. Unpack the archive into the directory. Edit the file DoorDriv.Ctl to reflect the information about your system. Follow the comments contained in the file. Enter your first name as SYSOPFIRST name. Enter your last name as SYSOPLAST name. Enter your BBS name as BBSNAME name. Select your BBS type as BBSTYPE. If your BBS type is not listed, you may have to run EchoDor with some converter program. Place the drive and directory of your BBS into the line marked BBSPATH. This tells EchoDor where to get the door information file. Page 2 EchoDor Version 3.11 3/16/92 If you run a "locked baud", uncomment the line BAUD and set your baud rate. This will override the baud specified in the door drop file. We'll leave the rest of the entries as they are for now. See the following sections for a complete list of parameters and their uses. Edit the file "ECHODOR.CTL" to reflect information about the echos you intend to carry. Follow the comments in the file. Enter your own zone, net and node numbers. Enter your name as SYSOPNAME name. Enter your name as COMMENTNAME name. Edit the 2 tables, AREATABLE and AREADESC to your own echo mail areas. The comments in the file should explain how to do this. See also the section titled ECHODOR.CTL parameter file. Now run: EchoUtil /USERFILE EchoUtil will ask if you want Hot keys on as the default. Answer either Y or N. EchoUtil will create the user file. Run the CheckOut program. This program checks a lot of the entries and will help you resolve a number of problems. If Checkout generates too much output for your screen, you can redirect the output to your printer by using the command: Checkout > PRN Set up a door batch file to something like the following: rem rem switch to the EchoDor directory and start rem EchoDor rem CD \EchoDor rem rem now run EchoDor and pass it the node number rem in this example the node number is passed as rem the first parameter of the batch file. If you rem only run a single node, change the %1 to 1. rem rem | this is the parameter which is the port rem | number. All other information will come rem | from the bbs door file. rem v ECHODOR %1 rem CD \rbbs rbbs (SEE the Example Batch file called ECHODOR.BAT) Page 3 EchoDor Version 3.11 3/16/92 Note: make sure that your batch file copies dorinfo*.def to the EchoDor directory. This is a very important file. Test the door in local mode with "ECHODOR /L" to make sure it is working. Page 4 EchoDor Version 3.11 3/16/92 DoorDriv.Ctl parameter file The DoorDriv.Ctl file controls the door's interaction with the communication port and provides information about the BBS type that is calling the door. This file is required and must be in the default directory when the door program is started. The DoorDriv.Ctl example file contains a number of comments which should help you in editing this file. This chapter contains a list of all the parameters for DoorDriv.Ctl and their use. Multiple DoorDriv.Ctl files It is sometimes necessary to have multiple DoorDriv.Ctl file when running a multiple line system. One modem might be one speed or different monitors might be used on different nodes. Door Driver now supports multiple control files. The specific file selected depends on the "node" number specified when starting the door. Local operation always uses "node" zero (0). The name of the file comes from replacing the last character of the file name (before the period) with the node number. If that file dose not exist, Door Driver will then look for the base file (DoorDriv.Ctl). The different control files might be named: DoorDriv.Ctl < base file used as default > DoorDri0.Ctl < used for node 0 (local) > DoorDri1.Ctl < used for node 1 > DoorDri2.Ctl < used for node 2 > . . DoorDriX.Ctl < X = node number > Up to nine nodes plus local is supported. Remember that some doors change the name of the Door Driver control file. The naming would be altered to use the new base name. Page 5 EchoDor Version 3.11 3/16/92 Parameters BACKGROUND This parameter specifies the default background color used by the door program. See the list of available colors at the end of this section for the color numbers that can be used. Only the numbers 0-7 can be used here. The format of this command is: BACKGROUND n Where n is the color number desired as the default background color for the door. Note that some doors may not honor this parameter and use other colors. BAUD This parameter is used to set the baud rate of the door if you use a system that runs a locked baud. The format of this parameter is: BAUD xxxxx The following fixed BAUD rates are supported: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400 If this parameter is not used the baud rate used will be the baud in the door control file written by the BBS system. BBSNAME This parameter is the name of the BBS that you want to have displayed to the user when the door closes. This parameter is required. The format of this line should be: BBSNAME name of my board DO NOT put quotes around the name of your board or they'll show, just enter the name as you would type it. BBSPATH Most doors require you to copy your door information file (written by your BBS) into the directory where the door resides. By setting BBSPATH, you instruct this door to read the door information file from the specified drive and directory. This avoids you having to copy the file and reduces start up time. This parameter is optional. If it is not specified, the door will look for the door information file in the current directory. BBSTYPE Page 6 EchoDor Version 3.11 3/16/92 Most doors will only run with a specific type of BBS. This door will run with a number of different types of BBS systems. To tell the door the type of BBS you have you must set the BBS type. This is a required parameter. The format of this parameter is: BBSTYPE type The type should be replaced with one of the following: RBBS - for RBBS-PC 16.1+ (DORINFOx.DEF file) RA - for Remote Access (DORINFOx.DEF file) QUICK - for QuickBBS (DORINFO1.DEF file) PCB12 - for PC-Board 12. PCB14 - for PC-Board 14. WWIV - WWIV BBS (CHAIN.TXT file) PHOENIX - Phoenix BBS (INFO.BBS) WILDCAT - for WildCat! BBS (CALLINFO.BBS file) OPUS17x - for Opus 1.7x (LASTUS##.DAT file) GT - for GT PowerComm (GTUSER.BBS file) GENESIS - for Genesis Deluxe (CALLINFO.BBS file) WC3.0 - for WildCat! BBS (DOOR.SYS file) GAP - for GAP bbs (DOOR.SYS file) LINE-A - command line parameters (see below) LINE-B - command line parameters (see below) CHATSYSOPCOLOR This parameter specifies the color to use for the SYSOP when in chat mode. The format of the command is: CHATSYSOPCOLOR nn Where nn is the color number desired for the color to use for text typed by the SYSOP during chat mode. See the list of available colors at the end of this section. The default for this parameter is "yellow" (14). CHATUSERCOLOR This parameter specifies the color to use for the USER when in chat mode. The format of the command is: CHATUSERCOLOR nn Where nn is the color number desired for the color to use for the text typed by the USER during chat mode. See the list of available colors at the end of this section. The default for this parameter is "light blue" (9). COLOR1 Some BBS systems set the color indicator differently than the door expects. If your users do not get color when they should, try including this parameter in the DoorDriv.Ctl file. Page 7 EchoDor Version 3.11 3/16/92 COMPORT Some BBS systems do not write the communications port number to the door control file. One example of this is PC-Board version 12. If you run a BBS of this type, you must tell the door which communications port to use by using this parameter. The format of this parameter is: COMPORT x Where x is a 1, 2 .... maximum port. DIRECTVIDEO The door uses BIOS type writes to display information on the local screen. This mode is best for people that run DV. If you want faster screen writes, include the DIRECTVIDEO parameter and the system will use direct screen writes. FOREGROUND This parameter specifies the default foreground color used by the door program. See the list of available colors at the end of this section for the color numbers that can be used. The format of this command is: FOREGROUND nn Where nn is the color number desired as the default foreground color for the door. Note that some doors may not honor this parameter and use other colors. HILIGHTCOLOR This parameter specifies the color to be used for highlight. See the list of available colors at the end of this section for the color numbers that can be used. The format for this command is: HILIGHTCOLOR nn Where nn is the color number desired as the default foreground highlight color for the door. Note that some doors may override this parameter. IDLETIME nn This specified the maximum idle time in seconds between keystrokes. When 2/3rds of the idle time has passed, the program will issue a beep. When the total time lapses and no keystroke has been make, the door will exit. This may be disabled by setting IDLETIME 00. MAXTIME nn Page 8 EchoDor Version 3.11 3/16/92 This parameter is used to specify the maximum time the user is allowed in the door. Some BBS systems require this parameter because the time remaining is not passed. GT is an example of this. In boards where the maximum time is passed, if the user has more time available than the value specified here, the users time for the door will be reduced to the specified MAXTIME. Maximum time is specified in minutes. This may be disabled by setting MAXTIME 00. MINTIME nn This parameter allows you to set the minimum amount of time the user must have remaining to be able to use the door. If the total time remaining is less than the time specified, the user will be told that he doesn't have enough time and the door will exit. Minimum time is specified in minutes. This may be disabled by setting MINTIME 00. MONO This parameter if present will disable color on the local display. This is required if you run a monochrome monitor. NOTIME filename This parameter if present will allow you to tell the door to display a file when the user runs out of time. PROMPTCOLOR c1 c2 c3 This parameter defines the colors used for some requests made by the door. All three items are color numbers from the list below. The first color number (c1) is the foreground color of the input field. The second color number (c2) is the background color of the input field. The third color number (c3) is the foreground color number of the "Prompt Text". QUIET This parameter will prevent ^G (bell) characters from ringing the bell on the local system. Page 9 EchoDor Version 3.11 3/16/92 STATFORE This parameter is the foreground color of the status line. If the status line is off (see the STATUS parameter) this command has no effect. Refer to the list of colors at the end of this section for the color numbers that can be used. The format of this command is: STATFORE nn Where nn is the color number desired for the status line foreground color. STATBACK This parameter is the background color of the status line. If the status line is off (see the STATUS parameter) this command has no effect. Refer to the list of colors at the end of this section for the color numbers that can be used. The format of this command is: STATBACK nn Where nn is the color number desired for the status line background color. STATUS This parameter turns the status line on the local side on and off. I suggest you try it turned on. If the status line causes problems then turn it off. The format of the command is: STATUS ON or STATUS OFF Note: Some doors disable the status line when running in Local Mode. SWAPFILENAME If it is desirable to have the door swap itself out of memory when shelling to DOS, this parameter must be specified. If the parameter is not specified, the door will remain in memory when a "shell to dos" is requested. If the parameter is specified AND there is available EMS to use, the door will be swapped to EMS in place of disk. The format of this parameter is: SWAPFILENAME Where is a drive/path/name of the file to be used by the door when swapping itself out of memory. If the path is not specified, the default start up path for the door will be used. If the part of the contains a pound symbol (#), the pound symbol will be replaced by the node number of the Page 10 EchoDor Version 3.11 3/16/92 running door. DO NOT ALLOW two copies of the door to use the same swap file!! . SYSOPFIRST This is the first name of the SYSOP. This parameter is required and should be entered as: SYSOPFIRST Name SYSOPLAST This is the last name of the SYSOP. This parameter is required and should be entered as: SYSOPLAST Name Page 11 EchoDor Version 3.11 3/16/92 Color Table The follow colors may be used for both background colors and foreground colors: 0 - Black 1 - Blue 2 - Green 3 - Cyan 4 - Red 5 - Magenta 6 - Brown 7 - Light Gray The following colors may be used only for foreground colors: 8 - Dark Gray 9 - Light Blue 10 - Light Green 11 - Light Cyan 12 - Light Red 13 - Light Magenta 14 - Yellow 15 - White Page 12 EchoDor Version 3.11 3/16/92 Special instructions PC Board 14 When using this door with PC Board 14 systems, a default security level of 50 is assigned all users. PC Board 12 When using this door with PC Board 12 systems, a default security level of 50 is assigned to all users. PC Board 12 also requires that the COMPORT parameter be specified. Opus 1.7x When using the door with Opus 1.7x systems, the following security levels will be used: Twit 32 Disgrace 48 Limited 64 Normal 80 Worthy 96 Privel 112 Favored 128 Extra 144 Clerk 160 Asst-Sysop 176 Sysop 208 GT PowerComm If you use this Door with GT PowerComm, you must set the MAXTIME parameter. The GTUSER.BBS file does not contain the amount of time remaining for the door. Genesis Deluxe When using this Door with Genesis Deluxe, you must set the COMPORT parameter. LINE-A operation This option is provided to allow doors to be called without door information files. All needed parameters are passed on the command line. The order of the parameters is not important; however, if you wish to use multiple DoorDriv.Ctl files, you must specify a port number (without a leading slash or dash) as the first parameter on the command line. Every other parameter begins with either a slash (/) or a dash (-) followed immediately by a single letter parameter type. That type is then followed immediately by the parameter. There should be no spaces between the dash/slash and the parameter type and there Page 13 EchoDor Version 3.11 3/16/92 should be no spaces between the parameter type and the parameter. For example: -b2400 is valid, -b 2400 is not valid. The following parameters can be specified: -B baud rate. A baud rate of zero is assumed local. -P communication port number, COM1 is -P0. -T time remaining. This is specified in minutes. -N users name. If specifying a users first & last name, use an underscore as a separator. For example: -NFirst_Last -S numeric security level. For example: -S50 is security level 50. -M sets the maximum time allowed in door. If the time remaining is greater than the maximum time, the maximum time will be used. This is specified in minutes. -G Specifies graphics/ansi. If the -G is followed by 0, graphics will be disabled. If the -G is followed by a non zero value, graphics will be enabled. If you wish to use a "node number" this must be specified as the first parameter without a slash or dash. These parameters should not be used with the /S (sysop log on) or the /L (local log on) options. LINE-B operation This parameter is provided to allow doors to be called without door information files. All needed parameters are passed on the command line. Every parameter is order dependent. This style of operation does not allow user names and provides a default security level of 50. The following command line is used: door