PiHex Version 1.0
-----------------

  *  First version. It worked. It was really slow.


PiHex Version 2.0
-----------------

  *  Faster. Much faster. About 100% faster. 


PiHex Version 2.2
-----------------

  *  Fixed a few minor bugs. Added version information to properties sheet.


PiHex Version 3.0
-----------------

  *  Changed range mechanism; now current range info is stored in PiHex.ini
     (in windows directory) and next range is in range.ini.

  *  Used for 200B range (two hundred billionth hexit).


PiHex Version 4.0
-----------------

  *  Displays Pentium equivalent speed in window -- the speed at which a
     Pentium would have to be running full-time to get as much done.

  *  About 25% faster implementation, uses Bellard's formula, which is 43%
     faster, for a net increase in speed of 79%.

PiHex Version 4.01
------------------

  *  Minor bug fixes.

  *  First public release.

PiHex Version 4.02
------------------

  *  Fixed a bug in a bug fix in version 4.01

  *  Performs a self-test when first run (actually, if it cannot find
     PiHex.ini in the windows directory), consisting of calculating the one
     hundred millionth hexit of Pi. This should take about 15 minutes on a
     Pentium 200.  During the self-test, it will display a speed
     significantly higher than the actual speed of your computer; ignore it.
     The speed will be more accurate once you get a real range to process.

PiHex Version 4.10
------------------

  *  If running on a laptop, PiHex only auto-continues if battery>75% life
     and AC line status <> offline (ie. online or unknown). If you want to
     drain your battery, you can tell PiHex to start calculating manually,
     but otherwise it won't.

  *  PiHex now displays correct Pentium Equivalent Speed for any range; 
     earlier versions only display correct speed for the beginning of the
     calculation (the later ranges of a calculation involve lower exponents,
     and are thus easier and faster).

  *  Now searches for range*.ini in the current directory instead of just
     range.ini -- this way people will not have to rename the file they get
     (eg. range1.ini) to range.ini.

  *  Fixed a bug in versions 3.0-4.02 which can cause PiHex to crash on exit.

  *  PiHex now checks to see if the CPU is overheating or if other problems
     are causing the FPU to malfunction.  Rather than exiting with an error
     message, PiHex now reports the problem and shuts down gracefully.

PiHex Version 4.11
------------------

  *  Bug fixes!  Now, PiHex searches for range*.ini, and actually finds it!
     Also, under NT 4.0, PiHex autocontinues when told to do so even though
     it can't get the power status from the OS.

PiHex Version 5.00
------------------

  *  Selects either the Pentium-optimized code or the P6-optimized code, as
     appropriate.  About 40% faster on P6 machines (PPro, PII, Celeron, Xeon)
     and 60% faster on K6 machines (K6, K6II).

PiHex Version 5.10
------------------

  *  The calculation thread priority can now be selected from between 1 and 5
     or 'Auto', which varies the thread priority to match any other low
     (idle) priority task.  This is of particular value when running another
     client at the same time, or when a 'cycle-hungry' screen saver is
     selected.

  *  Fixed a bug in PiHex 5.0 which could cause PiHex to incorrectly report
     that the CPU was overheating.

  *  Fixed a bug in versions 3.0-5.0 which sometimes caused PiHex not to ask
     that completed ranges be sent in.

  *  PiHex now stores its .ini in the PiHex directory, not the windows
     directory.  When it is first run, it checks to see if there is an .ini
     file in the windows directory, and moves it if necessary.

  *  Output files are smaller.


PLANNED FUTURE RELEASES
=======================

PiHex Version 6.00
------------------

  *  PiHex will communicate with a central server to send results in, and get
     new ranges.
