I right now have a WU with 37 hrs left on LaptopII. I see that I have the SETI WU, and three other WU's from other projects, one running, two "waiting to run".

I further see nothing new coming in "waiting to start".
I normally have a nice queue of WU's waiting to start.

If SETI's 37 hours left to run it the reason that nonde of my other projects are getting anything in to the queue, SETI will be toast.

>>RSM

---

http://sciencespringe.wordpress.com
http://facebook.com/sciencesprings

I right now have a WU with 37 hrs left on LaptopII. I see that I have the SETI WU, and three other WU's from other projects, one running, two "waiting to run".

I further see nothing new coming in "waiting to start".
I normally have a nice queue of WU's waiting to start.

If SETI's 37 hours left to run it the reason that nonde of my other projects are getting anything in to the queue, SETI will be toast.

>>RSM

Your laptop reports being "Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz"...
I would expect much better performance if that information is correct.

I right now have a WU with 37 hrs left on LaptopII. I see that I have the SETI WU, and three other WU's from other projects, one running, two "waiting to run".

I further see nothing new coming in "waiting to start".
I normally have a nice queue of WU's waiting to start.

If SETI's 37 hours left to run it the reason that nonde of my other projects are getting anything in to the queue, SETI will be toast.

>>RSM

If BOINC has bad values for the amount of time your machine is crunching, or a bad benchmark time, or the Duration Correction Factor, etc., it will appear that work is going to take longer than it actually will.

... and it may appear to be under deadline pressure, which stops downloading more work.

The easy fix is to just watch it and see what happens. This is especially true if that 37 hour number is decreasing faster than "wall time" -- not uncommon.

This has nothing to do with SETI per-se, and everything to do with BOINC.

If you leave it alone, it will eventually return to more reasonable values.

If you're impatient, I'm sure there are folks who will help you fix the client_state.xml file.

-- Ned

---