File & Directory Configuration
  ------------------------------
      The Fido configuration needs the locations of several paths defined.
      On this screen you will be entering the paths you want for incoming
      packets, bad packets, etc.  Each directory location is described in
      detail in the following sections:

    Dir of Incoming Packets
    ~~~~~~~~~~~~~~~~~~~~~~~
      This field refers to the location where incoming mail packets are
      stored.  Realizing that incoming packets can be large in size,
      specifying a drive with plenty of free space.

    Dir of Outgoing Packets
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~
      Enter the subdirectory where compressed outgoing packets will be
      stored before being sent out.

    Dir to store Bad Packets
    ~~~~~~~~~~~~~~~~~~~~~~~~
      In this field, enter the subdirectory where bad incoming packets will
      be stored.  A packet is considered to be bad when any of the following
      occur:

        * Invalid password in the packet file
        * File based errors such as unable to read the file from disk

    Dir of Nodelist Database
    ~~~~~~~~~~~~~~~~~~~~~~~~
      The compiled nodelist database is essential to Fido especially when
      dialing out.  This field points to the directory where your nodelist
      file is stored.  The location of the nodelist file to compile is
      located in PCBSetup | Fido Configuration | Nodelist Configuration.

    Work Directory
    ~~~~~~~~~~~~~~
      While processing mail packets temporary files will need to be created.
      In this field, enter the subdirectory where these temporary files will
      be stored.  Remember, the drive where this is located must have plenty
      of free space available.

      An ideal location to specify is one that is local to the node
      processing mail.  This helps cut down on network traffic and therefore
      increases the performance.

    Dir to store *.MSG
    ~~~~~~~~~~~~~~~~~~
      A popular standard for messages in FidoNet is known as *.MSG
      (star-dot-MSG).  Using the /MSG switch for the PCBFIDO environment
      variable, you can have PCBoard keep a mirror image of all netmail
      messages in MSG format.  Additionally, you may place .MSG files in
      this subdirectory to be imported into the netmail message base.  The
      use of MSG files are particularly useful for third party applications
      and integrating them with your use of PCBoard.

  Archiver Configuration
  ----------------------
      The Fido implementation in PCBoard supports four types of compressed
      packets:  1) PKZIP, 2) ARJ, 3) ARC, and 4) LHA/LZH. This particular
      screen is where the various compression programs are configured.  For
      each archiver the program name for compressing and decompressing must
      be specified.  Additionally, any necessary switches must be specified.
      The following shows a sample of what may be entered:

  Phone Number Translation
  ------------------------
      The Fido network spans many countries across the globe and relies on
      being able to call one node from another. Phone numbers for each site
      are obtained by searching the nodelist database.  Each entry in the
      nodelist contains the FULL contact number for each site.  For example,
      the phone number for a site in the United States may resemble this
      entry:

        1-352-555-1212

      Why would any type of phone number translation have to be done if the
      full phone number is there?  The quick answer is that many nodes call
      one another within a local calling area. Using the previous example
      number, we could say the following two phone numbers exchange mail:

        1-352-555-5555
        1-352-555-1212

      When the first site calls the second, it needs to be able to strip off
      the 1-352- because that is used only for long-distance calling.

      Creating the translation is very easy.  On this screen are two
      columns.  The first is the information to search for in a phone number
      and the second column lists the replacement information.  If nothing
      is entered in the Change To column, the matching information will be
      stripped.  The following entry shows how the 1-352- can be stripped.

            Find                    Change To
          ---------                 -----------------------
       1) 1-352-

    International Calling
    ~~~~~~~~~~~~~~~~~~~~~
      If the setup of the network requires international calls to be made,
      you must enter two entries in the translation list defining your
      country information.  These entries will look like the following if
      you live in the United States:

            Find                    Change To
          ---------                 -----------------------
       1) IP                        011
       2) IPX                       1-

      The first entry, IP, defines the international prefix.  In other
      words, international calls made from the United States must begin with
      011 followed by the country code, and other appropriate phone numbers.
      If unsure about the international prefix, contact your local phone
      service provider for additional information.

      The second entry, IPX, defines the country code.  The United States
      country code is 1.  Most phone service providers make this information
      available.  If in doubt, contact them for additional details.

    Prefixes and Suffixes
    ~~~~~~~~~~~~~~~~~~~~~
      Your situation may require the use of prefixes (numbers to dial before
      every phone number) and suffixes (numbers to dial AFTER every phone
      number).

      A classic example of this in the United States comes into play if you
      have call-waiting.  It is possible to disable call-waiting by dialing
      *70, before every phone number.  Another example for prefixing is in a
      business situation where a 9 must be entered before every outgoing
      phone call.

      Suffixes are not typically used as much but are still quite useful.
      For example, some long-distance carriers allow you to require a
      password or special code on every long-distance call.  This code is
      entered after the phone number--a perfect use of the suffix.  Prefixes
      are defined by entering GP in the Find field.  In the Change To field,
      enter the number(s) to add before every phone number.  Suffixes are
      done in much the same manner.  In the Find field, enter GS followed by
      the suffix to add in the Change To field.  As you may have guessed by
      now, GP stands for Global Prefix and GS stands for Global Suffix.

      Examples:

              Find                                  Change To
            ---------                               -----------
         1) GP                                      *70,
         2) GS                                      ,,1994

      The first example shows a prefix defined as *70, and the second shows
      a suffix defined of ,,1994.  The commas are used in modem dial strings
      to define a 2 second pause.

  Nodelist configuration
  ----------------------

      On this screen, you tell PCBoard where the nodelist file is stored.
      The nodelist compiler will use this information when compiling the
      nodelist.  There is no limit to the number of nodelists you can have.
      Each file will be appended into the database until there are no more
      lists to compile.

    Diff Filenames
    ~~~~~~~~~~~~~~
      A Diff (DIF) file is used to update existing nodelist.  If you are
      participating in the worldwide Fido network, you have seen how the
      full nodelist can be several megabytes in size.  To prevent members of
      the network from having to transfer such a large file each time,
      updates or DIF files are usually available from the same location
      where you can find a nodelist.

      The nodelist compiler will properly update the local nodelist database
      using the information stored in these DIF files.  To be properly
      updated, the DIF file must be in the same directory as the nodelist.
      Just the base filename of the DIF file needs to be entered on the
      screen as the extension simply refers to the revision of the file.

      To help explain the relationship between the nodelist
      and the DIF files, look at the following entry:

           Nodelist Path (No Extension)         Diff Filename
           ----------------------------         -------------
        1) C:\PCB\FIDO\NODELIST                  NODEDIF

      Here is what will happen:

        * Begin by compiling just the nodelist file

        * As time passes, DIF files will be distributed by your network.
          Pick up the DIF files, uncompress them to the same directory where
          the nodelist file listed in column one is.

        * Recompile the nodelist database with the compiler using the /DIFF
          switch.

      NOTE:  All filenames listed on this screen refer to the uncompressed
      filenames.  You must uncompress the files manually before attempting
      to compile the nodelist database. Compression types range from system
      to system.  Ask if you are unsure about the type of compression.

  FREQ Path List
  --------------
      When a Fido node requests a file from your site, PCBoard will search
      all subdirectories listed on this screen. If a matching filename is
      found in any subdirectory, the file is sent.

      NOTE:  It is important to remember that any file in these
      subdirectories can be obtained from a remote site. Therefore, do not
      put confidential files in these directories.

  FREQ Restrictions
  -----------------

      File Requests (FREQs) tie up your system for the time it takes to pick
      up the files.  Therefore, a way to restrict the amount of time, or
      bytes another site can pick up.  Several fields define how the file
      requests can be restricted.  The following describes each:

      Session Max Time

      Enter the maximum number of minutes another site can spend FREQing
      during the current call.

      Session Max KBytes

      Enter the number of kilobytes (1024 bytes) a remote site will be
      allowed to download during a single connect.

      Daily Max Time

      The value in this field represents the total amount of time a remote
      site can spend transferring files during any one daily period.  A day
      to PCBoard is considered to be from midnight to 11:59pm (via the host
      computer not the remote site).

      Daily Max KBytes

      Enter the total number of kilobytes a remote site may FREQ during a
      daily period (midnight to 11:59pm).

      Allowed Nodes

      This field defines which remote sites will be able to FREQ a file from
      your system.  The following describes each available option:

        A       All Fido sites regardless if they are listed in your user or
                nodelist will be able to FREQ a file.  Keeping in mind it is
                possible to FREQ using wildcards is another reason not to
                put confidential information in your FREQ paths.

        L       Any Fido site listed in the nodelist or in your user file
                will be able to FREQ a file.

        N       Only those Fido sites listed in the nodelist will be able to
                FREQ a file.  This option is ideal when you are involved in
                a smaller Fido-based network but do not want just any Fido
                capable mailer to be able to FREQ a file.

        U       Only those sites listed in your user file will be allowed to
                FREQ a file.

      Min Allowed Baud

      Because transferring files can be time consuming, you may choose to
      limit FREQs to only those sites capable of a certain baud rate or
      higher. For example, you may want to only allow those systems capable
      of a 14400 connection or higher to FREQ.  With this type of
      configuration, sites using 9600 baud modems would only be able to
      transfer mail and not files.

      In this field, enter the required baud rate for transferring files.
      Any site capable of the speed you enter or higher will be able to
      request files.

  FREQ Magic Names
  ----------------
      A "Magic Name" can also be seen as an alias to a filename
