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

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 the   NOTE
NOTE  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.

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

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.1 systems.

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

For additional information about PCBoard version 15.2, 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

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

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

What if my Download Text or Download PPE in PCBTEXT Record #61 Stops 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.

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

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.

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

Important Information about PPL!!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   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 availibility.  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.

   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 exessively 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

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

Important Information about PCBMail!!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

                How to make a PCBMail group in Windows ?

   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

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

   This manual and software assumes the reader has some basic prior
   knowledge of using PCBoard and Microsoft Windows.  All questions and
   comments related to PCBMail should be directed to...


                     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.0.

   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
      executables, 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 startup 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 dialog box prompting for an appropriate name and
   location of the PCBOARD.DAT file.

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

