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.

Mike.

"Bill" <bill@c.a> wrote in message news:vf6dnX_DRtE4WOvdRVn-gg@golden.net...

Cambridge Computer Recycling wrote:

Regularly, when I return to any of our machines, I find that seti driver

is

showing 1 unit ready to transmit, 1 unit needed to fill.  If I click on
transmit, the black box appears briefly, too briefly to read anything,

and

then goes, Seti Driver shows no units ready to transmit, but still 1 unit
needed to fill.  I then have to click on transmit again to get the black

DOS

box to appear and see the next WU upload.

I've noticed Seti Driver doesn't seem to transmit and receive instantly.
There is a deliberate pause of some 30 seconds or more between actions.
Is that what you're seeing?

If not, what are your settings in Seti Driver? List them all.

And are you running anything else with it, like SetiSpy?

 When I check my stats, no unit
has been credited after this.

Where are you checking your stats? If it's at the SAH website, I believe
they only get updated once a day.