Greg,
Most likely, that work unit had a known noise source that was drowning out any possibility of detecting a signal. After a few minutes, SETI decided that it couldn't work with the funky signal and went to go get another one. It happens from time to time.
You still get credit for the work...
Nooooooo!!
I lost a slave! It was a good one, too. For some odd reason, I was getting "unknown fatal error" messages and SETI@Home would crash. It was working well, too.
I tried to uninstall, and reinstall. Now the install won't work. Crap.
I'm now out one 400Mhz slave.
------------------...