http://setiathome.berkeley.edu/result.php?resultid=362363368


<core_client_version>5.5.0</core_client_version>
<message>
The system cannot find the path specified. (0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
ar=0.509127 NumCfft=65697 NumGauss= 385287860 NumPulse= 73827205759 NumTriplet= 6468852563968

</stderr_txt>

---

http://setiathome.berkeley.edu/result.php?resultid=367637657
<core_client_version>5.2.13</core_client_version>
<message> - exit code -1072365552 (0xc0150010)
</message>
<stderr_txt>
ar=0.393930 NumCfft=76015 NumGauss= 497965078 NumPulse= 95438232447 NumTriplet= 8184936415232

http://setiathome.berkeley.edu/result.php?resultid=361537372
<core_client_version>5.2.13</core_client_version>
<message> - exit code -1073741502 (0xc0000142)
</message>
<stderr_txt>
ar=0.439962 NumCfft=71235 NumGauss= 445839154 NumPulse= 85351402879 NumTriplet= 7247263514624

I got a -9 overflow error but received about 10 or so credits for it. That was an unusual number so I checked it. It probably was an RFI-contaminated unit that didnt resolve itself as such right away, as most do.

---

I got a -9 overflow error but received about 10 or so credits for it. That was an unusual number so I checked it. It probably was an RFI-contaminated unit that didnt resolve itself as such right away, as most do.

I had similar as follows:
Computer ID 2609187
Report deadline 30 Aug 2006 4:54:04 UTC
CPU time 70.740061
stderr out
<core_client_version>5.4.9</core_client_version>
<stderr_txt>
ar=0.792449 NumCfft=53093 NumGauss= 247555568 NumPulse= 26677390848 NumTriplet= 3723198922752
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.

</stderr_txt>
Validate state Initial
Claimed credit 0.0760234569545436

Had thought it was my computer's fault, but maybe, as you say, it's probably a "faulty" work unit.

---

img]http://www.boincstats.com/signature/user_59417.gif[/img

Had thought it was my computer's fault, but maybe, as you say, it's probably a "faulty" work unit.

Hi Keith, welcome to seti.

Here's what the Wiki says about a result overflow error. This type is relatively common and usually results from too much RFI in the signal.

tony

Had thought it was my computer's fault, but maybe, as you say, it's probably a "faulty" work unit.

Hi Keith, welcome to seti.
Here's what the Wiki says about a result overflow error. This type is relatively common and usually results from too much RFI in the signal.
tony

Yes, 2 other computers got the same result on that work unt and we each were granted a princely 0.08 credits!!! I've been in SETI since Classic began, but was apalled by the shoddy deal meted out to the faithful at the switch-over with an almost total disregard for communication with crunchers. I've just had a look at the present much improved set-up and am quite impressed - especially the queueing system.

Thanks, by the way, for a polite reply. Quite a contrast to some tripe I saw just before making this reply. Keith

I've been in SETI since Classic began, but was apalled by the shoddy deal meted out to the faithful at the switch-over with an almost total disregard for communication with crunchers.

Information on the fornt page of the original web site saying that Classic was ending & BOINC was where it was going to continue. An email mailout to all those that hadn't switched over prior to the Classic servers being shut down.
What more could they have done? Paid to have popups appear whenever you visited any such funded web site? I know i wouldn't have been too impressed with that plan.

---

Grant
Darwin NT

What more could they have done?

Sent you man in black to your door, saying you needed to change your crunching ways. :-)

---

Keith, in classic, that wu would have continued to run and run and collect data on all that worthless RFI. Under boinc, the count noise count gets to a certain point and seti will terminated the WU early, slap a -9 error tag on it and send it back. The "Low" credit is usually inline with what you might have gotten had it continued to the end.

I have nre WU's that won't even start. They just sit there wasting time. So I reset the projest over and over again. What's wrong?

---

So I reset the projest over and over again.

Resetting the project is the very last option and only done if all elese fails.

What's wrong?

If you would post your log we might be able to find out.

---

Grant
Darwin NT

Keith, in classic, that wu would have continued to run and run and collect data on all that worthless RFI. Under boinc, the count noise count gets to a certain point and seti will terminated the WU early, slap a -9 error tag on it and send it back. The "Low" credit is usually inline with what you might have gotten had it continued to the end.

What's that "certain point"? I've been sitting on a WU for over 24 hours and it hasn't even shown ANY progress. Seems that their certain point sucks!

No messages, no nothing.......just a unit that sits there and does nothing. This software sucks big time, stop defending it.

---

So I reset the projest over and over again.

Resetting the project is the very last option and only done if all elese fails.

What's wrong?

If you would post your log we might be able to find out.

When the wu doesn't start, it doesn't generate a log, so there is nothing to show. I've got one of them as well.

---

