Hello All,

On my Pentium M laptop I'm getting the following message....

13/09/2006 17:05:26|SETI@home|Requesting 429761 seconds of new work
13/09/2006 17:05:31|SETI@home|Scheduler request succeeded
13/09/2006 17:05:31|SETI@home|Message from server: No work sent
13/09/2006 17:05:31|SETI@home|Message from server: (won't finish in time) Computer on 51.0% of time, BOINC on 99.3% of that, this project gets 100.0% of that

All was fine before the outage at the weekend I would have a queue of about 5 to 6 work units now it won't go any higher than one!

Any clues?

As an addendum:

It's just downloaded a new work unit and it's reporting a time to completion of 600:15:30 which is going down by about 5 minutes evey second.... what??? the blazzers is going on???

---

http://www.boincstats.com/signature/user_74302.gif

Did you have a forced/ungraceful shutdown over the weekend? Mostly likely one or more performance parameters got messed up and BOINC is temporarily thinking the machine is a lot slower than it really is. What was the Computer On percentage before this happened?

It should straighten itself out in a few days to a week or so if left to it's own.

<edit> The very high Time to Completion is the hint that got me thinking along these lines. Usually that gets caused by a really low benchmark coming in, which does happen once in awhile for various reasons.

Alinator

Hello All,

On my Pentium M laptop I'm getting the following message....

13/09/2006 17:05:26|SETI@home|Requesting 429761 seconds of new work
13/09/2006 17:05:31|SETI@home|Scheduler request succeeded
13/09/2006 17:05:31|SETI@home|Message from server: No work sent
13/09/2006 17:05:31|SETI@home|Message from server: (won't finish in time)
Computer on 51.0% of time, BOINC on 99.3% of that, this project gets 100.0% of that

All was fine before the outage at the weekend I would have a queue of about 5 to 6 work units now it won't go any higher than one!

Any clues?

Have a look at your DCF (Duration Correction Factor - at the bottom of 'Your Computer' listing on this website, just above location). If it's gone much above 1, that would explain it - BOINC thinks that your machine is running much slower than its rating. Nothing you can do about it, it will gradually correct itself over the next 20 - 30 WUs.

Another possibility is that it happened to run benchmarks at an inconvenient moment, and got a very low answer. Check what BOINC thinks your speeds are, and if they seem low, re-run benchmarks manually when nothing else is active (and when the laptop is on mains power, and not when it's overheated after a heavy work session).

---

Ah,

Explains a lot, it did decide to re-boot after a windows update and I did have a benchmark time out due to the thing being in the middle of backup cycle verification (very CPU intensive). Thanks to the both of you for striking the match of enlightenment.

---

http://www.boincstats.com/signature/user_74302.gif

Yeah - I had this after a power cut. The estimated times went through the roof.

Unfortunately, mine didn't correct itself after many more units so a quick reinstall sorted that.

At times computers can be immensely dumb, I find. But then sometimes, my dogs outshine me with their intelligence ...

---

Was that with a 5x version? I had the refusing to correct eventually happen with 4x, but not any of the recent versions.

Alinator

Yeah - it was only a few weeks ago so it would have been a recent version. Sorted now, so no issue. I left it for a while to try to sort it, but the estimated times never came down, so I just reinstalled and job done!

---

You can alway manually edit your client state file. Just look for the duration_correction_factor tags and reset to 1.000000. Boinc must be closed down to do this. Oh, and be sure your are changing the duration_correction_factor for the correct project if you are attached to more than one. You might want to force a run benchmarks once you restart.

---

At times computers can be immensely dumb, I find.

"To err is to be human, but to really foul up something takes a computer!"

:)

At times computers can be immensely dumb, I find.

"To err is to be human, but to really foul up something takes a computer!"

:)

No, computers are neither dumb nor smart. They blindly follow the instructions given them via code. And very quickly, I might add. For better or worse.
To err is human, only programmers can make it worse.........

---

"Time is simply the mechanism that keeps everything from happening all at once."

No, computers are neither dumb nor smart. They blindly follow the instructions given them via code. And very quickly, I might add. For better or worse.
To err is human, only programmers can make it worse.........

That's what I was going to say! My Uncle had a calculator with a very rare error that couldn't find Pi properly (kept coming up with the wrong number). Was it the calculator's fault because it didn't "know" the right answer? Or was it the human's fault for causing a programming error?

---

No, computers are neither dumb nor smart. They blindly follow the instructions given them via code. And very quickly, I might add. For better or worse.
To err is human, only programmers can make it worse.........

That's what I was going to say! My Uncle had a calculator with a very rare error that couldn't find Pi properly (kept coming up with the wrong number). Was it the calculator's fault because it didn't "know" the right answer? Or was it the human's fault for causing a programming error?

Probably a machine-human interface error (otheriwse known as a loose nut behind the keyboard). One pixel short of a full screen, ya know?

---

"Time is simply the mechanism that keeps everything from happening all at once."

Probably a machine-human interface error (otheriwse known as a loose nut behind the keyboard). One pixel short of a full screen, ya know?

B42? Bingo!

---

OHS (operator head space)

Well excuse me for trying to inject a bit of humour into the forum, sheesh!!

:(

Well excuse me for trying to inject a bit of humour into the forum, sheesh!!

:(

Your bit of humor was well taken, we just expanded upon it a tad.

---

"Time is simply the mechanism that keeps everything from happening all at once."

OHS (operator head space)

PICNIC (Problem in chair, not in computer)

---

OHS (operator head space)

PICNIC (Problem in chair, not in computer)

Cf. “BMS error”: one whose cause lies Between Monitor & Seat.

---