home *** CD-ROM | disk | FTP | other *** search
-
-
-
-
- Credit Card Membership Registration Door v3.00
- Copyright (C) 1989, 1993 FeatherNet Software
-
-
-
-
-
- Introduction
- ------------
- CCDOOR is for the sysop of a pcboard v14 or later bbs who uses a paid
- subscription for user access. CCDOOR will take the information from the
- user, decide if it meets the required criteria, update the USERS file
- with the new security level and subscription date (if desired), and add
- all the Q's & A's to a specified file.
-
- CCDOOR utilizes the following to ensure valid information is submitted.
- (1) Phone # Trash file
- (2) Card # Trash File
- (3) Expiration Date limiting (36 Months)
- (4) Repetitous key trapping
- (5) 3 Major errors allowed
- (6) MOD 10 card number verification scheme
-
- The door should work on other bbs's as well. It will update the pcboard users
- file if the sysop elects. This may be a problem non-pcb sysops can live with.
- It does get the user's information and save it in a log file and prints both
- a hard coded report and a sysop definable report.
-
- Note: Version 2.14 added a dos errorlevel of 1 when ccdoor terminates
- normally after saving the report(s). An errorlevel of 0 upon
- termination of CCDoor means the user either made too many errors
- or chose not to complete the door script.
-
-
-
-
-
- Running The Program
- -------------------
-
- Setting up "CCDOOR" can be accomplished in a few minutes. Do not think of
- this as being complex and it will not be. Follow the below guide to the
- letter and you will have no problems.
-
-
-
- 1. I recommend you make a sub directory for CCDOOR to operate from. You may
- place it anywhere on your system, however.
-
- 2. Use PKUNZIP.EXE to extract the files into the chosen directory.
-
- 3. Edit the configuration file to suit your system's defaults. If you are
- networking or otherwise using more than one node, ensure a seperate
- configuration file (with a discrete filename) is made for each node.
-
- 4. Make a batch file to run the door from the bbs. Use my example as a guide.
-
- 5. Construct a TRASH file for card numbers you know are bad and place the
- numbers in them. CCDOOR will check for bad numbers AFTER the user enters
- and verifies the card number. If a forbidden number is used, the user is
- Immediately logged off and the door returns to pcboard for wrap-up.
-
- 6. Construct a TRASH file for illegal Phone Numbers.
- CCDOOR will check for bad numbers AFTER the user enters his phone #.
- If an illegal number is used, the user is either returned to the Phone #
- prompt or Immediately logged off and the door returns to pcboard for wrap-up.
-
-
- Using User's Responses to Write a 'Custom' Report
- -------------------------------------------------
-
- In response to several requests for more flexibility with the
- report ccdoor writes, I have taken action on the matter and have
- added a 'Custom' report option.
-
- The report will utilize the responses from users and the sysop
- will specify which fields to use and which terminator to use at the
- end of each field in the report ((1) CRLF, (2) Comma & Space,
- (3) two spaces, or (4) enclosing the field in quotes and
- separating each field by a comma
-
- The fields Usable in the custom report and their respective
- numbers are:
-
- (1) Letter Code of Credit Card selected (A, M, D, V, O)
- (2) Name User entered as 'Listed on Card'
- (3) Street Address
- (4) City user is from
- (5) State or Province user is from
- (6) Zip or Postal Code
- (7) Card number entered
- (8) Unnecessary (Same a #7. Used for continuity)
- (9) Card Expiration Date
- (10) Membership Option
- (11) Telephone Number
- (12) User's Name in bbs USERS file
- (13) The time when the report was written (HH:MM)
- (14) The date when the report was written (DD/MM/YY)
-
-
- If you DO NOT want to write a 'Custom' report, place a ZERO '0' in
- the .cfg file on the line stating the number of fields to use
- in the 'Custon' report and make no further entries pertaining to
- the 'Custom' report.
-
- If you ARE going to specify a 'Custom' report follow the guide in the
- sample .cfg file below.
-
-
-
-
- Note:
-
- Below is MY actual configuration file for v3.00. It is followed by a detailed
- description of each entry.
-
-
- Sample of REAL Configuration File ; I named mine "ccd.cfg" (node 1)
- ---------------------------------
- The Programmer's Inn
- Rooster Pierce
- c:\pcb\pcboard.sys
- c:\test
- c:\test\ron.scr
- c:\test\ron.ans
- c:\pcb\main\users
- c:\pcb\main\pwrd
- c:\test\cctrash
- 10
-
- Effective May 1, 1989, there are 2 Membership Options available, @FIRST@.
- The Full One Year Membership includes access to ALL MIDI Conferences,
- including the Patch and Sample Libraries.
-
- The Limited 3 Month Membership DOES NOT include access to the
- Patch and Sample Libraries. Access to those libraries is available
- with the One Year Membership ONLY.
-
- What is your Membership Option ( 1 = 1 Year/$95 2 = 3 Months/$30 )
- 2
- 80, 12
- 60, 3
- 0
- c:\test\ccinfo
- c:\test\ccphone
- 30
- 1
- 0
- 00000
- VMAOD
- 1
- What is your city
- What is your state or province
- What is your zip code or postal code
- Your City
- Which State or Province
- Your Zip or postal code
- Y
- 1
- c:\test\ccreport
- 1
- 5
- c:\test\cclabel, 1
- 2,1
- 3,1
- 4,1
- 5,1
- 6,0
- &H3F8
- 4
-
-
- Explanation of Above Configuration file
- ---------------------------------------
-
- The Programmer's Inn ;BBS name
- Rooster Pierce ;Sysop name
- c:\pcb\pcboard.sys ;Where to find PCBoard.sys (v2.13 and newer ignore it)
- c:\test ;Where to find the ccdoor menu files
- c:\test\ron.scr ;Full path/name of the script to use
- c:\test\ron.ans ;Full path/name of the script answer file to write to
- d:\pcb\main\users ;Path/name of the pcboard USERS file
- d:\pcb\main\pwrd ;Path/name of the pcboard pwrd file (See Below!!)
- c:\test\cctrash ;Full Path/Name for the Trash File (read only)
- 12 ;Number of Lines to read (includes the membership
- ;question). Any blank line is counted. This is ONLY for
- ;the membership question!!!
-
- There are 12 total lines in the above configuration file describing the
- membership options available on the bbs. The last line (line 12) MUST
- be the actual question asking which membership option a user desires.
-
-
-
-
-
- What is your Membership Option ( 1 = 1 Year/$95 2 = 3 Months/$30 )
- 2 ----------------------;Number of membership levels to use.
- 60, 12 ---------------- ;The access level and number of months for option 1
- 61, Unlimited-----------;The access level and Text to disable exp. updating
- ;If "00-00-00" follows the new access level the
- ;NEW expiration date will be 00-00-00. (000000)
- 1 -----------;Enter a "1" if CCDOOR IS TO UPDATE the users file or a "0" if NOT
- c:\test\ccinfo ---------;Full Path/Name of a text file with anything you wish
- c:\test\ccphone --------;FULL Path/Name of the Phone Trash file.
- 30 ---------------------;Number of lines in the script header (1-199).
-
- 1 --------------------- ;Place a "0" here to logoff users with more than 3
- ;illegal/incorrect responses or a 1 if you want them
- ;returned to the bbs
-
- 0 ;This is the security level required to access this door. Useful
- ;on systems with more than one TYPE ccdoor script.
-
- 00000 ;Registration Number. You get this from the author when you register
- ;the door.
-
- VMAOD ;Indicates this bbs wil accept Visa, Mastercard, American Express,
- ;Optima, and Discover
- 1 ;A "1" here tells ccdoor NOT to CHANGE the access level of a user
- ;whose access level is already HIGHER than the level given users
- ;successfully completing the CCDoor registration procedure.
- ;Otherwise place a "0" here
-
-
-
- What is your city ;The first three lines are for the
- What is your state or province ;questions themselves. leave enough room
- What is your zip code or postal code ;for the answer on the same line!
-
- Your City ;These three lines are for the review of
- Which State or Province ;answers. Limit these to 27 characters.
- Your Zip or postal code ;
-
-
- Y ;Place a "Y" here if you want ccdoor to compute the NEW
- ;expiration date from "today's" date. Any other letter will
- ;cause ccdoor to use the expiration date in pcboard's users
- ;file.
-
- 1 ;Put a "1" here if you wish a report to be
- ;written to a specified file name. A sample
- ;'hard coded' report format is listed below
-
- c:\test\ccreport ;Path/name of "report" text file.(if any)
- 1 ;a "1" signifies you are running pcboard
- ;v14.5 or greater. Use a "0" otherwise
-
- 5 ;Number of lines in 'Custom' report (0 if none)
- |----------------------------------------------------------------------------|
- | Note: The following lines pertaining to the 'Custom' report are to be |
- | included in the .cfg file ONLY if you have entered a number greater |
- | than zero in the entry above. If you DO NOT want to write a 'Custom'|
- | report, place a ZERO '0' in the above location in your .cfg file(s) |
- | and make no further entries pertaining to the 'Custom' report. |
- | It is likely that in a future release the .cfg file will be expanded|
- | and you must follow the syntax to prevent problems. |
- |----------------------------------------------------------------------------|
- c:\test\cclabel, 1 ;Path Name of file to write 'custom' report to and
- ;a '1' if you wish a blank line added after each report
- ;is written (otherwise place a zero here)
-
- Note: The above 'sample' ccd.cfg file will use 5 fields from the user's
- responses in the 'Custom' report. The first number in each entry
- is the FIELD to write and the second is the 'terminator' code.
- The terminator codes and explanations are:
-
- 0 = CRLF (Carriage Return and Linefeed
- 1 = ", " (Comma & Space)
- 2 = " " (Two Spaces)
- 3 = Enclose the field in Quotes and terminate it with a comma
-
- Note: If you are using a 'Custom' report, each field entry must be separated
- by a comma in the .cfg file as listed in the sample .cfg file above and
- in the below explanation.
-
- 2,1 ;Writes field #2 terminated by a comma and space
- 3,1 ;Writes field #3 terminated by a comma and space
- 4,1 ;Writes field #4 terminated by a comma and space
- 5,1 ;Writes field #5 terminated by a comma and space
- 6,0 ;Writes field #6 terminated by a Carriage Return/Linefeed
- ------------------------------------------------------------------------------
- &H3F8 ; Sample Serial Port Address (COM 1)
- 4 ; Sample IRQ # to use (COM 1)
-
- Note that you MUST include the port address and IRQ if you are using
- non-standard comm port adddresses.
-
-
- NOTICE: Note the Feb. 1990 addition to the config file above - the addition of
- the location of PCBoard's "PWRD" file. This is a flag to update the
- PCBoard.sys file with the user's NEW time allowed after successfully
- completing a script. Leave this line EMPTY if the PCBoard.sys file is
- NOT to be updated.
-
-
- Sample 'Hard Coded' report:
-
- SYSOP ;User's Name in USERS file
- 415-967-3484 ;Phone Number
- 07-28-90 ;Today's date
- 08:43 ;Current time
- RONNIE L. PIERCE ;Name on Credit Card
- 810 -F VERNON CIRCLE ;Street Address
- MTN VIEW ;City
- CA ;State or Province
- 94043 ;Zip or Postal Code
- V ;First letter of Credit Card type (V,M,A,D)
- 4123456789012345 ;Credit Card Number
- 11/90 ;Card expiration date
- 1 ;Membership option #
-
- You MUST remember to make a seperate .cfg file for each node.
-
- 7. Make a batch file to run the door. If more than one node, ensure a batch
- file is made for each node.
-
- PCBoard Door Batch File for CCDOOR
- ----------------------------------
- c: ; CHDIR to directory where CCDOOR .EXE
- cd\pcb ; file is located
- CCDOOR ccd.cfg c:\pcb\pcboard.sys ; Command line to run CCDOOR
- cd\pcb ; CHDIR back to PCBoard home directory
- BOARD
-
-
-
- To run in local (command-line) mode, enter the command line as follows:
-
- CCDOOR ccd.cfg c:\pcb\pcboard.sys /L
-
- Replace "ccd.cfg" with the name of your actual .cfg file for the node's
- ccdoor.
- Notes
- -----
-
- o You may use text instead of a number for the membership options in the .cfg
- file. If a text string is used the expiration date updating for that
- membership option is effectively disabled and the "review" of answers will
- display the text entered instead of a # of months.
-
- Sample from my .cfg file:
- ---------------------------
- What is your Membership Option ( 1 = 1 Year/$95 2 = Usage/$$$.ΒΆΒΆ )
- 2
- 80, 12
- 60, Usage
- ----------------------------
- o Will be considering a routine to output the subscription information in
- a custom report format if anyone has ideas on this.
-
-
-
- Script File Info
- ----------------
-
- *** The Following Questions are "Hard-Coded" into CCDOOR ***
-
-
- (1) a$="Which credit card will you be using (Visa/MC/Discover/AMEX?)"
-
- ********************************************************************
- *** Above question is not exactly hard-coded. Sysop may select ***
- *** the cards he wishes to support. Only those will be displayed ***
- *** in the question to the user. ***
- ********************************************************************
-
- (2) a$="What is your FULL NAME as it appears on the credit card?"
-
- (3) a$="Street Address:"
-
- (4) a$= CUSTOM: "What is your city"
-
- (5) a$= CUSTOM: "What is your state or province"
-
- (6) a$= CUSTOM: "What is your zip or postal code"
-
- (7) a$="Credit Card number (xxxx-xxxx-xxxx-xxxx format)?"
-
- (8) a$="Please repeat the number for verification."
-
- (9) a$="Expiration date (mm/yy format)?"
-
-
-
- Edit your script file as required for pcboard. CCDOOR ONLY supports the @FIRST@
- macro. Look at the file "RON.SCR" to see how to begin the script.
-
- The script header may now contain up to 199 lines. A "More" prompt occurs
- after 22 lines are displayed.
-
- Note that in the script file, precede the question asking the telephone number
- with a "#" as done in "ron.scr". This Is necessary to perform the phone number
- verification. Also, precede the question asking if a user really wants to
- process the membership order with a "&". Again this is necessary for proper
- program operation.
-
-
-
- Software License Agreement
- --------------------------
-
- ** You are free to copy and distribute CCDOOR provided: **
-
- ** No fee is charged for use, copying or distribution **
-
- ** It is not modified in any way **
-
-
- Registration
- ------------
-
- ***************************************************************************
- **** Removes Encrypted "UNREGISTERED" shareware notice and displays ****
- **** your bbs name in its place! ****
- ***************************************************************************
-
- You should register this product if used for more than a 30 day "trial"
- period. Registration will get you free upgrades and make available to
- you any future door product or BBSware from FeatherNet and Ron Pierce.
-
- Registration fee: $30.00 for a single Bulletin Board System.
-
- Clubs and user groups may charge a nominal fee not to exceed ($5.00) for
- expenses and handling while distributing CCDoor.
-
-
-
- Credit Card Door v3.00 Licensing Agreement
-
-
- Date:________________
-
-
- From: _________________________________
-
- To: Ron Pierce, FeatherNet SoftWare
-
- Subj: Credit Card Door Software License Application
-
-
- I, _________________________________,
-
- hereby apply for a license to operate the Credit Card Door (CCDOOR).
-
- I understand the registration fee allows me to free upgrades for
-
- one year (Except for any Shipping/Download Costs).
-
- Further, I will have continuous use of the FeatherNet SUPPORT BBS
-
- for problems, questions, and for just staying in touch.
-
- Enclosed is my Registration fee.
-
-
- Note: Make check or money order payable ONLY in US Dollars.
-
-
-
-
- Signed: ___________________________________
-
-
- Enter your bbs name EXACTLY as you will place it in the configuration file.
-
-
-
- _________________________________________________
-
-
- Check appropriate Block
-
- [ ] $30.00 Initial Registration Fee and free BBS Support
-
-
-
- Mail registration to:
-
- Ron Pierce
- 2022 Wall St.
- Butte, MT. 59701
-
-
-
- Disclaimer
- ----------
-
- Your acceptance and use of this program implies that you accept FULL
- responsibility for any damage or loss to yourself, your property, and
- your dog - if you have one.
- Every effort has been made to ensure no dangerous bugs are in the
- program.
-
- I, Ron Pierce, hereby disclaim all warranties relating to this software,
- whether express or implied, including without limitation any implied
- warranties of merchantability or fitness for a particular purpose. I
- will not be liable for any special, incidental, consequential, indirect
- or similar damages due to loss of data or any other reason, even if I
- have been advised of the possibility of such damages. In no event
- shall MY liability for any damages ever exceed the price paid for the
- license to use this software, regardless of the form of the claim.
- The person using the software bears ALL RISK as to the quality and
- performance of the software.
-
-
-
-
-