Keith, in classic, that wu would have continued to run and run and collect data on all that worthless RFI. Under boinc, the count noise count gets to a certain point and seti will terminated the WU early, slap a -9 error tag on it and send it back. The "Low" credit is usually inline with what you might have gotten had it continued to the end.

What's that "certain point"? I've been sitting on a WU for over 24 hours and it hasn't even shown ANY progress. Seems that their certain point sucks!

No messages, no nothing.......just a unit that sits there and does nothing. This software sucks big time, stop defending it.

It may be that you got a rouge WU that doesn't want to do anything. Have you tried re-booting your computer? I know it sounds like a dumb question, but many WU's have suddenly started by doing a re-boot. If you haven't, try that. If that doesn't work, then I would suggest aborting it and carry on and not sit and bicker over 1 wu. There's no sense in getting upset about it.

---

Why would a wu abort in error on one computer and not on any other? This one did for me:13ap06aa.2333.10880.403412.3.68

Thank you,
Nick

---

Why would a wu abort in error on one computer and not on any other? This one did for me:13ap06aa.2333.10880.403412.3.68

Thank you,
Nick

Your result on that WU says "aborted by user".

Perhaps yopu meant 12ap06ab.13805.13312.65906.3.78_3 where your result does show Exit status -1072365552 (0xc0150010). That WU was a -9 overflow for the others hosts, there is obviously an unfound problem which makes systems sometimes error out rather than exiting gracefully with the overflow information message. Typically you only lose a fraction of a credit, though.

                                                          Joe

Why would a wu abort in error on one computer and not on any other? This one did for me:13ap06aa.2333.10880.403412.3.68

Thank you,
Nick

Your result on that WU says "aborted by user".

Perhaps yopu meant 12ap06ab.13805.13312.65906.3.78_3 where your result does show Exit status -1072365552 (0xc0150010). That WU was a -9 overflow for the others hosts, there is obviously an unfound problem which makes systems sometimes error out rather than exiting gracefully with the overflow information message. Typically you only lose a fraction of a credit, though.

                                                          Joe

Thank you Joe.

Nick

---

It may be that you got a rouge WU that doesn't want to do anything. Have you tried re-booting your computer? I know it sounds like a dumb question, but many WU's have suddenly started by doing a re-boot. If you haven't, try that. If that doesn't work, then I would suggest aborting it and carry on and not sit and bicker over 1 wu. There's no sense in getting upset about it.

Thanks for the suggestions, but I've already shut it down. My point was that I don't just sit here waiting to see if a WU is going to run or not, so by the time I get around to finding out that it's a crap WU, I've wasted many hours of computing time on the piece of crap. Boinc s/w should be smart enough to abort these crap WU without intervention. Like I said, the software sucks.....we deserve better.

---

It may be that you got a rouge WU that doesn't want to do anything. Have you tried re-booting your computer? I know it sounds like a dumb question, but many WU's have suddenly started by doing a re-boot. If you haven't, try that. If that doesn't work, then I would suggest aborting it and carry on and not sit and bicker over 1 wu. There's no sense in getting upset about it.

Thanks for the suggestions, but I've already shut it down. My point was that I don't just sit here waiting to see if a WU is going to run or not, so by the time I get around to finding out that it's a crap WU, I've wasted many hours of computing time on the piece of crap. Boinc s/w should be smart enough to abort these crap WU without intervention. Like I said, the software sucks.....we deserve better.

I don't sit at my computer either waiting for any WU's to not run. I've never had that problem, and with being attached to many projects, I've never experienced this problem. Maybe I'm lucky, I dunno.

The developers are trying pretty damn hard to get the software to do many thing and fix bugs. No piece of software is 100% bug free. This isn't a perfect world, and humans are far from perfect. Sorry I couldn't help you more. I'm sorry the software sucks for you. Hope someone else can help you with your issue.

---

It may be that you got a rouge WU that doesn't want to do anything. Have you tried re-booting your computer? I know it sounds like a dumb question, but many WU's have suddenly started by doing a re-boot. If you haven't, try that. If that doesn't work, then I would suggest aborting it and carry on and not sit and bicker over 1 wu. There's no sense in getting upset about it.

Thanks for the suggestions, but I've already shut it down. My point was that I don't just sit here waiting to see if a WU is going to run or not, so by the time I get around to finding out that it's a crap WU, I've wasted many hours of computing time on the piece of crap. Boinc s/w should be smart enough to abort these crap WU without intervention. Like I said, the software sucks.....we deserve better.

Better is available from http://www.zadra.org/seti_enhanced/index.php.

I see that two of your three systems are Win98, and it's certainly true the stock client has issues on Win9X. That situation should be much better with the next version. There are several of us with Win9X doing what we can in Beta Test to ensure that.

As to deserving better, the project people are doing what they can to improve things. It will take time.

                                                           Joe