 This file contains important information regarding manual updates, as well
 as frequently asked questions about usage of the installation/upgrade
 procedure which could not be placed in the manual. Please read it
 carefully to see where it may apply to your installation.

 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-


      NOTE:  SEE THE INSTALL.DOC FILE IF APPLYING PATCHES.


 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 For additional information about PCBoard version 15.21, refer to the
 following files.

 WHATSNEW.150 -  A detailed list of differences between PCBoard 14.5a and
                 15.0
 WHATSNEW.151 -  A detailed list of what is new between v15.0 and v15.1
 WHATSNEW.152 -  A detailed list of what is new between v15.1 and v15.2

 WHATSNEW.    &
 ADDENDUM.DOC -  Detailed lists of what is new between v15.2 and v15.21

 PPE_INFO -      Descriptions of the PPL applications (PPS/PPE files) found
                 in the PPL subdirectory

 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 Important Information about Manual Updates!!!
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 -Pages 349-350-

    A clarification needs to be made in regards to COMM-DRV.  If a serial
    card is supported by COMM-DRV, that is no guarantee it will be
    supported by PCBoard. For example, some models of intelligent cards are
    connected through RJ-45 connectors which do not have enough wires for
    the RS-232 signals PCBoard requires.  These cards may not support the
    RTS or CD signals which are essential for host communications programs
    like PCBoard.

    Of the cards listed in the manual, only GTEK and Boca are known to have
    these type of connectors on their intelligent cards.   Other models
    from these manufacturers may work just fine like the GTEK BBS550 which
    supports all of the necessary signals.

 -Page 358-

    The example Arnet command line switch for the OS/2 CONFIG.SYS neglected
    to show the /Z:1 command line parameter necessary to force DTR high as
    control is passed to external protocols or programs.

 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 You may have downloaded this software as a single PCBOARD.ZIP file.  If
 so, to utilize this file, follow the procedure below:

     1) Create a \TEMP directory
     2) Unzip the PCBOARD.ZIP file into the \TEMP directory
     3) Then run the INSTALL program from the \TEMP directory

 INSTALL is capable of both first-time installations as well as upgrading
 existing v14.0 through v15.2 systems.

 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 Running PPEs on your system
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~

    What to do in case of Unable to Allocate Memory problems for PPEs
    -----------------------------------------------------------------
    Because of added memory requirements, some people may experience
    problems running out of memory when running PPE's, especially
    DESQview users where memory may already be tight.

    There are a couple of approaches to solving this problem.  The
    following outlines a few of them.  You may only need one of the
    solutions mentioned below, or you may need a combination of them or
    others.

    1) Reduce PCBoard's memory consumption.  You can do this by turning
       off the Pre-load PCBTEXT and Pre-load CNAMES options in PCBSetup |
       Configuration Options | Switches.  You can also reduce memory
       consumption during local logins by reducing the size of the
       scrollback buffer.

    2) Increase conventional memory availability.  Many memory managers
       allow usage of VGA memory when not in VGA mode.  For example,
       using QEMM you can add the following to your CONFIG.SYS file...

   DEVICE=C:\QEMM\QEMM386.SYS I=A000-B7FF  (plus any additional parameters)
                              ^^^^^^^^^^^
       This will add up to 96K of conventional memory to your system.  The
       drawback to this change is that you will no longer have EGA/VGA
       graphics capabilities.  Therefore, this change is only useful
       for multitasking environments such as DESQview which operate in
       text mode.

    3) If you are using DESQview, you can sometimes get more memory by
       NOT using DOS=HIGH in your CONFIG.SYS.  Rarely, you can get more
       *by* using DOS=HIGH. It is best to experiment both with and
       without and open up a DESQview window after each test to see how
       much memory is really free.

    4) You can adjust the amount of free memory even more by reducing the
       "DOS Buffers for EMS" and the "Shared Memory" settings found in
       the DV Setup program.  However, these changes should be a last
       resort unless the existing settings are excessively high.
       Recommended settings would be about 18-20 K for the shared memory
       and 6-8 K for the DOS Buffers for EMS setting.

    What to do if a PPE executes slowly or appears to halt
    ------------------------------------------------------
    This is usual a problem of overlay thrashing.  With the size of the
    overlay buffers set too small, PCBoard can spend an excessive amount
    of time pulling code into the overlay buffers which will have
    anywhere from a small to an huge impact on PPE performance.

    An overlay buffer size of 20 will probably work for most people who
    want to run PPEs.  If your PPEs will be accessing dBase files, then a
    buffer size of 25 or more may be necessary for optimum performance.

    You can set the overlay buffer size by using the OVLSIZE.EXE program
    to adjust your PCBOARD.EXE (or PCBOARDM.EXE) file like this:

       OVLSIZE PCBOARD.EXE      <-- tells you the current setting

       OVLSIZE PCBOARD.EXE 25   <-- sets the overlay size to 25

    Remember:  if your pcboard.exe file is set to read-only, you will
    need to make it read/write first, then run OVLSIZE, then make it
    read-only once again.  The procedure looks something like this:

       ATTRIB -R PCBOARD.EXE
       OVLSIZE PCBOARD.EXE 25
       ATTRIB +R PCBOARD.EXE

 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

                Common questions for first-time users of PCBMail:
                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 Q:  How do I make a PCBMail group in Windows?

 A:  1. Go to the file pull down menu item and select New Group...
                                                      ~~~~~~~~~~~~
     2. Enter in the group name and description into the text fields.

     3. Select New Item... from the file pull down menu.
               ~~~~~~~~~~~
     4. Enter PCBMail in the description field.
              ~~~~~~~
     5. Enter the path and file name of your PCBMAIL.EXE file.

     6. Enter the working directory for PCBMail to use.
        NOTE:  PCBMail needs this directory to store configuration
               information required to run PCBMail.

     Also to execute PCBMail login configuration only, you may execute
     PCBMAIL.EXE with a -CONFIG on the command line prompt.

     For example:  PCBMAIL.EXE -CONFIG

     You may also override the login name and password from the command
     line. The parameters for this is -USER[YOUR NAME] and -PASS[YOUR
     PASSWORD] Thus you can set PCBMail up to run from only one PCB.CFG
     file.

 Q:  I keep getting a dialogue box stating that PCBMail cannot find the
     PCBOARD.DAT filename.

 A:  Most likely it is a problem with your PCBMail login configuration,
     which is not pointing to the correct location of your PCBOARD.DAT
     file. Make sure that in the field that asks you for the location of
     your PCBOARD.DAT filename that you enter the entire name and location.

     For example:  C:\PCB\PCBOARD.DAT


 Q:  I want to run PCBMail with one executable on a server.

 A:  You must have the read only attribute set to read only.  See the help
     documentation for attrib in your DOS documentation. To set the read
     only attribute for PCBMAIL.EXE use [attrib +R pcbmail.exe] This lets
     you share copies of PCBMail over the network.


 Q:  I am running PCBMail from one copy of the PCBOARD.DAT file how do I
     set up PCBMail to work with this?

 A:  Your node number is located in the PCBOARD.DAT filename.  PCBMail has
     a configuration option which overloads this node number with one that
     you specify.  This is located in the login configuration dialogue box,
     which also lets you specify which node number you wish to use when
     logging into PCBMail.


 Q:  When I start PCBMail it will promptly exit without me doing anything?
     PCBMail will work when I am not running over my Novell network on my
     own hard drive.

 A:  This occurs when running NOVELL. This is potentially a problem with
     your BWCC.DLL file being too old. PCBMail does warn you of an outdated
     BWCC.DLL file. What you need to do is find all the occurrences of the
     BWCC.DLL and replace it with the one included with PCBMail.  A problem
     that some systems have running Novell is that Novell will scan
     backwards on your disk for a file. One way of forcing Novell to not do
     this is to place an option on your command line when loading PCBMail.
     An example of this is;

         SMODE 2 c:\pcbmail\pcbmail.exe

     What is SMODE?
         SMODE is a command line utility when specifies the searching mode
         in file retrieval.  SMODE causes problems because NOVELL may
         search in other directories other then the one that is specified
         of the current program.  The '2' in the command line tells NOVELL
         to not search beyond the working directory of the file.

     References to SMODE:
         Novell Netware Version 3.11 Utilities Reference, pp. 383 - 390
         Novell Netware Version 2.2  Using the Network, pp. 431 - 433


 Q:  I want to run PCBMail from one PCB.CFG file how do I do it? I also
     don't want to share my user name and password with other users using
     PCBMail.

 A:  You can override the login name and password from the command line.
     The parameters for this are -USER[YOUR NAME] and -PASS[YOUR PASSWORD]
     Thus you can set PCBMail up to run from only one PCB.CFG file.


 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 Upgrading your current version of PCBoard with this file
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 There are a few items you need to be aware of if you are using the install
 program to upgrade an existing version of PCBoard:

     1.  If you have multiple nodes installed, insure you have a BOARD.BAT
         and a PCBOARD.DAT in the directory where PCBOARD is going to be
         installed.  If you do not have these files, copy them from one of
         your node directories before you begin the install.  For example,
         If you have the following type of configuration

               \PCB--+
                     |
                     +---- NODE1
                     +---- NODE2
                     +---- NODE3
                     +---- NODE4

         where the \PCB directory does not have a PCBOARD.DAT or BOARD.BAT
         copy those two files from your NODE1 subdirectory so the INSTALL
         program can do a complete upgrade.

 NOTE                                                                NOTE
 NOTE  If you are running v15.X and upgrading to v15.2 then IGNORE   NOTE
 NOTE  the information shown below (items 2 through 5):              NOTE
 NOTE                                                                NOTE

         The INSTALL program does not know where to find all of your nodes.
         If you have multiple nodes you may have to upgrade each node
         manually.  If you do, the following lists the steps you must use
         to upgrade each node:

     2.  Run your BOARD.BAT and immediately exit your call-waiting screen.
         This will update the PCB environment variable so PCBSetup can
         properly set the options already in use.

     3.  Each BOARD.BAT you use must be changed.  Remove the line which
         says:

               if exist event.bat rename event.bat event.sys

         NOTE:  Do not remove the line which says "if exist event.bat event"
                or your events will *NOT* run.

         Also, change the line which reads PCB145 to run PCBOARD instead.
         If you are using the /M code, change it to PCBOARDM.

     4.  Change to each node directory and run PCBSetup.  If the
         PCBOARD.DAT file used by the node has not been upgraded, you will
         see a version change notice.  Acknowledge the notice and when you
         are at the PCBSetup Main Menu exit and save (using a full save -
         Y) to upgrade the PCBOARD.DAT file.

     5.  If each of your nodes uses its own copy of PCBTEXT you must
         manually upgrade each copy of PCBTEXT.  After you install the
         upgrade, you will find a FIXTEXT.EXE file in the same directory as
         your PCBOARD.EXE.  The syntax for the FIXTEXT program is:

               FIXTEXT <filename>

         Replace <filename> with the location of the PCBTEXT file to
         upgrade.

 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 Download Text or Download PPE in PCBTEXT record #61 has stopped working
 -------------------------------------------------------------------------
 PCBoard v15.2 splits the single file and batch file transfer prompts into
 two separate prompts.  Record #61 is now used only for single file prompts
 while record #728 is used for batch file prompts.  You may want to
 customize record #728 to match your prompt in #61, or keep them separate
 as they are used for the two different types of prompts (single and
 batch).

 Similarly, record #729 is a new one which corresponds with record #68,
 having to do with single versus batch uploads.


   ----------------------------------------------------------------------

     This manual and software assumes the reader has some basic prior
     knowledge of using PCBoard and Microsoft Windows.


                      Clark Development Company, Inc
                      3950 South 700 East, Suite 303
                          Murray, Utah 84107-2173

                            Voice 801.261.1686
                              BBS 801.261.8976
                              FAX 801.261.8987


     System Requirements

     Below is a list of hardware and software that is necessary for a base
     configuration of PCBMail v1.01.

     Hardware

         - IBM or compatible computer (80386 SX or higher)
         - 2 MB of memory
         - Hard disk drive with at least 1 MB of free space for PCBMail
           executable, plus another 1 MB free for storage of your saved
           messages and downloaded files.
         - Mouse
         - Printer (optional [required to print messages])

     Software

         - MS-DOS version 5.0 or later
         - Microsoft Windows 3.1
         - PCBoard Software v15.2 or higher

     To start PCBMail you need to execute the PCBMAIL.EXE from within
     Windows.  PCBMail will check your PCB.CFG for valid start up name and
     location of your PCBOARD.DAT file.  If PCBMail is unable to locate
     PCBOARD.DAT in the location specified it will bring up the
     configuration dialogue box prompting for an appropriate name and
     location of the PCBOARD.DAT file.

 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
