Core ver. 4.13, seti@home 4.05. Since upgrading to 4.05 my CPU time for each work unit has increased dramatically. Example: 95.64% completion with 97:25:21 hours CPU time. I used to complete a work unit in a 1/3 of the time. Running WinME Pentium III & 128 MB ram. Why is this happening & how can I correct?

---

Nothing youy can do about it.

The new Seti Client processes the WUs differently. Everyone has been similarly affected by the Seti version upgrade

---

> The new Seti Client processes the WUs differently. Everyone has been
> similarly affected by the Seti version upgrade

Everyone running Windows x86 is similarly affected by this SETI version upgrade. If you notice, Linux x86 users, Mac users, and SPARC users are all running SETI v 4.02.

You shouldn’t be running intensive scrutiny tests on one platform, and medium scrutiny tests on all the others. It just doesn’t make for good science and it doesn’t make sense!

We still haven’t gotten any explanation on why SETI v4.05 takes significantly longer to process a WU. I hope that the source of this bug is found and fixed. There are natural variations in how long it takes to complete one work unit to another, but even when checking the processing time on the identical sample test WU, v 4.05 takes longer than v 4.02!!

---

> Nothing youy can do about it.
>
> The new Seti Client processes the WUs differently. Everyone has been
> similarly affected by the Seti version upgrade
>

No idea what you mean. Does it perform more complex calculations so that the results are more valuable? In this case, why did not the developers do the same with other platforms clients? Or if the science behind 4.02 is different and even worth, is not the computation time and results wasted comapred to "new" 4.05?

Or if there is a bug in 4.05... does it mean the WUs are processed differently?

If there is a bug. it is 100% sure, all the results from the same WU are the same with 4.02 and 4.05? If they are, what is the difference caused by?

I think all these questions are legitimate and your "Nothing youy can do about it." is totally unacceptable for me, sorry.

And of course as the upload problems were solved, this is going to be teh most important issue now. But unfortunately, the team does not communicate...

---