I kept expecting this to come up, but it hasn't yet, so I'll add it.

This film has more holes than Swiss cheese.
1.) It starts with a simulation of what could happen to an airplane when y2k hits. The plane crashes and burns. Then they state that they have been running simulations for months, and this is the first time the plane crashed. So isn't it strange that, when y2k hits, that IS what happens to the plane? Talk about coincidence...
2.) Speaking of which, oh, wait, two things.
a.) The hero wants to ground all planes. TPTB protest, saying this is only one sim out of many, there's no proof, etc, etc, etc. Then, later, when y2k hits overseas (where the time changes first), a plane crashes - more on this later - they still don't want to ground the plane. There's still no proof. The clock changes, the plane crashes - and this isn't proof?!?
b.) So, they finally decide to ground the planes, 30 minutes before midnight. (I guess midnight on the East Coast, 'cause they all seem to be grounded at the same time.) Anyhow... They ask some guy, "Are all the planes down?" He answers yes. Then somebody ELSE comes by and says they have a mayday from some plane having trouble landing. I THOUGHT ALL THE PLANES WERE DOWN!?! The guy who said they were should be shot.
3.) The main point of the story is that the time change causes a reactor to blow, but they don't know at first because the boards don't show it. However, they're sure it will blow because they saw an exactly identical reactor overseas blow. Lots of questions here.
a.) WHY don't the boards show the change? The time changes, the boards don't change, so the hero says to reboot. They reboot, suddenly alarms go off. The reactor is starting its frantic race to annihilation, and the status boards don't know it? Why not? What does the time change have to do with it?
b.) They can't start the water flowing to cool the reactor, because the computer thinks the water tanks haven't been filled in 100 years. Okay, so the tanks were filled in 1999 and it's now 1900, and the tanks haven't been filled since..99 years IN THE FUTURE?!? How exactly does this work?
c.) The timing stank, especially in the closing, let's-blow-it-up-before-it-blows sequence. (Cool idea, but they could have gotten the timing closer, at least.)
d.) We won't even discuss the idiocacy of thinking the US, at least, wouldn't have checked that.

I've saved the best for last (almost). In Seattle, a baby heart monitor goes nuts because it was made in New York, so it thinks it's already 1900. Okay, it could happen. Except for one small detail, caused by the idiot producers themselves!
Remember that plane I mentioned, the first to blow up because of y2k? It's halfway around the world, in the Marshall Islands, on a US Air Force base. It's flying patrol, the clock changes, the plane blows up. Except, according to that baby monitor thing, it shouldn't blow up until the time changed here! Surely the plane wasn't built over there? And don't say they could have set the clock for local time, because in that case they could have fixed the y2k bug.

And the best for last. This part was great! Survival of the fittest in action.
Some guy, in Seattle, has stocked up for y2k. And he ain't leavin', and he'll defend his stockpile to the death. The reactor starts to go, they order an evacuation, the army starts going door to door making people leave. They come to his door, he comes out with a gun, "I ain't leavin'." That's fine, that's cool, that's his right. The first Army guy sends the second Army guy off to get someone. The survivalist fires into the air! The first guy ducks, the second guy turns back around, sees the first guy down, and shoots. What kind of idiot shoots when an Army person isn't looking?!? They're trained to shoot at a moment's notice!! I really felt sorry for the second Army guy. The survivalist should have known better.

I've been dying to write about this movie. Wish I'd kept track of all the things I found wrong with it. Here's a few:

The first fighter, in New Zealand or wherever it was, was flying across the time-zone when all the electronics went kablooey. They made it look like it was just because he crossed time zones that it happened. Pretty ridiculous.

OK, so the Ken Olin character enters a "Containment -- Human Fatality area", walks around where the actual nuclear stuff is practically exposed, and goes back outside to work with the people to blow up the water thing. Shouldn't he be glowing, or at least, dead?

They put oxygen and (hydrogen?) tanks into the 55-gallon drums. He says "seal them up tight". If they're sealed tight, how do the electronic cords keep from being clipped off? They toss them in the water, they leak air bubbles. If they're leaky, wouldn't it short out the electronics? They sink. If they're sealed tight, shouldn't they FLOAT? (Even though the tanks are heavy, there should be enough bouyancy to keep them afloat).

They blow up the water thing and water comes gushing into the "Containment-Human Fatality" area, as Olin and ANOTHER guy stand there and watch. Question is, how are they supposed to stop the water when it's full? None of the controls worked.

I thought when the woman with the baby had pains near midnight, they were going to blame THAT on a Y2K bug.

What do you think the chances are that this movie will ever be repeated after the first of the year?

The best part: We won't have to see a movie this bad again until Y3K.

This movie was made to make people panic and watch, was it not?

>This movie was made to make people panic and watch, was it not?

Ummm...not me! I haven't seen it and never plan to.

And another thing -- thousands of people in Times Square on New Year's Eve and not one of them has one of those glow necklaces, a flashlight, or even a lighter!

Actuaaly it would be Y10K. The computer would hit five digits (0-99 current problem)(0-9999 new problem), go back to the Year 0 A.D. and crash because 0 AD is an impossable date.

Yes this was the most irresponable movie ever made, and if it is ever shown again, I would be very surprised. I

Well, I'm glad that's over.

No, now we have to face the Y2037 bug. That's where the current standard for time (# seconds since 00:00:00 1 Jan 1970 GMT) becomes negative.