SETIDriver Problem

[taloah]

Does anyone know of any problems with SETIDriver and large WU cache? I have a new cruncher setup with a cache of 50 so I only have to check it every few days. Today I checked it and it only had 12 WUs done and SETISpy was yellow. I looked at the log and it had been idle for 15 hours :confused: . As soon as I transmited and it got down to 9 WUs done it started right back up with no intervention from me. Anyone else ever had this problem?

[[Oc]acaridans]

Ive never gone as high as 50, I did run one with a cache of 35 for a few months, that one never gave me a problem.
Have you reloaded it to see if that fix's the problem?

[LandShark]

or try to downclock a little, u might be pushing it too hard...

[kaillum]

SetiDriver has no problems with a large cache...

when b0rkley had major problems i had my cache set to 300 on all my machines, just to make sure that I had enough woo's for a couple of weeks, and SetiDriver handled it no probs....

sounds like it could be a problem with your box... if its overclocked, try dropping it back to standard an see if the problem persist.. :)

[rogerdugans]

Only time I have had problems like that was during overclock tweaking.....
I am not certain if the wu or setidriver itself was corrupted, but something (in my case) was definitely knocked out of kilter by going too high.

Since then, when I am tweaking I shut down Seti first and copy the entire seti folder into another folder as Backup.
When I THINK I have a stable OC I restart and turn off auto upload for a few WU.
If anything acts funky I replace the original seti folder with the backup- back in business.

If you haven't already, you may want to run the benchmark to check your results on that rig ;)

[hallen]

How much free disk space do you have? 50 wu's isn't too large for Seti Driver to handle unless you run low on disk.

Harvey

[OSUmaxx]

That's pretty strange. I have my rigs with a cache of 100 and I've never had a problem with it locking up.

[taloah]

hallen: Disk space is not the problem I still got about 1G left on the disk I bought from you. How high did you get the FSB on this chip(1GHz Duron if you forgot) before you had problems? I got it upto 117MHz right now.

[Oc]acaridans: I did try reloading SETIDriver, SETISpy, and the CLC to see if that was the problem. I wont know if it helped for a few days though.

[hallen]

taloah- I ranged up to 1250 on my 1GHz Durons. I'm not sure which one you have but 120MHz should be ok if you bump the VCore to 1.85v. After that you can just move up a little at a time as long as you feel comfortable.

Harvey