M
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
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 installMike said: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
Mike said: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
daylight savings time
I haven't paid much attention to this because it seems to me thatHi, we've got a special use XP Pro P2P network without
Interent access how can I manually patch the PCs for daylight
savings time?
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 said:Daylight savinG time.
Scraggy said:Enough with your initial already. It's not like you invented it.
Bob said: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?
I believe you're correct - most home users won't be seriously affected byHEMI-Powered said: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.
Business users either have an IT staff or should. Those peopleOf 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>
WhzzKdd said: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>
WhzzKdd said: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>
Bob said: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 said: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.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.