| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 25131 | 2002-09-26 21:10:00 | xp loses time | sasha (400) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 83569 | 2002-09-26 21:10:00 | hi i have a one month old computer with xp. it seems to lose time, up yo half an hour a day, i can update it bu synconsihing but hen it loses it again, but my other xp computer doesnot, bad battery? or someting else, thanks Simon | sasha (400) | ||
| 83570 | 2002-09-26 22:09:00 | If it's only one month old, take it back to who you bought it from and get them to fix it under warranty. It does sound like a dud battery, so they might need to replace it. Mike. |
Mike (15) | ||
| 83571 | 2002-09-26 22:13:00 | I agree. Never muck around with something under warranty. You pay for it is your purchase price anyway. Give the retailer the headache! BALDY:-) |
Baldy (26) | ||
| 83572 | 2002-09-27 02:54:00 | Hi Sasha, the battery only effects the realtime clock keeping it right while the machine is switched off. Once windows is loaded the screen clock down in the righthand corner is maintained by windows. If windows is very busy with background activities it misses some timer interupts and the clock looses time, coming right again the next time you load windows. If the clock is not right at load time then you may have a battery problem. Have a look at this MS known error:- support.microsoft.com |
Peter Cox (544) | ||
| 83573 | 2002-09-27 04:42:00 | Hi Sasha, Have you tried double clicking the time on the task bar then goto 'Time Zone' tab? |
shockwave (1089) | ||
| 83574 | 2002-09-27 05:24:00 | The battery clock runs all the time, but it is loaded into the OS only at boot time. After that, the OS maintains it, using an interrupt 18.2 times a second. If you are short of memory, the swapping which goes on can cause the clock interrupts to be missed. Perhaps you have too many programmes started. The timezone isn't going to make any difference. |
Graham L (2) | ||
| 83575 | 2002-09-27 10:33:00 | Is the computer on a network. The College that I'm at uses a Linux server and Win2k workstations. At the start of the year the network had only just been setup (I use that word loosely). The time was always out by a considerable amount. We'd set it right and reboot (or logoff and logon) and the time would be out again. It ended up being that the time zones were configured as Arizona. So win2k was correcting the time from the server for Arizona. Set the time zone to NZ and all was well. |
-=JM=- (16) | ||
| 83576 | 2002-09-27 22:11:00 | > The timezone isn't going to make any difference. It is if it's set to the wrong time zone, and you're using NTP to set the "correct" time, as it'll set the time to the appropriate time-zone, which could explain why it's always out. Mike. |
Mike (15) | ||
| 83577 | 2002-09-28 04:37:00 | Not by "half an hour". Timezones go by full hours. | Graham L (2) | ||
| 83578 | 2002-09-28 04:48:00 | Not quite true there Graham L: New Foundland GMT -3:30 Tehran GMT +3:30 Kabul GMT +4:30 Chennai,Kolkata,Mumbai,New Delhi GMT +5:30 Kathmandu GMT +5:45 Rangoon GMT +6:30 Adelaide, Darwin GMT +9:30 Babe. |
Babe Ruth (416) | ||
| 1 2 | |||||