Appendices
==============================================================================

  Point Support
  ~~~~~~~~~~~~~
    A point can be best described as a extension to a node.  In fact, the
    node acts as a hub to the point.  Look at the following illustration to
    get a better picture as to what is going on:

       +-------+        +------+ ----> Point
       | Net   |        | Node |
       | Hub   | -----> |      | ----> Point
       +-------+        +------+
           |
           +----------> +------+
                        | Node |
                        |      |
                        +------+

    Not every node will have points.  It all depends on if you want to share
    your Fido information with another system down from you on the
    hierarchical structure.

    The main point to realize in regards to a point system is that you will
    not be listed in any nodelists.  This means it is not possible to send
    netmail directly to a point site.

    The addressing for a point is different from that of other sites.  For the
    sake of example, let's assume you desire to be a point under our support
    BBS (1:311/40).  Basically what happens is that you simply add a
"point"
    or period followed by the point number.  Since we do not have points
    underneath us, you would become the first or 1:311/40.1.

  Working With a Satellite Feed
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Some services offer satellite delivery of Fido echo areas and netmail.
    This method of delivery cuts down on costs when carrying a full-feed or
    when you are a great distance from a hub.

    How does PCBoard import the messages if it never makes the call?  To
    add mail to your system, PCBoard will simply scan the inbound packet
    directory (PCBSetup | Fido Configuration | File and Directory
    Configuration).

    All you must do is get the packets from the satellite to the inbound
    packets directory and let PCBoard import them.  A good method for
    importing is either to use the /IMPORT command line switch or to
    periodically scan the inbound directory every x minutes with the
    setting in PCBSetup | Fido Configuration | Fido Configuration.

    Because satellites offer just the delivery of messages, you must make
    arrangements to send new messages from your system to a hub (most likely
    chosen by the satellite service provider).  Making this type of setup
    requires:

      1)  Make a user record for the outbound site.
      2)  Add RS conference flags for every area you send to the outbound
          site.  Otherwise, new mail will not be packetized for export.

  Fido User Records
  ~~~~~~~~~~~~~~~~~
    With any site you regularly exchange netmail or echo mail with, you'll
    need to setup a user record for each site.  Why must a user record be
    setup?

       1.  All password information for sessions, packets, and AreaFixing
           are stored in this user record.

       2.  Information about the echo areas you carry and allow others to
           carry (if acting as a hub) are extracted from the user record.

    To add a Fido user record, follow these steps:

       1.  Load System Manager and edit the user records by selecting User
           File Maintenance followed by Edit User Records.

       2.  Press ALT-A to add a new user record.

       3.  In the "Name" field, enter "~FIDO~" followed
by the address of
           the net coordinator.  To create an account for the Fido node
           1:311/0, enter the following:

             ~FIDO~1:311/0

       4.  Press F3 to view the Fido Form of the user record.  The screen
           resembles the following:

                                   Edit User Record (Fido Form)

             Name        : ~FIDO~1:311/0

             Passwords
             Session        :
             AreaFix        :
             Packet         :
             Phone Override :
             Security Level : 0
             Delete User    : N

       5.  Fill in the apporpriate passwords for the system.  If unknown,
           leave them blank.

       6.  Press F2 twice to get to the conference view.  Here we must mark
           those conferences that will be exchanging mail.  This differs
           depnding on if you are acting as a node or a hub.

           Nodes should put RS in each conference they will be exchanging.
           Hubs have a little more control in that they put an R to denote
           a site can access the conference and S to signify that they
           are carrying a conference.

           As far as a hub is conferenced, the following choice exist for
           conference registration:

               - Site cannot access the conference
              R       - Site CAN access conference but is electing not to.
              RS      - Site is carrying the conference feed.

       7.  A helpful hint in setting up Fido user records is to setup all
           Fido accounts using the same security level.  This way, you can
           capitalize on the global conference changes available within
           System Manager.

       8.  Save the changes by pressing ESC and chosing to save changes and
           you are ready to go.

  FidoNet Terminology
  ~~~~~~~~~~~~~~~~~~~
    AKA:  Refers to lso nown s.  Anytime your
site is known by more
          than one address, the additional addresses are called AKAs.

    AREAFIX:  A process where, as a site, your configuration for the host
              can be modified.  The type of things which can be modified are
              what echo mail areas can be modified, etc.

    CRASH:  Refers to sending immediately regardless of how your events are
            configured.  In the case of an event, this term has PCBoard send
            any crash mail to the nodes listed in the parameter list.

    ECHO-MAIL:  The majority of mail sent in Fido is termed echo-mail.  Each
                of the hundreds of conferences or areas send this publicly
                readable mail.

    FREQ:  Refers to ile uest.  A Fido node can request
a file from
           any other Fido node.  If the destination site/node has the file
           available, it will be transferred during that call.

    MAGIC NAMES:  In regards to FREQing a file, the name may not be known or
                  multiple files may be involved.  In a situation like this,
                  the site may have setup a magic name which will get the
                  appropriate file or set of files.

    NET-MAIL:  Netmail is a way to send private mail between users on two
               different nodes/sites.  Mail must include the users name and
               the node address.

    NODELIST:  The source file containing all information about nodes
               involved on the network.  Information includes phone numbers,
               SysOp name, name of the site, maximum speed, etc.

    POLL:  Call another site and request any waiting mail.

    ROUTE:  Refers to instructions on how mail will be sent.  Mail can be
            routed or sent to another node.

--- PCBoard (R) v15.3/M 10