Software

General discussion

Locked

3/11

By onbliss ·
****************************************
The Energy Policy Act of 2005 was passed by Congress and then signed into law by President George W. Bush on August 8, 2005. Under the new law, Daylight Saving Time begins three weeks earlier than previously, on the second Sunday in March. DST is extended by one week to the first Sunday in November. The new start and stop period begins March 2007.

The original House bill would have added two full months, one in the spring and another in the fall. According to some U.S. senators, farmers complained that a two-month extension could adversely affect livestock, and airline officials said it would have complicated scheduling of international flights. So, a compromise was worked out to start DST on the second Sunday in March and end the first Sunday in November.

Enactment of the Energy Policy Act of 2005 will not alter the rights of the states and territories to choose not to observe Daylight Saving Time.

Source: http://www.energy.ca.gov/daylightsaving.html

****************************************

The place where I work, had set up an exploratory committee err.. :-) a functional team to explore, identify and mitigate issues.

Reminds me of Y2K.....

I did not know about this until I received an email from a co-worker. How is the awareness about the change on March 11th?

Looks like MS XP SP1 requires some updates.

Things appear quite calm.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

My watch is still set for EDT

by NickNielsen In reply to even if

But that's because I lost the directions and have forgotten how to change the time. I'm so used to it now, I'll probably keep subtracting an hour from the time for weeks after we go back on daylight savings time.

Collapse -

Not the first time...

by dawgit In reply to 3/11

They did this once before, in the early 70's if I can remember that far back. (after the 60's, the 70's were still a bit foggy ;\ ) It was a diaster if I remember correctly, got quickly recinded. Oh-well, here we go again. Does the US have to repeat all of it's mistakes? -d

Collapse -

60s and 70s

by onbliss In reply to Not the first time...

The PCs were not there, and obviously the "perceived" impact to the common man was less, right? Days when Mini and Main frames ruled.... Main frames continue to still share the limelight.

Collapse -

We had computers, but...

by dawgit In reply to 60s and 70s

No PC's of course. I don't think at that time it had much effect on the computers at all in those days. Net-Time coordination was not an issue yet. There was also not much of a hic-up in our comms either as we were always on Zulu anyway.
It was the people that is was hard on. (I don't remember asking any cows about it though.) -d

Collapse -

Mid 70's

by CharlieSpencer In reply to Not the first time...

Because of the OPEC oil embargo, we went to a longer DST period to save on light bills and electricity generation.

Collapse -

XP patch has been out there for weeks.

by CharlieSpencer In reply to 3/11

There's been a patch for weeks, downloadable by the Windows Update system or manually from MS.

I raised this issue here over a year ago when the legislation passed. More people were interested in correcting my use of the phrase "Daylight Savings" instead of "Saving" than were actually interested in discussing the technical implications.

I wish we'd move the clock forward this spring and leave them there.

Collapse -

Oh Great...

by dawgit In reply to XP patch has been out the ...

Now I've something to worry about. A patch to fix the worlds computers for something that only affects the US. I can smell the mess already.

Collapse -

Not just U.S.

by CharlieSpencer In reply to Oh Great...

There's also a patch for an Australian time change. Everybody gets to play.

Collapse -

Was covered by the media when the Act went through

by TheChas In reply to 3/11

This was covered pretty heavily when the energy act went through congress.

I think there was even a TR discussion on it at the time.

What will be effected?

Any Windows system prior to Windows 2000. That means 95, 98, Me and NT systems will all need to have the time changed manually.

Any old system with a BIOS DST setting will not function correctly either.

A bigger issue for this go round than Y2K is embedded systems with DST built in.

Any time keeping device that adjust itself for DST will not change on the correct day starting this year. And, guess what? No patches for most of these systems. You will need a new device. Be it alarm clocks, DVRs, VCRs, watches, or cars. The clocks won't automatically adjust on the correct day anymore.

From a business standpoint, the biggest impact will be on labor reporting systems for third shift employees. Unless patched or upgraded, the systems won't handle the new date properly, and could credit or debit time for employees on the old transition date.

Chas

Collapse -

Many of the devices you point...

by onbliss In reply to Was covered by the media ...

...out have manual adjustments to set the time, don't they? If it is just a question of automatically adjusting on the correct day, people could possibly live with it.

Related Discussions

Related Forums