Patch for Daylight Savers Time

[Mike]

Hi, we've got a special use XP Pro P2P network without Interent access how
can I manually patch the PCs for daylight savings time?

Thanks,

Mike

 

[WhzzKdd]

Hi, we've got a special use XP Pro P2P network without Interent access how
can I manually patch the PCs for daylight savings time?

Thanks,

Mike

Download the patch from MS, put it on a flash drive, CD, etc., and install
it that way. You want KB931836 from download.microsoft.com.

 

[Elmo]

Hi, we've got a special use XP Pro P2P network without Interent access how
can I manually patch the PCs for daylight savings time?

Thanks,

Mike

How to configure daylight saving time for the United States in 2007
http://support.microsoft.com/kb/914387/#appliesto

 

[Peter Foldes]

Mike

The same way you have posted here. Take a disk or CD and download the file to the media and take that media to the computer without the Internet Access and install it

 

[Mike]

Mike

The same way you have posted here. Take a disk or CD and download the file
to the media and take that media to the computer without the Internet Access
and install it

Thganks everybody I haven';t had time to research the issue and now I won't
have to.

Thanks.

Mike

 

[Gary G. Taylor]

daylight savings time

Daylight savinG time.

 

[HEMI-Powered]

Today, Mike made these interesting comments ...

Hi, we've got a special use XP Pro P2P network without
Interent access how can I manually patch the PCs for daylight
savings time?

I haven't paid much attention to this because it seems to me that
even if my two PCs don't do it automagically at 2:00AM, I can fix
it once manually in about 30 seconds, along with fixing all the
dumb clocks I have in my house and my cars. Also, nearly all clocks
drift in time unless they're synch'ed to something valid, so I
occasionally have to manually tweak some of them. Doesn't seem to
be a big deal, or am I missing some catastrophic proportions Y2K
issue in the making because the government wants to try in vain to
save a little oil?

 

[Aardvark]

Mike

The same way you have posted here. Take a disk or CD and download the file
to the media and take that media to the computer without the Internet Access
and install it

Thganks everybody I haven';t had time to research the issue and now I won't
have to.

Thanks.

Mike

Research the issue??????????? No need for any ****ing research, just a bit
of gumption.

Common sense ain't that common, is it?

 

[Scraggy]

Daylight savinG time.

Enough with your initial already. It's not like you invented it.

 

[Bob I]

Enough with your initial already. It's not like you invented it.

His point is that there is not an "S" on the end of "Saving" in
"Daylight Saving Time", or were you just defending your initial?

 

[Scraggy]

His point is that there is not an "S" on the end of "Saving" in
"Daylight Saving Time", or were you just defending your initial?

JHC!

 

[WhzzKdd]

Today, Mike made these interesting comments ...

I haven't paid much attention to this because it seems to me that
even if my two PCs don't do it automagically at 2:00AM, I can fix
it once manually in about 30 seconds, along with fixing all the
dumb clocks I have in my house and my cars. Also, nearly all clocks
drift in time unless they're synch'ed to something valid, so I
occasionally have to manually tweak some of them. Doesn't seem to
be a big deal, or am I missing some catastrophic proportions Y2K
issue in the making because the government wants to try in vain to
save a little oil?

