Lawrence, there was a good chance it was being pre-empted but checked and littlepeaks only does WCG.

littlepeaks,

For a while the combined DDDT jobs, combined because it actually packs multiple tasks, would continue to 109 percent. Have not seen this with the zero redundancy version. Just 100%, pack and upload.

What BOINC version is this? Intel P4 2.8 ghz on XP is what I see when snooping. There is some serious zipping going on at the end and remember that the seeming 'stalling' could take near 1.5 minutes on a P4. For now, just let it sit. Maybe exit the client and restart if it does not pick up when your next job finishes. Suspending a task will stop new work fetching so be warned.

It could be helpful to yourself to switch on checkpoint_debug recording. This periodically makes an entry in the message log to tell that a task has made a discrete step progress. The 'how' you find in this FAQ:

http://worldcommunitygrid.org/forums/wcg/viewthread?thread=11332

This will tell you when the last one was made for a job, thus when running, tell if the WU is stuck completely when. No CPU time

I finally got it to report. When my next task finished, it still didn't restart DDDT, but downloaded and started another task. So, I suspended that task and disabled my network connection, so it wouldn't download any more tasks. DDDT still wouldn't resume. I clicked on suspend and then resume, and it still said "waiting to resume". So, I shut down and restarted BOINC. After about a minute, it said "ready to report". So I reconnected to the network, and it reported DDDT and the next task. And I got a "valid" for that WU.

Originally, my PC was sitting there at 100% completion for DDDT for over a half hour. So I guess the problem was that BOINC was confused.

Thanks all--