synchro.net

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

/ synchro.net / synchro.net.tar / synchro.net / modem.madness / SMMTRBBS / DSDROP30.ZIP / DSDROP.DOC < prev next >

Wrap

Text File | 1993-10-04 | 17.2 KB | 386 lines

═╦══╗ ╝ ╔══╗ ╔═══ ╔═══ ╦══╗ ╦══╗ ║ ║ ╠══╣ ║ ╔╗ ║ ╔╗ ╠═ ╠═╦╝ ═╩══╝ ╩ ╩ ╚══╝ ╚══╝ ╩══╝ ╩ ╩═ ╔══╗ ╦ ╦ ╔══╗ ╔══╗ ╦ ╔═ ╚══╗ ╠══╣ ║ ║ ║ ╠═╩╗ ╚══╝ ╩ ╩ ╚══╝ ╚══╝ ╩ ╩ It's not Shareware. It's SHOCKWARE! DSDrop Version 3.0 D'Agger Shock Drop Carrier Notifier Copyright 1993 by D'Agger Shock, All Rights Reserved September 24, 1993 ============================================================================== SHOCKWARE ~~~~~~~~~ This program is distributed on the Shockware basis. It is NOT crippled in any way. If you like it, and you use it, I ask that you please register. REGISTER.TXT is included with this archive. By registering, you will keep updates and other quality software coming! WARRANTY ~~~~~~~~ This program is distributed without warranty. D'Agger Shock will not be liable in any way for any damages caused from the use of this program. There is no guarantee that this program will work on your system. A friend of mine put it best when he said: "Hey, it works on my system!" TriBBS ~~~~~~ This program is desiged for use with the TriBBS Bulletin Board System only! TriBBS is a registered trademark of Mark D. Goodwin. ============================================================================== WHAT THIS PROGRAM IS SUPPOSED TO DO ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DSDrop checks if the last caller dropped carrier or not. If carrier loss occurred, DSDrop will send a logon notice to the caller, and if so desired a notification screen to the sysop, and a log file. The notification screen and log file contain all of the callers information. ============================================================================== MULTI-NODE SETUP ~~~~~~~~~~~~~~~~ Throughout this document there are examples for multi-node systems. If you are running a multi-node system, please take the time to follow the examples. If you are running only a single node setup, just use the node 1 examples. SHARE.EXE must be loaded for multi-node systems!!! To do this, put the following line in you Config.Sys: INSTALL=C:\DOS\SHARE.EXE ============================================================================== The next thing you have to do, is make a configuration file. A sample configuration file is included in this archive. This file can be any name. When you run DSDrop, run the name of the configuration file as DSDrop's first parameter. Example: DSDROP DSDROP1.CFG <- For node 1. DSDROP DSDROP2.CFG <- For node 2. Sample configuration file for Node 1: C:\TRIBBS <- Path to node 1's directory. C:\TRIBBS <- Path to THIS node's directory. C:\TRIBBS\TRITOOLS\DSDROP.ANS <- Path and name of color ANSI screen. C:\TRIBBS\TRITOOLS\DSDROP.BBS <- Path and name of Mono screen. C:\TRIBBS\TRITOOLS\DSDROP.RIP <- Path and name of RIP screen. BRIGHT GREEN <- Heading Color BRIGHT WHITE <- Text Color. SYSOP=1 <- Sysop's user number. SYSOPSCREEN=YES <- Send notification screen to Sysop? RIP=YES <- Using RIP? DAT=YES <- Use a data file? LOG=YES <- Log all carrier losses? C:\TRIBBS\DSDROP.DAT <- Path and name of data file. C:\TRIBBS\DSDROP.LOG <- Path and name of log file. Sample configuration file for Node 2: C:\TRIBBS <- Path to node 1's directory. C:\TRIBBS2 <- Path to THIS node's directory. C:\TRIBBS\TRITOOLS\DSDROP.ANS <- Path and name of color ANSI screen. C:\TRIBBS\TRITOOLS\DSDROP.BBS <- Path and name of Mono screen. C:\TRIBBS\TRITOOLS\DSDROP.RIP <- Path and name of RIP screen. BRIGHT GREEN <- Heading Color BRIGHT WHITE <- Text Color. SYSOP=1 <- Sysop's user number. SYSOPSCREEN=YES <- Send notification screen to Sysop? RIP=YES <- Using RIP? DAT=YES <- Use a data file? LOG=YES <- Log all carrier losses? C:\TRIBBS\DSDROP.DAT <- Path and name of data file. C:\TRIBBS\DSDROP.LOG <- Path and name of log file. LOCKOUT=100 <- Lock user out at ## of carrier drops. NOTE: All lines in the configuration file MUST be present wether you are using a feature or not! MAIN PATH: This is the path to the main TriBBS directory. THIS PATH: This is the path to the node that DSDrop is running in. ANSI SCREEN: This is the name of the Color ANSI that will be sent to the caller. If it's in the same directory, just the name is needed. Otherwise the full path must be specified. A samples has been included. MONO SCREEN: This is the name of the Non-color screen that will be sent to the caller. If it's in the same directory, just the name is needed. Otherwise, the full path must be specified. A sample has been included. RIP SCREEN: This is the name of the RIPScrip screen that will be sent to the caller only if the RIP= line is set to YES. If it's in the same directory, just the name is needed. Otherwise, the full path must be specified. A sample has been included. HEADING COLOR: This is the color for the Headings that DSDrop will send to the Sysop Notification Screen. TEXT COLOR: This is the color of the Callers information that is sent to the Sysop Notification Screen. SYSOP= LINE: This is the Sysop's user number. A user number is a number that TriBBS gives each caller. You can check to see what your user number is from the "Edit Users" option from TriBBS's Waiting for Caller screen. (Normally, this number is 1, because the Sysop is usually the first person to logon.) SYSOPSCREEN= LINE: Do you want a notification screen sent to the Sysop? There are two options. SYSOPSCREEN=YES which will send a notification screen, and SYSOPSCREEN=NO which will not. There must be no space to the left or to the right of the equal sign. RIP= LINE: Does you BBS support RIP graphics? There are two options. RIP=YES which will look for the screen specified in line 5, and send it to the caller, and RIP=NO which will not look for the screen or send it to the caller. If you are using TriBBS 4.x set this to NO. DAT= LINE: Do you want to use the Data file features? The data file contains important information about each caller that drops carrier. The features include a drop carrier counter, lockout flag, call waiting flag. There are two options. DAT=YES which will enable the above features for use with DropEdit and send the data to the file specified in line 13, and DAT=NO which disables both the above features and DropEdit. LOG= LINE: Do you want a log of all carrier drops? There are two options. LOG=YES which will log all carrier drop to the file specified in line 14, and LOG=NO which will disable the log. NOTE: You may want to set this to C:\TRIBBS\MWORK\CALLERS.LOG for ease of use. DATA PATH: This is the path and name to the dat file. If line 11 is set to DAT=NO, then this line will have no effect, but it MUST be present! LOG FILE PATH: This is the path and name to the log file. IF line 12 is set to LOG=NO, then this line will have no effect, but it MUST be present! LOCKOUT= LINE: This is the number of times a person can drop carrier before they become locked out. All lock outs are handled by DropEdit. If you do not want the lock out feature then you do not have to use it, but this line MUST be present! Example Sysop Notification Screen: Heading LIne Sysop's Name | __|__________ | { } This is a note from DSDrop to Dean D'Agostino. The following user has dropped carrier. __ __ H | User Name.......: Dean D'Agostino | E | User Alias......: Speedtorch | A | User Number.....: 1 | T D | User Password...: Register | E I | Security Level..: 100 | X N | City, State.....: Valrico, Fl | T G | Phone Number....: 813-555-5555 | | Date Dropped....: 10-04-1993 | L L | Time Dropped....: 12:50:08 pm | I I | Node Dropped....: 1 | N N | Carriers Dropped: 3 | E E | Call Waiting....: Yes | |__Locked Out......: No __| COLORS ~~~~~~ NOTE: The following colors are for the color ANSI screens ONLY! All colors can be used for the heading lines OR the text lines. Bright Colors Dark Colors ~~~~~~~~~~~~~ ~~~~~~~~~~~ BRIGHT RED RED BRIGHT GREEN GREEN YELLOW BROWN BRIGHT BLUE BLUE MAGENTA PURPLE BRIGHT CYAN CYAN BRIGHT WHITE BRIGHT GREY BRIGHT GREY GREY ============================================================================== In order for DSDrop to get the all of the information, you will need a LOGON.BAT. If you already have one, good. If not, here is an example of what yours can look like: Example LOGON.BAT for node 1: @ECHO OFF BOARD Example LOGON.BAT for node 2: @ECHO OFF NODE2 TriBBS will create ALL door data files needed before it leaves memory. Then, "BOARD" will go right back into TriBBS, leaving the door data files. The next thing to do to get DSDrop up and running is put it in your BETWEEN.BAT. This example assumes that you have used a separate directory for DSDROP. Example BETWEEN.BAT for node 1: @ECHO OFF CD\TRIBBS\TRITOOLS DSDROP DSDROP1.CFG CD\TRIBBS IF EXIST C:\TRIBBS\TRIBBS.SYS DEL C:\TRIBBS\TRIBBS.SYS Example BETWEEN.BAT for node 2: @ECHO OFF CD\TRIBBS\TRITOOLS DSDROP DSDROP2.CFG CD\TRIBBS2 IF EXIST C:\TRIBBS2\TRIBBS.SYS DEL C:\TRIBBS2\TRIBBS.SYS IMPORTANT: Notice the "If Exist" statement in the above lines. This MUST be the VERY LAST line of your Between.Bat! NOTE: DSDROP.EXE and the configuration file MUST be in the same directory, or you will have to specify the full path name! DOES YOUR MODEM DETECT CARRIER LOSS CORRECTLY? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In order for DSDrop to work, your modem must correctly detect carrier loss. Here is an excerpt from the "Freejack's Tips" section of the Tampa Bay TriBBS Newsletter explaining what to do. "If you have experienced problems where a caller has logged off and your BBS sometimes does not recycle, or a caller drops carrier and the BBS just sits there, most likely this is the problem of your settings in your NRAM of your modem.... TriBBS monitors the DCD (Data Carrier Detect signal) of the users modem. The problem lies in most factory settings on modems where they are set up for basically calling out, and not for receiving. Therefore, the modem is set with the &C or &C0, which forces the DCD signal active (ON) continuously. This factory setting gives TriBBS problems, because it forces TriBBS to monitor the DCD at the high setting and may fool it into thinking someone is still on line, where in fact they may have dropped or lost carrier... To check to see if this setting is in your active NRAM profile of your modem, type this command in your favorite communication program that you use to normally call out. AT&V <--This command allows you to view your NRAM settings. If you see the command (&C or &C0) in one of the lines in the active profile of your NRAM settings, then you will need to change this...the following is how you would do this: ATZ (Enter Return) <--This is to get your modems attention. OK <--Don't type this, this is what your modem should return. AT&C1 (Enter Return) <--This will place the new command in your NRAM. OK <--Don't type this, this is what your modem should return. AT&W (Enter Return) <--This will write the new setting to the NRAM. These commands should work for most modems on the market today. These are standard commands used by most of the modem manufactures. However, if you do have a problem, feel free to drop me a message on my BBS and I will be happy to help you out..." HOW TO RESET DSDROP ~~~~~~~~~~~~~~~~~~~ If there comes a time that you want or need to reset DSDrop's drop carrier counter, all you have to do is del the .DAT file. To reset just one caller, use DropEdit. SPEEDING UP DSDROP ~~~~~~~~~~~~~~~~~~ The longer your CALLERS.LOG file is, the longer it will take DSDrop to detect if the last caller dropped carrier or not. To speed things up a little, you can use a program that trims the CALLERS.LOG down to size. Perhaps one of the best is DSChop. It lets you choose your file size by the number of callers OR by the number of lines in CALLERS.LOG. HISTORY ~~~~~~~ 3.0 ~~~ DSDrop 3.0 was TOTALLY rewritten! It is now much faster than 2.1. The Drop Carrier counter is back and this time, it works! Now supports a RIP screen! Added a switch to the notification screen and the log feature as a request by the Sysop of The Dogger, Billybob Jenkins. 2.1 ~~~ Got rid of the Drop Carrier Counter. Was having too many damn problems with it. Everything else is still the same. The Drop Carrier Counter MAY be back in future versions. I don't know yet. 2.0 ~~~ Added multi-node support! The Sysop Notification Screen now tells which node the caller dropped carrier on. 1.0 ~~~ Wanted a better drop carrier detector that would not only send the caller a logon note, but also the Sysop. I didn't like having to check the CALLERS.LOG everyday to see if anybody dropped carrier. VIRUS INFORMATION ~~~~~~~~~~~~~~~~~ No program or virus checker is perfect so D'Agger Shock is now using McAffee Associates' VALIDATE.COM to check the executable files for your protection against viruses. The validation data for DSDROP.EXE, Version 3.0 is: File Name: DSDROP.EXE Size: 54,882 Date: 10-4-1993 File Authentication: Check Method 1: 339D Check Method 2: 1DD6 THANKS ~~~~~~ Thanks go out to these TriBBS Sysops of Tampa Bay Dennis Clevenger <- The beta tester An adult's Paradise! -> The EROGENOUS Zone from Hell! Files, Games, Messages. (xxx) xxx-xxxx Gary Price <- "Freejack's Tips" Games, Files, and -> Freejack's Place Messages. Adult Access. (205) 739-7121 Mike Lott <- Editor of the Games, Files, and -> Night City South Tampa Bay TriBBS Messages. Adult Access. (813) 949-5751 Newsletter WHERE I CAN BE REACHED ~~~~~~~~~~~~~~~~~~~~~~ WHERE TO REGISTER ~~~~~~~~~~~~~~~~~ To get in touch with me, I can be reached at one of the following places. My name is Dean D'Agostino. Just leave me a message. I can now be reached on WME in BBS Utilities and TriBBS Support. Just in case you lost REGISTER.TXT, the registration fee for DSDrop is $5.00. Please make Check or Money Order out to Dean D'Agostino, and mail to D'Agger Shock. Priadore The Blazing Phoenix BBS D'Agger Shock (813) 854-4961 (813) xxx-xxxx P.O. Box 1368 24 Hrs. Coming Soon Valrico, Fl 33549