I am running one or two other projects in addition to Rosetta under Boinc Manager. Every time Rosetta relinquishes the processor to another BOINC project, it seems to reset the next time around and start pretty much all over. For example, during its last cycle, it reported that it had worked for 3 1/2 hours on the WU, and now it says it worked just over 2. The time to completion also steadily increases as the WU goes on. I checked for errors, but Rosetta isn't reporting any. Einstein and SETI are cranking out results, while this project seems to languish. I also checked to ensure I'm not working one of the declared bad work units. If it's working and the time on the display is wrong, or even if I'm not getting credit for really big work units, fine. I just want to make sure I'm not wasting clock cycles on this project that could be put to better use on the other projects if there is an error.

---

A) Please post all questions in "Number Crunching", as that is checked at least hourly by someone who could help, while this area is only checked every few days (thus the "read me before posting" saying this...) because of a lack of volunteers to check these areas.

B) On the website, Your Account, General Preferences, "Leave applications in memory when preempted", set that to "yes" instead of "no". Rosetta only checkpoints at the 10% intervals, so switching out causes it to "reset" to that point, AND, there is a known bug that they're still chasing, where if it gets switched out at the wrong time, it gives an error. On OS X, there's no "down side" to setting that value to "yes".

---