Seti Race Stats for 5/6...

[artemedes]

43) Elfenix .......3280/5
69) Artemedes ....1907/15
74) Def ............1771/13
75) MaxSiren ......1759/12
79) MisterM ........1707/11
95) Fardringle ...1368/5
112)Mgpaulus ......1115/12
121)Cakin ..........1014/14
124)Sukhoi ........1004/2
210)Raysun2be ....388/0

 

[RaySun2Be]

Zero? Zero? What's up with that?

Thanks for the stats.


Dasm! Checked the PCs when I got to work, all were sitting there IDLE! :Q

I use SETISPY, and it was set to keep the client running. Tried restarting the client from within SETISPY, but had to kill SETISPY, start the SETI client, then start SETISPY again. Weird. Of course it happened sometime this weekend, lost at least a day's worth of work.

 

[cakin]

Ray,

Let Setispy start the client, dont start it manually. If setispy couldnt start the client, it may not be looking at the right client! verify your path.

Weekends over, I caught Sukhoi again, he will pass me late today or early Tuesday again. I keep getting a "been there, done that" kind of feeling. At least the numbers are larger!

At this rate in about a month and a half Sukhoi and I will be close to Mgpaulus.

 

[RaySun2Be]

Cakin,
I've tried that, but doesn't seem to work too well. There is only one client, in one directory and both the SETI and SETISPY client are in the same directory. Still don't know why they all went to idle over the weekend and never restarted.

 

[cakin]

in case it helps, here are my settings, not perfect, but they have worked for me so far...hope they help.

I renamed my seti client to: C:\SETI\setiathome.exe
and keep a master copy of the clients in c:\seti\programs
Client window title is: setiathome, i checked this is the full title.

In the client window, I have hide client checked.

Under client configuration
I have keep the client alive checked. and the check interval set for 5 minutes.
I also have checked, start client on seti spy start, restore client minimized, and stop client on seti spy exit (that way I can kill it from the system tray).

I also have a client paramter of: -proxy 192.168.0.1:5517 (which is my setiqueue machine)

In the setup-display window, I have everything but always on top checked.
In the setup-client window, I have 5 minutes and 60 seconds with both ignore statements checked.

best of luck...carl

 

[artemedes]

Everyonce in a while one of my machines will stop. It seems like the client will freeze if it has troubles uploading the finished work unit. I think this, because as soon as I restart the computer or client the first thing it does is send a WU and get a new one. Well, not all the time, but most of the time it freezes it is at the end of the WU.

 

[MaxSiren]

I used to have the same problem myself, but solved it by using Seti Driver. It works great cause as soon as one WU is done, Driver starts work on another unit immediately in a new process, so even if something goes wrong with the transmit, another unit is being worked on.

I have SetiSpy start Seti Driver, which in turn controls multiple client processes. Best combination for me by far.

 

[cakin]

RaySun2Be,

If this machine is in a standalone situation, I agree with the others and highly recommend the use of setidriver. I now have an NT server here at home where I run setiqueue. Before I put in the NT machine, I used setidriver on each machine independently.

 

[RaySun2Be]

Cakin & all,
Thanks for the help! I'll have to check the settings when I get back to work tomorrow.

I tried running SETIQUE, but couldn't get it to work through the firewall.