A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows 98 » General
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

Unofficial Time Zones Update (Testers wanted)



 
 
Thread Tools Display Modes
  #61  
Old February 21st 07, 08:03 PM posted to microsoft.public.win98.gen_discussion
PCR
External Usenet User
 
Posts: 4,396
Default Unofficial Time Zones Update (Testers wanted)

Gary S. Terhune wrote:
| Yes, at least ten totally new zones. For example, Mexico didn't
| change their laws, so they're on the old DST schedule instead of
| synched with ours. Thus, they need their own zones.

I don't quite understand. Are you adding additional Mexico zones,
instead of replacing the old ones? Then, how will Windows know which to
use in the Date/Time Properties requestor-- &/or anywhere else Windows
must use them?

| And some place in
| central Asia has segregated itself from Russia and its TZ schedule.
| Things like that.

So? These will be new ones where none existed before? That hopefully
will be OK. But I'm not sure I want a double set like you may be doing
with Mexico!

| Those are the ones missing MapID values. Plus a bunch if info that is
| useful only to WinXP/2K3 "Dynamic Updates" (accounting for future
| changes).

I am pleased you have chosen to decontaminate these XP keys, as MGDX may
have not.

| If you want to see the new ones, use the MGDX update on a fresh
| Registry and look for the ones that have "Standard Time" added to the
| names and missing MapID value.



