Apparently you are missing that there is a Rosetta specific preference for work unit runtime. You view and set this for each venue on the project website. The BOINC Manager does not show project specific values.

So... are you using a 6.6.x version of BOINC? If so, what is shown in the properties for the Rosetta task for CPU time used and how does that compare to the elapsed time?

I am running BOINC 6.6.20, and Rosetta Mini 1.75, and I still have to periodically restart my computer to force Rosetta to reset itself. What is the solution?

---

For some reason, probably known to the Boinc Developers but not to us users, this happens and the only thing to do is what you did. It has happened before, probably will happen again, and happens across many projects. This brings it down to a Boinc thing, not a project or user thing. Somehow, for some reason, Boinc forgets what it is doing and just kinds cruises thru not doing any crunching but accumulating clock time. As you said though, usually only on one unit of a multi-core machine. Not every unit, just some and not often enough to debug the problem by the ordinary user!

...except that it only happens with Rosetta.

Ummm not exactly, as I said I have seen it on other projects too. From my stats you can see I did not too much Rosetta but have done lots in other places. I have seen this on other projects too.

---

Apparently you are missing that there is a Rosetta specific preference for work unit runtime. You view and set this for each venue on the project website. The BOINC Manager does not show project specific values.

So... are you using a 6.6.x version of BOINC? If so, what is shown in the properties for the Rosetta task for CPU time used and how does that compare to the elapsed time?

I am running BOINC 6.6.20, and Rosetta Mini 1.75, and I still have to periodically restart my computer to force Rosetta to reset itself. What is the solution?

Does your Darwin computer do it too or just the Windows computer? I didn't see the problem when my Linux computers were crunching.

---

Does your Darwin computer do it too or just the Windows computer? I didn't see the problem when my Linux computers were crunching.

Only the Windows computer. The Mac has no problems...

---

...except that it only happens with Rosetta.

Ummm not exactly, as I said I have seen it on other projects too. From my stats you can see I did not too much Rosetta but have done lots in other places. I have seen this on other projects too.

Well, yes, exactly. Only Rosetta, and only on the Windows (Vista) machine.

---

Given that we've had to discuss problems with this and that about Rosetta, its interfacing with BOINC, and the ongoing Rosetta Mini fiasco to this extent... in my own famous words, what is going on here?

Are we contributing to research, or are we turning into alpha testers of Rosetta programs that happen to be trying to run projects as an afterthought? This is 2009; there should be, for example, no question about a program's compatibility across multiple, modern platforms. Vista, XP, 2000, Linux... someone should have figured this all out long ago and made WU's and the project itself watertight in this regard. So Vista is a clunker... well, tough... you want compatibility, make it happen!

Something else: you release a new version of something when it's ready. You release an improved version of same when IT'S ready. Looking at the Mini timetable on its version log thread, I see 4 versions, one after another. They have new features, claim to fix bugs, and on and on. Four of them inside of a couple months! Who's throwing this stuff out here? Is it necessary? And why aren't the problems with the main module and CPU interface, like calculations ceasing, being addressed? Is someone at Rosetta writing a new line of code and proclaiming, "New version 1.xx! Eureka, our problems are solved!"?

We as volunteers deserve better than having to putz around waiting for some new solution du jour to fix the latest bug. We didn't sign on to keep re-setting and starting/stopping BOINC just to keep this tin lizzy moving. I don't see this dynamic playing itself out anywhere else, and I mentioned in another, earlier post that if this kept up, I would detach...

Which I am. I've gone to POEM and returned the unfinished WU's to Rosetta. Someone please let me know when the Rosetta people figure out whatever it is that every other project seems to have... when they can get a program running that actually runs! I haven't the time or patience for such imperfections... and my flops agree...

Sorry to have to go, for now... but I want to do crunching without worries, and I by God will. There are plenty of good projects on BOINC that don't make you upset due to shoddy coding, which is all this is... I have used computers since 1978. I have seen the effects of bad registries, poor motherboards, lack of memory, and crappy code. This is crappy code, and I won't associate myself with it. Let me know when it's prudent to return, and why... Cesium...

---

The lovely lady you see isn't I, but Hayley Westenra, a classical crossover singer from Christchurch, NZ. There is no known voice as hers. Check her out- she's seraphic.

I have to agree. Once again, after restarting the Windows computer twice yesterday, Rosetta is back down to 50% instead of 100% CPU usage. So I'm going to detach the Windows machine from Rosetta - the Mac is handling Rosetta just fine.

Hey Rosetta! Let me know when it's safe to re-attach!

---

Am I the only one w/o serious problems with Rosetta?

