Well, it's just a trifle of a detail. Check out the Greenwich Clock site. It's now the 25th hour of December 31, 1999.

-- SH (squirrel@huntr.com), December 31, 1999

Answers

What's that saying?

"The devil is in the details."

-- Ariana (pergados@yahoo.com), December 31, 1999.

Could that be the reason why airlines have not had any problems?

-- Laqtis (gemini2@sprynet.com), December 31, 1999.

Kinda funny. Sure the *clock* is OK but the website sure has a problem.

-- Carlos (riffraff1@cybertime.net), December 31, 1999.

Squirrel that is funny :o)

-- Brian (imager@home.com), December 31, 1999.

This confirms THE PROBLEM for me! Please, check out the website http:/ /greenwich2000.co.uk/countdown/ THE PROBLEM WAS/IS REAL! ... i've captured the image of the bogus clock reading on the Greenwish mean Time web site and i encourage you to do same! Cheers, michael maser (British Columbia, Canada)

-- michael maser (mmaser@uniserve.com), December 31, 1999.

On my computer the time is correct for GMT.

-- Mara (MaraWayne@aol.com), December 31, 1999.

BIG DEAL!!!!!!!!!! Who cares????? The one in Paris crashed after running for a 1000 days.

I guess you doomers need something to grab on to. GAWD!!!!

-- (ha@ha.ha), December 31, 1999.

Actually, it's just a detail. A trifle. An oversight, I guess. By some computer programmers. You know? It's not important. Certainly it's not important to fix the date on the website for the Atomic Millenium Countdown Clock. I mean, its only the Greenwich Countdown Clock, you know? Why should we expect the Countdown Clock Website to be accurate? In fact, 25 or 26 hours in December 31 is .... just what I was expecting. One of those things......

So its obviously a FOF situation. They'll get to it before the weekend's out.

>"<

-- (squirrel@huntr.com), December 31, 1999.

If they couldn't even fix a clock that is being watched by the whole world, then imagine what is going to happen at other businesses like your bank.

Death by a thousand cuts.

-- Hawk (flyin@high.again), December 31, 1999.

Hmmmmmmmmmmmmmm.........it's now saying December 31, 1999 26:13

-- Linda (lindasue1@earthlink.net), December 31, 1999.

Something is odd here. When I visit the site I read the time as

01 Jan 2000 h:mm:ss UTC

And underneath this is a note that reads

Time information last supplied by NPL mm minutes ss seconds ago

Further down the page is another explanation of how your computer may behave. If your computer does not show the correct time, then it may not be Y2K ready.

-- Malcolm Taylor (taylorm@es.co.nz), December 31, 1999.

Malcolm -- I'm looking at a sritten month-date-hour calendar in the mid-lefthand side of the screen, which CLEARLY states the date is December 31, 1999 and its' 2600 hours. That is an error in programming at the NPL website, is it not? Can hardly be something generated locally.

Not that it matters.

-- Roch Steinbach (rochsteinbach@excite.com), December 31, 1999.

That clock works in conjunction with your PC and your JAVA. So, what you see is partially based on data from that site, and partially based on factors within your PC. This may help indicate why different people are getting different readings.

Jerry

-- Jerry B (skeptic76@erols.com), December 31, 1999.

Man, that thing is totally screwed!

My PC says 8:18 and that clock says 26:29

Even taking into account the hourly difference, the minutes are still way off.

-- Hawk (flyin@high.again), December 31, 1999.

FOF, HAwk. FOF!

-- (squirrel@huntr.com), December 31, 1999.

Sheeeessh, I just reloaded it and the clock when BACK to 26:25, but it is still moving FORWARD in time! What the heck could be taking them so long to fix it?

I think a lot of people are going to be suprised if they think it will be "business as usual" next week. I sure hope this type of thing isn't happening in hospitals, etc. Like the computers that decide how long to administer intravenous medication to patients and things like that. God help them.

-- Hawk (flyin@high.again), December 31, 1999.