I am not sure whether I have a similar problem.

I run the CLI under SETI Driver/Spy, with Driver pointing at SETI Queue.
The PC in question is a dual proc P3@933 (not overclocked) running Win2K
and firewalled by ZA Pro V4.5

A week ago after ZA updated to V5.0, all seemed to fall apart. The
network refused to work using my dial up ICS/NAT gateway. SETI Driver on
the other PCs refused to send completed WUs to SETI Queue on this box,
etc.

I assumed ZA5 was the culprit, and have since reverted to V4.5, and all
seemed to run faultlessly yesterday. NOTE:  This has taken some time to
diagnose, and over several days.

Last night all was running well. This morning the other PCs on the
network were crunching, but the firewalled PC had SETI Driver down. It
seemed unable to send the completed WUs to SETI Queue. Shutting down ZA
made no difference.

Further trial and error starting up SETI Driver/Spy, both with and
without ZA running, seemed to end with the system resources slowing down
to a halt.

I am now concluding I may have some unfriendly bug in the PC at fault,
and this is linked with the start up of SETI Driver and the CLI
(specifically).

I have just restored SETI Queue and one of the other PCs sent finished
WUs to the Queue. 

So I am shutting down the combo (Driver, Spy, the CLI) on this box, and
assuming I have a bug in the system. I need to update X-Block, Pest
Patrol and my AV for a thorough sweep of the system. Then a reinstall of
Driver and Spy.

Is this something like your experience, and is there any known unwelcome
bugs that take advantage of SETI?

Kind regards

John


In article <qnayc.1315$Wr.408@newsread1.news.pas.earthlink.net>, Michael
D. Ober <obermd.?@?.alum.mit.edu.nospam> writes

I assume that you are downloading the WINNT version from Berkeley.  Also, as
silly as this sounds, don't rename the client and also try running it
without SETI Driver - let's get SETI Driver out of the way while
troubleshooting.

Mike.

"Ron" <Figboot@comcast.net> wrote in message
news:D52yc.5799$2i5.2041@attbi_s52...

Thank you!  I've tried a "New" install and the problem persists and I do

NOT

overclock my CPU.  Any other thoughts?

-- 
Ron

All of my eMail is checked by Norton AntiVirus, with the very latest
definitions!  This ensures that NO ONE will receive a Virus from me.
"Ron" <Figboot@comcast.net> wrote in message
news:UXNxc.73449$Ly.15933@attbi_s01...

When I set up my new computer to run SETI@Home Command line and

SETIDriver,

I

receive this error message after about one minute:

"SETI@Home-cmdline.exe

has

encountered a problem and needs to close. We are sorry for the

inconvenience."

I send the error report and restart SETIDriver.  It happens again and

again.

I have run this same setup for the past four years without a hitch.  Any

ideas

what my problem is.  FWIW, I use a Cache size of six (6).

-- 
Ron

All of my eMail is checked by Norton AntiVirus, with the very latest
definitions!  This ensures that NO ONE will receive a Virus from me.

-- 
John Clark

In the "reply to", replace either "fredclark" or "Workgroup" with 
"jonclark" for direct e-mail.