08/28/90 - v1.1 Beta #5 ~~~~~~~~~~~~~~~~~~~~~~~ The security level is no longer checked if the seconds to wait is set to 0 or 1. To make room for future OTR modes, the number of seconds to wait should be set above 5. Depending on evolution, I may use the numbers 0 - 5 for mode definition. CONFIG CHANGE!!! Insert on LINE 10. Added an "Access List". If the seconds to wait time is set to 1 (one), the file defined on line 10 of the config file will be checked for the users name. If his name appears in the list he will be granted access to the door. If the number of seconds to wait is set to 1 but the access file does not yet exist or can't be found, one will be created using the name given. The last line of this file MUST contain the entry 9999. The access list change will be made to all OTR doors. 08/27/90 - v1.1 Beta #4 ~~~~~~~~~~~~~~~~~~~~~~~ Updated the dialing routines. 08/26/90 - v1.1 Beta #3 ~~~~~~~~~~~~~~~~~~~~~~~ Had a problem with my GAPCDR library and the comm port stuff wasn't working correctly. It is now! Minor enhancement... When a user accesses OTRPage and for some reason isn't allowed in, the local screen will give a quick reason why. 08/25/90 - v1.1 Beta #2 ~~~~~~~~~~~~~~~~~~~~~~~ Added support for different com ports. This is an update to the GAPCDR library so the config lines for these two items must be inserted at positions 4 and 5 in the config. Line 1: C:\GAP --- Path to default BBS directory Line 2: Remote Designs --- BBS name Line 3: 0 --- 0 = GAP; 1 = PCB Line 4: 4 --- Comm Port IRQ Line 5: 03F8 --- Comm Port Base Address . . . If you are not sure of your comm port's IRQ and Base Addr, you can get this info from your GAPSETUP menus. Use the seeting you have put there for the door. 08/24/90 - Version 1.1 ~~~~~~~~~~~~~~~~~~~~~~ Updated to keep in step with new programming tools. Added the option to turn off password protection. If the seconds to wait for passkey parameter is set to 0 (zero), there will be no security checks other than the minimum security level requirement. A password will still be required when the call back connection is completed. Update the entire call back procedure to match the improvements made to CallBack Door. 02/11/90 ~~~~~~~~ Final beta before release. The only change was to the way the door handles the password AFTER the callback. Instead of entering YOUR password, enter the password you have set for the door. That is the same password you used to enter the door in the first place. 01/05/89 ~~~~~~~~ Ok, BETA time! I made a few small changes, this door will not require a OTRCSYS.DAT. I decided to let it ride and probably not get any registrations. There will be no demo versions, what you see is what will go (other than bugs). The door will now ask you for your password after the callback is successful. Simply enter your board password. Added ability for the sysop to configure the number of tries per callback. Add a line to your config and place the amount on this line (line 11). A good start would be 3 or 5. 11/22/89 ~~~~~~~~ Hmmmm... no docs yet so have a ball figuring this one out! Okay-okay, I'll tell ya how.... c:\gap Remote Designs 0 5 ----- seconds to wait for passkey 126 ----- passkey ASCII scan code (126 = tilde) PASSWORD ----- take a guess 10 ----- minimum security to access the door ATDT ----- modem dial command 1 ----- seconds to wait for connect 714 ----- bbs'd area code As you can see this is like a cross between CallBack and OTRDor. Setup is simple, so not much to day there. Just let me know if it works ok and if you have any ideas for improvements. I doubt there will be much more to the thing so.... Also, I am thinking of limiting the demo version to 10 minutes on line after the call. Do we think that is fair?