Chris,

From the directory listing, I don't see any SETI Driver managed WUs ready to
return.  However, I do see a SETI Gate WU ready to return, and in-fact, it's
attempting to transmit and download a new WU.

Directory of D:\Seti\Setigate
31/12/2003 21:03 188,416 setiathome-3.08.i386-winnt-cmdline.exe
01/01/2004 09:39 0 lock.sah
01/01/2004 22:06 132 key.sah
01/01/2004 09:39 32 version.sah
29/01/2004 19:27 6 pid.sah
01/01/2004 09:43 249 temp.sah
01/01/2004 09:43 270 user_info.sah
01/01/2004 21:48 3,902 outfile.sah
01/01/2004 22:06 5,288 wtemp.sah        <== This line is a WU being
downloaded
01/01/2004 22:06 5,511 result.sah           <== This line indicates the WU
in this directory is ready to transmit

The SETI Client (based on my reverse engineering) does the following:

If a result.sah file exists, the client returns this file and then deletes
it.  Then it renames work_unit.sah to wtemp.sah and downloads a new WU into
wtemp.sah.  Once the download is complete, it renames wtemp.sah back to
work_unit.sah.  Then it starts processing this file, updating the files
state.sah, result_header.sah, output.sah, and key.sah every minute or so.
When it finishes processing, it appends the file output.sah to
result_header.sah.  It then renames result_header.sah to result.sah and
starts the cycle over.  If at any time, these files get out of sync, the WU
processing starts from scratch if there is a work_unit.sah or it attemps to
download a new WU if there is no work_unit.sah.

From looking at the directory you sent, here's the current state of SETI
Driver's cache:

1   -  Waiting to Process
2   -  Waiting to Process
3   -  Processing
4   -  Waiting to Process
5   -  Waiting to Process
6   -  Waiting to Process
7   -  Waiting to Process
8   -  Processing
9   -  Waiting to Process
10  -  Waiting to Process

Since there are no stop_after_send.txt files, SETI Driver should be
reporting:

Maximum Processes: 2
Desired Cache Size:  10
Current Cache Size:  10
Processing:               2
Waiting to Process:   8
Need to Fill:             0
Ready to Transmit:   0

Clear the AutoTransmit checkbox and the proxy settings.  The next time a WU
completes, manually click transmit and see if it transmits to Berkely.  I
suspect it will.  If it does, check your proxy settings.  Since SETIGate is
on the same machine as SETI Driver, try 127.0.0.1 for the host.  If it still
doesn't, let me know.

Mike Ober.

"Cambridge Computer Recycling" <sales@cambridge-computer-recycling.co.uk>
wrote in message news:7EBdc.1299$io3.887@newsfe1-win...

"Bill" <bill@c.a> wrote in message

news:vf6dnX_DRtE4WOvdRVn-gg@golden.net...

Cambridge Computer Recycling wrote:

<snip>

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?

No it is not.  I am used to that window.  This one appears too briefly to
even see what it says.

<snip>

 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.

No.  I get SetiGate  to check

http://setiathome2.ssl.berkeley.edu/fcgi-bin/fcgi?cmd=team_lookup&name=Digiguide+Users

which is updated in real time.

Chris
www.cambridge-computer-recycling.co.uk