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.