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

PLEASE USE THE REPORT.TXT FILE FOR ALL BETA REPORTS.  SEE THE TOP OF REPORT.TXT
FOR INSTRUCTIONS ON ITS USAGE.  DO NOT CALL VOICE FIRST, ALL BETA REPORTS MUST
BE SUBMITTED VIA SALT AIR FIRST IN ORDER FOR US TO PROPERLY LOG THE REPORTS
AND TRACK THEM.


   NOTE FOR FIDO TESTERS:
   ----------------------
   Fido has been delayed.  We'll try to get Fido into testing sometime after
   ONE BBSCON is over (August 18-21).


The WHATSNEW file lists the changes in PCBoard and its utilities in going from
v15.1 to v15.2 and does not even attempt to address the changes made in PPL.
For that, see the WHATSNEW.PPL file.  Nor does the WHATSNEW file describe any
of the changes that were made for UUCP or FIDO.  Separate documentation will
be provided for each of these.   (currently UUCP.DOC is available)


   INSTALLATION
   ------------
   To use the v15.2 beta file, you need to copy all of the new .EXE files
   over top of you current v15.0 or v15.1 files.  Now execute PCBSetup and
   exit with a "Y" to save the current setup (just this once, be sure to not
   use "Q" to save).  Run MKPCBTXT on each of your PCBTEXT files and
   you're done.  No other changes are necessary.


For PPL testing purposes, we ask that you try running both v15.0/v15.1 PPEs as
well as recompiling the PPS files that you have to ensure compatible on both
fronts.  Version 15.0, 15.1 and 15.2 compiled PPEs should all run without any
difficulty under PCBoard v15.2.

If you are experienced with PPL, please test the new functions and procedures
and, if possible, the dBase functionality as well.  See the file HOWTODBF.TXT,
in your BETA.ZIP download, for more information on using dBase in PPL.


   SLOW EXECUTION OF PPE's
   -----------------------
   Guaranteed!  If you experience slow execution of your PPEs, or if they
   appear to "stop dead" for a long period of time, the cause is the size of
   your OVERLAY buffer.  Don't bother sending in a BETA report.  Instead,
   just increase your overlay buffer size and that will fix it.

You can use the OVLSIZE program to adjust PCBOARD.EXE (or PCBOARDM.EXE) and
play around with various settings.  Going too low (less than 16) will probably
result in Borland's Overlay Manager *picking* a default FOR you.  Going too
high will simply waste memory.  Start with a value of 20 and go up or down
from there to see what gives you a) the amount of memory you need combined
with b) the amount of performance you require.  Higher overlay buffer settings
will generally INCREASE performance, but on a "diminishing returns" basis.
In other words, going from 16 to 20 will yield a tremendous increase.  Going
from 20 to 24 will show an increase, but only a small increase.  Going from
24 to 28 may not show a perceptible increase.  Experiment to be sure.

Once you decide on the best settings for your system, return to the BETA door
and then UN-flag, then RE-flag the main PCBoard executable(s) that you
download.  In RE-flagging the file, the BETA door will once again ask you for
your desired default overlay buffer setting.  It will remember that setting
from then on so that you won't have to remember to run OVLSIZE each time you
download a new executable.


   DOWNLOAD PPEs IN PCBTEXT PROMPTS
   --------------------------------
   Version 15.2 introduces two new, semi-redundant, prompts for the download
   and upload prompts.  These are records 728 and 729 in the PCBTEXT file.
   They correspond with records 61 and 68 respectively.

   What this means is:

   If it appears that your download PPE is NO LONGER BEING USED, the real
   problem is that it simply is not installed in the NEW prompts.  Copying
   the PPE from records 61/68 into records 728/729 will solve the problem.
   Use MKPCBTXT to edit/update your PCBTEXT files.


   WISHLIST REQUESTS
   -----------------
   Please remember, the feature set for v15.2 is frozen.  Your ideas and
   wishlist requests are welcome, but please do not expect them to be
   implemented in version 15.2.  As always, during the BETA cycle the goal
   is to "finish" the software as quickly as possible, removing any bugs and
   preparing the software for shipment.  The next development cycle will
   begin immediately after the beta cycle.  So the sooner the beta cycle
   finishes, the better.

   Your best bet is to utilize the FEATURES door on Salt Air since those
   features with the highest number of requests and priority standings are
   the ones that will be implemented first.


Thanks for your time and effort in helping us to ensure PCBoard's reliability
and success!

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