XP Keeps Changing My Timezone

  • Thread starter Thread starter zbud
  • Start date Start date
Z

zbud

XP keeps changing my timezone to Brasilia (GMT -3) from US Eastern
(GMT -5).

I have changed the internet time sync to various recommendations in
this group and even turned off the sync feature but this still
happens.

How can I FIX this ?

Thanks

Bud
 
if you go via control panel to "date and time" then to "internet time" tab,
there is below it a link called..learn more about time synchronisation from
help and support...which shows about 6 possible problems and solutions(eg if
there is a firewall involved or that one has to be connected to the
internet)....I do not know if any of ttose might be relevant?
 
if you go via control panel to "date andtime" then to "internettime" tab,
there is below it a link called..learn more abouttimesynchronisation from
help and support...which shows about 6 possible problems and solutions(eg if
there is a firewall involved or that one has to be connected to the
internet)....I do not know if any of ttose might be relevant?







- Show quoted text -
Click to expand...

It is the time zone itself that keeps changing. It's syncing correctly
but to the wrong time zone.

Someone pls help !!

Bud
 
In control panel date and time, have you selected the correct time zone?
What did you select? Where are you located?
 
In control panel date andtime, have you selected the correcttimezone?








- Show quoted text -
Click to expand...

I'm in US Eastern Standard (GMT -5) it keeps resetting to Brasilia
(GMT -3)
 
Did you try changing the date and time in the BIOS? Then also try changing
the same in the Control Panel.
 
i saw your previous messages about the tock time server and had
already done that. The sync part works fine it's just that the time
zone keeps changing

Bud
 
After changing the time zone in the window of date and time, are you sure
you click apply? Are you connected to a LAN?
 
BIOS is in read-only memory. Depending on hardware, the BIOS can be changed
using special techniques, but it never changes during normal use of a
system. The date and time however do change during normal use, especially
the time.

The date and time are stored in a Real Time Clock (RTC) chip in the system
(mother) board. The RTC's date and time values can be changed by the BIOS,
but the date and time are in a location separate from the BIOS, not in the
BIOS.

The RTC's date and time are a shared resource, such as the keyboard, the
display and physical (non-virtual) memory. Windows cannot allow applications
direct access to shared resources; instead, direct access to devices are
always done using a device driver. Therefore Windows cannot allow an
application to use the BIOS to change the date and time. Windows has a
device driver that is used to access the RTC.

The date and time that the BIOS changes is the same date and time that the
Control Panel changes. Application programs can change the date and time
using the SetSystemTime API function but that function does essentially the
same thing as what the control panel does. They all result in use of the
device driver.
 
Sam thanks for very ensightful reply, but the date and time are
accurate and are being synced correctly, the problem is is the
changing time zone. Any thoughts on that ??

Bud
 
I cannot help much except to suggest things that might be obvious.

There are utilities for monitoring registry changes. I am not familiar with
specifics but perhaps something such as that would help. If you can
determine when a change is made then that might be a big clue.

If you go to the TechNet Script Cener you might find a sample script for
monitoring the registry. I am not sure of that and I don't want to waste
your time but it might be worthwhile to look there.

Perhaps you could limit access to that key using security permissions and
the see what does not work.

Other people that have more experience as administrators might know if it is
possible to audit the registry for chagnes and do it by specifying a key or
something such as that. You might be able to determine what the program is
by logging relevant activity.
 
Back
Top