TRAM100.DOC

39.3 KB a4bc9aa51e3b2aa8…





























▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
▓▓▓▓▓▓▓▓ TagRAM v1.0  "Remote Autovalidation Manager" for TAG v2.6c1 ▓▓▓▓▓▓▓▓▓
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄

  Copyright(C) 1992,IBD Software - Written by Tony Mann & Bill VanWezenbeeck
                     Documentation Written by - Ray Bacon




























    ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******


                           TABLE OF CONTENTS


       Table of Contents . . . . . . . . . . . . . . . . .i
       Introduction. . . . . . . . . . . . . . . . . . . .ii
       TagRAM Support Sites. . . . . . . . . . . . . . . .iii
       Notes . . . . . . . . . . . . . . . . . . . . . . .iv
       Release Dates . . . . . . . . . . . . . . . . . . .v
       TagRAM Features . . . . . . . . . . . . . . . . . .vi
       Getting Started . . . . . . . . . . . . . . . . . .1
       Steps 1 & 2 & 3 . . . . . . . . . . . . . . . . . .1
       Remote AutoValidation Manager . . . . . . . . . . .2
       AutoValidation Manager Definitions. . . . . . . . .3
        Validation Key . . . . . . . . . . . . . . . . . .3
        Dial Attempts. . . . . . . . . . . . . . . . . . .3
        # of Phone Vals. . . . . . . . . . . . . . . . . .3
        Timeout Minutes. . . . . . . . . . . . . . . . . .3
        Send Beeps . . . . . . . . . . . . . . . . . . . .3
        BBS Rules (Download) . . . . . . . . . . . . . . .4
        Download Protocol. . . . . . . . . . . . . . . . .4
        Long Distance Calls. . . . . . . . . . . . . . . .4
        Sysop Comments . . . . . . . . . . . . . . . . . .4
        Hangups. . . . . . . . . . . . . . . . . . . . . .4
        User Aborts. . . . . . . . . . . . . . . . . . . .4
        Tramtrsh.fon . . . . . . . . . . . . . . . . . . .5
        Paths. . . . . . . . . . . . . . . . . . . . . . .5
        Modem Configuration Menu.. . . . . . . . . . . . .5  
        Modem Init-Strings. . . . . . . . .  . . . . . . .5
        Numeric Result Codes . . . . . . . . . . . . . . .6
        Opening Screen . . . . . . . . . . . . . . . . . .6
        Not Local Screen. . . . . . . . . . . . . . . . . .6
        Pre-Validate User. . . . . . . . . . . . . . . . .6
        Pre-Validate file format . . . . . . . . . . . . .7
        Post Validate Msg. . . . . . . . . . . . . . . . .7
        Already Validated Msg. . . . . . . . . . . . . . .7
        Pre-Down Rules Msg . . . . . . . . . . . . . . . .7
        BBS Rules File . . . . . . . . . . . . . . . . . .7
        Trashcan FON list. . . . . . . . . . . . . . . . .8
        TagRAM Logfile . . . . . . . . . . . . . . . . . .8
        Log Levels . . . . . . . . . . . . . . . . . . . .8
        Nuisance Calls . . . . . . . . . . . . . . . . . .8
       Long Distance Alert . . . . . . . . . . . . . . . .9
       Maketrsh.exe. . . . . . . . . . . . . . . . . . . .9
       TagRAM Maintenance . . . . . . . . . . . . . . . . .9
       Share & Multi Node. . . . . . . . . . . . . . . . .9
       911 or 000 Numbers. . . . . . . . . . . . . . . . .10
       Step 4. . . . . . . . . . . . . . . . . . . . . . .11
       TagRAM Batch file . . . . . . . . . . . . . . . . .11
       Step 5. . . . . . . . . . . . . . . . . . . . . . .12
       TRAMFON.LST . . . . . . . . . . . . . . . . . . . .12
       Step 6. . . . . . . . . . . . . . . . . . . . . . .12
       TAG Menu Command. . . . . . . . . . . . . . . . . .12
       Custom Screens. . . . . . . . . . . . . . . . . . .13
       Control T Codes . . . . . . . . . . . . . . . . . .14
       Control U Codes . . . . . . . . . . . . . . . . . .14
       Control S Codes . . . . . . . . . . . . . . . . . .15
       Sysop Function Keys . . . . . . . . . . . . . . . .15


                                        i


    ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******



                                  INTRODUCTION













     IBD Software would like to thank-you for choosing TagRAM as your on-line

     Auto-CallBack user validation editor.  TagRAM is the first fully

     configurable Auto-CallBack validator for TAG v2.6c.  At this time TagRAM

     will not work reliably on any Tag version prior to 2.6c.

     TagRAM is also the first written for low and high speed modems.

     To date TagRAM has been tested on US Robotics Dual Standard, US Robotics

     HST, MiCC Clarity 14400 Series FAX/Modem, the Old US Robotics HST,

     Everex EverComm 2400 Plus Internal, Hayes 9600 Smartmodem and the Hayes

     2400 Smartmodem.



























                                       ii

    ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******


                              TagRAM SUPPORT SITES

   Comments/Suggestions
   --------------------
   All comments or suggestions can be directed to 1 of 3 people.  
   Bill VanWezenbeeck or Tony Mann or Ray Bacon at the following locations.

   Bill VanWezenbeeck                   Tony Mann
   The BatModem BBS                     The Ice Palace BBS
   (713)876-0767                        (713)591-7939
   24hrs - 7days                        24hrs - 7days
   USR HST 14400 bps                    USR Dual Standard 14400 v.32bis
   FidoNet 1:106/1525                   FidoNet 1:106/821


   TagRAM Alpha Site                    TagRAM Documentation & Alpha Site
   -----------------------------------------------------------------
   CSI Online BBS                       Cobra BBS
   (409)321-3198                        (713)996-8762
   24hrs - 7days                        24hrs - 7days
   USR Dual Standard v.32bis            MiCC Clarity 14400/FAX v.32bis
   FidoNet 1:106/3198                   FidoNet 1:106/993
   SysOp: Gary & Lisa Jackson           SysOp:  Ray Bacon


   TagRAM Alpha Site                    TagRAM Beta Site
   ---------------------------------------------------------------
   The BayView BBS                      Joe's Bar & Grill
   (713)339-3221                        (713)674-4640
   24hrs - 7days                        24hrs - 7days
   USR Dual Standard v.32bis            USR Dual Standard v.32bis
   FidoNet 1:106/339                    FidoNet 1:106/777
   SysOp:  Russ Trahan                  SysOp:  Joe Harwell

   TagRAM Beta Site                     TagRAM Beta Site
   ---------------------------------------------------------------
   Humpy's Happy Hour                   Tek-Nique BBS
   (713)457-1189                        (713)473-7546
   24hrs - 7days                        24hrs - 7days
   USR Dual Standard v.32bis            Supra 57200 - 14400/FAX DS v.32bis
   FidoNet 1:106/7                      FidoNet - NO
   SysOp:  Humpy Harwell                SysOp:  Gary Harrison
   ---------------------------------------------------------------
   Griff's Tavern                       American Agenda
   (713)550-5999                        (713)568-3788
   24hrs - 7days                        24hrs - 7days
   USR Dual Standard v.32bis            14.4 v.32bis
   Fido Net 1:106/5999                  Fido Net 1:106/52
   Sysop:  Mike Griffin                 Sysop:  Robe Mode












                                       iii

 ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******



                                      NOTES

  Starting with this release of TagRAM Docs you will now find a pipe
  symbol (|) located to the left of the page at any point where a change
  has been made.





















































                                       iv

  ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******
  

  Thanks to the Authors and programmers of TAG we are able to release
  software such as TagRAM. The structure files that they generously
  offer to other programmers allow utilities such as this to exist.
  Many thanks need to go to "The TAG Team" for this utility.

  Release Dates:
  -------------
  Version 1.00a1 Wide BETA-First actual release (Not for general release)
  [ Compiled-09/08/92-Approx. 89% Complete ]

  Version 1.0a1 Wide BETA-First Completely Wide BETA-Will expire on 11/01/92
  [ Compiled-09/27/92-Approx. 95% complete ]

  Version 1.00 Standard - First Standard release 11/23/92
  [ Compiled - 11/23/92 100% complete] 

  Well, you know how it is, we always have to change something so
  maybe it should say 99.9% complete :)











































                                       v
  ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******


     Brief Summary of TagRAM Features
     --------------------------------
     ■ Multi-Node & Share Aware.
     ■ Multiple Validations per Phone Number - SysOp definable.
     ■ Inactivity timer - SysOp defines time period.
     ■ BBS Rules can be downloaded after validation - SysOp definable.
     ■ Available Protocol Engine - DSZ/GSZ - SysOp definable.
     ■ Phone Number can be changed before validation - SysOp defines.
     ■ Phone Translations Allow SysOp to easily Define Local/Metro Numbers.
     ■ Long Distance Validation - SysOp definable.
     ■ Multiple Dial attempts - SysOp definable.
     ■ SysOp Comment Updated - SysOp definable.
     ■ SysOp defines when/if a User is disconnected by TagRAM. eg. Bad Password.
     ■ SysOp defines the number of times a USER can abort TagRAM before Lockout.
     ■ Voice And/Or Data Number to Trashcan - SysOp definable.
     ■ Complete & Comprehensive Modem Control.
     ■ SysOp has complete control over TagRAM during Call Back Process.
     ■ All Screen's Can be personalized by SysOp with SDR and Special TagRAM    
       Codes.
     ■ All Screen's are definable by the SysOp in the TagRAM Configuration.
     ■ TAG Compatible trashcan's are created.
     ■ Definable Log levels.
     ■ SysOp defines length of delay before call back is initiated.
     ■ SysOp can define modem time out in seconds (30-120).
     ■ TagRAM will track nuisance calls/numbers - SysOp definable.
     ■ TagRAM will lower the SL on nuisance callers - SysOp definable.
     ■ Verbal and Numeric Modem result codes are supported.
     ■ Personalized Email to User - SysOp definable based on template files.
     ■ Prevalidation for VIP users - SysOp definable.
     ■ No Door files are required.
     ■ Validation Keys based on AGE - SysOp Defines KEYS and AGES.
     ■ Email can be sent to the SysOp alerting them of any long distance
       callers.





























                                       vi


  ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******


                               GETTING STARTED

  (STEP 1)

  Create a directory off of your BBS directory called TagRAM.

  The command is:  C:>CD BBS
                   C:\BBS>MD TagRAM

  (STEP 2)

  At this point you must un-compress the file TAGRAM.ZIP into
  the directory (TagRAM) that you just created.


  BIG NOTE:  DON'T FORGET: When you see  # (number symbol) replace with
                           the latest version number of TagRAM.

      EXAMPLE: TRAM100S.EXE

               New version is 100S

               The docs example say TRAM####.EXE, you would replace
               #### with 100S.
  You will see the # symbol used throughout the docs.  I use symbols so
  that I do not have to keep going back and searching for old version
  numbers.  I know, I can use search and replace but I just don't have
  the time to keep repeating the same function.


  (STEP 3)

  Now move to the TagRAM directory if you are not already there and
  load and run the program TRAMEDIT.EXE.

























                                        1

  ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******
  
  
  Listed below is an example of the screen that you will see.  Answer all
  of the prompts as they will apply to the TagRAM setup for your system.
  Remember that you may configure TagRAM to function as YOU want.

                        ********************************

   TagRAM v1.00 - "Remote AutoValidation Manager" - Configuration



  [A] Validation Key     :               [B] Dial Attempts      : 03
  [C] # of Phone Vals.   : 01            [D] Timeout Minutes    : 03
  [E] Send BEEPS [y/n]   : Yes           [F] Allow FON Change   : Yes
  [G] Rules are DL'able  : No            [H] Protocol GSZ/DSZ   : Disabled
  [I] Allow LD Calls     : No            [J] Add SysOp Comment  : Yes
  [K] Hangup on User     : Never         [L] # of User Abort    : 02
  [M] Add VOICE to Trash : Yes
  [N] Path to your BBS   : C:\BBS
  [O] Modem Init String  :
  [P] Opening Screen     : TRAMOPEN
  [Q] Not Local Screen   : NOTLOCAL
  [R] Pre-Validate MSG   : OKAY2VAL
  [S] Post-Validate MSG  : AFTERVAL
  [T] Already Val'd MSG  : TRASHFON
  [U] Pre-DL-Rules MSG   : Disabled
  [V] BBS Rules File     : Disabled
  [W] Trashcan FON List  : TRAMTRSH.FON
  [X] TagRAM Log File    : TagRAM.LOG
  [Y] Log Level to use   : 03 - Complete Logging [Debug]
  [Z] Nuisance Calls     :

  Make Changes - (A-X), [ESC]=Quit [?]




























                                        2

   ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******


                  "Remote AutoValidation Manager Explanations"


   [A] Validation Key

  TagRAM will allow you to use 1 to 3 validation levels.  When [A] Validation
  Key is selected you will see a new menu.  By setting the different prompts
  you may specify a validation key for ADULTS, KIDS, and Long Distance (I      
  recommend that you use the long distance validation with great care!).  You  
  may also set the age of the access for long distance validation.
  For any of the above features to work correctly insure that you have set the
  same validation keys in TAG.
 
  There is now an online HELP feature for the VALIDATION KEY menu.

   If the validation key that was specified does NOT exist TagRAM will abort   
   without attempting to validate the user.  You will be notified in your
   LOG file of this problem.

   NOTE:  See Page 48 of TAG 2.5g documents, this will explain how to setup your
          validation keys.

   [B] Dial Attempts

       Number of attempts (Times) that TagRAM will try to call the new user.

   [C] # of Phone Vals

       Maximum number of identical phone numbers allowed to be validated.  It is
       recommended that only ONE number be allowed.

   [D] Timeout Minutes

       Amount of time in minutes that TagRAM will sit idle before timing out and
       return to the BBS. (NOT ACTIVE IN TERMINAL MODE)

   [E] Send BEEPS [y/n]

       At different points throughout TagRAM it will send ALERT Beeps; an       

       example would be if you press the ESC key to abort the callback.

   [F] Allow FON changes

       By activating this command it will let your newuser CHANGE the phone     

       number that was listed in the NEWUSER questionnaire.  As many user have  

       two phone lines, one voice and one data, it is a good idea to allow this 

       option.








                                        3

   ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1******[G] 


   Rules are DL'able

   Your BBS rules will be downloaded to the new user immediately after
   validation.  Depending on which of the three options you choose.

   1. Yes    - User will be prompted if he/she would like to download the
               bbs rules.
   2. No     - Disable this function.
   3. Forced - User will go immediately to the protocol menu without being
               prompted.  He will be able to abort from that menu however. 
  
   [H] Protocol GSZ/DSZ

   You MUST tell TagRAM what protocol you are using, GSZ or DSZ.  It doesn't
   matter which one as TagRAM will look for the file that was listed in the
   setup.  TagRAM looks for your (GSZ/DSZ) in this order...

   First TagRAM checks your \bbs directory and if not found then checks your DOS
   PATH.

   [I] Allow LD Calls

       Setting this function to YES will tell TagRAM to make Long Distance      

       Calls.  If a Phone Number (After Translation) has a 1- on it then TagRAM 

       will only dial if toggled to TRUE.
 
   [J] Add Sysop Comment

       TagRAM will automatically add the users DATA/Validated phone number to   

       TAG's DATA phone field.  The SysOp can tell TagRAM to add or not add this
       information to the SysOp COMMENT Field.  If you choose to add the comment

       you will see the following information;

       TagRAM: ###-###-#### MM/DD/YR Hours:Minutes:Seconds

   [K] HangUp on User

       Will allow the SysOp to specify how to hang-up after validation.

          a.  Always hangs up on user
          b.  Never hangs up on user
          c.  Long Distance only - if a long distance call
          d.  Bad Password only
          e.  Long Distance or Bad Password

   [L] # of User Abort

       Number of times that the user may activate the door and abort out of the 
       door without completing the validation.  What TagRAM does is to count the
       number of times that the user says NO to the YES/NO prompt to continue
       with the validation process.





                                        4
 
  ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******
  

  [M] Add Voice to Trash

       Adds the users voice telephone number to TRAMTRSH.FON list.  By using
       this option TagRAM will help prevent multiple accounts by tracking
       both numbers that a user enters, (Voice and Data) numbers are listed
       in the TRAMTRSH.FON.

   [N] Path to your BBS

       This is your path to where TAG BBS files reside; i.e. C:\BBS

   [O] Modem Init String

       When you select [O] for the modem init string a new menu will appear.   


                        Modem Configuration Menu
       --------------------------------------------------------------
       [M]odem Recycle/Timeout          :60 Seconds
       [W]ait Time before Dial          :02 Seconds
       [N]umber of Hangup Attempts      :03 Attempts
       [I]nitialization String
       [P]re-Init String
       [H]angup String
       [B]usy String
       [D]ial String
       [V]iew Modem Strings
       [ESC] Return to Main Menu

   Due to the many different types of modems on the market today I am not
   going to try and give you an init string for your modem type.
   I have included a standard init string that works for my modem.
   At a later date TagRAM will have several setups for more common modem
   types on the market.
   Check your modem documentation for the configuration that works best
   for you.

    The Sysop may also control the initialization string sent to the modem.
  
    The following characters maybe used for that purpose:
  
      ^+ (DTR HIGH)
      ^- (DTR LOW)
      ~  (Pause 1/2 of a second)
      `  (Pause 1/20 of a second)
      '  (Pause 1/10 of a second)
      |  (Carriage Return)
      ^M (Carriage Return)
  
    Sample modem init string:
  
      ^-~~~^+~~ATX7M1&C1&D2S0=0H0|
  
                      OR
  
      ^-~~~^+~~ATX7M1&C1&D2S0=0H0^M
  
      ATX7M1%C1&D2S0=0H0^M <--- Most modems will NOT require the ^-~ or ^+~


                                        5


  ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******


  We now look for "Numeric" results from the modem as well as "Verbal". In
  the following list is what we look for and the response, please let us
  know if this is against the standards of your modem. We are pretty sure
  that these are "Standards" but we are not POSITIVE:

  ATV0 on most modems will set "Numeric" results.
  ATV1 on most modems will set "Verbal " results.

    Numeric Result       TagRAM "Verbal" Translation
    ---------------------------------------------------------------------
         0               OK
         1               CONNECT
         2               RING
         3               NO CARRIER
         4               ERROR
         5               CONNECT
         6               NO DIALTONE
         7               BUSY
         8               NO ANSWER
         9               <Reserved> Not Allowed by ANY know modems.
        10               CONNECT
        11               RINGING
        12               VOICE
        13               CONNECT
        18               CONNECT
        20               CONNECT
        21               CONNECT
        25               CONNECT

   [P] Opening Screen

       The Name of the file for your opening screen to TagRAM.

   [Q] Not Local Screen

       The Name of the file if the caller is not a local call.

   [R] Pre-Validate MSG

       Name of the file if the user is pre-validated.

       Another option for validating a KNOWN USER is:
    
        This will allow SysOps of TagRAM to Pre-Validate users.
        Lets say that you just got off the phone with a friend and he
        wants to log onto your BBS when he gets home but you are ready to
        leave for work. No problem validating him at whatever level you
        want.  Just add his phone number, name and the validation key
        that you want his account validated under and TagRAM will do
        the rest.  Once he calls and uses TagRAM to validate his account,
        it will find him in this file and automatically validate his
        account without dialing the phone.  He/She will be back on the BBS
        in a matter of seconds with thier NEW access... Once the account
        is pre-validated a * will be placed in front of that entry to let
        you know that it was processed.

        Modify the file called:  PRE_VAL.LST 


                                        6
   

  ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******




        Listed below is an example of the file format to use.

        Note: Each entry must be added on a separate line.


              Example:
              AREA CODE-PREFIX-SUFIX Users Name Key=V
                                 ^     ^    ^       ^
                                 |     |    |       |
                User FULL phone #|     |    |       |
                                       |    |       |
                       Users First Name|    |       |
                                            |       |
                             Users Last Name|       |
                                                    |
                           The Validation KEY to use|

    |********************************************************
    |* Here is an Example:
    |
    |* 713-123-4567 Gary Harrison KEY=V
    |
    |********************************************************



  To go along with the PRE_VAL.LST we have added the following Screens. If
  a user is Pre-validated the following screen will be displayed:

   PREVALED.MSG <-- Non ANSI users.
   PREVALED.CLR <-- ANSI users.

  If these files are not found then TagRAM will display nothing to the user
  after Pre-Validation.

   [S] Post-Validate MSG

       Name of the file sent to the user after successfully being validated.

   [T] Already Val'd MSG

       Name of the file sent to the user if his/her phone number has already
       been validated.

   [U] Pre-DL-Rules MSG

       Name of the file displayed to the user just prior to prompting them to
       download the BBS rules.  This file will only be displayed if the [G] is
       toggled to YES.

   [V] BBS Rules File

       The name of the file UPLOADED to the user if [G] is toggled to YES.


                                        7


   ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******



   [W] Trashcan FON List

       Name of the file where VALIDATED phone numbers are to be stored.  TagRAM
       scans this file to see if the users phone number has already been

       validated.

   [X] TagRAM Logfile

       TagRAMs activity log file, your SysOp.log will work just as well if you
       so choose.

   [Y] Log Level to use

       Depending on which option you choose, it will determine weather you have
       either a short activity log file or a large extensive log file showing
       everything that transpired while the door was in use.
       If you select the large log level ( I recommend this option on initial   

       setup of TagRAM) you have a complete session log to use for DeBugging    

       TagRAM.  Should you have a problem and refer to anyone of the TagRAM
       Alpha, Beta or Author sites we will ask for the information found in the
       TRAM####.LOG file.

   [Z] Nuisance Calls

       Nuisance calls are defined as those users that TagRAM is not able to
       successfully establish a reconnection.  Nuisance calls will be tracked as

       number or non-successful callback sessions within TagRAM.
       For each unsuccessful session TagRAM will write the users name and phone
       number to the nuisance.lst file.  Further help may be found within
       TagRAMs Tramedit utility.


  TagRAM now supports EMAIL that can be sent to a user based on several        
  factors.

   1> The user is NOT a local call (NOTLOCAL.TPL)
   2> The users phone number was already validated (TRAMTRSH.TPL)
   3> The user was successfully validated (VALDUSER.TPL)

     The .TPL files need to be located in your TagRAM directory and need
     to be ASCII text file which TagRAM will convert to the message.
     ALL imbedded ^P,^S and ^T codes are valid within these files. Have fun!












                                        8


    ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******


    LD_ALERT.TPL

    Email is now sent to the Sysop when a "Long Distance" caller attempts to
    validate but LD validation is "OFF".

    This feature is Enabled/Disabled via a .TPL file, if the file exists then
    TagRAM will send the message otherwise this feature will be considered as
    "Disabled".  Included is sample LD_ALERT.TPL file with this version.
    Using this feature will allow you to be alerted as to the presence of an
    "Un Validated" long distance user on your BBS so that you can take the
    needed action(s).

    MAKETRSH.EXE

    Included with TagRAM is a new program called MAKETRSH.EXE.  MAKETRSH
    will create a NEW TRASHCAN.FON list of all validated users from TAG'S
    USER.LST.  This feature will help the Sysop keep validated users from
    logging on multiple times as a new user when first setting up TagRAM.

    To use this program correctly you must first have run TRAMEDIT.EXE.

    It is not required that MAKETRSH.EXE is run but it is useful.

    TagRAM Maintenance:

    Added the /M - Maintenance Procedures to update your TRAMTRSH.FON file or
    whatever you named it. Here is a quick rundown on how to use this feature:

     Go to your \TagRAM directory and at the PROMPT enter the following:

     C:\BBS\TagRAM>Tram#### /m

     This will start the maintenance which will allow you to remove ALL users
     from the TRAMTRSH.FON file that you have DELETED from your USER.LST.
     This will allow those users to re-validate under NEW accounts without
     a problem.


                          Share & Multi-Node Detection


   TagRAM is Share Aware, if you have Share Loaded we will use it, if
   not, then we will use the standard DOS file modes.  Also if you are
   running TAG in Multi-Node, we will look in both, the \(D)(G)FILES and
   \MULTI directories for the needed TAG files such as the USER.LST,
   the VALIDATE.DAT, Etc.













                                        9


   ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******



                        What about 911 or 000 Numbers???


   Because it is unlikely that you want your BBS dialing numbers like 911 or
   000 you will want to edit the file TRAM_BAD.FON and be sure that it has
   ALL the numbers that you don't want to allow. The defaults cover just
   about ALL the common ones but you may want to add your BBS and VOICE phone
   numbers to it... Please DO NOT confuse this file with the TRASHCAN file
   that TagRAM adds the number to as users are validated. The two files have
   little in common.

   Note: This file MUST be named TRAM_BAD.FON and it MUST reside in the
         directory that TagRAM was executed from. An Example file is included
         with this archive so there in no need to create one, simply edit
         the one that is here.



































                                       10


    ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******


   (STEP 4)

   At this point it is now time to create the batch file that will run TagRAM.
   Listed below is an example of what your batch file should look like.
   TagRAM.BAT must be placed in your BBS directory or insure that your DOS
   path is set to correctly run batch files from a common directory.
   For instance I run ALL of my TAG batch files and TAG utilities from two
   separate directories.  Here is an example of what your path could look like;

   PATH=C:\;D:\;E:\;E:\BBS;E:\BBSBATS;E:\BBSUTIL

   By adding a correct path statement to your autoexec.bat file you will be able
   separate many of your files into their own directories thus making it easier
   to find and keep from cluttering up your BBS directory.

    TagRAM.BAT
   --------------
   @Echo Off
   C:
   Cd\bbs\tagram
   TRAM#### %1 %2 %3 %6 1
   Cd\bbs              / \
   --------------       |________________________________
                                                         |
   NOTE:  For Comports other than 1, change the last parameter accordingly.

   NOTE:  TRAM#### - Insure that where ## appears in the docs you change to
                     reflect the CURRENT version number of TagRAM.

   NEWLOGON.BAT
 
   You may also setup Tag NEWLOGON.BAT file to automatically take a new user
   directly into TagRAM.  The format of the the batch is shown below.
 
    @ECHO OFF
    C:
    CD\BBS\TagRAM
    TRAM#### %1 %2 %3 %6 %7
    CD\BBS




















                                       11

    ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******


   (STEP 5)

    Edit the TRAMFON.LST to include ALL numbers that you want to allow
    TagRAM to be able to dial.  This file works a little different than
    from what you may be used to, so I will explain a little about how
    TagRAM uses TRAMFON.LST.  TagRAM will read each line and with the
    information that you provide, do a translation of that phone number
    against the one that the users will be called back at, here is an
    example which will help me explain things better.  The ASCII listing
    will look like this:

        1-713- /
        1-409-321- / 409-321-
        1-713- / 713-

    The first line tells TagRAM if a phone number starts with 1-713- then
    strip off that number and replace it with nothing, as a result, TagRAM will
    dial ###-#### instead of 1-713-###-#### this is VERY useful as I will
    show you in the 2nd example.

    In my area there are some numbers where you MUST dial the "Area Code"
    but not the "1", so the only way that TagRAM will allow this type of
    situation is to do the translation.  Lets say that a user calls my
    board and wants to auto-validate at the number, 1-409-321-6785,
    (This is a local call to me but if I dial without including the 409
    area code, the call will NOT go through) now TagRAM takes that number
    and translates it to 409-321-6785 which can be called with no problems,
    (and it is a local call, not long distance).  As the problem with the
    409-321-#### in my area the SysOps in the 409 area code have a problem
    allowing users to validate from the 713 area code, no problem, the 3rd
    line takes care of them by replacing 1-713- with 713-

    In most cases you will only need to include your area code but we wanted
    things as flexible as possible. If you are not sure what to include in
    this file, then just put your area code and let ALL others be excluded
    from callbacks. (YAC = Your Area Code), you MUST include the / as the
    separator or TagRAM will not attempt to translate that line.

    1-YAC- /

    (STEP 6)

    Now create a Menu Command in TAG to allow the users to "Auto-validate"
    their phone number. This will leave you more time to tend to better
    things. An example command might be:

    Item #   : ???
    Long Desc: (/T)agRAM Autovalidation Utility
    ShrtDesc : (/T)agRAM Validator
    Key      : /T
    AR Flag  : N    <--- This is for example ONLY, I use N for New Users.
    Slevel   : 10
    Pkey     : <
    Pdata    : *TagRAM
    Flags    : Whatever you want, but be sure that new users have access.


    NOTE:  For further explanation and information on how to create a menu
           command, please refer to TAG version 2.5g MENU documentation
           on PAGE 6.
                                       12

    ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******



                         Creating and Using Custom Screens


   TagRAM will allow the SysOp to define screens that will be displayed
   depending on various situations.  You can create *.MSG or *.CLR and
   the appropriate screen, depending on the users COLOR setting, will be
   used automatically.  If a user has COLOR but no .CLR file exists,
   the .MSG file will be displayed.  If neither exist, then nothing is
   displayed to the user.  The COLOR Screens should be Un-Animated and
   saved to 255 lines.  TagRAM also allows the imbedding of control codes
   into your ASCII screens just as you do in TAG files.  See page 99 of
   the TAG documentation for the codes.

   The files are defined in TRAMEDIT, run the TRAMEDIT.EXE and you will
   see what I mean.


   Imbedding Information within your Screens
   -----------------------------------------
   TagRAM allows the SysOp to utilize the same "Control Codes" as in TAG.
   The only ones that are specific to TagRAM are:






































                                       13

    ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******



     -----------------------------------------------------------
    Control T Codes   (Specific to TagRAM - Not used within TAG):
     -----------------------------------------------------------

     ^TT=Will insert the users name from any MATCH in the TRAMTRSH.FON
         listing.  This will allow you to tell a user WHO validated the
         phone number that they are currently unable to validate.

     ^TV=The Phone Number that the user either validated at or attempted to
         validate at. This is useful in the NOTLOCAL.* and the TRASHFON.*
         files.

     ^TP=The password the user enters when they return. ALL incorrect
         passwords are also written to your log file.
   
     ^TA=This will display the users age.
   
     -----------------------------------------------------------
     Control U Codes (Same as in TAG - Page 99 of the TAG Docs):
     -----------------------------------------------------------
     ^UA=Users Address
     ^UB=Users Highest Baud
     ^UC=Users City, State
     ^UD=Users DSL
     ^UE=Users SF-Flags                                [Not Available]
     ^UF=Users AR-Flags                                [Not Available]
     ^UG=Users Birthday                                [Not Available]
     ^UH=Users Help Level
     ^UI=Users Last Download Base
     ^UJ=Users Name (Handle)
     ^UK=SysOps Comment on the User
     ^UL=Last  on Time/Date                            [Not Available]
     ^UM=Users Mailbox Status                          [Not Available]
     ^UP=Users Phone Number
     ^UR=Users REAL Name
     ^US=Users SL
     ^UT=Users Computer Type
     ^UU=Users First Name
     ^UX=Users Screen Size - Rows/Columns              [Not Available]
     ^UY=Message Base SubOp                            [Not Available]
     ^UZ=Users ZipCode
     ^U1=Users Total Number of DOWNLOADS
     ^U2=Users Download Kbytes
     ^U3=Users Total Number of UPLOADS
     ^U4=Users Upload Kbytes
     ^U5=Users Number of Calls to the BBS
     ^U6=Users Total time on the BBS                   [Not Available]
     ^U7=Users Number of calls for TODAY
     ^U8=Users time on the BBS for TODAY
     ^U#=Users Number in the USER.LST
     ^U$=Users Credits and Debits as in the USER.LST   [Not Available]
     ^U^=Users File Points
     ^U@=Users Time Bank Stats                         [Not Available]






                                       14

    ****** TagRAM v1.00 "Remote AutoValidation Manager" for Tag v2.6c1 ******


    -----------------------------------------------------------
    Control S Codes (Same as in TAG - Page 99 of the TAG Docs):
    -----------------------------------------------------------
    ^SA=The Path to your Alternate Text Directory (\Afiles)
    ^SB=Your BBS Name
    ^SC=The Last Caller to the BBS
    ^SD=Last Date                                     [Not Available]
    ^SE=Number of BBS Error for the Day
    ^SG=Path to your Data Files Directory (\Dfiles or \Gfiles)
    ^SH=The Number of Calls to the BBS for Today...
    ^SM=Path to your Messages                         [Not Available]
    ^SN=Caller Number
    ^SP=The BBS Phone Number
    ^SS=SysOp Name (Your Name)
    ^SU=The Path to your Multi-User Directory (\Multi)
    ^SX=Total Number of users on your BBS (Deleted User are NOT Counted)
    ^SZ=Your Chat Password                            [Not Available]
    ^S1=Maximum Batch Downloads (Batch Queue)
    ^S2=Maximum Batch Uploads   (Batch Queue)
    ^S3=Total Kbytes UPLOADED to the BBS for Today
    ^S4=Total Kbytes DOWNLOADED from the BBS for Today
    ^S5=Number of calls to the BBS for Today
    ^S6=Total Number of Messages Post for Today
    ^S7=Total Email sent for Today
    ^S8=Total FEEDBACK sent for Today
    ^S9=Total Number of UPLOADS to the BBS for Today
    ^S0=Total Number of DOWNLOADS from the BBS for Today
    ^S#=Your Node Number (0:0/0.0 if you have none)    [Not Available]
    -----------------------------------------------------------


                        SYSOP TERMINAL MODE FUNCTION KEYS



   [F1] = Recycle the Modem - Re-Dial without increasing the attempts.
   [F2] = Add 5 minutes to the users time online.
   [F3] = Subtract 5 minutes from the users time online.
   [F7] = Subtract 1 Dialing Attempt.
   [F8] = Add 1 Dialing Attempt.
   [ESC]= Abort TagRAM terminal and return to the BBS.



















                                       15