Daylight Savings Patch

"PCR" wrote in message
...
OK, I'm taking it in now. Will report back after running it tonight or
tomorrow. That's really a masterful write-up of the situation at your
site-- very erudite! I'm pleased to see...

if not exist %windir%\TZ_BAK.REG start /wait regedit /e
%windir%\TZ_BAK.REG

..., by Blanton's hand, to make just one backup no matter how many times
this current time zone fix is run. After all, additional backups would
only save what this fix itself is putting into the Registry. HOWEVER,
if, as you say, the dates of the time change can change again-- then at
that time it SHOULD be this current fix's data that needs to be saved.
SO (if you haven't already thought of it), the next version of this fix
should REPLACE that line with...

if not exist %windir%\TZ_BAK01.REG start /wait regedit /e
%windir%\TZ_BAK01.REG

...And maybe figure a way to delete TZ_BAK.REG too -- or have Blanton
figure it -- & w/o an error message!

I'm thinking about it. Not really sure what I'll do between nopw and then.

Also, I see you have included a script to run the Time/Date Properties
requestor to complete the fix-- move the change into that other Registry
key. But I thought you had qualms about that-- that some would need to
switch the zone to another one? Anyway, I extracted & ran just that
script, & it seems to have worked. It opened & shut, after changing the
date back/forth to activate the Apply button. It was just slow enough
for me to see the button was activated.

As noted in the write-up, people need to make certain that their time zone
setting is correct after running the patch. Something in the patch may have
failed, or they may be in an entirely different time zone. We've heard now
that supposedly same systems were resulting differently. One thing I can
report is that VBScript has to be supported for teh new version to run. In
fact, I need to put back the old instructions for events in which the
VBScript fails.

Finally, where you say: "This latest version of the update resets the
Time/Date applet automatically, however a full restart of the system is
required in some cases." I think the case (in Win98 anyway) is that
Windows will only actually make the time change during a reboot-- on or
after the date of change has arrived. At least, that's how it went on a
friend's machine-- after he took your fix a day late!

Yes, that's the normal reason to reboot, though NT and 2K don't seem to even
require the reboot to effect the change in time when the patch is deployed
during daylight saving time. It happens right as the patch finishes. I
suggest the reboot just to make certain.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com