Every now and then something sets my computer clock back up to several years. When I reset the clock, the report deadline for Climatepredictions then gets set to the old clock setting - eg 13/12/1901. Anybody know how I can correct the report deadline (and stop the clock being corrupted)? Thanx

---

Your battery on the MB that saved the clock information is probably getting low, and needs replacing. This happens every so often. Most are easy to remove and replace, but some are not.

I know there is a fix for the date on the WU, and it\'s hidden somewhere in these forums, but since I\'ve never had this issue, I am unsure where to look.

---

If you\'re only running the one project, the deadline date doesn\'t matter. But I would still recommend you fix your clock if you can, since it\'s likely to mess up other programmes on your PC. As Pooh Bear suggests, there\'s usually a standard watch battery attached to the PC\'s motherboard, these are fairly cheap to replace, but it can be fiddly.

---

I'm a volunteer and my views are my own.
News and Announcements and FAQ

Thanx for all your help - I changed the report_deadline tag in client_state and client_state_prev. I don\'t think it\'s a battery problem as it only seems to happen when the boinc einstein is running!

---

Thanx for all your help - I changed the report_deadline tag in client_state and client_state_prev. I don\'t think it\'s a battery problem as it only seems to happen when the boinc einstein is running!

Is the Windows Time service running? If so, it may be connecting to a time server that\'s set wrong. Stop and disable the service, or configure it to talk to a realy NTP server, such as us.pool.ntp.org.

Otherwise, I don\'t know.