| --
|
| Gary S. Terhune
| MS-MVP Shell/User
|
| "PCR" wrote in message
| ...
| Gary S. Terhune wrote:
| | Actually, I've *done* all that,
|
| Twice now, right? the second, to incorporate the hopefully final MS
| update of those zones?
|
| | and deleted a lot of crap that is only
| | useful to XP machines. Plus adding several MapID's where MS
| | couldn't be bothered. Gotta wonder which mop-wielding janitor they
| | saddled this project with. I mean that quite literally, not in any
| | way figuratively!
|
| I wonder too. I see you had to fiddle with things after the export.
| There's no chance totally new zones were created now, or visa versa?
| If so, do you have it covered in your doings?
|
| | --
| |
| | Gary S. Terhune
| | MS-MVP Shell/User
| |
| | "PCR" wrote in message
| | ...
| | "Gary S. Terhune" wrote in message
| | ...
| | | Note: http://support.microsoft.com/?kbid=931836 corrects some
| | | errors in the previous patches. I've nearly finished the updates
| | | to account for this and to add some features, but I won't be
| | | done until late tonight or tomorrow AM, Pacific time.
| |
| | Ah! Good! I hope that's their last update, though. So...
| |
| | You will run this update on an XP machine, & then export the
| | Registry key? That's how you do it, maybe reverting some of the
| | Registry values too (such as "Eastern Standard Time" back to just
| | "Eastern"? I guess that does it, then. Very good.
|
| --
| Thanks or Good Luck,
| There may be humor in this post, and,
| Naturally, you will not sue,
| Should things get worse after this,
| PCR
|

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR



  #62  
Old February 22nd 07, 08:42 AM posted to microsoft.public.win98.gen_discussion
Gary S. Terhune
External Usenet User
 
Posts: 1,846
Default Unofficial Time Zones Update (Testers wanted)

*I* am not adding a damned thing, except the MapID values. I *subtracted* a
bunch of stuff that's irrelevant to the legacy OSes. *Microsoft* added the
new Time Zones. Which is why people in other parts of the world need to
verify that they don't need an entirely new TZ setting instead of using the
same old one when they do the switcheroo.

Look at the damned Registry keys if you need to know more. Or just look at
the TZ tab in the Time/Date applet. They[re right there, assuming you've
applied the update(so).

--

Gary S. Terhune
MS-MVP Shell/User

"PCR" wrote in message
...
Gary S. Terhune wrote:
| Yes, at least ten totally new zones. For example, Mexico didn't
| change their laws, so they're on the old DST schedule instead of
| synched with ours. Thus, they need their own zones.

I don't quite understand. Are you adding additional Mexico zones,
instead of replacing the old ones? Then, how will Windows know which to
use in the Date/Time Properties requestor-- &/or anywhere else Windows
must use them?

| And some place in
| central Asia has segregated itself from Russia and its TZ schedule.
| Things like that.

So? These will be new ones where none existed before? That hopefully
will be OK. But I'm not sure I want a double set like you may be doing
with Mexico!

| Those are the ones missing MapID values. Plus a bunch if info that is
| useful only to WinXP/2K3 "Dynamic Updates" (accounting for future
| changes).

I am pleased you have chosen to decontaminate these XP keys, as MGDX may
have not.

| If you want to see the new ones, use the MGDX update on a fresh
| Registry and look for the ones that have "Standard Time" added to the
| names and missing MapID value.



| --
|
| Gary S. Terhune
| MS-MVP Shell/User
|
| "PCR" wrote in message
| ...
| Gary S. Terhune wrote:
| | Actually, I've *done* all that,
|
| Twice now, right? the second, to incorporate the hopefully final MS
| update of those zones?
|
| | and deleted a lot of crap that is only
| | useful to XP machines. Plus adding several MapID's where MS
| | couldn't be bothered. Gotta wonder which mop-wielding janitor they
| | saddled this project with. I mean that quite literally, not in any
| | way figuratively!
|
| I wonder too. I see you had to fiddle with things after the export.
| There's no chance totally new zones were created now, or visa versa?
| If so, do you have it covered in your doings?
|
| | --
| |
| | Gary S. Terhune
| | MS-MVP Shell/User
| |
| | "PCR" wrote in message
| | ...
| | "Gary S. Terhune" wrote in message
| | ...
| | | Note: http://support.microsoft.com/?kbid=931836 corrects some
| | | errors in the previous patches. I've nearly finished the updates
| | | to account for this and to add some features, but I won't be
| | | done until late tonight or tomorrow AM, Pacific time.
| |
| | Ah! Good! I hope that's their last update, though. So...
| |
| | You will run this update on an XP machine, & then export the
| | Registry key? That's how you do it, maybe reverting some of the
| | Registry values too (such as "Eastern Standard Time" back to just
| | "Eastern"? I guess that does it, then. Very good.
|
| --
| Thanks or Good Luck,
| There may be humor in this post, and,
| Naturally, you will not sue,
| Should things get worse after this,
| PCR
|

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR





  #63  
Old February 22nd 07, 11:21 PM posted to microsoft.public.win98.gen_discussion
PCR
External Usenet User
 
Posts: 4,396
Default Unofficial Time Zones Update (Testers wanted)

"Gary S. Terhune" wrote in message
...
| *I* am not adding a damned thing, except the MapID values. I
*subtracted* a
| bunch of stuff that's irrelevant to the legacy OSes. *Microsoft* added
the
| new Time Zones. Which is why people in other parts of the world need
to
| verify that they don't need an entirely new TZ setting instead of
using the
| same old one when they do the switcheroo.

So, for them, there might be more to do than to just update...

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Time Zones
&
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\TimeZoneInformation

....either for the purpose of the time change or time coordination or
something?

| Look at the damned Registry keys if you need to know more. Or just
look at
| the TZ tab in the Time/Date applet. They[re right there, assuming
you've
| applied the update(so).

I would expect Mexicans need to do nothing. I guess letting their keys
alone handles the time switch as before & coordination too. Why are you
or MS adding more?

| --
|
| Gary S. Terhune
| MS-MVP Shell/User
|
| "PCR" wrote in message
| ...
| Gary S. Terhune wrote:
| | Yes, at least ten totally new zones. For example, Mexico didn't
| | change their laws, so they're on the old DST schedule instead of
| | synched with ours. Thus, they need their own zones.
|
| I don't quite understand. Are you adding additional Mexico zones,
| instead of replacing the old ones? Then, how will Windows know which
to
| use in the Date/Time Properties requestor-- &/or anywhere else
Windows
| must use them?
|
| | And some place in
| | central Asia has segregated itself from Russia and its TZ
schedule.
| | Things like that.
|
| So? These will be new ones where none existed before? That hopefully
| will be OK. But I'm not sure I want a double set like you may be
doing
| with Mexico!
|
| | Those are the ones missing MapID values. Plus a bunch if info
that is
| | useful only to WinXP/2K3 "Dynamic Updates" (accounting for future
| | changes).
|
| I am pleased you have chosen to decontaminate these XP keys, as MGDX
may
| have not.
|
| | If you want to see the new ones, use the MGDX update on a fresh
| | Registry and look for the ones that have "Standard Time" added to
the
| | names and missing MapID value.
|
|
|
| | --
| |
| | Gary S. Terhune
| | MS-MVP Shell/User
| |
| | "PCR" wrote in message
| | ...
| | Gary S. Terhune wrote:
| | | Actually, I've *done* all that,
| |
| | Twice now, right? the second, to incorporate the hopefully final
MS
| | update of those zones?
| |
| | | and deleted a lot of crap that is only
| | | useful to XP machines. Plus adding several MapID's where MS
| | | couldn't be bothered. Gotta wonder which mop-wielding janitor
they
| | | saddled this project with. I mean that quite literally, not in
any
| | | way figuratively!
| |
| | I wonder too. I see you had to fiddle with things after the
export.
| | There's no chance totally new zones were created now, or visa
versa?
| | If so, do you have it covered in your doings?
| |
| | | --
| | |
| | | Gary S. Terhune
| | | MS-MVP Shell/User
| | |
| | | "PCR" wrote in message
| | | ...
| | | "Gary S. Terhune" wrote in message
| | | ...
| | | | Note: http://support.microsoft.com/?kbid=931836 corrects
some
| | | | errors in the previous patches. I've nearly finished the
updates
| | | | to account for this and to add some features, but I won't be
| | | | done until late tonight or tomorrow AM, Pacific time.
| | |
| | | Ah! Good! I hope that's their last update, though. So...
| | |
| | | You will run this update on an XP machine, & then export the
| | | Registry key? That's how you do it, maybe reverting some of
the
| | | Registry values too (such as "Eastern Standard Time" back to
just
| | | "Eastern"? I guess that does it, then. Very good.
| |
| | --
| | Thanks or Good Luck,
| | There may be humor in this post, and,
| | Naturally, you will not sue,
| | Should things get worse after this,
| | PCR
| |
|
| --
| Thanks or Good Luck,
| There may be humor in this post, and,
| Naturally, you will not sue,
| Should things get worse after this,
| PCR
|

|
|
|
|


  #64  
Old February 22nd 07, 11:54 PM posted to microsoft.public.win98.gen_discussion
Gary S. Terhune
External Usenet User
 
Posts: 1,846
Default Unofficial Time Zones Update (Testers wanted)

Here's the deal:

When you change the time zone, Windows reads the data from the chosen Time
Zones sub-key in
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Time Zones,
then writes that data to the one in CurrentControlSet. Mostly, it parses out
the "TZI" hex string into four parts and copies over the STD and DLT keys.

I can write a script that does that -- read what TZ is currently in use in
the CurrentControlSet, suck out the info from the HKLM\Software...Time Zones
sub-key, parse it out and write it back to the CurrentControlSet key. But if
the actual sub-key of HKLM\Software...Time Zones needs to be changed, as it
does for "Central Time (Mexico)" (which used to be plain old "Central Time")
and several others, then that trick doesn't work. Best one can do for
updating a bunch of machines in such a situation is to update one machine,
Export the CurrentControlSet\...\TimeZoneInformation key, then merge it into
all the machines that are in the same TZ, before or after updating the
machines with my patch or similar. So long as nobody messes with the
Date/Time applet, it really doesn't matter if the updates are applied or
not. They're only there to provide info to the applet when changes are made.
In legacy systems, anyway. In WinXP and up, there's much more to it than
that.

--
Gary S. Terhune
MS MVP -- Shell/User
http://grystmill.com/articles/cleanboot.htm
http://grystmill.com/articles/security.htm

"PCR" wrote in message
...
"Gary S. Terhune" wrote in message
...
| *I* am not adding a damned thing, except the MapID values. I
*subtracted* a
| bunch of stuff that's irrelevant to the legacy OSes. *Microsoft* added
the
| new Time Zones. Which is why people in other parts of the world need
to
| verify that they don't need an entirely new TZ setting instead of
using the
| same old one when they do the switcheroo.

So, for them, there might be more to do than to just update...

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Time Zones
&
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\TimeZoneInformation

...either for the purpose of the time change or time coordination or
something?

| Look at the damned Registry keys if you need to know more. Or just
look at
| the TZ tab in the Time/Date applet. They[re right there, assuming
you've
| applied the update(so).

I would expect Mexicans need to do nothing. I guess letting their keys
alone handles the time switch as before & coordination too. Why are you
or MS adding more?

| --
|
| Gary S. Terhune
| MS-MVP Shell/User
|
| "PCR" wrote in message
| ...
| Gary S. Terhune wrote:
| | Yes, at least ten totally new zones. For example, Mexico didn't
| | change their laws, so they're on the old DST schedule instead of
| | synched with ours. Thus, they need their own zones.
|
| I don't quite understand. Are you adding additional Mexico zones,
| instead of replacing the old ones? Then, how will Windows know which
to
| use in the Date/Time Properties requestor-- &/or anywhere else
Windows
| must use them?
|
| | And some place in
| | central Asia has segregated itself from Russia and its TZ
schedule.
| | Things like that.
|
| So? These will be new ones where none existed before? That hopefully
| will be OK. But I'm not sure I want a double set like you may be
doing
| with Mexico!
|
| | Those are the ones missing MapID values. Plus a bunch if info
that is
| | useful only to WinXP/2K3 "Dynamic Updates" (accounting for future
| | changes).
|
| I am pleased you have chosen to decontaminate these XP keys, as MGDX
may
| have not.
|
| | If you want to see the new ones, use the MGDX update on a fresh
| | Registry and look for the ones that have "Standard Time" added to
the
| | names and missing MapID value.
|
|
|
| | --
| |
| | Gary S. Terhune
| | MS-MVP Shell/User
| |
| | "PCR" wrote in message
| | ...
| | Gary S. Terhune wrote:
| | | Actually, I've *done* all that,
| |
| | Twice now, right? the second, to incorporate the hopefully final
MS
| | update of those zones?
| |
| | | and deleted a lot of crap that is only
| | | useful to XP machines. Plus adding several MapID's where MS
| | | couldn't be bothered. Gotta wonder which mop-wielding janitor
they
| | | saddled this project with. I mean that quite literally, not in
any
| | | way figuratively!
| |
| | I wonder too. I see you had to fiddle with things after the
export.
| | There's no chance totally new zones were created now, or visa
versa?
| | If so, do you have it covered in your doings?
| |
| | | --
| | |
| | | Gary S. Terhune
| | | MS-MVP Shell/User
| | |
| | | "PCR" wrote in message
| | | ...
| | | "Gary S. Terhune" wrote in message
| | | ...
| | | | Note: http://support.microsoft.com/?kbid=931836 corrects
some
| | | | errors in the previous patches. I've nearly finished the
updates
| | | | to account for this and to add some features, but I won't be
| | | | done until late tonight or tomorrow AM, Pacific time.
| | |
| | | Ah! Good! I hope that's their last update, though. So...
| | |
| | | You will run this update on an XP machine, & then export the
| | | Registry key? That's how you do it, maybe reverting some of
the
| | | Registry values too (such as "Eastern Standard Time" back to
just
| | | "Eastern"? I guess that does it, then. Very good.
| |
| | --
| | Thanks or Good Luck,
| | There may be humor in this post, and,
| | Naturally, you will not sue,
| | Should things get worse after this,
| | PCR
| |
|
| --
| Thanks or Good Luck,
| There may be humor in this post, and,
| Naturally, you will not sue,
| Should things get worse after this,
| PCR
|

|
|
|
|




  #65  
Old February 23rd 07, 12:46 AM posted to microsoft.public.win98.gen_discussion
PCR
External Usenet User
 
Posts: 4,396
Default Unofficial Time Zones Update (Testers wanted)

"Gary S. Terhune" wrote in message
...
| Here's the deal:
|
| When you change the time zone, Windows reads the data from the chosen
Time
| Zones sub-key in
| HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Time
Zones,
| then writes that data to the one in CurrentControlSet. Mostly, it
parses out
| the "TZI" hex string into four parts and copies over the STD and DLT
keys.
|
| I can write a script that does that -- read what TZ is currently in
use in
| the CurrentControlSet, suck out the info from the HKLM\Software...Time
Zones
| sub-key, parse it out and write it back to the CurrentControlSet key.
But if
| the actual sub-key of HKLM\Software...Time Zones needs to be changed,
as it
| does for "Central Time (Mexico)" (which used to be plain old "Central
Time")
| and several others, then that trick doesn't work.

I understand. Others could have been "Central Time" too, so you don't
know this one needs to be for Mexico. But can't you find out it is a
Mexican machine some other way? Let me see where United States is
mentioned in my Registry...

It's there 13 times, but apparently it's always in a list. That's no
help.

| Best one can do for
| updating a bunch of machines in such a situation is to update one
machine,
| Export the CurrentControlSet\...\TimeZoneInformation key, then merge
it into
| all the machines that are in the same TZ, before or after updating the
| machines with my patch or similar.

I think that MDGX site found a way to execute the Time/Date Properties
requestor. It says...

http://www.mdgx.com/add.htm#TZU
.......Quote.........
ALL Windows 95, 98 + ME users: at the end of installing this Unofficial
DST update you MUST confirm your Time Zone selection: when you see
Date/Time Properties you MUST click OK!
.......EOQ...........

Naturally, that still involves sitting at each machine to do that.

| So long as nobody messes with the
| Date/Time applet, it really doesn't matter if the updates are applied
or
| not. They're only there to provide info to the applet when changes are
made.
| In legacy systems, anyway. In WinXP and up, there's much more to it
than
| that.
|
| --
| Gary S. Terhune
| MS MVP -- Shell/User
| http://grystmill.com/articles/cleanboot.htm
| http://grystmill.com/articles/security.htm
|
| "PCR" wrote in message
| ...
| "Gary S. Terhune" wrote in message
| ...
| | *I* am not adding a damned thing, except the MapID values. I
| *subtracted* a
| | bunch of stuff that's irrelevant to the legacy OSes. *Microsoft*
added
| the
| | new Time Zones. Which is why people in other parts of the world
need
| to
| | verify that they don't need an entirely new TZ setting instead of
| using the
| | same old one when they do the switcheroo.
|
| So, for them, there might be more to do than to just update...
|
| HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Time
Zones
| &
|
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\TimeZoneInformation
|
| ...either for the purpose of the time change or time coordination or
| something?
|
| | Look at the damned Registry keys if you need to know more. Or just
| look at
| | the TZ tab in the Time/Date applet. They[re right there, assuming
| you've
| | applied the update(so).
|
| I would expect Mexicans need to do nothing. I guess letting their
keys
| alone handles the time switch as before & coordination too. Why are
you
| or MS adding more?
|
| | --
| |
| | Gary S. Terhune
| | MS-MVP Shell/User
| |
| | "PCR" wrote in message
| | ...
| | Gary S. Terhune wrote:
| | | Yes, at least ten totally new zones. For example, Mexico
didn't
| | | change their laws, so they're on the old DST schedule instead
of
| | | synched with ours. Thus, they need their own zones.
| |
| | I don't quite understand. Are you adding additional Mexico
zones,
| | instead of replacing the old ones? Then, how will Windows know
which
| to
| | use in the Date/Time Properties requestor-- &/or anywhere else
| Windows
| | must use them?
| |
| | | And some place in
| | | central Asia has segregated itself from Russia and its TZ
| schedule.
| | | Things like that.
| |
| | So? These will be new ones where none existed before? That
hopefully
| | will be OK. But I'm not sure I want a double set like you may be
| doing
| | with Mexico!
| |
| | | Those are the ones missing MapID values. Plus a bunch if info
| that is
| | | useful only to WinXP/2K3 "Dynamic Updates" (accounting for
future
| | | changes).
| |
| | I am pleased you have chosen to decontaminate these XP keys, as
MGDX
| may
| | have not.
| |
| | | If you want to see the new ones, use the MGDX update on a
fresh
| | | Registry and look for the ones that have "Standard Time" added
to
| the
| | | names and missing MapID value.
| |
| |
| |
| | | --
| | |
| | | Gary S. Terhune
| | | MS-MVP Shell/User
| | |
| | | "PCR" wrote in message
| | | ...
| | | Gary S. Terhune wrote:
| | | | Actually, I've *done* all that,
| | |
| | | Twice now, right? the second, to incorporate the hopefully
final
| MS
| | | update of those zones?
| | |
| | | | and deleted a lot of crap that is only
| | | | useful to XP machines. Plus adding several MapID's where MS
| | | | couldn't be bothered. Gotta wonder which mop-wielding
janitor
| they
| | | | saddled this project with. I mean that quite literally, not
in
| any
| | | | way figuratively!
| | |
| | | I wonder too. I see you had to fiddle with things after the
| export.
| | | There's no chance totally new zones were created now, or visa
| versa?
| | | If so, do you have it covered in your doings?
| | |
| | | | --
| | | |
| | | | Gary S. Terhune
| | | | MS-MVP Shell/User
| | | |
| | | | "PCR" wrote in message
| | | | ...
| | | | "Gary S. Terhune" wrote in message
| | | | ...
| | | | | Note: http://support.microsoft.com/?kbid=931836 corrects
| some
| | | | | errors in the previous patches. I've nearly finished the
| updates
| | | | | to account for this and to add some features, but I
won't be
| | | | | done until late tonight or tomorrow AM, Pacific time.
| | | |
| | | | Ah! Good! I hope that's their last update, though. So...
| | | |
| | | | You will run this update on an XP machine, & then export
the
| | | | Registry key? That's how you do it, maybe reverting some
of
| the
| | | | Registry values too (such as "Eastern Standard Time" back
to
| just
| | | | "Eastern"? I guess that does it, then. Very good.
| | |
| | | --
| | | Thanks or Good Luck,
| | | There may be humor in this post, and,
| | | Naturally, you will not sue,
| | | Should things get worse after this,
| | | PCR
| | |
| |
| | --
| | Thanks or Good Luck,
| | There may be humor in this post, and,
| | Naturally, you will not sue,
| | Should things get worse after this,
| | PCR
| |

| |
| |
| |
| |
|
|
|
|


  #66  
Old February 23rd 07, 02:48 AM posted to microsoft.public.win98.gen_discussion
Gary S. Terhune
External Usenet User
 
Posts: 1,846
Default Unofficial Time Zones Update (Testers wanted)

All MDGX is doing is automatically launching the Date/Time applet. Not a bad
idea, but I prefer the instructions being auto-presented. Can only shove so
much into a user's face before they get terminally confused (if you'll
pardon the pun.)

--

Gary S. Terhune
MS-MVP Shell/User

"PCR" wrote in message
...
"Gary S. Terhune" wrote in message
...

I think that MDGX site found a way to execute the Time/Date Properties
requestor. It says...

http://www.mdgx.com/add.htm#TZU
......Quote.........
ALL Windows 95, 98 + ME users: at the end of installing this Unofficial
DST update you MUST confirm your Time Zone selection: when you see
Date/Time Properties you MUST click OK!
......EOQ...........

Naturally, that still involves sitting at each machine to do that.



  #67  
Old February 23rd 07, 08:41 PM posted to microsoft.public.win98.gen_discussion
PCR
External Usenet User
 
Posts: 4,396
Default Unofficial Time Zones Update (Testers wanted)

Yea. OK. I wonder, did you carefully compare your Registry changes
against the MDGX ones? And were they the same, except possibly
for...?...

(a) Some values names.
(b) The addition of MapID's.
(c) The subtraction of XP/Vista stuff irrelevant to Win98/ME/2K.

I should take in your finalized one shortly. But really I need to
replace McAfee before fooling with anything else!


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR

"Gary S. Terhune" wrote in message
...
| All MDGX is doing is automatically launching the Date/Time applet. Not
a bad
| idea, but I prefer the instructions being auto-presented. Can only
shove so
| much into a user's face before they get terminally confused (if you'll
| pardon the pun.)
|
| --
|
| Gary S. Terhune
| MS-MVP Shell/User
|
| "PCR" wrote in message
| ...
| "Gary S. Terhune" wrote in message
| ...
|
| I think that MDGX site found a way to execute the Time/Date
Properties
| requestor. It says...
|
|
http://www.mdgx.com/add.htm#TZU
| ......Quote.........
| ALL Windows 95, 98 + ME users: at the end of installing this
Unofficial
| DST update you MUST confirm your Time Zone selection: when you see
| Date/Time Properties you MUST click OK!
| ......EOQ...........
|
| Naturally, that still involves sitting at each machine to do that.
|
|
|


  #68  
Old February 24th 07, 04:14 AM posted to microsoft.public.win98.gen_discussion
Gary S. Terhune
External Usenet User
 
Posts: 1,846
Default Unofficial Time Zones Update (Testers wanted)

I did not compare to the more recent offering from MDGX. Only did that the
last time around. I compared to a WinXP machine with the changes already
made. MDGX did the same, had to have. Or used the info directly from the KB
articles, which is less trustworthy, IMO. And I made no changes to Value
names, only to Key names. Let's keep our terms correct, OK, s.

--

Gary S. Terhune
MS-MVP Shell/User

"PCR" wrote in message
...
Yea. OK. I wonder, did you carefully compare your Registry changes
against the MDGX ones? And were they the same, except possibly
for...?...

(a) Some values names.
(b) The addition of MapID's.
(c) The subtraction of XP/Vista stuff irrelevant to Win98/ME/2K.

I should take in your finalized one shortly. But really I need to
replace McAfee before fooling with anything else!


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR

"Gary S. Terhune" wrote in message
...
| All MDGX is doing is automatically launching the Date/Time applet. Not
a bad
| idea, but I prefer the instructions being auto-presented. Can only
shove so
| much into a user's face before they get terminally confused (if you'll
| pardon the pun.)
|
| --
|
| Gary S. Terhune
| MS-MVP Shell/User
|
| "PCR" wrote in message
| ...
| "Gary S. Terhune" wrote in message
| ...
|
| I think that MDGX site found a way to execute the Time/Date
Properties
| requestor. It says...
|
|
http://www.mdgx.com/add.htm#TZU
| ......Quote.........
| ALL Windows 95, 98 + ME users: at the end of installing this
Unofficial
| DST update you MUST confirm your Time Zone selection: when you see
| Date/Time Properties you MUST click OK!
| ......EOQ...........
|
| Naturally, that still involves sitting at each machine to do that.
|
|
|




  #69  
Old February 24th 07, 06:29 PM posted to microsoft.public.win98.gen_discussion
PCR
External Usenet User
 
Posts: 4,396
Default Unofficial Time Zones Update (Testers wanted)

"Gary S. Terhune" wrote in message
...
| I did not compare to the more recent offering from MDGX. Only did that
the
| last time around. I compared to a WinXP machine with the changes
already
| made. MDGX did the same, had to have. Or used the info directly from
the KB
| articles, which is less trustworthy, IMO. And I made no changes to
Value
| names, only to Key names. Let's keep our terms correct, OK, s.

When you changed XP's "Eastern Standard Time" back to "Eastern", for
instance, that was... yea, you are right, a key name change. And, yea,
they all were key name changes, if they only were changes of the
sub-keys to...
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Time Zones

Well, all right, I guess you've got it all covered. It's a little
disconcerting that neither you nor MDGX may precisely match the values
in the MS article, but I haven't the time to do a full-scale
investigation. Probably, going with the ultimate actual changes to the
XP machine of the TZI values is the correct way. OK, then. OK, bye. That
was an impressive write-up on the issue, too, at your site.


| --
|
| Gary S. Terhune
| MS-MVP Shell/User
|
| "PCR" wrote in message
| ...
| Yea. OK. I wonder, did you carefully compare your Registry changes
| against the MDGX ones? And were they the same, except possibly
| for...?...
|
| (a) Some values names.
| (b) The addition of MapID's.
| (c) The subtraction of XP/Vista stuff irrelevant to Win98/ME/2K.
|
| I should take in your finalized one shortly. But really I need to
| replace McAfee before fooling with anything else!
|
|
| --
| Thanks or Good Luck,
| There may be humor in this post, and,
| Naturally, you will not sue,
| Should things get worse after this,
| PCR
|
| "Gary S. Terhune" wrote in message
| ...
| | All MDGX is doing is automatically launching the Date/Time applet.
Not
| a bad
| | idea, but I prefer the instructions being auto-presented. Can only
| shove so
| | much into a user's face before they get terminally confused (if
you'll
| | pardon the pun.)
| |
| | --
| |
| | Gary S. Terhune
| | MS-MVP Shell/User
| |
| | "PCR" wrote in message
| | ...
| | "Gary S. Terhune" wrote in message
| | ...
| |
| | I think that MDGX site found a way to execute the Time/Date
| Properties
| | requestor. It says...
| |
| |
http://www.mdgx.com/add.htm#TZU
| | ......Quote.........
| | ALL Windows 95, 98 + ME users: at the end of installing this
| Unofficial
| | DST update you MUST confirm your Time Zone selection: when you
see
| | Date/Time Properties you MUST click OK!
| | ......EOQ...........
| |
| | Naturally, that still involves sitting at each machine to do
that.
| |
| |
| |
|
|
|
|


  #70  
Old February 24th 07, 07:05 PM posted to microsoft.public.win98.gen_discussion
Gary S. Terhune
External Usenet User
 
Posts: 1,846
Default Unofficial Time Zones Update (Testers wanted)

My values precisely match what the UPDATES install. Which is what matters,
since I trust the Updates more than I do the authors of the articles -- at
least, I used to...

--

Gary S. Terhune
MS-MVP Shell/User

"PCR" wrote in message
...
"Gary S. Terhune" wrote in message
...
| I did not compare to the more recent offering from MDGX. Only did that
the
| last time around. I compared to a WinXP machine with the changes
already
| made. MDGX did the same, had to have. Or used the info directly from
the KB
| articles, which is less trustworthy, IMO. And I made no changes to
Value
| names, only to Key names. Let's keep our terms correct, OK, s.

When you changed XP's "Eastern Standard Time" back to "Eastern", for
instance, that was... yea, you are right, a key name change. And, yea,
they all were key name changes, if they only were changes of the
sub-keys to...
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Time Zones

Well, all right, I guess you've got it all covered. It's a little
disconcerting that neither you nor MDGX may precisely match the values
in the MS article, but I haven't the time to do a full-scale
investigation. Probably, going with the ultimate actual changes to the
XP machine of the TZI values is the correct way. OK, then. OK, bye. That
was an impressive write-up on the issue, too, at your site.


| --
|
| Gary S. Terhune
| MS-MVP Shell/User
|
| "PCR" wrote in message
| ...
| Yea. OK. I wonder, did you carefully compare your Registry changes
| against the MDGX ones? And were they the same, except possibly
| for...?...
|
| (a) Some values names.
| (b) The addition of MapID's.
| (c) The subtraction of XP/Vista stuff irrelevant to Win98/ME/2K.
|
| I should take in your finalized one shortly. But really I need to
| replace McAfee before fooling with anything else!
|
|
| --
| Thanks or Good Luck,
| There may be humor in this post, and,
| Naturally, you will not sue,
| Should things get worse after this,
| PCR
|
| "Gary S. Terhune" wrote in message
| ...
| | All MDGX is doing is automatically launching the Date/Time applet.
Not
| a bad
| | idea, but I prefer the instructions being auto-presented. Can only
| shove so
| | much into a user's face before they get terminally confused (if
you'll
| | pardon the pun.)
| |
| | --
| |
| | Gary S. Terhune
| | MS-MVP Shell/User
| |
| | "PCR" wrote in message
| | ...
| | "Gary S. Terhune" wrote in message
| | ...
| |
| | I think that MDGX site found a way to execute the Time/Date
| Properties
| | requestor. It says...
| |
| |
http://www.mdgx.com/add.htm#TZU
| | ......Quote.........
| | ALL Windows 95, 98 + ME users: at the end of installing this
| Unofficial
| | DST update you MUST confirm your Time Zone selection: when you
see
| | Date/Time Properties you MUST click OK!
| | ......EOQ...........
| |
| | Naturally, that still involves sitting at each machine to do
that.
| |
| |
| |
|
|
|
|




 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Win98 Daylight Savings Time Manual Update Required-- reminder 2 PCR General 46 January 21st 07 05:15 PM
i this error: the windows update servers are temp unavailable - Win98 Maurice N ~ MVP General 4 March 2nd 06 05:20 PM
Windows ME Update Order PA Bear General 12 November 14th 05 03:26 AM
Install Knox Perifs [email protected] General 3 September 12th 05 09:02 PM
Can't update time. Alos MSCONFIG can't update registery DSHIPMAN General 2 May 31st 04 08:43 PM


All times are GMT +1. The time now is 07:40 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.