OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: Y2K Problem in Windwos NT
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Y2K Problem in Windwos NT

  • To: NTBUGTRAQLISTSERV.NTBUGTRAQ.COM
  • Subject: Re: Y2K Problem in Windwos NT
  • From: Russ <Russ.CooperRC.ON.CA>
  • Date: Thu, 12 Mar 1998 14:30:14 -0500
  • Comments: To: Kastl <skastlMCS.NET>
  • Reply-To: Russ <Russ.CooperRC.ON.CA>
  • Sender: Windows NT BugTraq Mailing List <NTBUGTRAQLISTSERV.NTBUGTRAQ.COM>
I'm getting so many responses to this I felt I needed to send this
message.

Firstly, James Fang of Microsoft submitted a response that the problem
is known, and will be fixed in SP4. The KB article number on the problem
is Q175093.

Secondly, I'm amazed at the number of people who believe 2000 isn't a
leap year and are prepared to state so unequivocally. From
http://www.mitre.org/research/y2k/docs/PROB.html, which is a pretty
definitive treatise on Y2K, the following quote;

The year 2000 is a leap year. The three rules which the Gregorian
calendar uses to determine leap year are as follows:

1. Years divisible by four are leap years, unless...
2. Years also divisible by 100 are not leap years, except...
3. Years divisible by 400 are leap years.

Therefore, the year 2000 is a leap year according to rule number three.

See http://www.mitre.org/research/y2k/docs/LEAP.html for a complete work
on Leap Years.

Cheers,
Russ