I believe you're correct - most home users won't be seriously affected by
this. However, if the PC isn't patched, a user will have to fix the time
manually 4 times a year (assuming that the "automatically adjust for
Daylight Saving Time" is left ON) because they'll set it forward in March,
then the PC would set it forward again in April. And the PC would set it
back in October, before it is supposed to, so it would have to be corrected,
then fixed again in November when it is really supposed to be turned off.

And then there's the scheduling (PIM/PDA) issue. Users with appointment
schedulers could find their times messed up if the PC doesn't know how to
process the time change dates correctly.

Of course, in a corporate setting, there's payroll programs as well as
calendar and scheduling systems of a myriad of programs that can be
affected. For instance, in my Netware server, users can be limited to
login/logout times. If the clocks don't change correctly, the user could be
inadvertantly shut out. Or people doing shift work will come up short an
hour on their paycheck. Plenty of other examples out there. So, while not as
pervasive an issue as the Y2K thing was for many companies, this does
require a good bit of time and effort by the IT people to get it handled.
Where I work, it's down to the ol' "Wait and see..." period. Sunday is
coming up fast <g>

 

[HEMI-Powered]

Today, WhzzKdd made these interesting comments ...

I believe you're correct - most home users won't be seriously
affected by this. However, if the PC isn't patched, a user
will have to fix the time manually 4 times a year (assuming
that the "automatically adjust for Daylight Saving Time" is
left ON) because they'll set it forward in March, then the PC
would set it forward again in April. And the PC would set it
back in October, before it is supposed to, so it would have to
be corrected, then fixed again in November when it is really
supposed to be turned off.

As I said, I've paid zero attention to this; I'll either pick up
the patch in a normal MS update - maybe already have and don't
know it - or I'll manually change it 4 times on 2 PCs or I'll go
find the patch if I get annoyed enough. Someone posted a link to
the MS KB article that talks about that, and I captured it, so I
can fix my PCs if needbe.

And then there's the scheduling (PIM/PDA) issue. Users with
appointment schedulers could find their times messed up if the
PC doesn't know how to process the time change dates
correctly.

Understood. There are any number of issues, but for us retired
folk who just like to be pests on Usenet, having my system clock
off an hour when I schedule nothing or having my file
creation/modification times off an hour is of little consequence
to me personally.

Of course, in a corporate setting, there's payroll programs as
well as calendar and scheduling systems of a myriad of
programs that can be affected. For instance, in my Netware
server, users can be limited to login/logout times. If the
clocks don't change correctly, the user could be inadvertantly
shut out. Or people doing shift work will come up short an
hour on their paycheck. Plenty of other examples out there.
So, while not as pervasive an issue as the Y2K thing was for
many companies, this does require a good bit of time and
effort by the IT people to get it handled. Where I work, it's
down to the ol' "Wait and see..." period. Sunday is coming up
fast <g>

Business users either have an IT staff or should. Those people
also mass-distribute patches,updates, customizations, etc. AFTER
they have been thoroughly tested and approved. I should know, I
used to manage a group that did that. But, just centralizing
support is no guarantee and there's no hope for small businesses
drowning in high tech stuff they really have no time for.

I do not minimize the impact of this, I was joking about the
presumed rationale to the entire bizzare mess, some BS nonsense
about saving energy. Now, here's one for you: safety for our
children is significantly reduced by this change; it is already
quite dangerous for the kids walking to school early in the
morning since it doesn't get light until they're already in
school. And, the mass media completely blew Y2K out of all
proportion. One of my paranoid doctors actually converted
hundreds of thousands of dollars into gold bullion and stored it
in an expensive safe in his basement because he actually thought
the world would end. Total hogwash. The Y2K thing was a non-
event, again because it was planned for. I was part of that one,
too.

 

[HEMI-Powered]

Today, WhzzKdd made these interesting comments ...

I should add that my wife's main gripe is that she loses an
hour's sleep!

 

[Mike]

I believe you're correct - most home users won't be seriously affected by
this. However, if the PC isn't patched, a user will have to fix the time
manually 4 times a year (assuming that the "automatically adjust for
Daylight Saving Time" is left ON) because they'll set it forward in March,
then the PC would set it forward again in April. And the PC would set it
back in October, before it is supposed to, so it would have to be
corrected, then fixed again in November when it is really supposed to be
turned off.

And then there's the scheduling (PIM/PDA) issue. Users with appointment
schedulers could find their times messed up if the PC doesn't know how to
process the time change dates correctly.

Of course, in a corporate setting, there's payroll programs as well as
calendar and scheduling systems of a myriad of programs that can be
affected. For instance, in my Netware server, users can be limited to
login/logout times. If the clocks don't change correctly, the user could
be inadvertantly shut out. Or people doing shift work will come up short
an hour on their paycheck. Plenty of other examples out there. So, while
not as pervasive an issue as the Y2K thing was for many companies, this
does require a good bit of time and effort by the IT people to get it
handled. Where I work, it's down to the ol' "Wait and see..." period.
Sunday is coming up fast <g>

 

[Mike]

I believe you're correct - most home users won't be seriously affected by
this. However, if the PC isn't patched, a user will have to fix the time
manually 4 times a year (assuming that the "automatically adjust for
Daylight Saving Time" is left ON) because they'll set it forward in March,
then the PC would set it forward again in April. And the PC would set it
back in October, before it is supposed to, so it would have to be
corrected, then fixed again in November when it is really supposed to be
turned off.

And then there's the scheduling (PIM/PDA) issue. Users with appointment
schedulers could find their times messed up if the PC doesn't know how to
process the time change dates correctly.

Of course, in a corporate setting, there's payroll programs as well as
calendar and scheduling systems of a myriad of programs that can be
affected. For instance, in my Netware server, users can be limited to
login/logout times. If the clocks don't change correctly, the user could
be inadvertantly shut out. Or people doing shift work will come up short
an hour on their paycheck. Plenty of other examples out there. So, while
not as pervasive an issue as the Y2K thing was for many companies, this
does require a good bit of time and effort by the IT people to get it
handled. Where I work, it's down to the ol' "Wait and see..." period.
Sunday is coming up fast <g>

I'm concerned about three different networks one of them W2K Pro SP4,
another XP PRO SP2
(these two are isolated special use networks) and I've learned over the
years to be very careful
when making any changes.

Mike

 

[jj206]

His point is that there is not an "S" on the end of "Saving" in
"Daylight Saving Time", or were you just defending your initial?

Maybe the original poster was doing some sort of statement or
implying that time is almost always plural to human beings,
except when we say "Gimmie a sec will ya". Not sure, but when have you
experienced a time singularity ?

LOL

geothermal

 

[Frosty]

Maybe the original poster was doing some sort of statement or
implying that time is almost always plural to human beings,
except when we say "Gimmie a sec will ya". Not sure, but when have you
experienced a time singularity ?

LOL

geothermal

Is this like the debate regarding "Happy New YearS"?
'Cause if it is I wanna put in my 2¢ that THAT really FROSTS my
gonads!

I mean if Happy New Years was correct we'd only have to say it once in
our lifetimes, not three times a year like now.

Frosty

 

[Bob I]

Is this like the debate regarding "Happy New YearS"?
'Cause if it is I wanna put in my 2¢ that THAT really FROSTS my
gonads!

I mean if Happy New Years was correct we'd only have to say it once in
our lifetimes, not three times a year like now.

Frosty

It would be correct when referring to past occurrences.

 

[Frosty]

It would be correct when referring to past occurrences.

Yeah, but why would you wish anyone "Happy (past) New Years!"?