Y2KTOOLS Rev. 6 (pktdate 1.5)
-----------------------------
- New: The Pktdate program is now being able to talk German and Russian.
- New: Pktdate will now display the sender of a mail if it has a broken
  date field.
- New: Pktdate will now also fix the PKT header date field.
- New: Pktdate can now also fix structural errors like produced by the JFRQ
  request prozessor (totally spilled date field).
- Chg: Small changes in logfile format to make it more Binkley - like.
- Fix: type 2.2 packets (FSC 0045) are being recognised and for those packets,
  the packet header date will not be checked (because there is none).
- Fix: The DOS version of Pktdate is now able to deal with much greater
  PKT files, and if a PKT file should still be too large, Pktdate will now
  print a proper error message and exit, instead of doing nonsense.
- Fix: Since pktdate 1.4, the second field could be fixed to an illegal
  second value in very rare cases.
- New reason code 512 ("no NULL in date field") introduced, mainly
  for internal reasons. Code 4 will only occure if code 512 occured,
  but not necessarily vice versa.
- Pktdate now tries harder not to "eat" the first character in the name
  field when the date field is too short and not padded with garbage.
  A new reason code 1024 ("FTSC date field too short") has been intro-
  duced to reflect this.

Y2KTOOLS Rev. 5 (pktdate 1.4)
-----------------------------
- New: Pktdate now fixes bugs like "01 Jan :0" (instead of "01 Jan 00").
- New: Pktdate now fixes bugs like "01 Jan 0" (single digit year number).
- New: Speculative PKT file structure error correction now also works for
  Fastecho style .QQQ files (if -q option is given).
- New: The packet header date is now displayed (but not automatically checked
  or corrected).
- New: Bugs like "01 Jan 100  18:19:2" now fixed to "01 Jan 00  18:19:20"
  instead of "01 Jan 00  18:19:02".
- Chg: An uninitialised date field ("01 Jan 70 00:00:00") is now directly
  reset to the system date instead of doing any other sort of speculative
  correction.
- Chg: Only a warning is issued if a zero length file is encountered, instead
  of an error.

Y2KTOOLS Rev. 4 (pktdate 1.3)
-----------------------------
- New: German documentation added.
- New: Pktdate: Option "-k". This option will cause pktdate to make a backup
  copy of a PKT file before it is modified (and only if it has to be modified).
  So you can, at a later time, investigate who was that person that originally
  wrote the message with the broken date field and inform that person. The
  backup copies will have the file name extension ".Y2K", so they will not be
  processed a second time by your tosser.
- New: Jamdate tool, display date time stamps in JAM message bases (but no
  auto correction, just like msgdate and sqdate).
- New:  Pktdate now returns the highest reason code that it displayed as error
  level.  So you could check this in the batch file, e.g.
- New: Pktdate: The new command line option "-q" will make pktdate work with
  Fastecho .QQQ style files (in the Fastecho temporary outbound).
- New: FTSC timestamps with correct date field, but unparseable time stamp
  (like "01 Jan 99  12:75:61" will now be treated better, i.E. the time will
  be replaced by zeros where applicable, but the date will be retained.
- Fixed serious bug in pktdate 1.1 that mainfested itself in that
  - if the FTSC date field was unparseable (code 2), it was fixed to
    nonsensible values (like 00 Jan 00) instead of the current date.
  - if the FTSC date field was flawy (code 1) or in the Seadog format (code
    16), the date plausibility checks were omitted.
- Fix: Cosmetical fixes for pktdate log output. In the DOS version, the "fixed
  to" string was empty or even contained garbage instead of what pktdate
  actually wrote to the PKT file. In all versions, in case of a spilled
  date field the "from" string (before "fixed to") could have one single
  garbage character at the end.
- The Linux executables are now linked dynamically; this reduces the size
  of the distrubtion archive to the half ... :-)


Y2KTOOLS Rev. 3 (pktdate 1.1)
-----------------------------
- Wrong reason codes were displayed.
- Reason codes are now documented :-).
- Pktdate now tries to correct unplausible dates more intelligently
  ("speculative error correction").  It tries to undo the common 7 bit
  overflow (2048 instead of 2000, and so on), and it tries to just adjust the
  date to the current date.  If any of these corrections falls within
  tolerance boundaries (which are more strict than the tolerance boundaries
  used for testing if correction is necessary at all, though), the correction
  is accepted.  If no correction can be accepted, the date is adjusted to the
  current date, as previously.
- Pktdate now recognises Seadog-style date strings (strings like
  "Thu  1 Apr 99 10:05" instead of "01 Apr 99  10:05:00", written by programs
  like Seadog or DLGMail) and will not complain about them or even replace them
  with the current time. However, you can use the -S command line flag to
  make Pktdate rewrite those date fields to the new format.
- No executables for NT/Alpha any more, but anybody using this can easily
  compile the code on his own. If this is a problem, contact me.

Y2KTOOLS Rev. 2 (pktdate 1.0)
-----------------------------
- New: pktdate can fix broken PKT files!
- New: Executables for Win32, NT/Alpha, Linux and Amiga.

Y2KTOOLS Rev. 1
---------------
- First release.
