|
|
|
|
![]() ![]() |
Nov 3 2006, 03:39 AM
Post
#1
|
|
|
NiGHTFoX - Hiding in the dark Group: Members Posts: 680 Joined: 3-April 05 Member No.: 3,584 |
I'm also experincing this issue on my desktop and my laptop. I'm wondering if there's some crappy update MS released that is really screwing up the system clocks?
Everytime I reboot my system, CMOS and Windows says it's 6:44 (or 6 whatever) PM when it is really 10:44 PM. I'll reset the time in CMOS as well and boot into Windows to find it is 6:44 AGAIN! In SuSE, the time is correct! I'm having a similar issue on my laptop! WTF is going on?!? I've NEVER had anything crazy as this happen before! [N]F |
|
|
|
Nov 3 2006, 04:29 AM
Post
#2
|
|
|
Advanced Member Group: Members Posts: 112 Joined: 3-November 06 From: USA, CA, Los Angeles Member No.: 16,947 |
I'm also experincing this issue on my desktop and my laptop. I'm wondering if there's some crappy update MS released that is really screwing up the system clocks? Everytime I reboot my system, CMOS and Windows says it's 6:44 (or 6 whatever) PM when it is really 10:44 PM. I'll reset the time in CMOS as well and boot into Windows to find it is 6:44 AGAIN! In SuSE, the time is correct! I'm having a similar issue on my laptop! WTF is going on?!? I've NEVER had anything crazy as this happen before! [N]F Umm I don't think that windows is messed up becasue their are two time servers that are setup on your system. Try the following - Go to Time and Date Properties then go to Internet Time, make sure that a check box tittled "Automaticall synch with an Internet Time Server" is checked and select "time.nist.gov" Its also correct, you might also want to run Update. If that does not help, it might be because you are using the wrong time zone. Hope this helps. Anyways i don't and have never had any problems. I'll come back to this post to try to help you out if that does not work. See ya |
|
|
|
Nov 3 2006, 01:31 PM
Post
#3
|
|
|
Super Member Group: [HOSTED] Posts: 658 Joined: 12-July 06 From: Ontario, Canada Member No.: 14,464 |
Please verify:
1. Do you have the correct time zone? 2. Correct date on calendar? 3. If on Windows XP, synchronization with Internet Time Server "time-a.nist.gov"? 4. All security patches and updates applied? You can get Windows updates at http://update.microsoft.com It would help to check those and also tell us the version of Windows you are using. |
|
|
|
Nov 6 2006, 08:43 PM
Post
#4
|
|
|
Super Member Group: [HOSTED] Posts: 522 Joined: 25-April 05 Member No.: 4,374 |
I don’t know of any patches for this. If nothing else works you may want to change your CMOS battery. It’s a long shot but worth trying.
|
|
|
|
Nov 7 2006, 05:39 PM
Post
#5
|
|
|
Way Out Of Control - You need a life :) Group: [MODERATOR] Posts: 1,980 Joined: 16-August 05 Member No.: 7,896 |
I don’t know of any patches for this. If nothing else works you may want to change your CMOS battery. It’s a long shot but worth trying. If it's a CMOS battery problem, it has to false the same way with Windows or with Linux. And it's correct with Linux. So I think it's not a hardware battery problem, it's something else. |
|
|
|
Nov 7 2006, 10:27 PM
Post
#6
|
|
|
Member [ Level 1 ] Group: Members Posts: 46 Joined: 18-October 06 Member No.: 16,664 |
If it's a CMOS battery problem, it has to false the same way with Windows or with Linux. And it's correct with Linux. So I think it's not a hardware battery problem, it's something else. Besides that, if the problem were at CMOS battery, i think BIOS will halt for checksum failure (not pretty sure, but i recall that both CMOS and Real Time Clock reside into the same chip, so if there is a decay at the battery voltage, the RTC chip would reset all CMOS values. |
|
|
|
Nov 8 2006, 08:34 AM
Post
#7
|
|
|
Way Out Of Control - You need a life :) Group: [MODERATOR] Posts: 1,980 Joined: 16-August 05 Member No.: 7,896 |
Besides that, if the problem were at CMOS battery, i think BIOS will halt for checksum failure (not pretty sure, but i recall that both CMOS and Real Time Clock reside into the same chip, so if there is a decay at the battery voltage, the RTC chip would reset all CMOS values. Not sure. I had often had battery problem on the computer clock, and the date and time simply disappeared at each system powerdown. And no BIOS halt due to checksum failure, because it's not a checksum error or a fatal error, it's only a local time possible error, but we could also really be January 1st 1970, so the hardware has to be able to boot today. |
|
|
|
Nov 9 2006, 01:28 AM
Post
#8
|
|
|
Colonel Panic Group: [MODERATOR] Posts: 2,731 Joined: 25-March 05 From: Toronto, Ontario, Canada Member No.: 3,233 |
Make sure that SuSE's time is not UTC and set to be "local time".
Windows only operate under "local time" and not "UTC". Linux/UNIX default is "UTC". xboxrulz |
|
|
|
Nov 9 2006, 01:08 PM
Post
#9
|
|
|
Way Out Of Control - You need a life :) Group: [MODERATOR] Posts: 1,980 Joined: 16-August 05 Member No.: 7,896 |
Sorry, but what is UTC ? Unified Techical Collapsus ?
|
|
|
|
Dec 14 2006, 04:57 AM
Post
#10
|
|
|
Super Member Group: [HOSTED] Posts: 658 Joined: 12-July 06 From: Ontario, Canada Member No.: 14,464 |
UTC = Universal Time Coordinates
GMT = Greenwich Mean Time That is the basic time zone located in England which is used to determine the time in each time zone region throughout the world. Is the problem fixed yet? |
|
|
|
![]() ![]() |
Similar Topics
|
Lo-Fi Version | Time is now: 6th September 2008 - 08:25 PM |