help with seti!!!

[Lithium381]

I've had the same unit in my Q(setidriver) processing for about a day now...and it still says it's going to take another day and a few hours to complete....i'm running two proccesses(one processor) and i normally finish one in 10 hours.....what's wrong with this one? i've had two finish before this one has gone what seems to be even one precent

 

[LadyStarDust]

Could be a very low angle range WU, which is especially bad on a win9x machine. Running two instances of Seti on one processor can also slow a WU down. Sounds like you just have a bad WU, or maybe you finally found ET

 

[Smoke]

Lithium381, you could give it one of LadyStarDust's tweaks.

Slap that Sucker!



I tried the "2 Processes Idea" and there was no noticeable gain and even a possible loss of production. "Shot Can" one of those processes. Just change the 2 back to a 1 and Save Configuration. You will not lose a thing. One will finish and the other partially done WU will start up right where it was when you shut it down.

 

[ober]

Don't be surprised to see your progress bar jump when you switch from 2 to 1 on the Maximum processes. If the older WU is in the second slot, it will be the one that SETI Driver terminates anyway. It will pick back up where it left off when the other WU completes.

Mike.

 

[Smoke]

Lithium381

In case you didn't know, you just got advice from SetiDriver's Author, ober!

Thanks for the great program ober and it's nice to have you visit. BTW, we would love to have you join our Seti TeAm.

 

[Lithium381]

having two procceses completes two in 18-20 hours....and one finishes in 10 hours by itself, so no big loss, possible gain....i've heard about certiant work units that take forever....and can i just drop that one somehow, or just put it at 1 proccess at a time till it's passed? it STILL says 1 day and two hours left

 

[Fardringle]

Now and then, people have reported units taking an extremely long amount of time to finish. It's almost as if Windows is getting 'stuck' while processing the WU, and rebooting almost always fixes the problem...

 

[Smoke]

Lithium381,

I noticed you are running Win98SE on both of your rigs. That OS handles VLARs very poorly unlike Win2000. If you don't want to change your OS, then you really need to use OKs Proxy. You made reference to "Q(setidriver)"? Are you running SetiDriver and SetiQueue?

If you are using SetiDriver (my assumption) place a check in the Proxy/Socks Server section next to the Proxy Server selection. Then in the Host: orangekid.teamanandtech.com and in the Port: 5001 and then click Save Config.

You will get fewer VLARs by using OKs Proxy.

 

[Assimilator1]

SB
I asked Mike what team he's in the other day ,he's in Arsetech.
I guess he could always switch