Server won't send new work
15 Aug 2006 14:44:52 UTC
Topic 191684
(moderation:
My system at work will not accept new work. I get the message "reached daily quota of 1 result." This does not happen on my machine at home and they appear to be set up the same way.
Any ideas?
Server won't send new work
)
Your quota is 1 because the results you have returned failed to validate. The error codes you received are usually indicative of the these possible problems: 1/ an "out of date" graphics card driver (see this thread); 2/ you need to update your version of DirectX; or, 3/ your computer may be having memory probems (check with memtest).
Since BOINC took over I've
)
Since BOINC took over I've not been able to do any work for the SETI project.
I don't receive any work even after resetting and downloading BOINC several times. Reading the answers from the Message boards only tells me: If you have a problem - you have a problem! If the problem is outdated PC's or drivers, why don't you publish a set of minimum critera including a testprogram to run to validate if the PC and drivers are ok?
Can I get my (for several years well functioning SETI) support back?
Thanks.
Orla Helgren-Nielsen,
Denmark
orlahelgren-[at]-mail.tele.dk
RE: My system at work will
)
You keep getting "Client Errors" (that reduce your daily quota). Part of the computation, however, seems to run correctly. Open the BOINC Manager, select "Tasks" Tab, mark the one that is "running" and click "Show Graphics". If you get a Client Error just then (or when the BOINC screensaver comes up) , it's proabably an outdated or broken graphics driver. As a workaround you may set your screensaver to "Blank" instead of BOINC. It may also be a memory problem as pointed out earlier, but that would be my second guess.
BM
BM
Orla, you are posting this on
)
Orla, you are posting this on the Einstein forums. The Einstein project is something totally different. Please post your specific problem in the Seti Help Desk forums and someone will look into it.
Well, it was either DirectX
)
Well, it was either DirectX or bad drivers. Updated both and it is now working. seti@home always worked, however.