Since SETI Driver depends on the SETI Client to do all the processing and
transmitting, it's probably not a SETI Driver problem.  This really sounds
like you have a problem with your hardware.

Also, if you don't like SETI Driver, I'll refund your $0.00 you paid for it.
So delete it from your system and use a different caching program.  I
suspect you'll have the same problem with most caching programs that manage
the SETI CLI program.

Mike Ober.

"Ed" <ed.neider@mailinator.com> wrote in message
news:1086553677.20609.0@nnrp-t71-02.news.uk.clara.net...

"Benu" <flashl@bigfoot.com> wrote:

B> I posted the "Setiqueue Blues" message, the computer
B> internals are clean, yet the problems that I conveyed still
B> exists. I strongly feel that the problems that I am
B> experiencing with seti driver and setiqueue are somehow a
B> setiqueue software/network related problem.

Definitely a bug within Setiqueue or Setidriver.  I remember the only
time I ever used Setidriver was a few years ago when I used to use
Windows 98.  The following morning I found my machine had frozen
solid.  Whilst Win98 was a load of crap, Setidriver is the only app
I've ever used which managed to completely hose my machine.
I hope Michael Ober does more testing before releasing these days...

Best regards to you Benu.

---
Benu used , a fine choice.

Benu's great post contained 65 lines.
The thread "Re: Similar SETI problems" has been very informative.