I was about 24 hours into my first run, when I had to flash my bios, which also entailed clearing the cmos and time/date.

When I came back up, and before I could stop it, climate prediction started to run, and shortly therafter popped up and said, \"this unit is passed due, and you may want to abort it\". I just suspended it, and fixed the time and date, and then when I restarted boinc manager, it said the cpn work was due in 1905, and got right to work...

I reset the project, and started a new one, because I didn\'t want it taking 100% of crunching time.

This may be a boinc bug, or specific to cpn, I\'m not sure.

It could be reproduced easily enough, by exiting boinc, and setting the date to 0-0-0, or something, and firing up boinc again.

Don

It's a known issue with BOINC.

In common with a lot of software it doesn't handle the date and time going back very well. There has been some discussion of this problem on the BOINC development mailing list in relation to NTP time synchronisation. The plan is to make the BOINC client use the PC tick count instead of the time for its time related operations (work scheduling, benchmarking, deadlines. etc).
<br><a href="http://www.teampicard.net/"><img src="http://www.teampicard.net/images/picardmini.gif"></a><a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/team_display.php?teamid=3">Join us here</a>