Warning

 

Close
Confirm Action

Are you sure you wish to do this?

Cancel Confirm
AR15.COM
4/19/2006 9:19:46 AM EDT
I just checked my clock on windows and it says that it is 5:50 ES.  That is not what my watch says and I know that is right because it matches the clocks here at school.

I updated it and it still is off.  Why would this be doing this?

The time zone is right.
4/19/2006 9:23:00 AM EDT
[#1]
battery going bad..
4/19/2006 9:24:24 AM EDT
[#2]

Quoted:
battery going bad..



I am on a power cord.  And no my battery is not bad.
4/19/2006 9:25:13 AM EDT
[#3]
CMOS battery
4/19/2006 9:26:13 AM EDT
[#4]

Quoted:
CMOS battery



What he said.
4/19/2006 9:27:46 AM EDT
[#5]

Quoted:

Quoted:
battery going bad..



I am on a power cord.  And no my battery is not bad.



4/19/2006 9:28:02 AM EDT
[#6]

Quoted:
I just checked my clock on windows and it says that it is 5:50 ES.  That is not what my watch says and I know that is right because it matches the clocks here at school.

I updated it and it still is off.  Why would this be doing this?

The time zone is right.



Canadian Daylight Savings time. Jennifer Granholm (Canadian Governess of Michigan) decreed it from her throne, all the while blaming the Engler leadership for the budget deficit, racial tensions, the ash borer problem, and the hairball her cat puked on her new shoes.

/it's probably the battery on your motherboard
4/19/2006 9:28:15 AM EDT
[#7]
the watch size battery on your motherboard
4/19/2006 9:30:07 AM EDT
[#8]

Quoted:

Quoted:
battery going bad..



I am on a power cord.  And no my battery is not bad.



Right... In that case its eather a PEBCAK or ID10T Error.. Thats all the help I can give..
4/19/2006 9:32:45 AM EDT
[#9]

Quoted:
CMOS battery



How so? I the computer is on and I JUST updated the time.  Does this battery run the clock when the computer is on?
4/19/2006 9:35:17 AM EDT
[#10]

Quoted:

Quoted:

Quoted:
battery going bad..



I am on a power cord.  And no my battery is not bad.



Right... In that case its eather a PEBCAK or ID10T Error.. Thats all the help I can give..


Thanks.  This was a place to start.
4/19/2006 9:40:25 AM EDT
[#11]

Quoted:

Quoted:

Quoted:
battery going bad..



I am on a power cord.  And no my battery is not bad.



Right... In that case its eather a PEBCAK or ID10T Error.. Thats all the help I can give..



HAA!
4/19/2006 9:45:18 AM EDT
[#12]
Even if the CMOS battery is dead, the computer will still hold time, assuming the computer is not shut off.  

4/19/2006 9:50:10 AM EDT
[#13]
Aliens.
4/19/2006 9:51:19 AM EDT
[#14]
It's George Bush's fault
4/19/2006 9:53:02 AM EDT
[#15]
Mine did that the other day and after awhile it reset itself !
4/19/2006 9:56:45 AM EDT
[#16]

Quoted:
It's George Bush's fault



It's true.

George Bush has altered all of the Windows clocks so he can help the CIA spy on American citizens who are doing nothing wrong.
4/19/2006 10:04:34 AM EDT
[#17]
Oh crap my clock stops and losing time to. If the battery does go bad will it still work as a computer?
4/19/2006 10:07:56 AM EDT
[#18]

Quoted:

Quoted:
CMOS battery



What he said.



I concur
4/19/2006 10:19:12 AM EDT
[#19]

Quoted:
Oh crap my clock stops and losing time to. If the battery does go bad will it still work as a computer?
 




No it won't work at all I'll stop buy and take it off your hands, for a fee. Are you intrested in buying some beach front property?

4/19/2006 10:28:25 AM EDT
[#20]
Most likely you have something that looks like this on you motherboard.



Very simple fix. Just replace it. Note: if your jack is the type that has a metal arm across the top of the battery holding it in, be very careful in getting the battery out because if you snap the arm off you are screwed.  Also note if you have a store bought computer the chances of losing custom BIOS setting required for the computer to run are minimal. If someone “made” the computer for you god knows what he has done in the BIOS and you could encounter problems.

good luck


ETA: I didn't comprehend it was a laptop. So you will more then likley need more than good luck. probably a c note and a compUSA...
4/19/2006 10:38:14 AM EDT
[#21]

Quoted:
Most likely you have something that looks like this on you motherboard.

members.cox.net/lesinaz/pics/86910.jpg

Very simple fix. Just replace it. Note: if your jack is the type that has a metal arm across the top of the battery holding it in, be very careful in getting the battery out because if you snap the arm off you are screwed.  Also note if you have a store bought computer the chances of losing custom BIOS setting required for the computer to run are minimal. If someone “made” the computer for you god knows what he has done in the BIOS and you could encounter problems.

good luck


Its a notebook, I dont think it will be easy for him
4/19/2006 11:48:51 AM EDT
[#22]
The CMOS battery keeps the CMOS energized when the machine is powered down.. It dying isn't enough reason to freak out.  

On a laptop, I wouldn't bother to replace the battery UNLESS it was under an easy access panel on the bottom or something.  I've used a number of machines with dead mobo batteries, and the time issue you're experiencing is about the only downside.  You can get freeware windows apps that will automatically update the system clock from the internet (I used to use one called AtomTime.  It's way out of date, but still does everything it's supposed to, even in XP).

Now.. once the time is set, the machine shouldn't lose it's time again until you shut it down.
4/19/2006 11:51:20 AM EDT
[#23]
If your on a network, the server can set your clock. I worked on a machine that kept setting the time ahead two hours I couldnt figure it out. I would set the clock back to the right time, then 15 minutes later it was two hours fast. Finally I found the culprit a Windows 2000 Server that had the wrong time on it.
4/19/2006 6:38:02 PM EDT
[#24]

Quoted:
If your on a network, the server can set your clock. I worked on a machine that kept setting the time ahead two hours I couldnt figure it out. I would set the clock back to the right time, then 15 minutes later it was two hours fast. Finally I found the culprit a Windows 2000 Server that had the wrong time on it.



No shit.  I can't believe everyone fixated on the friggin CMOS battery.  If it's a home machine, he probably has it set to update via NIST or time.windows.com.

4/19/2006 7:34:37 PM EDT
[#25]

Quoted:

Quoted:
If your on a network, the server can set your clock. I worked on a machine that kept setting the time ahead two hours I couldnt figure it out. I would set the clock back to the right time, then 15 minutes later it was two hours fast. Finally I found the culprit a Windows 2000 Server that had the wrong time on it.



No shit.  I can't believe everyone fixated on the friggin CMOS battery.  If it's a home machine, he probably has it set to update via NIST or time.windows.com.

i3.tinypic.com/vyxea0.jpg



Thanks!! That must be what it is.  It never lost the time. It just kept resetting it to a different time(3 hours ahead).
4/19/2006 7:39:50 PM EDT
[#26]

Quoted:

Quoted:

Quoted:
If your on a network, the server can set your clock. I worked on a machine that kept setting the time ahead two hours I couldnt figure it out. I would set the clock back to the right time, then 15 minutes later it was two hours fast. Finally I found the culprit a Windows 2000 Server that had the wrong time on it.



No shit.  I can't believe everyone fixated on the friggin CMOS battery.  If it's a home machine, he probably has it set to update via NIST or time.windows.com.

i3.tinypic.com/vyxea0.jpg



Thanks!! That must be what it is.  It never lost the time. It just kept resetting it to a different time(3 hours ahead).



WELL???? WTF is the results of that one?

4/19/2006 7:50:31 PM EDT
[#27]
Pull up an MSDOS prompt and type in TIME <ENTER> then immediatly compare it against the time in the lower right systray, if the BIOS time is different than the WINDOWS SYSTRAY time you probably need a new CMOS battery.

If they are the same and you still are having clock problems we need to know your OS.  There are several different antivirus programs that can affect certain windows os systems.