which can be
      FREQed.  A common example of an alias is for a remote site to FREQ a
      file called "FILES" on your system. This is commonly understood to be
      a list of files available on your system.  What do you do though if
      your list is called ALLFILES.LST?  Since FILES is a de facto standard,
      you want to make this available to other nodes but do not want to
      waste the space an additional copy occupies.  That is where the magic
      name comes in handy.  Simply make an entry similar to the following:

           Magic Name            Filename
           ----------            --------
        1) FILES                 C:\PCB\FILES\ALLFILES.LST

      From this example you can tell that the alias or magic name is entered
      in the left column and the actual filename to send is entered on the
      right.

      NOTE: For this to work, the C:\PCB\FILES\ subdirectory MUST be listed
      in the FREQ Path list.  FULL pathnames are required.

      A more sophisticated example involves wildcarding. You produce a
      program which consists of 3 zip files (3 disks). Rather than having
      remote sites requesting BOBOB-1.ZIP, BOBOB-2.ZIP, and BOBOB-3.ZIP you
      want them to simply FREQ BOBOB. The following example illustrates:

           Magic Name            Filename
           ----------            --------
        1) BOBOB                 C:\PCB\FILES\BOBOB-?.ZIP

      Notice how the ? DOS wildcard character is used to make sure all 3
      disks are included when BOBOB is requested.

  FREQ Deny Nodelist
  ------------------
      Some remote sites may abuse their ability to FREQ. To deny these sites
      the ability to FREQ from your system, add them to this list.  The
      entire node number/address must be entered.

