My computer has been "running" WU 04ja04aa.7402.7008.28414.4_1 for 12 hours and 19 minutes. However, the progress bar still reads 0.0%, and the time to completion has been frozen at 86:27:39 since I turned the computer on more than seven hours ago. How do I get rid of this WU or kick it to get it moving?

I am running Windows 98se on a PC.

Which BOINC client are you using and on what kind of PC exactly? At minimum tell us about your CPU.
----------------------
Jordâ„¢

I had a similar problem with one of the first three units I worked on. I just did a complete exit from the BOINC program, rebooted my system, and started BOINC up again. Everything started working just fine after that. It's worth a try. :)

> Which BOINC client are you using and on what kind of PC exactly? At minimum
> tell us about your CPU.
> ----------------------
> Jordâ„¢
>
>
>

Pentium III processor, 256 meg RAM, 17G HD with 9.25G free. Using BOINC 3.19, Windows Intel x86. (Exiting and rebooting did not help.)

Have you tried rerunning your benchmarks?

In the GUI go to File, run Benchmarks.
When done, go to the Projects tab, rightclick on Seti@home and choose Update.
You do need an internet connection for this.

If you want to get rid of the WU and with that all WUs in your cache at this moment (so do watch out!!), you can go to the Projects tab, rightclick Seti@home and choose Reset project.


----------------------
Jordâ„¢

> Have you tried rerunning your benchmarks?
>
> In the GUI go to File, run Benchmarks.
> When done, go to the Projects tab, rightclick on Seti@home and choose Update.
>
> You do need an internet connection for this.
>
> If you want to get rid of the WU and with that all WUs in your cache at this
> moment (so do watch out!!), you can go to the Projects tab, rightclick
> Seti@home and choose Reset project.
>
>
> ----------------------
> Jordâ„¢
>
>
>

Had run benchmarks but had not updated. Updating cleared the one other WU in my display (which was showing "ready to send"). After updating, the remaining WU was still stuck, so I performed the reset and got rid of it. Thanks!