Hello,

me and nearly all people i know from the ESL Team have the same problem:

If the PC get restarted Boinc begins at 0 % with calculating. Even when the result reached 90 %, after a restart it becomes 0 %

Sorry for my bad english.

Can anybody help me?

Did you check the runtime? If it's still as it was before restarting, everything is ok, the percentage will catch back.

If the runtime is 0min 0 sec, there's something wrong, please check this.

---

I have the same prob and elapsed time / time remaining get resetted, too.

this is a known problem with Rosetta 5.59. The checkpointing is working ok apparently, so it's only the % that's restarting, and as Tom posted, and it will catch back up to where it should be if you let it.

However, if the CPU time is also restarting then work is being lost. Of course, work done since the last checkpoint will always be lost following a restart.

HTH
Danny

P.S. I hope ESL can keep up the good work!

---

just out of curiosity, would it be possible to include a save button to create a check point manually before restarting either ROH or windows?

this is a known problem with Rosetta 5.59. The checkpointing is working ok apparently, so it's only the % that's restarting, and as Tom posted, and it will catch back up to where it should be if you let it.

However, if the CPU time is also restarting then work is being lost. Of course, work done since the last checkpoint will always be lost following a restart.

HTH
Danny

P.S. I hope ESL can keep up the good work!

---

...would it be possible to include a save button to create a check point manually?

Nope. But they are talking about checkpointing about every 5 minutes, if your preferences allow BOINC to write to disk that often. And so that would mean on average you'd only lose 150 seconds. So, hopefully that's even BETTER then the manual system you suggest, because it would be happening for everyone, not just those that know to perform a manual step first.

---

Rosetta Moderator: Mod.Sense

since ESL members often tune or overclock, is it possible that both of you tuned the shutdown of windows to accelerate it? It could cause the WU to be lost or resetted, try to close Boinc manually before restarting.

---

thx for the hint, I actually use XP-Antispy and there is an option called "Quick Shutdown"

I'll test it later, whether it helps turning this option off or not

...would it be possible to include a save button to create a check point manually?

Nope. But they are talking about checkpointing about every 5 minutes, if your preferences allow BOINC to write to disk that often. And so that would mean on average you'd only lose 150 seconds. So, hopefully that's even BETTER then the manual system you suggest, because it would be happening for everyone, not just those that know to perform a manual step first.

So the write to disk every X minutes is the saving of a data checkpoint to the drive? So by changing your settings to write to disk every 60 seconds for instance is doing what?

---

As with many things BOINC, it is a control over how much BOINC uses your machine. So, if projects are honoring the settings, it allows you to LIMIT the amount of disk access performed (not counting the swap space). However, it doesn't work the other way around. I mean setting a low value doesn't CAUSE disk writes, or checkpoints to occur.

My understanding is that the Project Team is working on changes that will make checkpointing about every 5 minutes possible. If your preference were set to write at most every 20 minutes, then you'd be getting a checkpoint roughly every 20 minutes. If your preference were set to write to disk at most every 1 minute, you'd still only get a checkpoint when Rosetta is able to do so, about every 5 minutes.

---

Rosetta Moderator: Mod.Sense

I'v got the same problem.
All the processing task return to 0% which have been calculated for hours after system restarted. What a bug!!

It's just for the display and doesn't actually mean work was lost. The cpu time is the best indicator of work done. This minor but seemingly major bug has been fixed in the next release that is currently being tested on ralph.

fine. good 2 know :)

OT question: are there any beta versions of boinc? ;)

It's just for the display and doesn't actually mean work was lost. The cpu time is the best indicator of work done. This minor but seemingly major bug has been fixed in the next release that is currently being tested on ralph.

fine. good 2 know :)

OT question: are there any beta versions of boinc? ;)

It's just for the display and doesn't actually mean work was lost. The cpu time is the best indicator of work done. This minor but seemingly major bug has been fixed in the next release that is currently being tested on ralph.

yes, you can download them here:
http://boinc.berkeley.edu/download_all.php

I tested the most recent ones, they are very buggy, I wouldn't recommend anyone to use them for real production.

---