Beijing Paradise BBS Backup

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

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

Wrap

Text File | 1993-05-14 | 32.4 KB | 712 lines

┌────────────────────────────────────────────────────────────────────────────┐ │ ▒▒▒▒ RA-CCD v1.0 ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │ └────────────────────────────────────────────────────────────────────────────┘ ┌─────────┐┌──────────┐ ┌────────┐┌────────┐┌────────┐ │ ┌───┐ ││ ┌───┐ │ │ ┌────┘│ ┌────┘│ └┐ │ │ │ ││ │ │ ├────┤ │ │ │ │ ┬───┐ │ │ └───┘ └┤ └───┘ │ │ │ │ │ │ │ ┤ │ │ ┌────┐ │ ┌────┐ ├────┤ └─────┤ └─────┤ ┴───┘ │ │ │ │ │ │ │ │ │ │ │ ┌┘ └──┘ └──┴──┘ └──┘ └─────────┴─────────┴────────┘ "The RemoteAccess Credit Card Door" Written by Harry Konstantinou / Dynamite BBS (c) Copyright 1992-93 All Rights Reserved Harry Konstantinou / Dynamite BBS G.P.O. Box 1359 Canberra City ACT 2601 Australia (06) 241-7388 / (06) 241-7399 +61 62 241-7388 / +61 62 241-7399 Netmail: 3:620/250@fidonet 28:2600/250@signet ┌────────────────────────────────────────────────────────────────────────────┐ │ ▒▒▒▒ Table of Contents ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │ └────────────────────────────────────────────────────────────────────────────┘ Introduction . . . . . . . . . . . . . . . . . . . . . . . 3 Disclaimer. . . . . . . . . . . . . . . . . . . . . . . . . 3 How to Register . . . . . . . . . . . . . . . . . . . . . . 4 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . 5 Installation . . . . . . . . . . . . . . . . . . . . . . . 7 CCDCFG (Configuration Program). . . . . . . . . . . . . . . 8 File Menu Option. . . . . . . . . . . . . . . . . . . . 8 INFO. . . . . . . . . . . . . . . . . . . . . . . . . 8 REGISTRATION. . . . . . . . . . . . . . . . . . . . . 8 DOS SHELL . . . . . . . . . . . . . . . . . . . . . . 8 System Menu Option. . . . . . . . . . . . . . . . . . . 8 PATHS . . . . . . . . . . . . . . . . . . . . . . . . 8 MESSAGE DETAILS . . . . . . . . . . . . . . . . . . . 9 MISC OPTIONS. . . . . . . . . . . . . . . . . . . . . 9 Options Menu. . . . . . . . . . . . . . . . . . . . . . 10 ACTIVE OPTIONS. . . . . . . . . . . . . . . . . . . . 10 ACTIVE C/CARDS. . . . . . . . . . . . . . . . . . . . 10 Item Manager Menu Option. . . . . . . . . . . . . . . . 10 TRANSACTION EDITOR. . . . . . . . . . . . . . . . . . 10 Viewing . . . . . . . . . . . . . . . . . . . . . . 11 Keys. . . . . . . . . . . . . . . . . . . . . . . 11 Editing . . . . . . . . . . . . . . . . . . . . . . 11 External ANS/ASC Files. . . . . . . . . . . . . . . . . . . 13 Multi-Node Operation. . . . . . . . . . . . . . . . . . . . 13 Version Information . . . . . . . . . . . . . . . . . . . . 14 Final Note! . . . . . . . . . . . . . . . . . . . . . . . . 14 - 2 - ┌────────────────────────────────────────────────────────────────────────────┐ │ ▒▒▒▒ Introduction ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │ └────────────────────────────────────────────────────────────────────────────┘ Welcome to RA-CCD, the ultimate Online Credit Card Subscription Door for RemoteAccess version 2.00 and up. I'd firstly like to thank you for showing some sort of interest in this program, believe me, you will not be disappointed! Two different configurations of RA-CCD are available, these being the Registered Setup of RA-CCD or the Unregistered Evaluation Setup. As I am myself still a student, I strongly urge you to register this program so that more time and programming resources can be spent bringing you more programs and utilities to make your life as a BBS System Operator a lot easier. Although RA-CCD was tested and worked correctly under RemoteAccess version 2.00, it should also "theoretically" work under QuickBBS and RemoteAccess versions 1.10/1.11. I don't have any ways to test this so if someone running the above versions of software can test this and let me know it would be very much appreciated. What I basically mean by theoretically, is that RA-CCD knows about QuickBBS (v2.75 and v2.76) and RA (v1.11) drop files (exitinfo.bbs and dorinfo1.def) and can (should) convert between the two as required with the need for you to do anything. ┌────────────────────────────────────────────────────────────────────────────┐ │ ▒▒▒▒ Disclaimer ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │ └────────────────────────────────────────────────────────────────────────────┘ RA-CCD is guaranteed to do absolutely nothing. If it trashes your Hard Disk then that is your problem. You may use RA-CCD for a period of 30 days on a trial basis in order to determine it's suitability for your particular need. After this period you *MUST* register RA-CCD to legally continue running it. Registration entitles you to use RA-CCD and any future versions of RA-CCD for as long as you wish, subject to any licensing conditions attached to future versions. Please refer to 'HOW TO REGISTER' section of this document for further information. Harry Konstantinou (Dynamite BBS) is in no way obligated to provide any future versions of, or support for RA-CCD. Site and group registrations are available, but are dealt with on a case by case basis only. You may NOT modify or otherwise reverse-engineer RA-CCD in any way shape or form. RA-CCD may not be used in any unlawful or illegal manner. - 3 - ┌────────────────────────────────────────────────────────────────────────────┐ │ ▒▒▒▒ How to register? ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │ └────────────────────────────────────────────────────────────────────────────┘ To register simply print the registration form (REGISTER.FRM), and send it with your registration payment to; Harry Konstantinou C/- Dynamite BBS GPO Box 1359 CANBERRA CITY ACT 2601 AUSTRALIA Please note that you must fill out the registration form correctly in order for your details to be processed. Not doing so will result in delays in your key file arriving. Cheques and money orders should be made payable to 'Dynamite BBS', and not Harry Konstantinou. (Please note Credit Cards are also accepted - See REGISTER.FRM for more information) Please include either a FidoNet address or a stamped, self-addressed envelope so that receipt of your payment can be acknowledged. (only if required) REGISTRATION FEES : NonCommercial / Commercial : $AUD20 - Currently only one type of registration is available. Both Commercial and NonCommercial BBS systems can register for the flat rate of $20 (Australian). Please note that registration with Australian dollars is the easiest for me, but if this is unavailable to you, US dollars shouldn't be too much of a problem. An extra few dollars to aid me in converting the currency over wouldn't be too bad also. :) - 4 - ┌────────────────────────────────────────────────────────────────────────────┐ │ ▒▒▒▒ Overview ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │ └────────────────────────────────────────────────────────────────────────────┘ Remoteaccess Credit Card Door (RA-CCD) is an online credit card door to accept user subscriptions, and update a user record accordingly. Features include ; - Internal Credit Card Validation Routines (optional) - Up to 15 Credit Cards can be defined (5 hard-coded) - Up to 20 Transaction levels for the Registered version - A sales tax (Markup %) can be configured per transaction item - A shipping or other flat rate can be configured per item - A shipping address can be asked for per transaction item - Users security level can be updated per transaction item - Users security flags can be updated per transaction item - Users subscription expiry date can be updated per item - Asking for a voice phone number can be configured globally - A "MinSecLev" (Minimum Security Level) option, so that you can setup "Upgrade" security levels (described later-on) - Optionally post a message to the system operator (name can be defined) in ANY message board of the Hudson message base - Optionally run an external program after a transaction item has been completed - Internal message editor so that users can post a message to the system operator (named can be defined) regarding a subscription query - Internal paging routines so that users can page the sysop online regarding a subscription query. A minimum security level to page can be defined. RA-CCD also follows the RA specific paging routines (times, Scroll-Lock On/Off, etc) - And much, much more! RA-CCD is specifically designed to be an online credit card door for user subscriptions and BBS registrations. This is basically why it is limited to 10 transaction items for the unregistered version, and upto 20 transaction items for the registered version. Future versions of RA-CCD may have the facility for more transaction items, but this will basically only be incorporated if demanded. There are 15 different types of credit cards that can be configured. Hardcoded are BankCard, MasterCard, VisaCard, American Express and Diners Club. The internal validation routines will validate all these credit cards (automatically) except for Diners Club. The 10 optionally defined credit cards do not use the internal validation routines for obvious reasons. - 5 - Once a subscription has been accepted, RA-CCD produces the following text file (in the defined path) called CCDOOR.TRA ; ════════════════════════════╡ Transaction Details ╞════════════════════════════ Harry Konstantinou completed on Tuesday April 13, 1993 at 9:03:48 p.m. **Name of Transaction Item Here as defined** **Name on Credit-Card** Card Type : **Card Type** **C/Card Number** - *FAILED* Expiry Date : **Card Expiry Date** Amount $ 60.00 MarkUp $ 6.00 (10.00%) Shipping $ 10.00 -------------- TOTAL $ 76.00 ============== **Users phone number if defined** ═══════════════════════════════════════════════════════════════════════════════ The text '*FAILED*' is only printed to the end of the credit card number if the number failed the internal credit card validation routines and you have configured RA-CCD to NOT 'Refuse credit cards'. If you have configured RA-CCD to not accept credit cards that fail the internal validation routines, then RA-CCD will not accept the transaction, and therefore not create this file. If defined, after a transaction has been accepted, RA-CCD will run the external program for that transaction item, and also if defined will post a message to the system operator (or whoevers name is defined in CCDCFG) to inform them that a transaction has taken place. RA-CCD also includes internal logging routines, so that you can see exactly what each user has done in the credit card door. For example if a user enters the door, and enters an "invalid credit card number" it will be outputed to the logfile (as defined in CCDCFG), as well as a lot of other 'useful' information. RA-CCD has been tested and is working on a 386/33 with 4 megs Ram, running 2 nodes under Desqview and on a LAN (Netware Lite). - 6 - ┌────────────────────────────────────────────────────────────────────────────┐ │ ▒▒▒▒ Installation ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │ └────────────────────────────────────────────────────────────────────────────┘ RA-CCD requires you to make a config file with all your settings. You can do this by running the 'ccdcfg.exe' program. This is the program where you setup all your paths, transaction items and credit card transactions as well as a few miscellaneous options. Please see the section labelled 'CCDCFG' for more information or help on the configuration part of RA-CCD. To run RA-CCD I suggest you run it from a type 7 that loads up a batch file which would change into the RA-CCD directory and then run the actual door with any command line parameters needed. The first parameter is the path to the dorinfo1.def and exitinfo.bbs system files, if they are in the local directory then no need to pass any parameters on loadup. Also please note that the *N parameter is only required for multi-line systems, but the *M is required by most systems, as this will swap RA out, and give more available memory for RA-CCD to function more efficiently. When installing you must remember that the "Path to Dorinfo/ExitInfo" MUST be the FIRST parameter passed on the command line, whereas the node number the user is on, MUST be the second parameter passed from the command line. For Multi-Node systems I suggest the following batch file ; @ECHO OFF CD\DOORS\CCDOOR CCDOOR C:\RA\LINE%1\ %1 CD\RA\LINE%1 Your optional command line in the menu would look like this ; *C /C C:\BATCH\CCDOOR.BAT *N *M The same "style" of batch file can be used for a single node system as well, the only difference is that you do not have to pass the node number on the command line (as the second parameter) Since I run a multi-line system here, this batch file will load up RA-CCD from any line, and is very quick as it does no file copying of dorinfo's and exitinfo files. If you prefer to copy exitinfo.bbs and dorinfo1.def to the RA-CCD directory, then do not forget to copy them back after the door has exited, and rewritten them. This is crucial for RA-CCDs' upgrade functions to work correctly. ■ RA-CCD requires ; - a copy of 'ccdoor.cfg' (created by CCDCFG.EXE) in the current directory - that the RA environment variable be set (SET RA=C:\RA). Refer to the actual RemoteAccess manual for more information on this. - 7 - ┌────────────────────────────────────────────────────────────────────────────┐ │ ▒▒▒▒ CCDCFG ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │ └────────────────────────────────────────────────────────────────────────────┘ File Menu; ══════════ - Info This option simply displays a window listing credits for RA-CCD and CCDCFG. - Registration This option also displays a window that gives you details on registration for RA-CCD, please note that RA-CCD cannot be run for more than 30 days in the unregistered evaluation mode. - DOS Shell Just in case you wish to 'Drop to DOS' while in CCDCFG to check something out. Type "EXIT" from the DOS prompt to return operation to the configuration editor. - Exit Pretty clear I would think :-), this exits CCDCFG. If any changes were made to any option from the Systems or the Options menu, then it will prompt asking you if you wish to save these changes or not. System Menu; ════════════ - Paths - LogFile Path/Name This is the path to the logfile you wish to create (if at all). This must be a valid DOS Filename (and directory if required). If you are running on a multi-node system, you can setup RA-CCD to write separate logs for each node. You do this by placing the '*N' parameter in the filename. For example ; LogFile Path/Name: CCDOOR*N.LOG will write a 'CCDOOR1.LOG' file for Node 1, a 'CCDOOR2.LOG' for Node 2, etc. RA-CCD picks up the current node as the second parameter passed on the command line upon execution. (Refer to the Chapter on Installation) - Receipts Path If you wish your transaction (receipt) file to be placed in a separate directory, then simply place the name of the directory here. CCDCFG will attempt to validate its existence and will ask you if you wish to create the directory if it does not exist. Please note that you are NOT required to place the name of the transaction file here just the valid path. - 8 - - RA Message Base This is the path to the Hudson Message Base as indicated in RACONFIG. If you are not going to use any of RA-CCDs' internal message base posting routines then you are not required to place anything here. - Message Details - Msg Area Nº This is the Hudson message base board number to post all RA-CCDs' messages into. Valid range is from 0 to 200. If you are not going to use any of the internal message posting routines, then you should set the message base board to '0'. Make sure that you have a valid and correct "RA Message Base" path specified in the 'Systems=>Paths' menu. Note that ALL 'queries; and ALL 'Notify' Messages will go into this message board. - Address To If you plan to use the internal message base routines, then this is the name of the user to post ALL the messages to. All the messages include the 'Subscription Queries' from users, and all the 'Notify Messages' from RA-CCD itself to notify you that a user has subscribed. - Misc Options - Min Paging Level If you do not want ALL users to have the ability to page you from inside of RA-CCD then set the 'Minimum Security' Level to access this option. Valid range is 0 to 65535. Setting to 0 will allow all users inside of RA-CCD to page you. Note that RA-CCD does enforce (if it can find a valid copy of CONFIG.RA) and use RA's internal 'Maximum Page Times' and also the actual 'Paging Times' (Days and Hours). RA-CCD also follows RemoteAccess in that it uses the 'Scroll-Lock' key to silence the page. With Scroll-Lock on, the paging will take place, with Scroll-Lock on, it will continue to page but will not actually make any noise at the local console. RA-CCDs' paging routines also require it to find a copy of 'PAGE.RA' in the RA system directory as pointed to by the RA Environment variable. - 9 - Options Menu; ═════════════ - Active Options - Refuse C/C Whether or not you wish to refuse credit cards that do not pass the internal credit card validation routines. Setting this to "YES" WILL refuse credit cards that fail the validation, whereas setting this to "NO" will simply flag the entry as '*FAILED*' in the transaction/receipts file (CCDOOR.TRA) and continue with the transaction. Note that only 'BankCard', 'MasterCard', 'VISA Card' and 'AMEX' (American Express) use the internal validation routines, whereas the 10 extra definable credit cards do NOT use any type of credit card validation done by RA-CCD. - Phone Prompt If you wish to ALSO ask (Globally) for a contact phone number while a user is entering in their information, set this option to YES, if not simply setting it to NO will not ask for a contact phone number. - Active C/Cards - BankCard * Automatic Validation Present * - MasterCard * Automatic Validation Present * - Visa * Automatic Validation Present * - Amex * Automatic Validation Present * - Diners Club Do you accept any of these credit cards?. Set to ACTIVE if you want RA-CCD to allow the user to process a transaction with that type of card. - Card #1 TO Card #10 Here you can define up to 10 different credit cards that you accept. No internal credit card validation is processed on any of these 10 cards, so if you do not wish to use the above internal validation routines for say MasterCard, then simply set the above MasterCard option to "Not Active" and enter a new MasterCard option. Item Manager Menu; ══════════════════ - Transaction Editor This is the most complex part of the installation. But it can also be the most simplest if you take the time to read and understand the following properly. You can have up to 10 different transaction items for the unregistered evaluation copy of RA-CCD, and up to 20 different transaction items for the registered version. - 10 - - Viewing The following keys are available for use while you are viewing item details; RIGHT/LEFT/UP/DOWN ARROWS & HOME/END KEYS - Allows you to move from one item to another with the use of these keys. ENTER (Edit) - Edit the current transaction, refer to the section below labelled 'Editing' for further information. F2 (Search By ItemName) - This function provides a quick method to move through the currently selected database to find the record you wish to edit or view. INS (Add New Record) - Creates a new record for entry in memory, but does not actually write it to disk until you press ESCAPE and then choose 'Y'es to save changes. DEL (Delete Current Record) - Removes the currently active record (transaction item) from disk and memory - Editing Pressing the ESCAPE key after you have finished editing, will ask you if you wish to save changes. Replying YES to this will save changes to DISK. The following fields are used and should all be set as required; Name : This is the name of the transaction item ie: "Full Membership (1 Year) Level 120" If this field is blank, then this particular transaction item will NOT be displayed to the user. Amount : How much does this option cost (valid range is from $0.00 to 9999999.99) MarkUp : A "MARKUP" Percentage. This is more specifically designed for if you are using RA-CCD for a shopping door, or if you maybe charge your 'bank fees' to your users. (Valid range is from 0.00% to 100.00%) Shipping : How much to add to the AMOUNT and MARKUP for the shipping of this good. Again mainly for online shopping purposes. Ship To : Ask for a "Delivery Address" for this particular item. Sec.Level: What Security Level to upgrade user too, after he/ she has completed a credit card transaction successfully. (Valid range is from 0 to 65535) - 11 - MinSecLev: Minimum security level required to access this option, this is specifically designed for 'Upgrade Access levels' so that, if a user is at access level 1, and he/she wishes to upgrade to access level 2, the program makes sure they are ON access level 1, and if the are, shows them this option, if not, it doesn't allow them to upgrade to the new level, until they have paid for access level 1 privileges. Set to 0 to disable. (Valid range is from 0 to 65535) ExpiryDay: How many DAYS to add to the 'Subscription Expiry Day' field in RA. I set this to 365 or 366 depending on how you feel :-).. (valid range is from 0 to 65535) A Flags : Flag settings. This follows the RA 2.00 specific B Flags : type of flags. Valid options are as follows ; C Flags : X = Turn flag ON (or leave ON) D Flags : O = Turn flag OFF (or leave OFF) - = Leave flag ALONE (do not toggle) External : This option simply executes a DOS Shell after a valid transaction has taken place. RA-CCD is simply swapped to either EMS/XMS or Disk, depending on which one is currently available, and which will be the most efficient for the DOS Shell. If this field is blank, RA-CCD will not attempt to exit to any external program. You can use this option for quite a lot of things. Currently, no parameters are passed to the program. You are NOT required (and should not) pass the extension of the file to execute. For example, simply placing "TEST" will attempt to execute 'TEST.COM' then 'TEST.EXE' then 'TEST.BAT'. - 12 - ┌────────────────────────────────────────────────────────────────────────────┐ │ ▒▒▒▒ External ANS/ASC Files ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │ └────────────────────────────────────────────────────────────────────────────┘ There are a few hard-coded ANSI/ASCII screens required/not-required, but will be displayed if required. These should ALL be placed in the same directory as CCDOOR.EXE and CCDCFG.EXE. CCDMAIN.ANS/ASC This is the main menu, and is NEEDED for the program to work at all :) CCDWARN.ANS/ASC This is a 'warning' bulletin supplied with the door, that tells the user, that it is an offence to use a credit-card if it is stolen or otherwise, not allowed to be used or whatever, you will have to edit this file and insert your 'BILLING' name at the bottom of both the ANSI and ASCII versions. CCDHELP.ANS/ASC This is the help screen for the main menu, if exists, it will allow the option to be pressed, if the file does not exist, it will not allow the caller to access this option at all. CCDHELP1.ANS/ASC If exists will activate the option, and allow it to be pressed. This is the first of two help screens that the sysop can put whatever he/she feels like it in there, maybe show the 'access' levels and prices, so that the user does not have to actually perform a credit card transaction before he/she can see the prices, etc... CCDHELP2.ANS/ASC Same as above, if this file exists, will allow the user to press/access this option, if it doesn't, will not let the user access this option. ┌────────────────────────────────────────────────────────────────────────────┐ │ ▒▒▒▒ Multi Node Operation ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │ └────────────────────────────────────────────────────────────────────────────┘ Multi node operating is described all through this manual, but there are a few things I thought I should remind you all of here ; - Don't forget to - Place the "*N" parameter in your LogFile Path/Name option under the "System=>Paths" option. - Pass the NODE number as the second parameter on the command line when executing the door. ie: CCDOOR.EXE C:\RA\LINE2 2 ^Node Number If you have not forgotten the above few hints, then you should have no problem in running RA-CCD in a multi-node environment under both a Network or a Multi-Tasker. - 13 - ┌────────────────────────────────────────────────────────────────────────────┐ │ ▒▒▒▒ Version Info ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │ └────────────────────────────────────────────────────────────────────────────┘ 1.00 - Initial Release :) ┌────────────────────────────────────────────────────────────────────────────┐ │ ▒▒▒▒ Final Note ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │ └────────────────────────────────────────────────────────────────────────────┘ RemoteAccess Credit Card Door (RA-CCD) was written in and compiled with Turbo Pascal 6.0. Thanks also go to the authors of the Techno- Jocks Turbo Tool Kit which has helped make my coding easier in this and several other projects I am working on. Thanks also go to Motor City Software, authors of JP-DOOR, an excellent Unit for BBS Door Programming. If you have any Comments or Bug Reports please send me a message to either of the following address; Harry Konstantinou FidoNet 3:620/250 - Dynamite BBS. SigNet 28:2600/250 I hope RA-CCD is of some use to some of you. RemoteAccess : (C) Andrew Milner and Continental Software. Turbo Pascal : (C) Borland. Desqview : (C) Quarterdeck JP-Door : (C) Rod Hancock and Motor City Software - 14 -