I haven't even crunched a hole workunit... and I've trien some of them.. I think when I switch between projects... and rossetta removes from memory... an error happens. Anyone has the same problem?

---

I haven't even crunched a hole workunit... and I've trien some of them.. I think when I switch between projects... and rossetta removes from memory... an error happens. Anyone has the same problem?

Yes.. ;) It's better to leave Rosetta in memory. Then you don't loose the in-between steps of the processing.

---

Grrrrrrrrreetings from the Lazy Cat...

I haven't even crunched a hole workunit... and I've trien some of them.. I think when I switch between projects... and rossetta removes from memory... an error happens. Anyone has the same problem?

Yes.. ;) It's better to leave Rosetta in memory. Then you don't loose the in-between steps of the processing.

Jemand der keine Ahnung von BOINC hat (und der nichts gegen Cheater unternimmt), sollte keine Ratschläge erteilen.

greetz littleBouncer

Jemand der keine Ahnung von BOINC hat (und der nichts gegen Cheater unternimmt), sollte keine Ratschläge erteilen.

greetz littleBouncer

Please, folks. I'd prefer that we kept a 'supportive' environment for everyone, experienced or not. After all, if we held such a strict constraint throughout everything, what would most people have to talk about?

---

There are a few problems with Rosetta@Home doing a hard stop halt. One of the cases seems to be related to restarting.

Since I my computers have at least 1G RAM, I have always used "leave in memory". This setting seems to help some people.

If you are continuing to get these hard stops, more details helps. Yes, the developers can chase down the data in your account. But, a summary of the computer CPU. RAM, speed, overclock or no, messages in the messages tab, exactly what seems to cause the halt ...

The more information you can provide, the easier it is for people to help you.

---

Paul --

This "hard stop error" you refer to also occurs during the stoppage of Rosetta so the benchmark test program can run. I know that Climate Predictor had this problem in the past - did they ever get it fixed for their process? If so, maybe a similar method might work for Rosetta ....

---

Paul --

This "hard stop error" you refer to also occurs during the stoppage of Rosetta so the benchmark test program can run. I know that Climate Predictor had this problem in the past - did they ever get it fixed for their process? If so, maybe a similar method might work for Rosetta ....

I was not aware of that. It certainly is possible that there is something similar going on. The current problem with CPDN and the benchmark is that BOINC does not give CPDN enough time to halt before it gives up. This is supposed to be addressed in the newer clients.

One of the big qustions there is if Rosetta@Home is a "Compound Application", if so, the CPDN problem may be related.

*MY* experience with CPDn is for no problems on Windows XP for 7 systems running 24/7 with essentially no operator interaction. WIth OS-X, I can't even get the models to start. Which HAD been a worry for me as I could only run 3 project on the PowerMac and was worried about loss of work. But, with SZTAKI and Rosetta@Home, I am good to go now with 5 projects on the PowerMac.

Now, I am debating lowering Predictor@Home's resource share ... probably won't ... but thinking about it ...

---