IT Employment

General discussion


Problem with the clock

By mattw ·
I have a user who's clock at the bottom right of his screen gkeeps falling behind. I have tried installing Tardis and configuring, and disabling the Energy Saver mode, but the problem keeps happening. Any suggestions?


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Problem with the clock

by Kevin Reetz In reply to Problem with the clock

Is it a new PC? What about the battery? That would be my first choice.

Good luck!


Collapse -

Have seen this before

by SheilaU In reply to Problem with the clock

We have had same issue - try going into Control Panel and going into Regional settings. Go to Time tab, and make sure time style is set to hh:mm:ss:tt - that seems to correct the issue. Good luck!!

Collapse -


by mattw In reply to Have seen this before

Hi ~

Thanks for the insight, although what does the :tt stand for?


Collapse -

Determines AM or PM

by SheilaU In reply to Reply

According to the help in that function, the :tt dictates AM or PM, so the clock does not just read 9:41, it reads 9:41 PM. Hope that helps!!

Collapse -

CMOS Battery

by toltec58 In reply to Have seen this before

yup, I'd check the battery.

G Luck!

Collapse -

Battery problem

by alex In reply to Problem with the clock

I have had that problem before and it has been the battery is starting to fail. Even in a newr PC I have seen some bad batteries. I agree you should start there.


Collapse -

Hate to even say this one...

by Brian Lusk In reply to Problem with the clock

First off, try all the hardware items listed in previous posts first. You might also check to see if the latest MS Windows patches might fix it up as well. If you can't replace the failing hardware, you might just create a login script for the computers that have the problem, and use the NET TIME command to synchronize with a server on the network.

Now, on to this: I hate to even mention this one, because I am not convinced that this problem even exists.

I read an article some time back about a problem with computer clocks in the year 2000. According to the article, the extra time required to calculate the 4 digit year caused a slow-down in the clock of the computer.

Personally, my response is "Yeah Right", but I thought it would be interesting to bring up.

Brian Lusk

P.S. Mention of this is in NO WAY a personal endorsement of the supposed problem, but is merely an interesting tidbit I ran across. My personal feelings is that this "problem" is a purely theoretical one that has little or no basis in fact. I recommend that, should you desire to persue it further, you research the web and find it, since that is how I found it.

Collapse -

Check time on Server!

by rzan In reply to Hate to even say this one ...

I have this problem at home. Since I am running a home network, I have seen the clock on my Win98 machine drift off by 15 minutes or so. After some carefull investigation, I notices that the time on my server was off by that much. Don't forget that when you are on a network, the time on your machine is set by the server. If the clock on the server is off, then the whole network will synchronize the wrong time with the server. The server doesn't care what time it is, as long as everyone hasthe same time displayed.

Collapse -

I was thinking of something else...

by Brian Lusk In reply to Check time on Server!

I was actually thinking of a company server, but in reality PC time doesn't synchronize with the server unless you actually issue a command to do so (at least on Windows-based networks).

I have machines at work that are as much as one or two hours off, and I have to manually reset the time (about once every year, that is). I use the time synchronization with a server when I can't go ahead and replace the affected hardware.

Brian Lusk

Collapse -

clock slow down

by rlepage In reply to Hate to even say this one ...

The y2k clock issue was not that the clock slowed down but that the time in the clock buffer wasn't valid when it was read. If the chip was single buffered it was possible to read the time frome the buffer before it was completely loaded. The chipdesigners cheated and set the valid flag before the buffer was loaded as there was plenty of time to load the buffer before it was read again. Then cpu speeds increased and this time window was no longer there. Double buffered chips do not have this problem, there is always a valid buffer to read. The problem shows up mostly on machines that are power cycled frequently. The system reads the time from CMOS on startup and then free runs until it is booted again.

Related Discussions

Related Forums