http://wwp.daylight-saving-time.com/usa/dst-2007.htm
a 2005 Energy Bill will cause the effective dates for Daylight Saving
Time in the U.S. to begin at 2 a.m. on the Second Sunday in March and
end at 2 a.m. on the First Sunday in November, beginning in 2007. Will
the automatic adjustment for DST in the various versions of Windows
cause the clock to be set incorrectly?
James A. Fortune
CMDAP...@FortuneJames.com
MPAP...@FortuneJames.com
I did read from a KB article the following "SUMMARY
Some system BIOS adjust the computers built-in real-time clock to
compensate for daylight savings time automatically. Windows NT can also
be configured to adjust for daylight savings time. If both the BIOS and
Windows NT adjust the close for daylight savings time, your clock will
be one hour off."
I gather that if it is a software update, it will work fine. If the
System bios is also used, you could have a problem
I wonder how DST is handled for a state like AZ which has no DST.
There is a time zone specification in Windows special for AZ, and other
areas like east Indiana that do not observe DST. I presume those
settings cause the system to never adjust for DST (^:
--
Smartin
Curious question. Surely other systems have a built-in algorithm to
handle DST adjustments also. The impact of changing the DST "rule" could
be interesting.
However, since my little ol' PC synchronizes with time on the net every
week or so, should I worry?
--
Smartin
> According to:
>
> http://wwp.daylight-saving-time.com/usa/dst-2007.htm
>
> a 2005 Energy Bill will cause the effective dates for Daylight
> Saving Time in the U.S. to begin at 2 a.m. on the Second Sunday in
> March and end at 2 a.m. on the First Sunday in November, beginning
> in 2007. Will the automatic adjustment for DST in the various
> versions of Windows cause the clock to be set incorrectly?
Don't you have the time service running on all your computers so
it's going to update correctly, anyway?
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
You and David have a great idea. You only need to worry about your data
for a maximum of four weeks per year :-), the week between the false
changing of the clock until the synchronization, the week between the
failure to change the clock and the synchronization, and the two weeks
for the vice-versa case.
James A. Fortune
MPAP...@FortuneJames.com
Of course you can change the default frequency from one week to a lot
less:
http://support.microsoft.com/kb/223184/en-us
-Tom.
Change the clock on your PC to just before the effective date/time and see
what happens after the clock ticks over.
--
Terry Kreft
<CDMAP...@FortuneJames.com> wrote in message
news:1161282224.3...@i3g2000cwc.googlegroups.com...
The timezone offset on the client machine still has to be correct. If
my machine thinks that it is on EST (-0500) when it should actually be
on EDT (-0400) then it will still be "off" by an hour after
synchronizing with an NTP server.
For example, my machine would display 10:21 (EST) when it was really
11:21 (EDT). Both times are "correct" in that they correspond to 15:21
UTC, but it's the localized time that is at issue here.
I !!!!!think!!!!! that unless something changes these registry settings
(below) on my computer then the changes will be made in the first week
of April and the last week of October.
Will something change them automatically? I'd guess that MS or Nist or
someone else will send out a reg file or patch we can import that will
do this.
If not they can be edited manually in regedit (maybe not a good idea
for the not-so-brave)
or with
Private Declare Function SetTimeZoneInformation _
Lib "kernel32" _
(lpTimeZoneInformation As TIME_ZONE_INFORMATION) _
As Long
ot they can be exported, edited in notepad or similar and them imported
back.
Perhpas they are modified by time updates but doubt it. Messing with
people's registry settings is unlikely to win friends and influence
people. Well, of course if you are MS, obviously you don't care about
that.
But what are they? They're supposed????to be SystemTime Types
Private Type SYSTEMTIME
wYear As Integer
wMonth As Integer
wDayOfWeek As Integer
wDay As Integer
wHour As Integer
wMinute As Integer
wSecond As Integer
wMilliseconds As Integer
End Type
but they don't look like that to me. Perhaps Windows cheats on the
storage and just stores the ordinal of the Sunday with respect to month
in place of day of week and hour in place of day (day of month).
Key Name:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation
Class Name: <NO CLASS>
Last Write Time: 2006-04-02 - 05:38
Value 0
Name: Bias
Type: REG_DWORD
Data: 0x12c
Value 1
Name: StandardName
Type: REG_SZ
Data: Eastern Standard Time
Value 2
Name: StandardBias
Type: REG_DWORD
Data: 0x0
Value 3
Name: StandardStart
Type: REG_BINARY
Data:
00000000 00 00 0a 00 05 00 02 00 - 00 00 00 00 00 00 00 00
................
Value 4
Name: DaylightName
Type: REG_SZ
Data: Eastern Daylight Time
Value 5
Name: DaylightBias
Type: REG_DWORD
Data: 0xffffffc4
Value 6
Name: DaylightStart
Type: REG_BINARY
Data:
00000000 00 00 04 00 01 00 02 00 - 00 00 00 00 00 00 00 00
................
Value 7
Name: ActiveTimeBias
Type: REG_DWORD
Data: 0xf0
ramble ... ramble ... ramble
Any idea what that service is called?
I popped MyComputer|Manage|Services And Applications|Services and didn't see
anything called "Time".
Windows XP Pro.
--
PeteCresswell
I don't believe that bill actually passed to become law.
How many devices, other than your computers, do you have that are *hard wired*
for the old dates. I have a couple of clocks, 3 VCRs, and 2 TVs that adjust
automatically. They are not radio controlled. I would have to set every one 4
times a year. In the spring to put the new time in. In the spring to take out
the automatic updates. And again twice in the fall.
And next year when the Democrats are in control of congress they are going to
make PI an even 3 so it will be easier for the school kids to work with.
Chuck
--
<g>
--
Terry Kreft
"Lyle Fairfield" <lylefa...@aim.com> wrote in message
news:1161345644.1...@i42g2000cwa.googlegroups.com...
Well I was /trying/ to be funny anyway (^: You're absolutely right.
Actually, I'm a little surprised this pronouncement didn't create more
noise. Looking at Google Trends, the news went out, but it seems very
few people listened.
Mark Foley will be a school teacher then. He'll teach the boys about
mud PIs. He'll also teach a tutorial on dice to his students; the girls
will be in the pass line, the boys in the come line.
I'm very impressed that you dug out this information. Also, the
information that Gord provided was something I didn't consider.
I think your theory is pretty close. One problem is that there isn't
always a 5th Sunday in October. Would the OS figure out that the day
of the date is greater than 31 and "fall back" ;) to the 4th Sunday?
James A. Fortune
CDMAP...@FortuneJames.com
Windows Time.
But just after I posted, I realized what someone else has already
said, that it doesn't have an effect on the local time setting, so
won't fix this problem.
I'd assume there will be a patch through Windows Update for this.
Dunno what happens to older versions of Windows that aren't
supported any longer.
> However, since my little ol' PC synchronizes with time on the net
> every week or so, should I worry?
That sets GMT, which won't address this particular problem.
And why only once a week? The Windows Time service checks a couple
of times a day.
> I have a couple of clocks, 3 VCRs, and 2 TVs that adjust
> automatically. They are not radio controlled. I would have to
> set every one 4 times a year.
TV devices get their time signal from the local PBS affiliate, so
there shouldn't be an issue. TiVo gets it from its daily connection
to TiVo's servers, and will probably get a patch to the underlying
Linux-based operating system for this. I would expect other DVRs to
be the same.
Clocks, well, those won't work so well.
OTOH, maybe they'll be able to pass something that enforces net neutrality...
Seems tb split pretty closely along party lines.
--
PeteCresswell
>Chuck <lib...@schoollink.net> wrote in
>news:2mehj2lfhrurcohi6...@4ax.com:
>
>> I have a couple of clocks, 3 VCRs, and 2 TVs that adjust
>> automatically. They are not radio controlled. I would have to
>> set every one 4 times a year.
>
>TV devices get their time signal from the local PBS affiliate, so
>there shouldn't be an issue. TiVo gets it from its daily connection
>to TiVo's servers, and will probably get a patch to the underlying
>Linux-based operating system for this. I would expect other DVRs to
>be the same.
>
>Clocks, well, those won't work so well.
Ocasionally I lose power, none of my time keeping devices rerset thamselves
automatically.
Chuck
--
Occasionally I laugh at a post. but after reading this post, I don't think my
pants will ever dry.