My only guess is that my manual win xp update was duplicated by dell support;yes,still under warranty.
no biggie
Discussion on:
View:
Show:
I have 17 Pelco Digital Video Recorders running Windows 2000 SP4. The patch did not work on any of them. On 6 of my infant monitoring systems the patch only worked on 3 machines. Did anyone else have this problem.
We found that most of ours needed to have the check mark on "Automatically adjust clock for daylight saving changes" removed and replaced on the Time Zone tab.
Did you change the time zone to a different one and apply that and then change to the correct time zone again so as to get the new rule applied. I haven't had any complaints on the 30 some systems I have patched.
The company I work for has experienced nothing but problems since the switch. Servers keep crashing, time on network computers keep resetting back one hour. The entire network has also slowed almost to grinding halt.
Im also having some issues with a few Windows XP sp2 computers that jump back an hour after be set to the correct time. The domain controller works perfectly, and about 25 other pc's that log onto the domain keep correct timing.
Anyone have any information on why a select few computers would be having problems? Or what a way to fix it would be?
2007 DST patches were applied, i tried synching it to the domain controller with w32time, and also tried synching it to an outside time server. This works great for about 3 minutes, then it jumps back an hour.
Anyone have any information on why a select few computers would be having problems? Or what a way to fix it would be?
2007 DST patches were applied, i tried synching it to the domain controller with w32time, and also tried synching it to an outside time server. This works great for about 3 minutes, then it jumps back an hour.
It works well on all XP and 2000. You can use the admin tool but unless you buy it, you can only fix 3 computers on your network.
http://www.intelliadmin.com/DaylightSavingFix.exe
http://www.intelliadmin.com/blog/2007/01/unofficial-windows-2000-daylight.html
http://www.intelliadmin.com/Downloads.htm
http://coolthingoftheday.blogspot.com/2007/02/windows-2000-dst-patch-utility.html
http://www.intelliadmin.com/DaylightSavingFix.exe
http://www.intelliadmin.com/blog/2007/01/unofficial-windows-2000-daylight.html
http://www.intelliadmin.com/Downloads.htm
http://coolthingoftheday.blogspot.com/2007/02/windows-2000-dst-patch-utility.html
Ill try that DaylightSaving fix from the link you had posted. Im hoping it will end this frustrating problem!
I assume that you used the Windows Patch KB931836 on the systems. At home I just patched my XP system with tzedit just to see what would happen and have had no issues with it. That could be a last effort. I have heard of others with issues about the change and getting it to sync with a time server as well. Haven't heard how/if they have it fixed yet.
Yep that is the patch I had applied across the systems, I also tried Tzedit and had no luck with it.
What is bothering me is that I can get it synched up with the time server. So says the command after i run it "Command completed successfully" and the system clock moves to the correct time. But then about 3 minutes later it reverts back to where it was.
What is bothering me is that I can get it synched up with the time server. So says the command after i run it "Command completed successfully" and the system clock moves to the correct time. But then about 3 minutes later it reverts back to where it was.
The few computers that would not keep the correct system time were updating from a 911 system where the time was incorrect in the actual 911 dispatch application that was being served.
Ahhh the fun of being the new "computer Guy"
I just wanted to thank everyone for their input, was still very much appreciated.
Ahhh the fun of being the new "computer Guy"
I just wanted to thank everyone for their input, was still very much appreciated.
The Canada Revenue Agency might have had a DST glitch that causedthe problems they are having receiving electronic income tax returns and processing returns. Staff were sent home and returns are piling up. The service was down since Mar 5 and is supposed to be back up on the 15th.
Although CRA doesn't say that it was because of DST, they say "A malfunctioning software patch is the cause of this service interruption." What with the timing, it's a heck of a coincidence. And, word on the street is that it was DST.
If that doesn't count as major, what would?
Although CRA doesn't say that it was because of DST, they say "A malfunctioning software patch is the cause of this service interruption." What with the timing, it's a heck of a coincidence. And, word on the street is that it was DST.
If that doesn't count as major, what would?
I saw a few problems with Outlook calendars getting messed up. Both parties to a meeting needed the update and then a re-invite to meeting. Also some UNIX based boxes had problems requiring reboot. It was not disastrous, but there were problems.
I suspect that someone at Microsoft is full of it - or not using the same OS they sell to the rest of us.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle

































