Beijing Paradise BBS Backup

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

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

Wrap

Text File | 1993-09-15 | 36.2 KB | 931 lines

CallID v1.05 Copyright (C) 1993, Robert La Ferté LogiNord SoftWare FidoNet 1:167/235 ┌────────────────────────────────────────────────────────────────────────────┐ │ CallID v1.05 ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └────────────────────────────────────────────────────────────────────────────┘ What is CallID?.............................................. 2 Software requirements........................................ 2 Hardware requirements........................................ 2 Supported environments....................................... 3 Configuration................................................ 3 Keywords............................................. 4 AreaCode..................................... 4 Confirm...................................... 4 Hex.......................................... IDString..................................... 5 LogFile...................................... 6 MaxBack...................................... 6 Offset....................................... 6 OutOfBounds.................................. 6 Password..................................... 7 PassKey...................................... 7 Private...................................... 7 UserFile..................................... 8 WhereTo...................................... 8 Calling Syntax............................................... 9 -b................................................... 9 -c................................................... 9 -x................................................... 9 -?................................................... 9 Installation................................................. 10 Information on the User...................................... 11 Private numbers.............................................. 11 Out-Of-Area/Remote location.................................. 12 Valid numbers................................................ 12 Not found in database................................ 12 Found more than once................................. 12 Found and is unique.................................. 13 Rejection file............................................... 13 Files created on a previous run.............................. 13 Thanks....................................................... 14 Questions, suggestions, problems............................. 14 Registration................................................. 15 Disclaimer................................................... 16 ──────────────────────────────────────────────────────────────────────────────1 ┌─────────────────────────────────────────────────────────────────────────────┐ │ What is CallID? ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └─────────────────────────────────────────────────────────────────────────────┘ CallID is a utility that gives your system the intelligence to recognize who's online *before* the user even enters his name. It uses the phone company's caller identification information passed by SupraFAX and ZyXEL modems to your mailer to identify your users. This is the first release of LogiNord's CallID. I had to work with the software and hardware that was available *now*, so future versions of mailers and modems may require that I update CallID to reflect the changes. ┌─────────────────────────────────────────────────────────────────────────────┐ │ Software Requirements ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └─────────────────────────────────────────────────────────────────────────────┘ Several mailers can be used with CallID. I have tried BinkleyTerm, some have been able to make it work with Chris Irwin's D'Bridge, and the new version of FrontDoor (2.20) works too. ** BUT! ** Since CallID is very flexible in the way it works, it will probably work with any software that writes the required information to a text file. CallID works with most DOS-like operating systems, as long as it supports function calls that were added in MS-DOS 3.xx and later. In plain-jane DOS environments, this means you must run PC or MS-DOS 3.00 or higher. ┌─────────────────────────────────────────────────────────────────────────────┐ │ Hardware Requirements ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └─────────────────────────────────────────────────────────────────────────────┘ On the hardware side, many modem manufacturers state that their products are able to get hold of the Caller ID information the phone company sends (when you're a subscriber to such a service), but very few of them work in the real world. The only modems I've been able to get a sample of their output, are the SupraFAX and the ZyXEL models. CallID v1.05 was tested mostly with a ZyXEL U-1496, in real-time tests, and output of the SupraFAX modem was sent to me for offline work. Both formats are supported, if CallID doesn't work with your modem, please send me information on the make/model along with a sample logfile. It will be added to the list of supported models. ──────────────────────────────────────────────────────────────────────────────2 ┌─────────────────────────────────────────────────────────────────────────────┐ │ Supported Environments ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └─────────────────────────────────────────────────────────────────────────────┘ CallID was tested in plain-Jane MS-DOS 5.0, with QuarterDeck's QEMM 6.01, and under QuarterDeck's DESQview. All these combinations work, CallID accesses all files (except the ones it creates) in file-sharing mode, so it doesn't interfere with the rest of the system's work. ┌─────────────────────────────────────────────────────────────────────────────┐ │ Configuration ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └─────────────────────────────────────────────────────────────────────────────┘ Configuring CallID v1.05 is easy, you just have to edit the file called CALLID.CFG that came in this archive, and change its contents so it reflects your installation. Let's get through the configuration file's keywords and meanings. Keyword Signification ─────────────── ──────────────────────────────────────────────────── AreaCode Default area code for numbers without them. Confirm Character used to confirm the user's name for Maximus. Hex Phone number reported is in hexadecimal ASCII. IDString String that precedes the caller's phone number in the logfile. LogFile Complete path & name of BinkleyTerm's logfile. MaxBack Maximum numbers of line to read from the logfile's end. Offset Offset of phone number in hexadecimal ASCII string. OutOfBounds String replacing the phone number for a user who calls from an area that doesn't support Caller ID. PassKey User's way to disable password poking. Password Sysop's permission to poke the user's password too. Private String replacing the phone number for a user who blocked the Caller ID. UserFile Complete path to Maximus' USER.BBS file. WhereTo Where will CallID create its info files. That's it! ──────────────────────────────────────────────────────────────────────────────3 Now let's go through each keyword, and give its exact use and syntax: AreaCode: Some sysops use a formatting utility so all the phone numbers in USER.BBS look the same way, instead of having odd-looking numbers all over. Since CallID needs to scan the user database to find the current user's information, it also needs to compare phone numbers. Some numbers may not have the area code attached to them, so CallID needs a default area code to patch these numbers. Don't worry, CallID *never* writes to the user database, so this area code will never be written in a user's record. Example: AreaCode 514 Confirm: When you log on a Maximus system, and you enter your name, Maximus always asks for a confirmation of the name entered. Example: Please enter your first name: Robert last name: La Ferte Robert La Ferte [Y/n] ? See? The `Confirm' keyword defines the character that will be used to confirm to Maximus that the name that is poked by CallID is indeed the correct name. Now this character isn't tha same for every language, and that's why the `Confirm' keyword exists. In English, like in the example above, we'd use the letter `Y', for "Yes". In French, where the question would be: Robert La Ferte [O/n] ? we'd use the letter `O' (for "Oui"). Example: Confirm O Hex: Some Supra Corporation modems write the user's phone number in a strange form: an hexadecimal ASCII string, like this: # 15 Feb 23:06:29 BINK Mesg = 030739363831373039 The first two digits (03) in this case represent DDN information (Dialable Directory Number). The next two represent the number of digits in the variable length string, and the rest is the phone number. In this case, the number represented is 9681709 (my system's phone number). To make CallID compatible with these modems, you must use the `Hex' keyword and the `Offset' keyword in the configuration file. ──────────────────────────────────────────────────────────────────────────────4 The `Hex' keyword doesn't take any arguments, it simply indicates to CallID that the number will be in an hex ASCII form. The `Offset' keyword... is explained later in this file. IDString: The `IDString' keyword is used to define the *exact* string that is written in the mailer's logfile, preceding the current caller's number. In the case of BinkleyTerm/Dos used with a ZyXEL U-1496 modem, the line in the logfile is: # 08 Feb 01:17:33 BINK Caller Number: 9681709 This is a real line, taken from a real installation. In this case, the `IDString' would be: Caller Number: Of course, you could use BINK Caller Number: and CallID would find it, but if you use only Number: you may get CallID confused if it finds that particular string *before* the one you're searching for. In the sample configuration file you will find int the archive, that's the way CallID was configured to work with the installation described above. In a SupraFAX installation under OS/2, the same line would look like this: # 25 Jan 15:21:49 BINK Nmbr = 5149681709 So the IDString would be Nmbr = I chose to make CallID case-sensitive while it's searching for `IDString', `Private' and `OutOfBounds'. If you have some other utility that writes similar strings in the logfile, but in a different mix of upper and lower case, CallID will not get mixed up. In most cases, this is more preferable than the other way, since some strings may not be found, or may be found twice... Examples: IDString Caller Number: IDString Nmbr = ──────────────────────────────────────────────────────────────────────────────5 LogFile: CallID needs to read BinkleyTerm's logfile to find the phone number of the person online. Since that file probably has a different name on every installation, you must specify the complete path & name to that file, including drive specifier if needed. Example: LogFile C:\Bink\Binkley.Log MaxBack: CallID reads the BinkleyTerm logfile *backwards*, to find the Caller ID information supplied by the phone company. If your logfile is extensive, i.e. you have many utilities writing to it, you may need to change this parameter. This is the maximum number of lines CallID will read backwards to find the information. If it doesn't find the information in these [MaxBack] lines, it will simply act as if the user wasn't known. Example: MaxBack 10 Offset: The `Offset' keyword is only significant if you also use the `Hex' keyword. This is to support the hexadecimal-ASCII output of some SupraCorp modems. If you have this in your logfile: # 15 Feb 23:06:29 BINK Mesg = 030739363831373039 then you need the `Offset' keyword. :-) This is to tell CallID how many digits to trash before getting to the real phone number. In this case, it would be 4: # 15 Feb 23:06:29 BINK Mesg = 030739363831373039 ^^^^│ 1234└─ Start of real number CallID would then ignore the first 4 digits. If you don't need `Offset' but still need hexadecimal-ASCII compatibility, set `Offset' to zero (0). CallID will then simply trash.. 0 digits. *** Remember that hexadecimal values are represented by *pairs* of digits. `Offset' will probably always be an even value. OutOfBounds: Nope, no stroke penalty here.. :-) The `OutOfBounds' keyword, while it resumes very well my last golf round, defines for CallID the string that would replace the caller's number in the logfile when the user calls from an area that doesn't support the Caller ID function. I don't have an example for the SupraFAX, but for the ZyXEL modem, it looks like this: # 08 Feb 01:17:33 BINK Reason for no Caller Number: Out-Of-Area ──────────────────────────────────────────────────────────────────────────────6 As you see, the IDString is still there, so CallID will find it, but when it will scan for a phone number, it will find the string that is defined for `OutOfBounds', so CallID will know that the caller's number isn't available. Example: OutOfBounds Out-Of-Area Of course, if your modem reports something else, you enter it here, *exactly* as it appears in your system's logfile. Remember that CallID is case-sensitive during the search in the logfile. Password: I know, I got out of sync with the list above, but you'll soon understand why.. This keyword is used by CallID to determine if the sysop wants it to poke the current caller's password along with the user's name. In some installations, the sysop will not allow this, so the `Password' keyword must be set to "No". If the sysop wants CallID to poke the user's password along with his name, (s)he must set the `Password' keyword to "Yes". PassKey: The `PassKey' keyword is dependant of the `Password' keyword, and is used by the users of your BBS. In installations where the sysops allows password-poking, there may be some users who don't like that action, and they may want to protect themselves by entering their password manually. In such a case, you can define a character that can be used as a "key" to disable the password-poking feature. Any character valid for a password for Maximus can be used. Why is it dependant of the `Password' keyword? Because it can only be used when the sysop normally allows password-poking, since `PassKey' will *not* work the other way round; that is, allow a user's password to be poked anyway, even if the sysop set the `Password' keyword to "No". Passkey will only have an effect if Password is set to "Yes". Example: PassKey * In which case, all users using a password beginning by the character `*' will have to enter their password manually, while all the other users will have their password entered by CallID. Private: This keyword works in the same was as the `OutOfBounds' keyword, but for users who deliberately blocked the Caller ID function. In these cases, you may want to take a different action, you'll get an example in a later section of this file. The string defined by the `Private' keyword should be the same reported in your mailer's logfile when the user blocked his number, as allowed in certain phone company districts. ──────────────────────────────────────────────────────────────────────────────7 Example: Private Privacy Remember that CallID will find anything if you take great care of specifying the exact string your modem reports, case included. UserFile: To scan the USER.BBS file, CallID must be able to find it... Please specify the complete path, but path *only*. CallID knows that the file is called USER.BBS in Maximus installations. Example: UserFile C:\Maximus\ You can omit the terminating backslash, CallID will work with or without it... WhereTo: CallID will create a number of files for Maximus to use. Each file has it's own utility and signification, they'll be given later in this file. If you run a multi-line system, you *must* specify a different path for every node, thus use a separate configuration file for every node. This allows for greater flexibility. Example: WhereTo C:\Bink\CallID\ You can omit the terminating backslash, CallID will work with or without it... IMPORTANT! CallID needs all of this information, and will tell you if one or more parameter is missing. It will identify the missing part, to simplify your configuration work... ──────────────────────────────────────────────────────────────────────────────8 ┌─────────────────────────────────────────────────────────────────────────────┐ │ Calling Syntax ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └─────────────────────────────────────────────────────────────────────────────┘ CallID's syntax is simple, yet flexible: CallID.Exe -cCfgFile.Ext [-x] [-b] CallID.Exe -? -c<Config file name> Is used to get the configuration filename, which should be written next to '-c', wuthout any spaces between, like this: -cCallID.Cfg If you don't specify a configuration file on the command-line, CallID *will not work*, and you'll get the help screen, as if you used the -? switch. -x CallID writes lots of information on screen while it works. If you want to get rid of most of this information, use this switch. It also speeds up the execution of CallID a little. -b By default, CallID uses direct video writes. If you run under DESQview, or a similar environment, you may want CallID to use BIOS calls instead. This switch changes CallID's behavior in this manner. -? Get Help on CallID's configuration and syntax. ──────────────────────────────────────────────────────────────────────────────9 ┌─────────────────────────────────────────────────────────────────────────────┐ │ Installation ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └─────────────────────────────────────────────────────────────────────────────┘ Installation of CallID is straightforward, and shouldn't cause any problems in most installations. CallID works by using an combination of an environment variable and a batch file. The only modification you'll have to make to your installation is: 1. Adding two lines to your batch file calling Maximus. 2. Modifying the line calling Maximus. To your batch file, you insert these two lines *just before Maximus gets called*: d:\path\CallID -cd:\path\Callid.Cfg d:\path\CallID!.Bat The first line executes CallID-the program, and the second one calls CallID-the batch file. To ensure proper operation, you should specify complete pathnames to every call. In the example above, replace "d:\path\" by the drives and paths required by your own installation. Don't look in the CallID distribution archive for the CallID!.BAT file, it doesn't exist. This file will be created by CallID.Exe during its execution, and it will contain only one line: SET CALLID=<user information if available> You should reserve enough space in the environment to allow CallID to create another variable. (If you require more information on how to allocate environment memory, please refer to your MS-DOS manuals.) When the batch file CALLID!.BAT executes, it will place information in your computer's environment, and it's *this* information that will allow Maximus to know who's there before the user identifies (her)himself. If password-poking is allowed, you may find in the batch file, the following string: SET CALLID=Robert;La;Ferte;Y;Password In which case, the batch file will create the environment variable `CALLID', and this variable will have "Robert;La;Ferte;Y;Password" as a value. If password-poking is disables, you'd only find: SET CALLID=Robert;La;Ferte ─────────────────────────────────────────────────────────────────────────────10 After the batch file creates that environment variable, your original batch file calls Maximus. You must add this to your Maximus command-line, just after the name of the Maximus executable: -j%CALLLID% This tells Maximus to take the user name in an environment variable called "CALLID", and to use that information to login the user. *** And what if the number is blocked, is out-of-area, or if the caller isn't a registered user? Simple. The environment variable will be emptied by CallID (it will not exist anymore) and Maximus will simply ignore the "-j" parameter on its command-line. The user will then be able to login manually, as if CallID never existed. But on the next call, CallID will be able to identify that user, since his phone number will then be known. ┌─────────────────────────────────────────────────────────────────────────────┐ │ Information of the User ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └─────────────────────────────────────────────────────────────────────────────┘ CallID will get in BinkleyTerm's logfile, the information given by the phone company on the current user. There are three possibilities for that information: ■ The current user's number is private, or has been blocked by the user. ■ The current user is calling from a location which doesn't support Caller ID information, or is calling from outside your area. ■ The current user's number is available. For each of these cases, CallID will behave differently: Private Number, of number was blocked: ────────────────────────────────────── The current user has a confidential number, and information will not be given by the phone company, *or* this user chose to block the Caller ID function. CallID will then create a file called "PRIVATE.DAT", to indicate that this user's number is unavailable. The "CALLID" environment variable will be destroyed. By creating a MECCA file, you could take a different action for these users. In one beta installation, the sysop chose to drop carrier on these users, telling them that he didn't like user who hid themselves by blocking the number. He then invited them to call back with the Caller ID function unaltered. Of course, you could decide to do something else, you're the boss! :-) ─────────────────────────────────────────────────────────────────────────────11 Remote location, or from out-of-area: ───────────────────────────────────── Caller is from an unsupported area. CallID is then unable to get ths information for this user. It will create the "NOPHONE.DAT" file, and exit. The "CALLID" environment variable will be destroyed. CallID finds a valid number: ──────────────────────────── This is the most complex part of CallID's behavior. Not *that* complex, but it's here that the fun begins! When CallID finds a valid number, it will search through the user databse to find a match for that number. Again, there are three possibilities: ■ Number isn't found in the user database. ■ Number is found more than once. (more than 1 user uses it) ■ Number is found, and is unique. For each of these cases, CallID will behave differently: Number wasn't found: ──────────────────── This may be a new user, or a regular user calling from an unknown location. CallID will then create a file called "NUMBER.DAT", that will contain the found phone number, then exit. The "CALLID" environment variable will be destroyed. Number found more than once: ──────────────────────────── Two - or more - users registered with the same number, *or* a regular user is calling from another regular user's place. Since it is impossible at that time to identify the user positively, CallID will take the "best" action possible: it will *not* poke any password, but it will offer the first name that matched. As an example, if you have "Don Juan" and "Don Camillo" at the same number, and that CallID finds "Don Camillo" first, it will offer that name to Maximus. When Maximus will load, it will ask the user for a confirmation of the name, like this: Don Camillo [Y/n] ? If it's Don Juan calling, he will simply reply "N", and then enter his own name. ─────────────────────────────────────────────────────────────────────────────12 The phone number found will still be written to the "NUMBER.DAT" file, so you can display it within a MECCA file, and a file called "DOUBLE.DAT" will be created so you can take appropriate action. You could use that file to display a specific string from a MECCA file... Number is unique: ───────────────── Ahh.. there we are! The user online is already registered, and is the only one using this phone number. CallID will write his number in the "NUMBER.DAT" file, and then his name in the "USERNAME.DAT" file The environment variable "CALLID" will then contain the user's name, and if password-poking is allowed and the user didn't disable it by using the `PassKey' character as first character of his password, his password will be there too. ┌─────────────────────────────────────────────────────────────────────────────┐ │ Rejection file ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └─────────────────────────────────────────────────────────────────────────────┘ CallID v1.05 has a new feature: it can use a rejection file containing phone numbers of people you do not want to give access to your system. If CallID finds a valid phone number in your logfile, it will try to open a file called "CALLID.PHN", which is the list of rejects. If the file exists *in the same directory CallID was called from*, CallID will use it. If it doesn't exist, CallID will continue execution without complaining since this is an optional feature. The format of this file is important, and you should take the time to look at the sample file provided with the distribution archive. CallID is actually restricted to North-American phone numbers, and the rejection file uses that format. You can use a semi-colon in the first column to add comments to the reject file. Of course, the less lines it contains, the faster CallID will process it. If CallID finds the number in the reject file, it will create a file called REJECT.DAT on disk, in the directory specified in your configuration for the other .DAT files. In your very first MECCA file (usually Logo.Mec), test for the existence of that file. If it exists, your next step would be the [hangup] token... This feature doesn't exist in the current version of Maximus (v2.01wb). That's why CallID supports it right now. Thanks to Mark R. Williamson of Digital Dreams BBS (1:379/606) for the suggestion - you have it as described Mark! :-) ┌─────────────────────────────────────────────────────────────────────────────┐ │ Files created on previous runs ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └─────────────────────────────────────────────────────────────────────────────┘ All the files that CallID created on a previous run are destroyed during the current run. This is done to ensure that no false information is transmitted, and so that CallID will stay safe to use. ─────────────────────────────────────────────────────────────────────────────13 ┌─────────────────────────────────────────────────────────────────────────────┐ │ Thanks: ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └─────────────────────────────────────────────────────────────────────────────┘ To Jean Paul Dumas (1:167/217), who got me into this in the first place, who wrote the original MECCA files, and for whom CallID was written at the beginning. To France Chapdelaine (1:167/235), who wanted to play Nibbles on the machine used to write CallID, and who had to stay alone in front of the TV waiting for me to get my hands off the keyboard. Thanks honey... :-) To Mark R. Williamson (1:379/606), who reported a strange critter (squashed), and who asked for the reject file feature. It was a good idea, and he deserves the credit for it. ┌─────────────────────────────────────────────────────────────────────────────┐ │ Questions, suggestions, problems... ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └─────────────────────────────────────────────────────────────────────────────┘ If you have questions on, or ideas for, CallID, please get in touch with me, either by netmail: Robert La Ferte LogiNord BBS 1:167/235@fidonet.org or by using "Postes Canada": LogiNord SoftWare c/o: Robert La Ferte 1175 Dompierre Mascouche, Quebec Canada J7L 2T6 When reporting problems (aarghh!), please send along: ■ Your configuration file for CallID. ■ A sample of your logfile. ■ A description of your installation. ■ A description of the problem, with mucho details! ■ The phone number of your system, and/or netmail address. ─────────────────────────────────────────────────────────────────────────────14 ┌─────────────────────────────────────────────────────────────────────────────┐ │ Registering CallID ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └─────────────────────────────────────────────────────────────────────────────┘ CallID is not free. You must register before the expiration of the 30-day evaluation period. I feel that 30 days is lots of time to evaluate a piece of software that will be used every single time a user logs on your system. CallID also represents many hours of work, used between phone calls to remote sites to get information, to test preliminary versions, to debugging, to refining CallID's behavior. Since this is written for Maximus, I can't ask for much, so CallID's registration cost is 10$, US funds. Please *do net* send cash by mail, since it *may* get lost. Checks are better, and Money Orders are *the best* thing. You can get the mailing address in the "Questions, Suggestions, ... " section above. CallID *is not crippled* in any way, all functions *do* work. In the unregistered version, my logo appears at the end of the run, in both normal and -x modes. Registering will get rid of that display, and since that display lengthens the execution time, the registered version of CallID runs a little faster... :-) Registration will get you a thank-you note, and a keyfile. This keyfile must be located in the same directory as the CallID executable so CallID can find it. The keyfile will be valid for all future versions of CallID. Supporting shareware is the ONLY way to keep it alive. I register, do you? ─────────────────────────────────────────────────────────────────────────── ─────────────────────────────────────────────────────────────────────────────15 ┌─────────────────────────────────────────────────────────────────────────────┐ │ Disclaimer ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └─────────────────────────────────────────────────────────────────────────────┘ This software and accompanying materials are distributed "as is" without warranty, express, implied or statutory, including but not limited to any implied warranties of merchantability and fitness for a particular purpose. In no event shall the author or anyone involved with the creation and pro duction of this product be liable for any direct, indirect, incidental, or consequential damages resulting from the use of this program. Your use of this program constitutes your agreement to this disclaimer and your release of the author from any form of liability or litigation. All trademarks mentioned in this document are the property of their respective owners. Thanks.. Robert La Ferte ─────────────────────────────────────────────────────────────────────────────16