Modem Related Options for PCBFido
-----------------------------------------------------------------------------
      New to the PCBSetup | Modem Information | Modem Setup screen are
      fields relating to the Fido configuration.  These fields control what
      command PCBoard will send to your modem for dialing other systems, and
      how many attempts should be made when a call results in a busy signal
      or failed attempt.  These fields are as follows:

        Modem Dialout String           : ATDT
        Max # of Redials on Busy       :    1
        Max # of Attempts to Connect   :  100

    Modem Dialout String
    ~~~~~~~~~~~~~~~~~~~~
      The command entered in this field is sent to the modem before a number
      is dialed.  Notice the default of ATDT which is a standard for nearly
      every modem.  The only time you may have to use something different is
      when the modem must be switched from say fax to data mode or some
      other special circumstance.

    Max # of Redials on Busy
    ~~~~~~~~~~~~~~~~~~~~~~~~
      When dialing a node it is not uncommon to get a busy signal as a
      response.  This field controls how many attempts PCBoard will make
      before it returns to the call-waiting screen to let the dial-timer
      expire again.

    Max # of Attempts to Connect
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      A call that results in a NO CARRIER, VOICE, or an unexpected modem
      response is considered to be a failed attempt. After an attempt fails,
      PCBoard will return to the call waiting screen.  This field controls
      the number of failed attempts that may accumulate when trying to send
      this packet.  Once a packet reaches this limit, it will not be sent
      until you view the outbound queue and reset the failed attempts
      counter.

cont...