Posted on 12/20/2006 9:03:24 AM PST by krogers58
Starting in the spring of 2007, daylight saving time (DST) start and end dates for the United States will transition to comply with the Energy Policy Act of 2005. DST dates in the United States will start three weeks earlier (2:00 A.M. on the second Sunday in March) and will end one week later (2:00 A.M. on the first Sunday in November).
(Excerpt) Read more at support.microsoft.com:80 ...
Could have a mini-Y2K situation in the IT world, many people are probably not even aware of the changes.
I wish it stayed DST all year long.
Shouldn't that be "next year"?...or are we on daylight savings years?.......
Better notify the Russians. They have a history of forgetting DST..........
It is next year, however the start date is less than 3 months away....
FYI, Microsoft is not making an update available for Windows 2000 Professional.
None of that folly here in Hawaii. We stay the same all year long.
All of you Polly Anas can just wither away on the second Sunday in March. I've got a NDSS (new daylight savings scheme) survival kit hidden in a cave near my place. I have enough food, water and ammo to last until we go back to standard time! </Y2K flashback>
DST is a scam, but the real mystery is who profits. It does nothing one way or the other at this latitude. Right now it is still dark at 10 AM and dark again at 4 PM and the time between is twilight with sometimes a slight orange or pinkish glow on the tops of the black spruce. In the summer when the schoolbus argument might work there are no schoolbuses and it isn't dark anyway.
my VCR is programmed to change in early April and late Oct. though you can do manual time changes--yes I still have one, though eventually I'll transfer the last of my tapes to DVD either through a friend who has a DVD recorder, or I'll
buy my own DVD recorder (they're getting cheaper in price)
I've written software, which calculates the time change, based on the april - october timeframe. I have started re-writing the code, to take the new changes into effect. Its just a real pain. Our systems, essentially, gather real-time data (every 15 minutes), from numerous army depots, and I have software that checks to make sure there is no latency in the data, and if there is, a page is sent out to our technicians. Again, its an issue I'd rather not have to deal with. Many networking encryption algorithms are also based on an exact time stamp, and this could throw a few systems off of the networks. It's not going to be anything close to Y2K, but it is an issue, that programmers never had to even think about. The funny thing, is that Microsoft is only releasing the patch as an optional component, and not making it a critical update.
Exactly.
Or push it up half an hour and leave it there.
This is one of my pet peeves -- the needless time change twice a year that was started as a phony solution to a phony problem.
I was told it was for the farmers. Like a real farmer gives a hoot what a clock says!
When DST was forced on the Canadian public, the province of Saskatchewan's farmers basically said "the grain don't care what time it is" and still to this day Saskatchewan stays on standard time year 'round.
The biggest problem is kids would be walking to school in the dark.
Could be much worse --- We could change the clocks on election day. Imagine all the stupid people unable to tell what time it is.
Wouldn't work for a lot of places. Even in the eastern portion of my time zone, it would be still be dark or nearly dark at 8:00am for several months a year. For people in western portions of time zones, it would be much worse, espcially the farther north you go. In Cleveland, the sun wouldn't rise in November - January until almost 9:00am.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.