Üßß ßßÛ Û Û Üßß ÛßÜ Û Û Version 1.2 Ûß Üß ßÜß ßÜ Ûßß ßÜß ßß ßßß ß ßß ß ß Table of Contents ----------------- Description ........................................... 1-1 Installing ............................................ 2-1 Configuring ................................... 2-2 Single-line ................................... 2-3 Multi-line .................................... 2-4 Command-line Options .................................. 3-1 -nodirect ..................................... 3-2 -verbose ...................................... 3-3 -node n ....................................... 3-4 -setup ........................................ 3-5 -maint ........................................ 3-6 -makelist ..................................... 3-7 -rem First Last ............................... 3-8 Miscellaneous ......................................... 4-1 remove.txt .................................... 4-2 Purchasing ............................................ 5-1 1-1 Description If you run an EzyCom v1.20 BBS and are frustrated by user just simply dropping carrier to log off then this program is for you. EzySpy is a shareware program that will count how many times a user has dropped carrier and sends a warning message to that user after a certain number of carrier drops, and optionally lowers their security level if they continue dropping carrier. Other features include multi-node support and the ability to generate ANSI and ASCII lists. 2-1 Installing Steps: 1. Place EzySpy in a directory. 2. Run ezyspy.exe -setup and configure to your liking. 3. Edit the main BBS batch file and add ezyspy.exe anywhere after EzyCom exits. See section on 'Command-Line Options' for a list of switches. 4. Add 'ezyspy.exe -maint' to your maintenance. 2-2 Configuring Make sure the EZY environment variable is set. When you first run ezyspy.exe you will be presented with the setup screen. Configuring is quite self-explanatory, so you should only refer to this section if you are having trouble. Be sure to enter the FULL PATH AND FILENAME for any items requiring a filename (ie. c:\ezy\ezyutil.exe). Drops-1 - This is how many carrier drops it takes to get a warning message. EzySpy will send the message specified by 'Msg-1 text' when a user reaches this number. The valid range is from 2 to 20. Msg area - is the message area used to send all messages. The valid range is 1 to 208. Msg from - is the name that is placed in the 'From' field of all messages. Make sure that it's properly capitalized. Msg-1 subj - is what is place in the 'subject' field of the warning message. Msg-1 text - is the full path and filename of a text file containing the warning message. Drops-2 - is the number of additional carrier drops before EzySpy drops the user's security level. This is how many carrier drops, after the warning message is sent, before the users security level is dropped and the message specified in 'Msg-2 text' is sent. The valid range is from 2 to 20, or 0 to disable this feature. Lwr level - is the security level to lower users to. The valid range is from 0 (lock out) to 32767. Ezyspy will not change the user's security if it is lower than this number. Msg-2 subj - is what is placed in the 'Subject' field of the message which is sent when EzySpy lowers the user's security. Msg-2 text - is the full path and filename of a text file containing the message to be sent when EzySpy lowers the user's security. Mutli-line - is a Yes or No to whether or not your system has more than one phone line. If this is set to Yes then EzySpy will NOT lower the user's security because the userbase may be locked by another node. However, it is also possible for the userbase to be locked on a single-line BBS aswell. If this is the case nothing bad will happen, only that the user's security won't be lowered. To take care of this, simply run EzySpy with the -maint switch described in section 3-1 'Command Line Options'. Log path - is the full path and filename of EzyCom's log. Ubase path - is the full path and filename of EzyCom's userbase (users.bbs). Ezyutil path - is the full path and filename of EzyCom's utility 'ezyutil.exe'. Record path - is the file used by EzySpy to keep track of carrier droppers. 2-3 Single-line Add ezyspy.exe to your main BBS batch file anywhere after a user logs off. Include the full path aswell (ie. c:\ezyspy\ezyspy.exe). If you have any programs that add to EzyCom's log file or alter 'today.bbs' (unlikely), make sure that EzySpy is executed before such programs. To specify a node, use -node #. To have lists generated whenever there's a change add -makelist. Example: c:\ezyspy\ezyspy.exe -node 2 -makelist It would be a good idea to add the command 'ezyspy.exe -maint' to your daily maintenance. 2-4 Multi-line Similar to single-line installation, except repeat the process for each node using the proper node number. Also, you MUST add 'ezyspy -maint' to your daily maintenance. 3-1 Command-line Options This section describes the switches or arguments you can place after the actual command to change some of the actions that are taken during the execution of the program. You can also get quick descriptions by entering ezyspy -h on the command line. 3-2 -nodirect Disables direct screen writes and forces BIOS screen writes. This option should only be used if your PC doesn't support direct screen writes or if EzySpy doesn't display properly. 3-3 -verbose Makes EzySpy spit out more information on what it's doing. Use this if you get an error to see what the problem is. 3-4 -node n Where n is the node number. By appending this switch you are telling EzySpy to check if the last caller on this node has dropped carrier. When this is left out, then it is assumed to be node 1. 3-5 -setup Launches the EzySpy configuration editor. 3-6 -maint Use this to perform maintenance during which the following is done: 1. Send warning messages to users who should have got them, but for some reason didn't. 2. Drop security levels of users who should have had them dropped, but didn't (most likely due to the userbase being locked at the time). 3. Clear EzySpy records of the names specified in remove.txt (see the section on 'Miscellaneous'). NOTE: If a user requires #1 AND #2 of the above, only #1 (send warning) is done. #2 (drop access) is done either the next time -maint is executed or if the user drops carrier again. This is so the user doesn't get the warning and access dropped all at once. 3-7 -makelist (registered version only) Output one ASCII and one ANSI (ezyspy.asc and ezyspy.ans), in EzySpy's directory. These files are lists of all carrier droppers and the number of carrier drops by them. Use these at your discretion. A good idea might be to have a menu item like 'View Carrier Drop List' and simply display the file. NOTE: The lists are generated only when EzySpy detects a carrier drop. If you add the -maint switch, the list are made right after maintenance is complete (ie. ezyspy -makelist -maint). 3-8 -rem first last Deletes (removes) the ezyspy record of the user specified by 'First Last', the first and last names of the user to be removed. Proper capitalization is not required. Example: ezyspy -rem john doe Another way of removing names from the list is by creating a file called remove.txt described in the next section. 4-1 Miscellaneous 4-2 remove.txt If you create a text file in EzySpy's directory called 'remove.txt', then EzySpy will search through it and clear records matching the names found in it. Just place one name (proper capitalization is not needed) per line and the next time maintenance is executed these records will be cleared. If the name is not removed from EzySpy's record, make sure there are no leading or trailing spaces in the name. 5-1 Purchasing If you find EzySpy useful and would like the registration password to enable the -makelist feature then please send $4 CDN or $3 US to: Peret Roca 360 E.36th Avenue, 420 Vancouver, BC Canada V5W 4B9 (Make cheque or money order payable to Peret Roca.) I will give you the password and instructions on how to use it. There are several ways I can contact you: 1. Internet - Mention your e-mail address. 2. Fidonet - Mention the node address (zone:net/node.point) and your name. 3. Mail - Enclose a self-addressed stamped envelope with payment. Please send questions, suggestions, comments, bug reports, etc. to: rocap@unix.dsoe.com