"DaffyDŽ" wrote in message
...
"Gary S. Terhune" none wrote in message
...
"DaffyDŽ" wrote in message
...
"Gary S. Terhune" none wrote in message
...
"DaffyDŽ" wrote in message
...
"Franc Zabkar" wrote in message
...
On Thu, 18 Sep 2008 18:04:27 -1600, "DaffyDŽ"
put
finger to keyboard and composed:
"Franc Zabkar" wrote in message
.. .
These are your original headers as I see them:
================================================== ==========
Date: Wed, 17 Sep 2008 20:40:05 -1600
================================================== ==========
Your time zone appears to be set for GMT-16 hours (?) whereas
Pacific
Daylight Time (PDT) is GMT-7 (USA & Canada).
Here are the headers from my email sent moments ago:
Date: Thu, 18 Sep 2008 17:56:44 -1600
You still have a problem. What Time Zone do you see when you
double-click the clock in the Systray?
- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.
(GMT-8:00) Pacific Time (US & Canada); Tijuana.
Which means your clock should read UTC -7. Because we're still on
Daylight
time. See my reply to Franc, at 2:27 Pacific Daylight Time, for a fix.
Or
just go to my site and follow the trail.
--
Gary S. Terhune
MS-MVP Shell/User
http://grystmill.com
I did more fiddling around with TZ Edit and D4 and my system clock is
now
synch'd with my watch. Hopefully the headers for this message should be
accurate.
Looks fine to me. But it bothers me that using my update file didn't fix
the
issue immediately, or didn't you try it without D4 in the mix? Without D4
being involved, the updater should have fixed the issue and I'd be very
interested to know if that wasn't the case. I don't know of any mechanism
in
Win98 that would change that Registry key or its sub-keys.
Turns out that the most recent update to the TZ info in WinXP and above
was
released a month ago.
http://support.microsoft.com/kb/951072/
I'll be updating my files tomorrow, Sunday, but don't be surprised if
it's
Monday or even Tuesday before I upload everything. The very first and
only
monitor I ever bought for myself was a ViewSonic A75s, a CRT with "short
depth" dimensions. Spent the better part of its life powered up and
serving
as my primary monitor. More recently it's been attached to whatever
machine
happens to need it, usually my test machine. Well, when I cranked it up
this
morning it started doing a snap, crackle, pop like it wanted to
reincarnate
as an arc welder, so I've got to drag a used monitor out of the shed
tomorrow. Kinda sad, actually. that monitor had great color. IIRC,
there's
not much left in the shed that will work decently enough, or be "short"
enough to fit on my desk. Gotta see if any of my "clients" have any flat
panels that need to be "recycled". Might have to buy a new one. That's
revolting.
Forgot to ask more about TZ Edit. Does it run in the background, like D4,
or only when I click the executable? I'm still not sure how it works. Do I
need D4 if TZ Edit is already on my computer? Or does your registry fix
also
negate the need for a time synchonization program?
TZEdit is a simple wizard that allows you to edit the data in
HKLM\Software\Microsoft\Windows\CurrentVersion\Tim e Zones. It does not run
in the background, it doesn't sync your clock.
My patch is likewise passive. It's intended purpose is to simply update
pre-XP Windows systems to account for changes in the onset and finish dates
of Daylight Savings Time. I only injected it here because I saw that it
could be useful for recovering from your specific (and AFAIK rare) issue. If
D4 had been uninstalled before using my patch, and if my patch actually
completed (I'd do it manually to be certain, using the REG file and
restarting the system,) I'm almost 100% sure that the clock would have been
restored to like-new (and updated) Time Zone info. It's almost certain that
D4 that gave you all the grief, and based upon this event, alone, I'd stop
using D4. Period. I haven't got the time, right now, to attempt repeating
your issue, but I suspect the addition of Windows 2K/XP/2003 support to D4
somehow left the 9x part in an unstable state. It's either that, or your
system was already unstable and/or overly tweaked.(?) Find another app to do
the job. If it doesn't have it's own scheduler running in the background,
see if it's a good candidate for Task Scheduler. Just have to know the
command-line switches.
--
Gary S. Terhune
MS-MVP Shell/User
http://grystmill.com