Beijing Paradise BBS Backup

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

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / RADCD104.ZIP / RADCD.DOC < prev next >

Wrap

Text File | 1995-10-07 | 47.2 KB | 1,070 lines

** RemoteAccess Dropped Carrier Detector ** ** Version 1.04 ** Master Code Compatible (c)Copyright 1994,95 Rand Nowell - RaLin Enterprises Coding and Documentation by: Rand Nowell < This is "Cowboy Software" ! > - PROGRAM DOCUMENTATION - ┌────────────┐ ┌────────────┐ │ ≡≡≡≡≡ °°°° │ --->--->--->ACK!!! │ ≡≡≡≡≡ °°°° │ └────────────┘ └────────────┘ - Contents - Legal Stuff.............................1 Copyright - Distribution - Disclaimer Important Notice........................2 What's it do?...........................2 Start-Up Commands.......................3 Multi-Language Support..................5 Required Files for RADCD................5 Multi-Node Systems......................6 Configuration...........................6 Double Checking Drops...................7 Door Hangup Configuration..............10 User Name Validation...................11 Double Checking Drops..................11 Users Dropping more than once..........12 Scanning User Drops....................12 The View Command.......................13 The Sysops Report......................13 Ansi/Ascii Display Files...............14 The Message File.......................14 Message Macros.........................14 Testing RADCD..........................15 Registration...........................15 We Listen!!............................15 Credits................................16 Author Contact.........................16 Where to get RADCD.....................17 RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 1 ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ COPYRIGHT ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ RADCD, the program documentation, and any support type files, are the Copyrighted (C)1994-1995 work of Rand Nowell dba Ralin Enterprises. All rights are reserved. Copying, duplicating, selling or otherwise distributing this product except as noted in the Distribution Policy below is a violation of Federal Copyright Law. Any copyright infringment proceedings will be handled under the courts and laws of California, USA. All Software produced by the author will be referred to and released under the collective name of " Cowboy Software " . This is a registered name. It's not currently used as the business name, that remains as RaLin Software, but instead refers to any software produced by the author and distributed by his company RaLin Enterprises. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ DISTRIBUTION ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ 1. Feel free to distribute the Shareware version of this program as often as you like to any interested parties. Distribution to Electronic Bulletin Boards is encouraged. 2. Please do not distribute this program without all the original related files such as documentation, readme files, registration forms etc. 3. Please distribute ONLY the original authenticated ZIP format file. 4. Please obtain our written permission before including the program with any "bundled" software packages. 5. Please do not accept payment for the program; a copying fee of $5.00 per diskette may be charged by a non-profit user-group. 6. Please do not alter the program or documentation in any way. 7. Individuals, groups, vendors or other software distribution companies which market diskettes containing shareware or test-drive evaluation programs, for profit, must obtain written permission from RaLin Enterprises prior to distribution. This will insure that you have the most current copy. DISTRIBUTION of the REGISTERED version of this program is in violation of the license agreement and copyright law. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ *** DISCLAIMER *** ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ This program is supplied "as is" without warranty of any kind. The entire risk of using, and results from the use of, is assumed by you the user. You assume all costs of repair, servicing and corrections stemming from the use of this program. Rand Nowell and/or RaLin Enterprises, or any other associated RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 2 company of the program author will not be held liable for any damages from the use of this program. No warranties are expressed or implied. ******************************************************************** To the original licensee of the REGISTERED version of the program, RaLin Enterprises DOES warrant that the program disk(s) on which the program is recorded, be free from defects in material and workmanship under normal use and service for a period of (90) ninety days from date of delivery as evidenced by your receipt. Our entire liability and your exclusive remedy shall be replacement of the defective disk not meeting the standards of this limited warranty. And in no case shall exceed the cost of reimbursement of monies paid for program registration. The Author is not obligated to produce further versions of this program. The Author also reserves the right to convert any SHAREWARE program, to that of COMMERCIAL status without prior notice. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ IMPORTANT NOTICE! ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ All features available in previous versions of RADCD, are still freely available in this Shareware copy, along with the new multi-language support. However, the abilitiy to modify a users security level for exceeding a specified number of drops, is a registered feature, and requires that you purchase a Registration Code to unlock this features There are numerous changes in this release, new keywords, keywords changed, new suppport files, startup commands etc. Please be sure to at least view the CHANGES file and the SAMPLE.CFG ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ What's It Do? ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ RADCD will read your defined RA.LOG, and scan for the line that RA writes when the caller drops carrier (HANGUP). If this line is found, RADCD will post a message to the user, a message you design, about the nasty habit of dropping carrier. When a dropped carrier is detected, RADCD writes pertinent info to a log file, RADCD.LOG, in the same directory as RADCD.EXE, or a directory+filename you define in RADCD.CFG Some DOOR's allow hangup from within, this will cause RA to report Carrier lost.... RADCD allows you to configure up to 10 strings that your Door(s) write to the log, if they do, and will ignore the dropped carrier if one is found, in the last RA session entries. Instructions for configuring doors that do NOT write to the RA log are included. More is explained later. RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 3 The log file is read "backwards", so even if it is HUGE, the minimum number of lines is read, stopping at the the first line entered for the callers session. Goes very quick! The location of the RA logfile is obtained from CONFIG.RA, as are any other file locations that the program needs, other than those configured by you, the Sysop. RADCD would normally be called from the "After BBS" section of your batch file. The message is posted in the message area you specify in the config file. Both JAM and HUDSON bases are supported. The program also obtains the user name, the log entry date, and the time of the Lost Carrier entry, from the RA.LOG The User Name is displayed on the screen at run time, the time and date, along with the name are used when posting a message to the user. These, along with other strings may be included in the message you create by way of "Macro Characters", more on that later.... RADCD also maintains a user file, tracking the number of times a user drops carrier. If you so wish, you may have RADCD modify the security level of any user dropping carrier more than a number you define. When the users security level is modified, a message is posted to the user, and also a short notification to you, the Sysop, about the modification. The messages written may be edited by the sysop, and support the message macros as does the Drop Detect User Message. This Security Modification function is only available when running in Registered Mode. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Start Up Commands ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ The program requires 250k memory available to properly run. Direct screen writes are used, thus older CGA monitors may have a problem with screen displays. RADCD accepts several start up switches. Switches must be preceded by either the minus(-) or slash(/) character, and must be separated by at least one space. ?,/?,-h Will display a help screen menu. -P Will invoke a 10 second pause at programs end, allowing you to read the screen display. ANY key press during the pause, will clear the pause and terminate the program. -S Will over-ride config command to create/update display screens. ie: No updating of screens at runtime is done. RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 4 -Z Will handle erasing the RADCD.DAT file, in RADCD's directory. The command RADCD /Z should be a part of your nightly maintainence. -N Will generate fresh and empty screen files. Good for perhaps weekly maintainence. Or, if this is your first time, to create screens for RA to find, even without drops, so there are no screen not found errors. THIS COMMAND WILL OVER-RIDE THE "DOSCREEN" KEYWORD SETTING IN CONFIG IF IT IS COMMENTED OUT If no screen name was defined, it will post an error message and exit. -C Specifies an ALTERNATE configuration file to be used. This MUST be the FIRST command option to work correctly... Immediatly following the /C or -C switch, should be the full PATH+FILENAME of the alternate file. IF you do NOT give the full path to the alternate file, it will NOT work! You been advised.... Example: -cD:\TEMP\OTHERDC.CFG You might wish to setup another configuration file that specifies a different Message FIle to send to the user, under certian circumstances. Then to send that OTHER message, you simply specify the alternate config file on the command line. -SCAN {+} Normally would be run in a midnight maintainence event, this will scan the RADCD.USR file, checking the total drops for each user in the file. If one any are found that have exceeded your Maximum Drop count, RADCD will a) Generate a Security Modification message to the user b) Modify the users security level c) Write a short notification message to you SCAN should be the only command given, as no others will be run after it. -PURGE {+} Used to keep the size of the user file (RADCD.USR) down. After a time, there may be callers listed in the file, who either do not call your system anymore, or do not drop carrier anymore. If their drop count is zero, they can be removed from the file with this command. This command will also remove any user records marked as DELETED. (See VIEW below) -VIEW (Portions Registered Only) Displays the users in RADCD.USR along with the count of dropped carriers detected to date. Allows you to mark a record as DELETED, which can be removed with the PURGE command. See The VIEW Command below. RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 5 ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Multi-Language Support ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ As of Version 1.04, support is added for multiple language use for messages written to the user. RemoteAccess places a number in each users record for the language they have chosen to use, or a ZERO if none has been chosen. The number used corresponds to the position of the language in the list you see when in RACONFIG. What RADCD does, is when it needs to post a message to the user, either notifying them of a dropped carrier detection, or when modifying their security, is check what language number is in the users record, ie: 0,1,2,3,4 and so on. It then looks for a message file with that extension, for the dopped carrier notification it will look for a file names DCDMSG.0, DCDMSG.1, DCDMSG.3 and so forth. For a Security Modification message, it looks for files named like SECDOWN.0, SECDOWN.1, SECDOWN.2 etc. The purpose of this is so the user can receive a message in their native language, ie: GERMAN, DUTCH, ENGLISH, SPANISH etc. or, if you are using language files like COWPOKE, ABUSIVE, STARTREK, the message can be written in that vernacular. If no message file with an extension matching the language number in the users record is found, RADCD will use the message file with the extension .0 - This is the default, and this means you MUST have at the minimum, one DCDMSG.0 and one SECDOWN.0 - or RADCD will not run. See next section for required and or created files used by RADCD. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Required Files for RADCD ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ Some files will be created by RADCD, others must be created by you. Sysop created files should have a sample included in the archive. REQUIRED FILES: RADCD.CFG Program configuration file (TEXT) DCDMSG.0 Default Carrier Drop Notification message SECDOWN.0 Default Security Modification message DROP.RPT Message to Sysop when modifying user security. CREATED BY RADCD: RADCD.USR User file, created & maintained by RADCD See "Scanning Users" later for more. RADCD.DAT Tracks user drops for the current day See "Users Dropping more than once" later for more. ALL SUPPORT AND MESSAGE FILES FOR RADCD "MUST" BE KEPT IN THE SAME DIRECTORY AS RADCD.EXE. A RADCD directory is reccomended. RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 6 ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Multi-Node Systems ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ RADCD supports RA running in a multi-node setup, pertaining to the LOG file it scans, and also for the RADCD.LOG. RADCD will read the CONFIG.RA file to get the log name. It first searches the current directory for CONFIG.RA, if not found it looks in the directory specified with the RA environment variable. So lets say you run a 3 line system, and for each load up of RA you set the NODE environment variable, we'll use set NODE=2 for our example. When you have the TASK variable set, you can use RA's "node" macro (*N) in the log name, ie: F:\RA\NODE*N\RA*N.LOG RADCD will scan the log name, and insert the current task number into the log name. Given our example NODE=2, the above would parse out to: F:\RA\NODE2\RA2.LOG - make sense?? This also applies to the RADCD logfile, in the config, you can insert the *N aywhere in the logfile name/location, and RADCD will substitute the current NODE number. Example: LogFile=F:\RA\LOGS\RADCD*N.LOG - becomes F:\RA\LOGS\RADCD2.LOG RADCD first checks for a %TASK% environment variable, if found this is used for all occurances of *N used anywhere. If the %TASK% is not found, it checks for %NODE% being set, and if so, used that one. If neither is found, RADCD figures you're running single line, and if the *N macros exists in any filename, it will NOT work correctly. ************************************************************************* Remember, RADCD looks for a CONFIG.RA in the current directory FIRST, then looks at the environment specified directory. So if you use multiple CONFIG.RA files for different nodes, make sure you are in the proper NODE directory before RADCD is called! ************************************************************************** ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Configuration ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ The configuration file is a simple text file named RADCD.CFG. It MUST reside in the same directory as RADCD.EXE. A sample file has been included, you can edit it to reflect your system and preferred message base info etc., and use it. Comment lines may be included, by having the FIRST character, in column ONE be a semi-colon (;). These lines are ignored by RADCD. Currently, there are some twenty or more items to/can be configured for RADCD. The configuration is done with "keywords", and the format is RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 7 KEYWORD=VALUE if a variable or name is needed, or KEYWORD alone, if it turns On/Off an option. The equals sign (=) is the separator, and is used by RADCD to determine just where the VALUE starts, the VALUE being what you want used as the configuration item. There may be spaces between the KEYWORD, EQUALS, and VALUE if you need them for readability, myself, I always keep them together. Keywords may be in any or mixed case. Values, for the most part can be any case, but SysopName and System will be displayed AS THEY ARE LISTED. The "VALUES" for each "NoDrop" keyword, MUST be in the same case they will be found in the log, for them to work. KEYWORDS: - UserMsgBase - Users notification message If you want the message posted to the HUDSON message base, then this would be the full path to the Hudson Message Base, ie F:\RA\MSGBASE If you want it posted to a JAM message file, this should be the full path to the JAM message file: ie F:\JAM\GENERAL NO extension to the JAM filename, it is automatically handled. This document will not go into details about the JAM messaging system. - UserBaseType- Type of message base If the message is going to the HUDSON base, this should be "H", without the quotes. If going to JAM, it should be "J", again, no quotes. - UserBoard- User message board number (HUD) Only required if posting to the HUDSON base, this should be the NUMBER of the message area, and it MUST be ZERO padded to 3 digits. Ex: Message Area #4 would be 004 MsgFile- IS NO LONGER SUPPORTED - SysopName- This is your Sysop Name. It does NOT need to match RA's, it is only used in conjunction with the message macros, so it can be anything you wish. - System- The name of your BBS. Again, it need not match that in CONFIG.RA. - UsePrgName- After several requests, and seeing the problem myself, I did what should have been done from the get-go. The message RADCD sends to a user is now written as From: the defined sysop name. But if you DO want it to be from the Program, activating this keyword will send the message "From" RADCD. RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 8 - UseHandle- Tells RADCD to substitute the users HANDLE in the Sysop's Report, and the generated display screens. If not used, the users real name will be written. - BadNameMask- RADCD is pre-defined to see if characters common to a bad connection, or faulty IEMSI connect, are in the user name, thus causing it to NOT send a message to this non-existant user. With this keyword you can ADD to that list, fine tuning the bad connect checking. Pre-defined characters are: {}[]._ You can add up to 249 more. - DCDLogFile- You may specify, with this keyword, where RADCD will write the logged information. If not defined, the log will be written/maintained in the same directory as RADCD.EXE. The RA variable *N may be used anywhere in the log path\name, it will be substituted with the current NODE value. - RALogFile- If you want to process a SPECIFIC RA.LOG, regardless of what the current TASK or NODE is set to, and you ise the *N macro in the RA.LOG name, then define this keyword. RaLogFile=C:\TMP\RATST.LOG will have RADCD process THIS log file, Allways! - DoScreen- Tells RADCD to create/update the defined Ansi/Ascii screens with callers who have dropped carrier. (see section on screens later) - ScreenFile- Allows you to specify the directory, and root name of the display files. Do NOT supply an extension, RADCD will do this at runtime. (see section on screens later) You can supply two screen names, just add a pipe symbol to the end of the ScreenFile= line, immediatly followed by the second screens path and name. See the sample config file. - CopyCol- RADCD is hard-coded to start scanning for the user name in column #13 of the logfile. This is correct for the COMPACT log format specified in RACONFIG. If you use a different format, you should load a copy of the log into a Text Editor, and count over, from column one, to the FIRST character of the user name. This column number is what you will specify as the CopyCol value. - ExpandedLog- If you are using the EXPANDED log format, you should include the line: ExpandedLog This will tell RADCD to scan for the Date and Time of a Drop differently than for the default Compact log style. It also determines how RADCD knows it has read all the current session information, as the line containing the dashes is not written to an expanded format log. RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 9 You do NOT need any config keyword for Compact format, as it is the default, if ExpandedLog is NOT used. - NoDrop- Specifies a string (case sensitive) that RADCD should watch for, to reverse the Carrier lost action, if the carrier was correctly dropped from within a Door Program. You may configure up to 10 strings, each one preceded by the keyword NoDrop. Each Keyword/Value on its own line. The string may be up to 25 characters in length. Any more will not be stored. The 25 character length allows you to configure sec levels to ignore Dropped Carrier for, ie: NoDrop=Security level 50 will not post messages to callers with Sec of 50, even if they drop carrier. You can also give User Names here. The string must match what RA writes to the log NOTE: The check of NoDrops is done in the order they are listed in the config file. - ClipLogo {+} When running in Registered Mode, and this keyword is defined, RADCD will not include the Created By box in messages/reports. - MaxDrops {+} With this keyword, you define the maximum number of times a user can drop carrier before they are subjected to RADCD's security modification. - DropSec {+} This is the security level that will be applied to the users account by RADCD when they have reached or passed your MaxDrops count. ──────────────────────────────────────────────────────────────────────── The following group of keywords apply to the sysop messages posted to you. Messagebase type, location etc. ──────────────────────────────────────────────────────────────────────── - ZapMsg- Yes, do report If this keyword is not activated, then all the following are ignored. This one tells RADCD that you DO want a report created when you /Zap the data file. - Net- Create a netmail message rather than normal message If defined, RADCD will use the netmail configuration for the report, else it uses the message base items. YOU SHOULD SETUP BOTH, EVEN IF YOU WANT A NETMAIL REPORT (and have a mailer) THAT WAY ITS SIMPLY A MATTER OF COMMENTING OUT THE NET KEYWORD TO SWITCH TO MESSAGE BASE REPORTS. - Node- Fidonet Node Address This is your Fido (or other) mail address that should be used to RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 10 address the report. The SysopName used above will also be part of the message addresing. You could also use this to have RADCD generate the report to another address, say your system at home/office. - MailPath- Your Mail Directory The directory where the *.MSG should be written to, ie: where your mailer will look for new messages. ─────────────────────────────────────────────────────────────────── ** these below are for report to the message base ** ─────────────────────────────────────────────────────────────────── - SysopMsgBase- Full path to your HUDSON message base, =OR= Path and root filename of the JAM base. (just like the UserMsgBase) - SysopMsgBoard- Zero pad to three digits The number of the message board, if its Hudson. It is ignored if the SysopBaseType is J for JAM. - SysopBaseType- H=Hudson J=JAM You must specify the type of message base being used. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Door Hangup Configuration ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ NOTE on NoDrop. (READ THIS.....) Some doors that allow Hanging up, or Quitting the BBS, do NOT write to the RA.LOG, in fact probably most, do not. You can still work with these, all you need to do, is in the batch file that runs the door, after the command to run the door, insert a line that will ECHO a line of text to the RA.LOG Example: Suppose you run a door called FileVu. In your batch file, you might have, FILEVU C:\RA\DORINFO1.DEF as the command to run the program. All you need to do is insert a line such as: echo User ran FileVu >> C:\RA\RA.LOG right after the program call, when the program exits, it returns to the batch file, and this line is processed. Then in RADCD.CFG, include a line that looks like: NoDrop=FileVu Now, when RADCD sees the Carrier lost line in RA.LOG, it sets the Dropped Carrier flag, but as soon as it finds your created value, "FileVu" it turns OFF the flag. Another use for the NoDrop, is if you want callers with a certian security level to not receive messages for dropping carrier..... RA writes a line "Security level #####," to the log file, where ##### can be any defined sec level up to the maximum allowed. So if you want to allow callers with sec level 50 to drop carrier, simply add a line such as NoDrop=Security level 50 to the RADCD.CFG RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 11 Two important things to remember, the search for a value is done case SENSITIVE, it MUST match exactly what is written to the log, and listed in the config file. The other is, when you create your own, as in our example, you use the DOUBLE > character ">>" after the string to Echo. This is the command to DOS, to APPEND the line to the log file. If you forget, you will OVER-WRITE your RA.LOG Also, some doors do not allow a caller to hangup, but DO allow the Sysop to hangup on the user. These should also be configured, if you think you may hangup on the user in the door. Another note, when RADCD detects dropped carrier, it writes to the screen, ! User dropped carrier If it finds an "Authorized Door hangup string" it will then display ■ Authorized Door Hangup : "value", where value is the NoDrop string you supplied, and RADCD found. Comments may be inserted in the config file, any line with a semi-colon (;) in column ONE, of the line is ignored. You can use the ; to comment out a keyword also. Why you would, I don't know. If it all sounds confusing, that's because it can be so!! <smile> Some experimentation on your part will get you up and running smoothly in no time. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ User Name Validation ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ As of version 1.02, any user name found in the RA log, is validated against the user index file. This makes for a FAST check, and eliminates messages being posted to callers who have not completly finished the logon process. RADCD will post the invalid name to the RADCD.DAT file, so that it is displayed to you in the Sysop Report, but no user message will be generated. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Double Checking Drops ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ RADCD insures that the User Name in the logfile is not garbage, as can happen with bad IEMSI calls or a user sending escape sequences trying to crash the system. If carrier is lost, but the user name does not contain an Alpha character staring the name, its considered an incomplete call, and no message is posted. When you run a frontend mailer, the connection can sometimes be broken during the time the mailer is loading RA. In this case there is no name for RADCD to check, usually there will only be two lines in the log, the first line RA writes, and the second, Lost carrier. RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 12 So RADCD counts the important lines read from the log, and if this count is NOT greater than 3, then RADCD displays the message: "BLAM!! Never even got started..." and also logs an appropriate line to its log file. This is considered a connection that never got established. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Users Dropping more than once ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ Because a user "may" call and drop carrier more than once in a days time, repeated messages could be generated, cluttering up your message base. RADCD maintains and reads a small data file in the EXE directory, called RADCD.DAT. This file is checked if carrier drop is detected, if a message has already been sent to the user, RADCD will NOT send another one. But it WILL log the fact that the user dropped carrier again, also giving you the total times they did so. The file tracks the number of times they have dropped, and this value is updated each time they do. IMPORTANT! This data file becomes worthless if left as is for multiple days, if a caller drops carrier today, and then again tomorrow, if the data file exists, with their name in it, they will not get a message. YOU SHOULD DELETE RADCD.DAT IN YOUR NIGHLY MAINTAINENCE!! See Sysop's Report next section. During the log scan, if drop is detected, the data file is checked, if the user has been sent a message, you are advised of this and no message is sent, but, again, the drop is logged, along with the total times the user has dropped. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Scanning Users ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ {+} Once or twice a day, or in your midnight event, you will want to have RADCD scan the user file for excessive drops. Simply run RADCD -scan This will scan the RADCD.USR file, if any user in the file has dropped more than the maximum allowed number, RADCD will: 1. Generate a message to the user, advising them about security change. 2. Change the users security to what you have defined in RADCD.CFG 3. Generate a short report to the Sysop about the modification. 4. Reset the Total Drops in the user file back to 0, for this user. After a Security Modification or two, most users will STOP dropping carrier on you. Or perhaps they just call no more. RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 13 So you may end up with a few users in the RADCD.USR file that are not needed anymore. To pare down the user file, run RADCD -purge What this will do is remove any user that has ZERO (0) drops recorded. This will also remove user records you have marked as DELETED during a VIEW Session. See The VIEW Command below. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ The VIEW Command ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ Just a short course on using the VIEW command. This will display the records in RADCD.USR, listing the callers name, and total drops to date. The normal Up/Dn arrow key movements, as well as PgUp/PgDn, Home and End will move the selector bar. You can also do a search for a username, by pressing a LETTER key. The search only works on the FIRST letter of the users name. To mark a record as DELETED, to be removed during PURGE, simply press the SpaceBar when a users name is highlighted. To UN-Delete a record, press SpaceBar again. You must be running in REGISTERED mode to mark a record as deleted. If you are not registered, then RADCD will simply beep at you when you hit the spacebar. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Sysop's Report ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ When you delete the RADCD.DAT file, in your nightly maintainence, with the /Z switch, RADCD can create a report for you. This report lists the names of callers who have dropped since the file was created, along with the number of drops. This report will also list those names that RADCD determined were invalid, ie: garbage characters, or a user name that did not get stored in USERS.BBS.... just to let you see what has come through. Only validated names get sent a message, so you need not go hunting for messages addressed to &*&^$*& <smile> The report can be sent to you as a regular message, in a Hudson or JAM message base, or, if you run a mailer, as a netmail message to you. Whether the report is generated, and what message format to use, is determined in the configuration file. Refer back to configuration for the specific keywords. This report is hard coded, there is no message template for you to edit. RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 14 ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Ansi/Ascii Display Files ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ RADCD will create/maintain an Ansi and Ascii screen file listing callers who dropped carrier. The file may be displayed to callers, or just viewed by the Sysop. These files need to be displayed with Menu Type 45, as it does not pause on its own, or add a Press Enter prompt. See Configuration, above for settings. As mentioned earlier, you can create TWO files, with the same config line. Refer back to "Configuration" This is handy if you have a Bulletin Door, that requires names to be in a specific name format, like Bob DaCastellos LWBULL, as well as creating a typical file for RA display. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ The Message Files ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ Using your favorite Ascii Text Editor, you can create the messages that will be sent to the user who has dropped carrier. They must be named DCDMSG.# for the Carrier Drop notification and SECDOWN.# for the Security Modification message. The # would reflect the language choices available for your system. Refer back to Multi-Language Support earlier. You can make use of several macros to insert text into the message when it is posted. A sample RADCD.MSG has been provided. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Message Macros ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ The most important thing to remember about using the macros, is that each one MUST be preceded by the at character (@). If you wish to use a literal @ in the message text, you must precede it with another @. So the line "Call me @ 223-4455" must be written as "Call me @@ 223-4455" If you use an incorrect macro, or use the @ alone, the "macro" will be replaced with "<MACRO ERROR @??????>" where ???? is replaced with the problem character(s). If you use our RASIS program, then you should be familiar with how the message macros work, they are done in the exact same manner. There are currently seven (11) macros available for you to use: @F - Users first name only @L - Users last name only @N - Users full name @D - Date of Drop @T - Time of Drop @M - Maximum Drops Allowed RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 15 @! - Security to be set for excessive drops @C - Total number of drops for user This one only true value in SECDOWN messages @U - User Name - Only Valid in DROP.RPT @B - The BBS name @S - The Sysop name ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Testing RADCD ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ If you wish to test RADCD locally, you can either call from another system, and drop carrier..... have a friend call and drop carrier, or, edit the RA.LOG that will be used, and insert "Lost carrier" after one of the time strings, it should be placed right above the line that says "User off-line" Make sure you do NOT include the quotes, and that there is a carriage return at the end of the line. Also, it is IMPORTANT that you use the exact same case as shown above. RADCD does NOT scan on a case-converted line, but scans for EXACT text. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Registration ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ All functions available in previous versions of RADCD, are still freely available, as is the Multi-Language support. The security modification and messages are only available when running in registered mode. See RADCD.REG for info on obtaining your Registration Code. This version of RADCD is compatible with Cowboy Software's MASTER registration code. (See included ORDER.FRM) ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ We Listen to You! ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ List of requested features from Sysops Name Implemented Feature in Version ----------------------------------------------------------- ------------- Rick Hinbaugh Have /Z(AP) list days drops to sysop in message. 1.02 Lots of Sysops Have user message sent from Sysop rather than Program. 1.03 Several other minor enhancements requested. RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 16 Many.... Option to Modify Security 1.04 Paul Voogd Suggested Multi-Language support 1.04 ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Credits ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ RemoteAccess - Andrew Milner, Wantree Development. (The BEST!) JAM(mbp) - Copyright 1993 Joaquim Homrighausen, Andrew Milner, Mats Birch, Mats Wallin. ALL RIGHTS RESERVED. LWBULL - Bob DaCastello, LlanoWare RADCD uses modified message base code from Mark May, Mythical Kingdom. RADCD is programmed under BP 7.0, Borland International Any other products mentioned are Copyrighted by their respective authors. I would like to thank the following for their continued support in testing and bashing RADCD. Well, the list has grown.... rather than listing the names, I will say: "Your contined help, bug reports, comments and suggestions have been very helpful, and greatly appreciated!!" and I would also add... "You know who you are, and you can pat yourself on the back, for a job well done!" ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ BETA Versions Available ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ Rather than always making a Open BETA version available, as in previous releases, due to the addition of Registered Only options, Beta versions will only be available to the beta members. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Author Contact ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ I hope you find RADCD useful, and would appreciate hearing from you if you do. I can be reached at the following: Netmail - 1:215/710 BBS - 1-510-226-7731 Voice - 1-510-651-6177 Internet - ralin@msn.com (subject to change) Mail - Rand Nowell RADCD 1.04 RemoteAccess Dropped Carrier Detector Page 17 RaLin Enterprises 4641 Wheeler Dr. Fremont, Ca. 94538-1937 ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Where To Get RADCD ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ The latest version of RADCD should always be available from the following: Also at most any RADIST site. ** USA ** RaLin 1-510-226-7731 1:215/710 (Author) USA RA-USA 1-803-279-5006 1:360/1 USA Abuser BBS 1-305-581-7549 1:369/139 (CBSW Dist) USA -------------------------------------------------------------------------------- ** SWEDEN ** FrontLine BBS +46-8-7391510 2:201/437 (CBSW Dist) SWEDEN -------------------------------------------------------------------------------- ** HOLLAND ** A new site is in the setup stages - --------------------------------------------------------------------------------- ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ eof RADCD.DOC ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