Release 2.0.3d:
by John A. Magliacane <kd2bd@amsat.org> (17-Jun-2000):

* Several small bugs in the KepCheck() and SaveTLE() functions of predict.c
  were identified and repaired.  The problems centered on the fact that
  unsigned chars were used to accumulate TLE checksums.  Occasionally,
  the checksums exceeded the capacity of an unsigned char, and rolled
  over through zero as a result.  These variables were changed to
  unsigned integers.

* A small problem in the AutoUpdate() function in predict.c was identified
  and fixed.  Occasionally, Keplerian data for a satellite would not
  update if it had the same reference epoch as that in PREDICT's
  orbital database.  This problem was the result of extremely small
  rounding errors introduced by the complier that caused intermittent
  logic errors when trying to compare two double precision floats for
  equality.  This problem was solved by changing these variables from
  doubles to floats.

* The Keplerian "torture test" was a bit too brutal for some element sets.
  The check for a '-' on position 59 of TLE line 1 was eliminated since some
  element sets have a '+' in that position.


Release 2.0.2d:
by John A. Magliacane <kd2bd@amsat.org> (01-Apr-2000):

* A solar illumination feature was added to predict the percentage
  of time a satellite spends in sunlight per day.

* Orbital predictions for satellites that appear to have decayed
  since the last Keplerian orbital update are no longer attempted
  by the program.

* Date and time used to start orbital predictions may now be
  abbreviated to Day/Month/Year only (00:00:00 is assumed).
  The default remains the current date and time.

* System clock/calendar is now read to millisecond precision,
  permitting more "lively" real-time tracking mode displays.

* The UTC timezone offset now may be set correctly for users living
  in half hour timezones.

* Internal timezone calculations are no longer confused by environmental
  variable TZ.  If TZ is properly set to a timezone name (as required
  by some other satellite tracking programs), the TZ setting is used by
  PREDICT instead of the UTC timezone offset specified in the predict.qth
  file.

* The command-line parsing code was modified to prevent segmentation
  faults from occurring if command-line options are incorrectly issued.

* Some other minor coding changes were made.
