So maybe everytime my BOINC client contacted the SETI@home server my edit is away?

No, every time that the client restarts that info is rewritten. The CPU detection only happens at BOINC start-up, just as GPU detection only happens at that time.

How do you manage to edit client_state without restarting BOINC? ;-)

That's easy, but it's useless. The only time BOINC reads clent_state.xml is at startup. Sorry, Sutaru.

                                                               Joe

Unless you're suffering from this particular problem, I wouldn't advise anybody to change their BOINC version just because of this status change. v6.10.43 is much better for general use than v6.10.18

Of course, if you have a CUDA card with limited RAM or an OS which uses a lot of VRAM, you may need to change, but the VRAM requirements of SETI/CUDA shouldn't ever be a problem if your card has 512MB or above.

I have not had any problems with 6.10.43 with CUDA

But I am experiencing a weird problem with the CPU processing.

With 4 WUs running simultaneously on a very busy quad, when a task completion time gets close to the deadline, that task does not go into high priority, but the task with the shortest completion time does start running high priority!

If the time situation worsens, then the task with the next shortest completion time goes high priority as well!

And same again!

Has anyone else seen this?

---

Flying high with Team Sicituradastra.

With 4 WUs running simultaneously on a very busy quad, when a task completion time gets close to the deadline, that task does not go into high priority, but the task with the shortest completion time does start running high priority!

If the time situation worsens, then the task with the next shortest completion time goes high priority as well!

And same again!

Has anyone else seen this?

Yes, this bug should hopefully be fixed in v6.10.45 and later, but there's been one report later-on (but without specifying version), but still it's possibly another bug was hiding under the fixed one...

---

I have been running 6.10.43 for a while now, and I had my cache set for 5 days. I used the Reschedule tool, and it has taken me close to two weeks to deplete my cache. It should completely deplete sometime this evening or tonight. Other than that I have not had any ather issues. My GPU was crashing WU's even with 6.10.18, so the crash bug introduced in 6.10.25 didn't seem to be my main problem. I did run out of GPU work over a week ago, most likely due to the rescheduler. The good thing was that with no GPU work, I had no errors, and my system completed a virus scan last night without rebooting.

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website