I agree with George that this sounds like a bad WU.  Delete the WU folder
and then reset your cache size.  As for knowing which WU folder, all you
need to do is check the "Display Transmit" box to see which WU is
transmitting and clear the "Hide Processing" box to see which WU(s) is/are
currently processing.  The title bar of the command prompt session will be
"SETI nn" for processing WUs and "SETI nn Transmit" (if I remember
correctly - it's been a while since I looked at this code).  The 'nn' will
be the cache number.

SETI Driver catches and deals with most of these bad WUs - this is the first
time I've heard of SETI Driver not detecting one in over a year, but I know
they appear more frequently than once a year.

Mike Ober.

"CBS" <cbspam_smith@hotmail.com> wrote in message
news:QGvPa.73942$TJ.3872122@twister.austin.rr.com...

Hi,
How can I tell which folder this bad workunit might be hiding in?  Is

there

a way to open up a results file of a workunit (that is not being currently
worked on by S@h
application?
Thank you,
C. Brent Smith




"f/f george" <an16365785@nonanon.penet.de> wrote in message
news:vaqrgv0nr1dpmqecm35n91jggg0rt69on9@4ax.com...

It could be a bad unit. Sometimes there are units that just won't
finish, Seti Queue finds these occasionally and if you just delete
them the computer will just continue on and you just lose any work
done on that unit.

 On Thu, 10 Jul 2003 20:53:05 GMT, "CBS" <cbspam_smith@hotmail.com>
wrote:

Hi all,

I have encountered an odd problem with a Win 2K machine that is running
SetiDriver as it caching program.

Suddenly and without warnign it has started to report that it still has

to

"1 WU to Send and 1 to Fill"  I also use Setiwatch to track the results

of

this machine (and three others) weirdness is that it is transmitting

its

workunits (stays in sync with SetiWatch and S@H site, plus with a
spreadsheet I fill in using data from S@H site and SetiWatch.)  If I

force a

transmit it immediately loads the new data into cache folder number 35

me

after about 15 sec I know that  it still needs to transmit and fill

because

the icon stays yellow instead of going to blue.  Does anyone know what

might

be causign this and how to possibly fix it?  I have rebooted the

machine

and

restarted SetiDriver numerous times ... it has never exhibited this

behavior

on any other machine.

Thanks,

C. Brent Smith

-- Have you checked your Smoke Detector...LATELY?