-=> Quoting Jean Parrot to Nancy Backus on 01-04-08  11:16 <=-

 NB>> You're using the one that hubby fixed, I think.
 JP> Yes, I am. Good hubby of yours.

I tend to agree with you there...  :)
 
 NB>> That is the kludge
 NB>> for post-Y2K dates.  Before the fix, anything post-Y2K showed up as 10,
 NB>> whether it was 2000, 2001 or 2008, as there was only space for 2
 NB>> numbers there, and it took the first two of the 99 + X, but not the one
 NB>> that really at least let one know which year it was.  Now there's the
 NB>> capability for 3 numbers, so the year is shown as 100, 101, 108 etc
 NB>> for dates Y2K and following.

 JP> I did not pay attention to this bug in the first  screen that
 JP> BW shows, it is still there. I know that the .rep itself was cured
 JP> and properly too, Dale did fine job too, his was tricking BW in
 JP> doing a proper date stamp. This date in the .qwk name does nothing.

Correct, it is mostly a cosmetic thing, just the way the reader listing
of message packets pulls in the date on the file for the user's viewing.
In the non-fixed reader, that listing merely was eg 05 Jan 10, no matter
what the actual year was.  Richard fixed it so that it would at least be
a useful year date, so now the above would be 05 Jan108 or whatever the
appropriate year was.  The date on the message itself shows as 05 Jan 08
or however you configure your reader to show the date.  :)

ttyl        neb

... BBS: A place where you are recognized as a friend!

___ Blue Wave/QWK v2.20
--- SBBSecho 2.12-Win32