This is an indication that the SAH files aren't being updated properly by
the client.  Check your security settings on the hard drive and the SETI
Driver folder, ensuring you have full access (or at least "modify") access
to these folders and files.  Also, to confirm the WU number, clear the SETI
Driver "Hide Processing" checkbox and save the SETI Driver configuration.

Mike.

"m" <no_nomine@hotmail.com> wrote in message
news:Psk7b.996$eA5.318@newsfep1-gui.server.ntli.net...

I have a PIII/1.2GHz laptop that I do some processing of SETI units on.,
along with other things. I shut it down to transport it about. I run it,
along with a couple of other machines, through a SetiQueue server. I have
the obvious proxy settings and auto transmit ticked as well. The last

couple

of times that I have restarted it after a shutdown, the partially

completed

unit that it was processing has resumed at 0% - i.e. from the beginning.

It

has just done this on a unit that was over 70% complete. this is with cli
3.03, SetiDriver 1.6.3.6 and a queue size of 5.

Does anyone know of a possible cause? should I turn off auto transmit?

TIA

M