Seti is hung up! I can't process a WU !

[przero]

Seti will not start processing a new WU. What's up with that? Help!

 

[Robor]

Give us a little more info on the problem. Questions...

What OS are you running?

What SETI client are you running?

Are you using an additional program (SetiDriver, SetiQ, etc)?

Are you using a proxy or connecting directly to Berkeley (default)?

 

[CraigRT]

You're going to have to include all the steps on what you are doing, i'm sure no one can help you unless you be more specific, unless there is some known problem or something. (I am not aware of any!) So tell us what's up.

 

[Smoke]

Yes, more detail would allow more help.

But a general rule is to restart your computer and see if that clears up the clog. 😉

 

[ICXRa]

I had this same problem last week. I ran NDD and it found and corrected a problem with the file system. Consider running Scandisk or NDD and reboot as Smokeball said and see if it corrects your problem.

 

[przero]

Win XP Professional
setiathome-3.03.i386-winnt-cmdline.exe
SetiDriver
Directly to Berkeley.

I keep a 45 unit cache. Proceesing times avg. 3 hours 25 min. It just hung. When I double click SetiDriver it shows no Est. time, time left or completion time. And 0.00% completion on bar.

Rebooted to no avail.

 

[LiveLongAndProsper]

This happened to me a few days ago. 🙁
In my case, the culprit was a bad work_unit.sah file (undersized-with no header information) in the subdirectory SetiDriver was trying to process. I exited SetiDriver, deleted the subdirectory with the bad file, then restarted SetiDriver and all was OK.
Normal work_unit.sah file size is 348k or 359k in Windows. Hope this helps....

 

[przero]

I re-installed the client and deleted all my WU's and got new ones. So far ,so good.

 

[Baldy18]

This may be the problem that was addressed on the SETI@Home forums here. Anther member of our team had this problem and a registry edit allowed him to download WUs once again.