View Single Post
  #112  
Old March 19th 07, 01:02 AM posted to microsoft.public.win98.gen_discussion,microsoft.public.win98.apps
PCR
External Usenet User
 
Posts: 4,396
Default Daylight Savings Patch

"Gary S. Terhune" wrote in message
...
|
| "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.

Well, this seems to work by my testing...

IF EXIST %windir%\TZ_BAK01.reg GOTO Done
IF EXIST %windir%\TZ_BAK.reg DEL %windir%\TZ_BAK.reg
START /wait regedit /e %windir%\TZ_BAK01.reg
"HKEY_Local_Machine\Software\Microsoft\Windows\Cur rentVersion\Time
Zones"
one

SO... you end up with just a TZ_BAK01.reg next time & only once. It
isn't the greatest solution because you have to adjust for each new fix.
The one after that would need to delete the "01" & create an "02". I'm
sure there must be something even better that never would need
adjusting.

| 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.

OK, fine, but move that into the instructions at bottom of the Readme,
which you didn't fully update. There no longer are error messages or
multiple backups...

........Quote the Readme..........
INSTRUCTIONS:

Download the appropriate EXE file using links below and run the EXE.
(I
suggest saving this Update for possible future needs.)

Your time zone information and the settings for your system will be
auto-
matically updated with one prompt for you to allow the Registry merge.
Ignore
"File not found" messages.

A backup of the previous Time Zones Registry key, named TZ_BAK.reg,
will be saved to your Windows directory. If you perform the procedure
more
than once, the older backup file will have a numerical extension, e.g.
TZ_REG.001. The highest numbered backup is the oldest, i.e., the
original.
........EOQ.............................

| 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.

It worked for me in 98SE. Not sure, but I may have a while ago updated
the script engine.

| 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.

OK, then.

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