From: Gary Britt 

On a Win98 machine with the patch applied.  Go into control panel
timedate.cpl and select a timezone different from the one you want and hit
apply.  Then go back and select the timezone you do want and hit apply.
That should cause the new timezone DST info that was in the patch to be
re-intialized for the operating system.

This .vbs script file does the re-initializing automatically on Win2K.  I
don't know if it will work on Win98 but very well might.  If you get an
error on the event log writing lines on Win98 just delete that part of the
script.  I'd manually check to make sure the time zone settings appear in
the same place in the registry for Win98.  If they don't you might have to
edit the script accordingly for win98.

----------------------------------------------------
Set objSh = CreateObject("WScript.Shell")

'Get the StandardName key of the current time zone
szStandardName =
objSh.RegRead("HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\Standa
rdName")

'Enumerate the subkeys in the time zone database
const HKEY_LOCAL_MACHINE = &H80000002 Set
objReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\default:St
dRegProv")
szTzsKeyPath = "SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time
Zones" objReg.EnumKey HKEY_LOCAL_MACHINE, szTzsKeyPath, arrTzSubKeys

'Step through the time zones to find the matching Standard Name
szTzKey = ""
For Each subkey In arrTzSubKeys
     If (objSh.RegRead("HKLM\" & szTzsKeyPath &
"\" & subkey & "\Std") =
szStandardName) Then
         'Found matching StandardName, now store this time zone key name
         szTzKey = subkey
     End If
Next

If szTzKey = "" Then
        'Write entry to the Application event log stating that the update
has failed to execute
        objSh.LogEvent 1, "DST 2007 Registry Update and Refresh failed to
execute on this computer.  Time zones failed to enumerate properly or
matching time zone not found."
        Wscript.Quit 0
End If

'Launch control.exe to refresh time zone information using the TZ key name
obtained above
objSh.Run "control.exe timedate.cpl,,/Z" & szTzKey

'Get current display name of refreshed time zone
szCurrDispName = objSh.RegRead("HKLM\" & szTzsKeyPath &
"\" & szTzKey & "\Display")

'Write entry to the Application event log stating that the update has executed
objSh.LogEvent 4, "DST 2007 Registry Update and Refresh has been
executed on this computer." & chr(13) & chr(10) & chr(13)
& chr(10) & "Current time zone is: " & szCurrDispName
& "."

-----------------------------------------------------

waldo kitty wrote:
> has anyone else had problems with their win98 boxen and the free DST patch
> from intelliadmin.com? i downloaded the patch and ran it on all the win98
> boxes we have here and none of them appeared to make the switch...
>
> but (you knew there was going to be one, right?) this may be complicated by
> all our machines using AboutTime v4.8 to sync with NIST over the internet...
> i either get them to go an hour behind (stay in EST) or they go an hour too
> far forward...
>
> i had to adjust my TZ environment variable on my OS/2 server to get it to
> get right when syncing with NIST but the windows boxes still go off to the
> wrong time when AboutTime is set to sync with the OS/2 server...
>
> i've also an old mandrake (v7.1, IIRC) box that i have to manually update
> the time in the BIOS... it has the correct time and when i tell the windows
> boxes to sync to it, they get the proper time whether the intelliadmin patch
> is installed or not...
>
> however (!) if i tell that mandrake box to sync with NIST, it, too, gets the
> wrong time (stays in EST)... of course, this effects all the boxen set to
> sync with it...
>
> i guess my real question is this... has NIST fallen down on the job?? maybe
> i need to be looking elsewhere on how to fix up the mandrake box as it
> appears to have the same problem the windows boxen do??
>
> my eyes are so crossed from all this mess that i'm looking out thru opposite
> ears :(
>

--- BBBS/NT v4.01 Flag-5