EVDoor HISTORY file prior to v3.0 release... Alot of this information is obsolete and is only provided for information purposes only. EVDoor v2.4b -*- 12 May 1991 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For clarity and promotional considerations, our name has changed when referring to the Door, we have chosen EVDoor vice Eagle Verify Door. We will still call it Eagle Verify Door, but have shorten the name somewhat for visual purposes. However, all executable filenames have remained the same. Added another [Y/N] switch to disconnect ALL callers/user who elect to abort the verification/callback. You set this switch using EVCONFIG.EXE to modify your .DAT file. It is the last selection within the EVCONFIG display screen. If you have an existing .DAT file, this field will be BLANK, and will not show in reverse video until you have added a 'Y' or an 'N'! Be sure to RUN the new EVCONFIG.EXE upon your existing .DAT files and press F10 to save your .DAT file(s)!! Setting this switch to Y will "disconnect" ALL callers/users, even those with a security level of 110 or greater! With this in mind, I have added another option on the main menu for the SysOp to (E)xit the door without getting disconnected. The (M)aintenance & (E)xit options on the main menu will only be displayed to those with a security level of 110 or greater. Only the (E)xit option is available on UNREGISTERED copies of the Door. The (M)aintenance option is ONLY available to REGISTERED owners of the Door. Eagle Verify Door v2.4a -*- 29 April 1991 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Corrected a BUG in the "adjust user expiration" function. Added another option to the SysOp/Maintenance Menu to allow you to exit from the door within the Maintenance Menu area, rather than having to return back to the Main Menu to exit. Changed/Added to the Search function in the SysOp/Maintenance Menu. When doing a search, if any matches are found, you are prompted as to whether or not you wish to view the matches found, the default used to be NO, has been changed to YES, also once you have been displayed all of the matches, you are now asked as to whether or not you wish to delete one of the matches found. As a result of a request of a user, I have added another display file (ABORT.VD/VDG). This is used to display a message to the user should they elect to abort/quit the callback/verification process. If the user selects [Q] from the Verify Door Main Menu, this file will be displayed. Edit it as necessary. Also added another option to the SysOp/Maintenance Door Menu. [E] will allow you to exit from the verify door and Maintenance Menu without having to go back to the main menu, thus avoiding the ABORT message logged to the callers log and the displaying of the new ABORT.VD/VDG display file. Eagle Verify Door v2.4 -*- 24 April 1991 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Multi-Node/Network support has been added to this release! Those users upgrading need only to copy the following files into the verify door's home directory: EVERIFY1.EXE EVERIFY2.EXE EVERIFY.NET <- IMPORTANT - whether you have multi-node/network operations or not, you MUST have this file in the home directory of the verify door beginning with v2.4! Multi-Node information: (REGISTERED VERSIONS ONLY) If you are running any multi-tasking software, have a network, or PCBoard v14.5+ /E3 or above and you want to use the door on more than one node, you must of course have SHARE.EXE installed! Failure to do so WILL LOCK the door up with a "SHARE VIOLATION"! See the files within the EVD-NET.ZIP for example usage of the door under multi-node operations. If you try to run the door on more than ONE NODE without having the registered users KEY file, it will not work! This is called inventive to register the door to access the multi-node capabilities of the door. Eagle Verify Door v2.3c -*- 15 April 1991 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Added ERROR logging! If an error occurs, it will be written to a file in the same directory as the .EXE files (EVERIFY1/EVERIFY2) and given the filename of ERROR.LOG. Version 2.3b was never released! Without a "true" networking environment to test the door within, I can not fully implement file locking on the necessary files. So until I can purchase my network the changes listed below (v2.3b) are for future releases. With the exception of the file sharing capabilities I tried to put in v2.3b, everything stated below still holds true, with the exception of running the door under more than ONE NODE!. DO NOT TRY this as you will get a SHARE VIOLATION and we all know what that does!? Once I have my network up and running I will add multi-node and file locking capabilities to the door. Eagle Verify Door v2.3b -*- 14 April 1991 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ We have added "limited" networking/multi-node/multi-tasking support within the door. Since I do not presently have a network to fully test the door the added functions are limited. I have tested the new functions under DESQview (without running PCBoard, my development system is a 4 meg 20 mhz 386, however my board is only a 10mhz 286 and DESQview doesn't work well on it with it's DTK BIOS!). Due to the limitations, DO NOT use the door on more than TWO (2) nodes at a time! Basically the changes are each copy of the door running needs to have it's own configuration .DAT file (goes without saying!, but am saying it anyway). All of the temporary files created by the door will now have the filename of the .DAT file you pass to the door when calling it up. But, each temporary file created will have a different extension identifying it. It is VERY IMPORTANT that the filename you choose to name your configuration .DAT files HAVE AN EXTENSION! (ie: CONFIG.DAT) This enables each copy of the door running to have it's OWN temporary files to work with, so conflict doesn't occurr between them (this is more for future use than anything else at this point). Eagle Verify Door v2.3a -*- 11 April 1991 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Have modified the code to except the configuration file for the door to be entered on the command line. This allows you to use multiple configuration files for the door. YOU MUST modify your batch file used to call up the door from within PCBoard and add your configuration filename. Example: c:\pcb\doors\everify everify1 c:\pcb\pcboard.sys c:\pcb\main\users everify.dat everify2 c:\pcb\pcboard.sys c:\pcb\main\users everify.dat ^^^^^^^^^^^ NEW v2.3a This modification not only allows you different configurations but I have enclosed an example INSTAREG batch file to use along with the Verify Door. You can now use your INSTAREG (v2.95 and above) door and the Verify Door together! INSTAREG v2.95 and above generates an errorlevel, equal to the security level of the user when InstaReg is finished, so that errorlevels maybe checked in the door batch file to determine whether or not to send the user into another door, based upon his/her security level. See the file INSTAREG for examples! Eagle Verify Door v2.3 -*- (late) 10 April 1991 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ An an effort to avoid the term "CrippleWare", I have reactivated the search for PHONE NUMBER MATCH. The new features, as related to v2.2 and above, can only be used by those users with a KEY file to unlock them. The KEY file is only available to REGISTERED users. REGISTERING your door will allow you to download a KEY file from my BBS, right on-line. The KEY file will unlock the search for USER NAME MATCHES and allow SysOps to access the Door Maintenance Menu that is used to maintain the VERIFY.FON file, which makes your life a whole lot easier being able to do this from within the door, helps keep this file clean and up to date. Eagle Verify Door v2.3 -*- (early) 10 April 1991 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ New to v2.3 is a SysOp Maintenance Function Menu. It will help you maintain your VERIFY.FON file and other associated functions that used to have to be completed out-side of the door. If your security level is 110 or above, you will be shown a different menu than that of a new user. Selecting (M) will allow you to access the Door's Maintenance Function Menu. However, the list of command on this menu are ONLY available to REGISTERED users/sysops. When you registered your copy of the door, you will be given a KEY file that will "un-lock" this restriction and allow you to access the Maintenance Menu. We have a special Door available, so that registered users can download their KEY file right on-line! Additional information has not been added to the EVERIFY.DOC file concerning the use of the SysOp/Door Maintenance Menu as it is pretty much self-explanatory after you use it. Once you have the KEY file you can access this menu. There are 4 commands available on this menu. (V) View the VERIFY.FON file (S) Search the VERIFY.FON file (D) Delete a User from the VERIFY.FON file (Q) Quit/Return back to the Main Menu (V) = Obviously is for viewing the entire VERIFY.FON file (S) = Will prompt you for a KEY STRING to search upon. It will stop at the FIRST find of a MATCH. You will be then prompted as to whether or not you wish to view ALL records in the VERIFY.FON file that matches this KEY STRING. This is handy should you forget the spelling or phone number of the user you want to delete. (D) = Delete a user. This basically works just like the search function described above, but will prompt you with the record that it finds and ask you if you want to DELETE this user! It will NOT delete multiple records, only one at a time. So you have to do each one. Each find and delete will totally rewrite your VERIFY.FON file. A backup is made, and given the name VERIFY.BAK, and will only contain the MOST RECENT changes you have made! Use CAREFULLY! Know what your doing! (Q) = Again obvious, returns you back to the Main Menu. Eagle Verify Door v2.2a -*- 07 April 1991 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Eagle_Verify Door is NOLONGER offered FREE. It is now totally SHAREWARE and after you have used it for 30 days, you are required to registered it for $20, plus shipping and handling of $3.50. If after the 30 days of evaluation you do not register it, you MUST discontinue using it! This includes ALL previously released and earlier versions of the Eagle_Verify Doors! You can save the $3.50 and download the verify door from my BBS, "after" your registration check, money order is received. OR if you have the door already running on your system, you can download the KEY file to register your door. All "registered users" receive FREE updates once registered! Added a KEY.EVD file. This will enable "old registered" users to now use the "current" and "future" releases of the verify door. Without having to get a re-compiled program when a new version is released. This also, allows users who wish to register the verify door to download only the KEY.EVD file and have their verify door registered, this of course AFTER they have sent in their REGISTRATION CHECK! When current registered users/sysops change their BBS name, all they'll have to do is download a new KEY file and their new BBS name will be incoded into the verify door. Saves time and money in mail, downloads! Added in a search for USER NAME match in the VERIFY.FON file. Works just like the search for PHONE NUMBER match routine. Purpose of this new function is for example. Say a user gets purged from the user records due to inactivity. But his NAME and PHONE NUMBER as used when he first used the verify door remains in the VERIFY.FON file. He calls back, uses the same user name, but uses a different phone number! The old configuration would not catch the user and verify him. With this new feature, the VERIFY.FON file is searched first for a phone number match, if not found, it now searches for a USER NAME match. The reason I added this feature was I have had one user use as many as 5 different phone numbers to get verified, after he was purged for inactivity! This will catch him NOW! To upgrade to this release, copy the following files into the verify door directory: EVCONFIG.EXE EVERIFY1.EXE EVERIFY2.EXE LOGO.VD LOGO.VDG SORRYNM.VD <= NEW v2.2 SORRYNM.VDG <= NEW v2.2 Eagle Verify Door v2.1e -*- 24 November, 1990 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Time calculations within the door are now corrected with the release of CKIT v1.75A. Corrected a bug with some systems not hanging up the phone line if the DISCONNECT ALL CALLERS switch was set to Y (Yes/On). Contrary to some believes, EagleWare is NOT FREEware!! It is CONTRIBUTIONware. It is FREE in so as much as it is a fully functional piece of software, and YOU GET WHAT YOU PAY FOR! The flashing UNRegistered Copy shown is meant as "incentive" to register your copies of EagleWare. What amazes me is the systems that charge for access to their boards (Subscription Systems) and yet do not registered the software that makes their board worth subscribing to in the first place, be it network mail software or BBS utilities, like the verify door itself. Running a BBS is very costly, this I know from first hand experience. I also know that some Sysop's simply can't afford to pay for all the shareware they use, and normally will get around to registering one day. But it's the ones that are making money off their users and NOT registering the software THEY themselves use, that are taking advantage of the entire "Shareware - ContributionWare" system!! Remember folks, you get what you pay for! Eagle Verify Door v2.1d -*- 21 November, 1990 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Thanks to Steve Tom, (a SysOp from San Diego - Sorry Steve forgotten the name of your FINE BBS), the Verify Door now has improved manuals. Took out the "hard-coded" disconnect display. The files DCONNECT.VD/VDG now contain instructions and information for users that you want to be displayed to them right before they are disconnected from the BBS. The Door is now "completely" display configurable by the Sysop. Please note that when you edit this new file (ANSI/Graphics) version, that you do not embed the "clear screen" command in the file, or all lines that are previously displayed by the door will NOT be seen by your users. All of the other .VDG files can, and should, have the "clear screen" command embedded into the files and should. Should have explained this in the previous releases, but didn't think it was important. In order for both executables to work correctly, I have to pass a lot of information from EVERIFY1.EXE to EVERIFY2.EXE. Up to five (5) .TMP files maybe created by EVERIFY1.EXE. The temporary files and their use is as follows. $$$1.TMP -> Stores the users phone number, name, date, ect. $$$2.TMP -> A zero byte file that identifies the user as a long distance caller. $$$3.TMP -> A zero byte file that means the users phone number was NOT found in the VERIFY.FON file $$$4.TMP -> A zero byte file that means the user has successfully reconnected and is "on-line" $$$5.TMP -> A zero byte file that means the users PREFIX part of their phone number was FOUND in the PREFIXLD.FON file. $$$1.TMP is created and stores the users phone number, name, and current date. $$$2.TMP will always be created if the user answered YES to the "ARE YOU A LONG DISTANCE CALLER" prompt. If you allow long distance calling then EVERIFY2.EXE uses this file to "know" that the user is a long distance caller and to disconnect them after verification. If you do not allow long distance calling, then the door will close and $$$4.TMP will NOT be created and EVERIFY2.EXE will ABORT the verify. $$$3.TMP will be created if the users phone number was NOT FOUND in the search of the VERIFY.FON file. This will "tell" EVERIFY2.EXE to look for and open up $$$1.TMP and if the verification is successful to write the users phone number, name, date to the VERIFY.FON file and to insert the users phone number into the data/business phone number field of their user record if you have this switch turned on. $$$4.TMP is the "KEY" file that EVERIFY2.EXE acts on. If this file does not exist, EVERIFY2.EXE will "always" abort the verify. The ONLY time this file is created is if the user reconnected successfully or you test the door in the LOCAL mode. This file was not created in v2.1c and that is why v2.1c always failed the verify in the LOCAL TEST MODE. It works correctly now. $$$5.TMP is created if the users PREFIX is found in the search of the PREFIXLD.FON file and it treats the user as if they were a long distance caller and to disconnect them after verification. If you do not wish to make calls to local but TOLL numbers in your area, place the appropriate PREFIX's in the PREFIX.FON file so that if the users PREFIX is found in the search of the PREFIX.FON file, the verification will abort. EVERIFY1.EXE deletes all $$$?.TMP files if found when loaded. This creates a "clean slate" to work with for the door. These $$$?.TMP files will remain until the next time the door is opened. Eagle Verify Door v2.1c ~~~~~~~~~~~~~~~~~~~~~~~ Re-did some of the screens and took out the door's personality! Should make the "West Coasters" Happy. We'll see how many "register" the door now. Re-named and re-drew several display screens. SEE the SETUP.DOC for a complete listing of files that we changed and ADDED !! Added in the ability to DISCONNECT ALL CALLERS after a completed verification. This will require you to DELETED your OLD EVERIFY.DAT file and re-run EVCONFIG.EXE !!! Modify the WELCOME.VD file to tell your users you are using this feature ! Added in another .FON file. PREFIXLD.FON is a file you can use to mark and tag your local PREFIX's that are local, but are a TOLL number from your BBS and don't require the number "1-" to be dialed. If you do in fact allow Long Distance calling, and you do have local but TOLL numbers this file will help you in making sure that the local but TOLL number users get disconnected after verification. If you don't want to make calls to these local but TOLL numbers, you can either set the DISCONNECT ALL USERS switch to Y (Yes) to disconnect all users automatically after verification, or type in all you local but TOLL prefix's into the PREFIX.FON file and those numbers found will NOT be called at all. This file is ONLY searched if the caller entered N (No) at the "Are you a Long Distance caller (Y/N) (Enter = No)?" prompt. If you allow Long Distance calling and the user answers the above prompt with a Y (Yes), they will be asked if they are within your local AREA CODE. If they answer Y (Yes) to this second prompt, their phone number as entered will have a "1-" placed onto the front of the number to be dialed. They will NOT be prompted for their AREA CODE then. Added a LOGOFF.VD/VDG file that is displayed to users that are automatically logged off. They will NOT be shown the GOODBYE.VD/VDG files. Only users that do not get automatically logged off will be shown the GOODBYE.VD/VDG files. Added a SECURITY.VD/VDG file to be displayed to users who do not have the correct security level to access the door. Eagle Verify Door v2.1b ~~~~~~~~~~~~~~~~~~~~~~~ Never released.... Local coding and test. Eagle Verify Door v2.1a ~~~~~~~~~~~~~~~~~~~~~~~ Totally recoded the door into two different executables. Several SysOp's are still have problems with the return from a good connection. We ran into the same problems several years ago, and coding in two different .exe solved the problem. Hopefully this will do the trick. Version 2.1a uses all of the same files as v2.0 except the EVERIFY batch file used to callup the door has changed. PLEASE see this FILE BEFORE you run the door. Instead of just one EXECUTABLE (EVERIFY.EXE) as in v2.0, we now have two EXECUTABLES (EVERIFY1.EXE and EVERIFY2.EXE). Hopefully, this will take care of the remote keyboard lockup. Because we are using two different .exe files, we have to create alot of .TMP files to pass along information from one module to the other. So this version (v2.1) has alot more I/O. Make sure you have the statement in your config.sys set to about FILES=10, because the door opens up to 7 files at a time in this version.