• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Help!

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

JAWS

Member
Joined
Jun 16, 2001
Location
Xtremesystems
I think I remember reading something about SETI not working with Win Xp. I finally get my new system, and for the third night in a row, I wake up with the error message: "SETI Client-Sever has Encountered a problem” That’s not the exact message, but close enough.

System ran fine the first night. Results were better than expected. I can't even complete one WU without getting this message! :mad: I even tried re-installing SETIspy/Driver. Any hints/help would be greatly appreciated.

Sorry, I'm a little frustrated.
 
Jaws,

SETI itself is not a problem under XP (i'm running dual durons wtih two seti clc instances on XP pro as I type this). I know SETISpy had problems with XP and I'm not sure about Driver. SETITeam works OK though.

Are you using any of those other progs with your SETI?

Cy
 
I'm using Xp Pro.

Hallen, I just came back to edit my post about the start up problem. Every time I start SETI, I get the same error message. Sometimes I get lucky and bypass the error. Maybe I should try the new version, as I'm using 3.0.7 also.

Cy, the only program I run is zone alarm. I turned everything else off last night.

One more thing, I noticed that the SETIspy icon doesn't have the little red dot in the middle while it's running. I have no idea if this means anything. Thanks for the replies.
 
Just a suggestion: try changing the "program compatibility" in Windows XP to Win98 or W2k for SetiSpy/Driver. If you need help doing it, click <Start> <Help and Supprt> and type "Program Compatibility Wizard" in the Search box.
 
yup. Spy had problem w/ XP, whether it's Home or Pro. usually when u start Spy, it'll show u a problem message.

solution:
~ close & restart for 2-4 times, it usually works fine.
~ or set the compatible to Win2k & disable visual effect.
~ or get 3.1.0.

good luck.
 
Well setting it to be compatible with Win2k seems to work. :)

shhhhh, don't tell my computer its working. LOL

Thanks again for the replies
 
I noticed for with XPPro that Spy must be started after Mcafee which is a bit slow to auto load in XP. I occasionally get the error messge regardless but all i do is shut down and restart spy.

but the good thing is that driver is still running even if you miss the error message so you dont lose crunching time
 
Now it looks like after one WU completes, SETIspy will not move onto the next WU. System just crashes. :( Any ideas?

Should I try 3.1.0?
 
same here. 2 rigs in XP Pro, 1 laptop in XP Home. both running 24/7 SETI w/out a single crash!!

Jaws --> IF ur system crash after finished a WU or when it finished and tried to grab another one from berkeley, then it's the o/c problem! i was having that same problem on 2 of my machines too! sometimes it runs fine for 2-3WUs, sometimes it will crash when finished 1 and grabbing another one. uninstall, reinstall many times. 3.1.0, 3.0.7, any versions i've tried already. no help. and then, after i've drop down the FSB a little (just drop it for 1-2MHz), everything runs fine. no problem for weeks already!! try to down ur FSB/memory/system speed a little and see if it helps. at least that's my case.

good luck! :cool:
 
Back