Re: OFF TOPIC: Y2K problems with news reader (was Re: Armaggedon)

[/dev/null@.com (Justa Lurker)]

It was Sun, 02 Jan 2000 06:21:30 GMT, and urbanophile@mindspring.com
(Urbanophile) wrote in misc.transport.urban-transit:
| >>Well, FWIW I have noticed a minor problem with my news reader (Free
| >>Agent); it's putting the date down as "1/1/0" rather than "1/1/00."
| 
| >I'm using Agent version 1.7, and it shows 1/1/00
| 
| I'm using Free Agent version 1.0, (c) 1995.  My policy is: Why bother
| upgrading if what you have does the job?

In the language of a Y2K expert, if it isn't showing a correct date,
it isn't doing it's job.  But it still posts, reads, and sorts, so for
everyone but the picky Y2K expert it works.

BTW: I have 1.11 and it shows 1/1/2000 (and did show 12/31/1999).

Y2K bug!
When setting the date in command mode on a PC, the date command
assumes 19xx if you provide a two digit year.  If one provides a four
digit year (1999 or 2000) the date command works fine.  So the fact
that the shortcut of typing the last two digits is not available for
years starting with 2000 is a bug.  Horrors!  Got to love those Y2K
experts, but missing shortcuts are the most common 'bugs'.

JL