
                    Authorized Gravis Node Policy Document
                          Revised August 12th, 1993


        There are a few basic tidbits of information that we wish to
   lay out for you here - nothing fancy, just some tips to keep you
   rolling along.

                1.0 - General requirements for all Gravis Nodes
                2.0 - Your BBS Information
                3.0 - Where to turn for help


1.0 - Requirements for all Gravis Nodes

                  1.1 - Polling Gravis
                  1.2 - ANSI / high ASCII in messages
                  1.3 - Standard ZIP archiving method
                  1.4 - Hatching of files into the net

      To be called an 'Authorized Gravis Node' you will need the following:

             A valid Fidonet or SBCNET node number
             Carry all Gravis file and message areas available to
              you.  Refer to GRAVECHO.TXT for a current list.
              Note that there are 4 extra areas when using your
              FidoNET node number.
             Allow new users access to the Gravis message and file
              areas on your BBS on there first call.
             Be approved by Advanced Gravis

1.1 - Polling for Gravis Mail and Files.

        As of July '93 traffic has averaged 200K/week of mail and
    1Mb/week for files.  However, if there is a major update you
    can expect the traffic to be higher.  All nodes will be required
    to POLL their host AT LEAST once per week.  All trafic is monitored
    and if it appears that a node is lagging behind they will be warned.
    You get two warnings.  On your third you will loose your Authorized
    Node status.

1.2 - ANSI / high ASCII in messages

        You must disable high bit ASCII and ANSI color codes from all your
    out going mail.  There are many communications programs and computer
    platforms that do not support ANSI, and having these codes in the
    message base can cause lockups of these systems.

1.3 - Standard ZIP archiving method

        Currently, PKZip v1.10 is the preferred format for all files and
    message bundles transferred through Gravis.  True, PKZIP v2.x gives
    better compression but V1.10 is still the standard.

1.4 - Hatching of files into the net

        It is strongly recommended that you hatch only NEW files that
    directly relate to Gravis products. We want to try and keep the
    amount of traffic at a reasonable rate.  Not everyone can afford
    $100 phone bills.

        I keep pretty much up to date on any new Gravis related files
    out there so be carefull when hatching. Make sure that the file
    has not already been hatched.

2.0 - Your BBS Information

         We will be compiling a list of all Graivs Nodes.  Including phone
    number, themes, baud rates, locations etc...  This information will
    be made available via the net and also in all future Gravis
    software products.  This information will usually contained in the
    README file or a file called GRAVNODE.TXT.

3.0 - Where to turn for help

      You may reach me, John Smith, at any of the following addresses:

       Advanced Gravis                     Tel (604) 431-5020
       3750 North Fraser Way, #101         Fax (604) 451-9358
       Burnaby, BC, Canada                 BBS (604) 431-5927 V32bis
       V5J 5E9

       Compuserve: 71333,350   SBCNET: 13:900/3
       FidoNET: 1:153/978      InterNET EMAIL: john.smith@gravis.com

I would like to thank Rob Butler (1:124/3109) of SBCNET for letting
me use some of the information contained in SBC-KIT.ZIP.

