                                                                    Page No. 1.

                        Sound Blaster Connection Network
                   North America Policies Document Release #2
                           Revised 27th January, 1993
                        (C) Copyright Rob Butler 1992,93


        Welcome to SBCNet!  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 up to date with how the rest of the network functions.  This file is
   layed out into a few specific sections, which are outlined below.

                1.0 - General requirements for all SBCNet members
                         .1 - Polling your HUB / HOSTs
                         .2 - ANSI / high ASCII in messages
                         .3 - Standard ZIP archiving method
                         .4 - Hatching of files into the net
                2.0 - Net Co-Ordinator duties
                3.0 - Region Co-Ordinator duties
                4.0 - Where to turn for help


1.0 - General requirements for all SBCNet members

        With that said, lets begin with the requirements of all SBCNet
    members.  To be considered a "full" member of SBCNet, you need to have
    the following three items : an SBCNet node number, your system must
    receive the Zone or Regional sysop echo, and you must receive and process
    the nodelist updates from your HUB / HOST.  That's it!  Whether or not
    you receive any other message or file echos for SBCNet is entirely up to
    you!

1.1 - Polling your HUB / HOSTs

        Generally, the traffic in SBCNet is moderate, on the order of 15
    to 30 messages per day.  Also, file traffic averages approximately 500k
    per week.  It is preferable that persons in HUB/HOST positions poll the
    level above them at least three times per week.  Individual nodes should
    also poll this often, however the actual frequency is set by your HUB/
    HOST, and if you have any questions you should contact them.

1.2 - ANSI / high ASCII in messages

        If you run a BBS program that allows you to post with ANSI colors
    and graphics in your message base, then you MUST disable this option for
    the SBCNet echos if you wish to have echomail access.  There are many
    comm programs and computer platforms that do not support ANSI, and having
    these codes in the message base can cause lockups of these systems.  In
    addition, two out of three times the message is turned into garbage by
    each systems' mail tossing program.

1.3 - Standard ZIP archiving method

        Currently, PKZip v1.10 is the prefered format for all files transfered
    through SBCNet.  This includes the use of PKZip v2.04c, as this version is
    known to create grunged archives, and cause other system problems.  <cont.>
    

-----------------------------  SBCNet Info File  -----------------------------
                                                                    Page No. 2.
1.3 - Standard ZIP archiving method <cont.>

    There are exceptions to this rule for mail tossers;  the use of other
    compression programs is perfectly acceptable, so long as all systems
    that you connect with are able to use the chosen format.  If you do use
    another archiving program for file transfer through SBCNet (which is
    discouraged) then please be sure that you use a format which is widely
    available to all users on several computer platforms.  Also, do not use
    beta versions of programs, as there may be unforseen problems.

1.4 - Hatching of files into the net

        If you desire to send files out through SBCNet, then there are a few
    guidelines to keep in mind.  First off, it is preferable that persons in
    the HOST position do the acutal hatching of files;  however, this is left
    to the discretion of the individual HOSTs.  This is done to be sure that
    files are hatched into the correct file areas with adequate descriptions,
    and that that they are in the prefered archive format.
        Secondly, it is strongly encouraged that no files older than 1 month
    (30 days) be hatched through the net, so that the larger members of
    SBCNet do not have large numbers of duplicate files coming in over the
    network.  Also, by having only the best, most recent files sent through
    SBCNet, it gives SBCNet an "eliteist" perspective that many other networks
    do not have.

2.0 - Net Co-Ordinator duties

        Net Co-ordinators have a few responsibilities to their area, first
    and formost being the routing of mail to and from the Region Co-Ordinator,
    and their individual nodes.
        NCs should assign node numbers to new nodes, and they should forward
    the applications for these nodes (as well as the updated nodelist net
    segment) to their RC.  Your nodelist net segment should be sent to your RC
    on Wednesdays for processing, and the segment should be named NET###.UPD.
    For instance, you could have NET100.UPD, NET425.UPD, etc.  In addition,
    when you forward application files to the RC, you should name them as
    NET_NODE.SBC giving you examples such as 100-6.SBC, 425-1.SBC, etc.
        Also, as an NC, you should have both AreaFix and Raid setup to process
    inbound area requests.

3.0 - Region Co-Ordinator duties

        Region Co-ordinators have many more responsibilities than do the NCs,
    and as such it is preferable that a RC have some prior experience as
    either a NC or a RC.  Below are outlined the jobs that an RC needs to
    perform.
        1) All RCs will route mail to and from the ZC, and to the individual
           NCs that they feed, UNLESS there is a Host for your geographic
           region - for instance, in Canada, all RCs should poll 13:5000/0
           (Karl Schmitz).  All RCs (unless you have a host for your area that
           you poll otherwise) will receive ALL mail and files from the ZC at
           13:13/0.
        2) All RCs are solely responsible for your region. If you receive new
           applications, you will forward node requests to the NC for the
           requester's area. If there is not yet an NC for that area, then you
           will assign new net numbers for that area.  If the applying node
           does not fall under your region, you should forward the application
           to the ZC.

-----------------------------  SBCNet Info File  -----------------------------
                                                                    Page No. 3.

        3) If you read through the nodelist, you will notice that each region
           has a block of 100 or so numbers that are set aside. When adding
           new NET numbers, use sequential order (ie, 101, 102, 103) for the
           new NETs.  Each NET should be named City_Net : for example, you
           could have Dallas_Net, Miami_Net, Albany_Net, etc.
        4) Please forward nodelist updates and applications to the ZC.  Fully
           configured versions of MakeNL are available to you if you require
           them so that nodelist processing will become totally automatic.
           Your region nodelist updates should be sent to the ZC as
           REG####.UPD, where #### is your region number.  New applications
           for node numbers should be named NET-NODE.SBC.
        5) It is prefered that RC's (and NC's) have both AreaFix and Raid
           setup so that nodes can add/delete areas without your direct
           intervention.  A configured copy of Raid is available should you
           need it.
        6) All RC's should carry all message and file echos, and at the very
           least read through the local regional and zone sysop echos on a
           regular basis for any news updates.

4.0 - Where to turn for help

      If you have any problems or questions, please contact your net or region
  co-ordinator, or me!

      Rob Butler, SBCNet Zone 13 Co-ordinator   FIDONet 1:124/3109
      The Music Connection                      SBCNet 13:13/0 13:1000/0
      (214)596-2827 for HST/v32 callers                13:100/0
      (214)964-3743 for 96/2400bd callers              

                                 or, if you wish

      Matthew Taylor, SBCNet Co-ordinator       FIDOnet 3:622/407
      Lake Macquarie BBS                        INTLnet 58:2200/105
      +61-49-562853                             SBCnet 15:4000/0
                                                EZYnet 80:1000/303
      
                                     --*--

    Sound Blaster/Sound Blaster Pro is a registered Trademark of Creative Labs.
    IBM PC is a registered Trademark of International Business Machines.
    FIDOnet is a registered Trademark of Tom Jennings.
    Sound Blaster Connection Network is a Trademark of Ultra Force.
