I know that when year 2000 came around, there was a rush to update the times on computers. That was for 2000. Since then, I think there is less of a need as the OS can do it automatically.
Are there special preparations needed?
- Follow via:
- RSS
- Email Alert
Question
0
Votes
Answers (4)
0
Votes
TWO days TOO late . . .
The Summer & Winter regime revolves around the 'summer and winter solstice', which are astronomical calculations based on the orbits of the Moon around the Earth, and the Earth's orbit around the Sun.
However, 'Daylight Savings' has nothing to do with summer or winter in the strictest sense: - it is the practice of advancing standard time by one hour in the spring of each year and of setting it back by one hour in the fall in order to gain an extra period of daylight during the early evening.
This practice was initially adopted only around 1905 - 1910 AD.
This adjustment was recently made at 02.00 hours GMT on Sunday 28th October 2007.
The concept of the Y2K bug was a fallacy - unless anyone knows different, as far as I heard the only computers that had a problem were astro-navigation ones that belonged to NASA.
However, 'Daylight Savings' has nothing to do with summer or winter in the strictest sense: - it is the practice of advancing standard time by one hour in the spring of each year and of setting it back by one hour in the fall in order to gain an extra period of daylight during the early evening.
This practice was initially adopted only around 1905 - 1910 AD.
This adjustment was recently made at 02.00 hours GMT on Sunday 28th October 2007.
The concept of the Y2K bug was a fallacy - unless anyone knows different, as far as I heard the only computers that had a problem were astro-navigation ones that belonged to NASA.
30th Oct 2007
Replies
Ours won't kick in this year until 4 Nov. There have been a few automatic devices (computers included) that kicked in the change early this year due to the change in the law. Here is a link.
http://aa.usno.navy.mil/faq/docs/daylight_time.php
http://aa.usno.navy.mil/faq/docs/daylight_time.php
IC-IT
30th Oct 2007
I tried a patch for my PDA that screwed everything up. Now I am just updating the clocks by hand. My computer updated automatically for me yesterday so I changed the clock and will do so again on Sunday.
I sure hope they don't do this silliness again next year.
I sure hope they don't do this silliness again next year.
Tig2
30th Oct 2007
since the patch was loaded. Actually, I think I had to do it 2x.
Anyway, my IPAQ is an hour off until the 4th
Anyway, my IPAQ is an hour off until the 4th
w2ktechman
30th Oct 2007
Although Mike had more trouble than I did. I just got to the clock setting and reset it to the correct time after it did the auto update. I will go back and reset it on Sunday again, no big deal.
But the gov ninnies should have known better than to schedule such silliness during the deer opener!
But the gov ninnies should have known better than to schedule such silliness during the deer opener!
Tig2
30th Oct 2007
I dont think that this came up at the meeting...
More likely they were sitting around saying things like"Come on people, we need to deflect attention from Bush and Cheney again"...
More likely they were sitting around saying things like"Come on people, we need to deflect attention from Bush and Cheney again"...
w2ktechman
30th Oct 2007
There is a patch for DST to edit the time zones so your computer won't auto update on the wrong date.
ThumbsUp2
30th Oct 2007
And my HP is updated but I have been using my Dell since the HP TU'd on me. My partner also patched his system, it's fine.
I will admit that I was a bit concerned, especially after seeing how well the patch worked for our PDAs. GRRRR!
I will admit that I was a bit concerned, especially after seeing how well the patch worked for our PDAs. GRRRR!
Tig2
30th Oct 2007
Even though you're using the Dell, it may already be patched because MS pushed it out as critical a number of months ago.
It may only need the correct time zone selected because the patch doesn't do that for you.
It may only need the correct time zone selected because the patch doesn't do that for you.
ThumbsUp2
30th Oct 2007
Hey OM,
You said "The concept of the Y2K bug was a fallacy - unless anyone knows different, as far as I heard the only computers that had a problem were astro-navigation ones that belonged to NASA."
Actually, we had many computers that had a Y2K issue. When tested before Y2K, they rolled from 1999 to 1900 instead of 2000. Y2K BIOS patches were not available for these older systems and never would be. We had to replace each and every one of them before Y2K rolled around. Of course, it was time to replace them anyway, as they had far outlived their life expectancy (IMHO). But, none the less, they had to be replaced.
So, you heard wrong.
You said "The concept of the Y2K bug was a fallacy - unless anyone knows different, as far as I heard the only computers that had a problem were astro-navigation ones that belonged to NASA."
Actually, we had many computers that had a Y2K issue. When tested before Y2K, they rolled from 1999 to 1900 instead of 2000. Y2K BIOS patches were not available for these older systems and never would be. We had to replace each and every one of them before Y2K rolled around. Of course, it was time to replace them anyway, as they had far outlived their life expectancy (IMHO). But, none the less, they had to be replaced.
So, you heard wrong.
ThumbsUp2
30th Oct 2007
Fair point.
OldER Mycroft
30th Oct 2007
I was hired to be the Y2K guy at a firm that did a billion dollars of business a year.
They always cheaped out and tried to stretch their equipment as far as possible.
What we had to replace:
1 mainframe class computer (16 years old), about $400,000 (replaced with a mini-computer).
PCs (and custom software) at customer sites - 3,500 x $2000 per machine, plus installation costs, and redevlopment costs.
Of the 400 pieces of software I tracked, 90% were fine. Of the remaining 10%, about half were "serious" business halting issues, the rest were resolved but would have been worked out with work arounds.
James
They always cheaped out and tried to stretch their equipment as far as possible.
What we had to replace:
1 mainframe class computer (16 years old), about $400,000 (replaced with a mini-computer).
PCs (and custom software) at customer sites - 3,500 x $2000 per machine, plus installation costs, and redevlopment costs.
Of the 400 pieces of software I tracked, 90% were fine. Of the remaining 10%, about half were "serious" business halting issues, the rest were resolved but would have been worked out with work arounds.
James
JamesRL
30th Oct 2007
Driving around Morocco in a Hymer B564.
While the rest of the computer world crapped themselves, I drove around in the sun, emailing digital photos around the globe.
Then it was 2001, and I drove North to 57' N.
While the rest of the computer world crapped themselves, I drove around in the sun, emailing digital photos around the globe.
Then it was 2001, and I drove North to 57' N.
OldER Mycroft
30th Oct 2007
Most of our customers insisted that we provide proof that we were ready for Y2K in early 1999 - the latest was April.
So we worked very hard till we could provide proof, then finished up our New Years planning (communications etc).
The last half of the year wasn't stressful at all since we were pretty well prepared.
New Years day wasn't big since our customers were not back in the office.
The first business day there were a few minor issues to fix.
James
So we worked very hard till we could provide proof, then finished up our New Years planning (communications etc).
The last half of the year wasn't stressful at all since we were pretty well prepared.
New Years day wasn't big since our customers were not back in the office.
The first business day there were a few minor issues to fix.
James
JamesRL
1st Nov 2007
0
Votes
Energy Savings
Months after Indiana passed the law that got it in step with the rest of the country, the federal government announced a major change in Daylight Saving Time. In Aug. 2005, Congress passed an energy bill that included extending Daylight Saving Time by about a month. As of 2007, DST starts the second Sunday of March and ends on the first Sunday of November.
So it's a phony attempt at energy savings by trying to keep lights off by making the day longer.
So it's a phony attempt at energy savings by trying to keep lights off by making the day longer.
Updated - 30th Oct 2007
0
Votes
Depends on the System
If you are running Windows XP or Vista and are current with all patches, then the changes to daylight savings time in either the US or Australia will be automatic.
If you are running Windows 2000, all you need to do is download TZEdit from Microsoft and manually adjust the Daylight Savings Time calender for the new dates.
For Windows 95 and 98, you can use regedit to manually change those systems also.
There are many clocks and other devices with built in clocks that do not have patches for the changes to DST. This includes most VCRs and older Atomic Clocks.
For the energy savings skeptics out there, the big savings has very little to do with the amount of time your home lights are on or off. The big savings come from reducing the peak power demand by not having street and parking lot lights on before 5 PM.
Chas
If you are running Windows 2000, all you need to do is download TZEdit from Microsoft and manually adjust the Daylight Savings Time calender for the new dates.
For Windows 95 and 98, you can use regedit to manually change those systems also.
There are many clocks and other devices with built in clocks that do not have patches for the changes to DST. This includes most VCRs and older Atomic Clocks.
For the energy savings skeptics out there, the big savings has very little to do with the amount of time your home lights are on or off. The big savings come from reducing the peak power demand by not having street and parking lot lights on before 5 PM.
Chas
30th Oct 2007
0
Votes
Outlook
I see there was an update for Outlook itself...so that means that outlook uses a time that is different from the rest of the OS?
9th Nov 2007
