Michael D. Ober wrote:

I'm looking at the files right now.  As for the 30 second pause, it's part
of SETI Driver itself.  I discovered while writing SETI Driver that if the
same system sent multiple WUs back at the same time, the SETI Data Server
wouldn't credit the account properly.  So I put in a forced 30 second delay
on the return of WUs.  SETI Driver starts the transmit session, then tells
Windows to notify it in 30 seconds to see if the session is complete.  If it
isn't it then waits for Windows to tell it the transmit session is complete.
If it is, it goes to the next WU.

Cool...that explains the pause.

I wasn't too concerned about it...just noticed it when I first got Seti
Driver and it went to get my cache of WU's.