Forum Home
Press F1
 
Thread ID: 19655 2002-05-20 09:19:00 PC clock Guest (0) Press F1
Post ID Timestamp Content User
49786 2002-05-20 09:19:00 Running Win XP home edition and Office XP on a new (less than 3 mths old) Dell P4, 1.7, 256 RAM etc etc. and NO matter what I do to reset the clock it is always out of sync.
I've ticked the box to have the clock automatically sync with an internet time server (in our time zone) and it's presently saying sync'd at 7.40pm when in fact it's 8.25pm and the PC clock is saying 12.45pm.

Any suggestions??
Thanks
Jane
Guest (0)
49787 2002-05-20 09:35:00 Um, this may be a bit insulting, but do you have your timezone set for NZ under the Date and Time Timezone tab?

John
Guest (0)
49788 2002-05-20 09:40:00 No insult taken but yes, I'm not that stupid!! I checked that aleady!

A friend suggested it may be the battery in the CMOS???

Jane
Guest (0)
49789 2002-05-20 11:15:00 Take it back to the seller and make them fix it as you would have paid plenty of good money for it - you just don't need something that is faulty.

Read the fine print before opening the machine and changing the battery, as it may void your total warantee.
Guest (0)
49790 2002-05-21 04:23:00 First it's NOT a timezone problem. Timezones are by *hours*. They change every 15 degrees of 'the vertical lines on the globe'.

You should set the BIOS ('battery') time. The OS time is set to the value that the battery clock has when you boot up. If the battery is failing, the time is the first symptom. It might slow down. It might speed up. Depends on the oscillator characteristics. It might he a little fast or slow, anyway, because it is controlled by a miniature 32768Hz crystal. That can be a bit off the nominal value. See if you can get the right time at boot time, anyway. That is faily important. Then try using the net time again.

I don't know how the net time programme you use works, but it might try to set the BIOS time, then the OS time. It might fail if your antivirus software objects to a programme talking to the world and *changing the BIOS*. It might object to the same thing happening to an OS setting. Check log files for eeevidence of this sort of thing.
Guest (0)
49791 2002-05-21 09:10:00 Thanks for all your suggestions. Checking them out as we speak.
Jane
Guest (0)
1