The worst that has happened so far was with version 1.75 that failed validation... but that's mostly it.

---

Am I the only one w/o serious problems with Rosetta?

The worst that has happened so far was with version 1.75 that failed validation... but that's mostly it.

I only have the problem with the Windows machine. A 3 hour work unit appears to intermittently be taking over 6 hours.

---

I only have the problem with the Windows machine. A 3 hour work unit appears to intermittently be taking over 6 hours.

I've had them go 8, 9 hours with no end in sight. Windows? It may not be perfect, but it's the BMOC, and you have to work with it. Linux and Apple are not the bad boys on the block... Bill Gate$ and Micro$oft are. Like it or not, that's what most of us run, and if interfacing with the OS is Rosetta's problem, well, it's Rosetta's problem... not mine. Again, all the other projects, including POEM, seem to be running great on King Bill's Windows...

So why mess about with a prog that doesn't cut the mustard?

---

The lovely lady you see isn't I, but Hayley Westenra, a classical crossover singer from Christchurch, NZ. There is no known voice as hers. Check her out- she's seraphic.

So I abort the running Rosetta work, and Boinc won't let me detach from the project, so I could only "Allow no new tasks" and "Suspend". Anyone know why I can't Detach? This is a Boinc thing, because I couldn't Detach from any projects if I wanted to...

---

deleted

So I abort the running Rosetta work, and Boinc won't let me detach from the project, so I could only "Allow no new tasks" and "Suspend". Anyone know why I can't Detach? This is a Boinc thing, because I couldn't Detach from any projects if I wanted to...

Are you running any other projects on the Windows machine? If not just go to add/remove programs and dump Boinc and then reinstall. I have never had the problem of being unable to detach before. If you go the dumping route make sure you delete all directories related to Boinc before reinstalling or you might find your old stuff still there after you reinstall. Boinc is sneaky, like all Windows programs.

---

The Windows machine is running Seti, Seti Beta Test, Poem, Docking, and Boincsimap, all with no problems. Rosetta is the only project with the cpu usage problem.

---

The Windows machine is running Seti, Seti Beta Test, Poem, Docking, and Boincsimap, all with no problems. Rosetta is the only project with the cpu usage problem.

I just don't know why you can't detach from Rosetta, as long as all the existing units are gone you should be able to detach. But you can go to the Projects tab and set Rosetta to Suspend, that will prevent any new work from coming your way and also stop all crunching of existing Rosetta units.

---

I just don't know why you can't detach from Rosetta...

I say this totally respectfully, as I am addressing the programmers of Rosetta: it's because their programs have more errors in them than the 1985 Los Angeles Dodgers infield. I told you, shoddy code... of course nobody's going to know why you can't detach... not unless Rosetta will open their source code and present it to the community, preferably compiled -and- decompiled. Otherwise, you'll continue to have program cancer, which Rosetta ironically tries to treat :p You've already seen the metastasis in some areas...

Call up Rosetta directly and tell them your issues... they have a damn good concept. It's a pity they're wasting away time and resources on poor computation coding...

---

The lovely lady you see isn't I, but Hayley Westenra, a classical crossover singer from Christchurch, NZ. There is no known voice as hers. Check her out- she's seraphic.

Before we get too critical of programmers, could I ask the folks in this thread that are having such problems to report their BOINC versions and system types?

michaelmastro said they are running BOINC 6.6.20 on Windows. Are others that are having CPU usage problems using a v6.6 version of BOINC? The programmers at Berkeley are working to correct a number of problems they've introduced in that version.

---

Rosetta Moderator: Mod.Sense

I just don't know why you can't detach from Rosetta...

I say this totally respectfully, as I am addressing the programmers of Rosetta: it's because their programs have more errors in them than the 1985 Los Angeles Dodgers infield. I told you, shoddy code... of course nobody's going to know why you can't detach... not unless Rosetta will open their source code and present it to the community, preferably compiled -and- decompiled. Otherwise, you'll continue to have program cancer, which Rosetta ironically tries to treat :p You've already seen the metastasis in some areas...

Call up Rosetta directly and tell them your issues... they have a damn good concept. It's a pity they're wasting away time and resources on poor computation coding...

Most of us run Rosetta without issues - I've got machines running that I installed BOINC on nearly three years ago on which BOINC/Rosetta hasn't been touched since. I know it's frustrating when it doesn't work but in the vast majority of cases it does.

---

I'm having this issue occasionally with Rosetta on my dual-core x64 Vista machine. Not frequently enough to warrant detaching, but enough to warrant leaving a message.

Got the same problem on both Athlon X2-computers a couple of days ago. Interestingly time keeps running, but no (or almost no) cpu-utilization.