Tweet
3.03 update (machines, SetiQ, etc.)
Well, I upgraded to 3.03 last week at the last possible minute (ok, the next morning). I was asked in another thread about any tweaks, etc. that I've done to keep my systems running decently. I haven't done any (since most of the machines are using idle cycles here at work).
I'm running SetiQ 3.03beta2 currently (I know, there's a newer one out now...I'll upgrade eventually). The machine its running on is Windows 2000 Server. I had SetiQ crash on me overnight a few times (see the stats page for the 0's). I'd lock the computer at the end of the day. When I'd come back the next morning SetiQ would be dead. It didn't make a difference if it was minimized in the system tray or open. I installed it as a service and it was fine last night. There are instructions on the SetiQ web page telling how to do that.
My clients are all running 3.03 (who'd have guessed). Here are some approximate averages as tracked by SetiQ:
Celeron 400 with Win2K Server (running SetiQ, Outlook 2000 and other office stuff during the day): 16 hr 25 minutes
PIII Xeon (733 I think) with Win2K Server (doing various web and similar server things): 7 hr 10 min
PIII 933 (various tasks, Seti running in the background 24x7 most of the time): 6 hr 45 min to 7 hr 0 min
PIII 866 (testing during the day, Seti not running): 6 hr 46 min to 7 hr 20 min
Note that some of these machines haven't returned more than a few WU's yet. I've got a few machines at home that I'll get up and running in the near future (PIII450, PIII450@600 (4.5x133), PII233, K6-2 400 (6x66)). No times on them yet, though.
Any questions?
I'm running SetiQ 3.03beta2 currently (I know, there's a newer one out now...I'll upgrade eventually). The machine its running on is Windows 2000 Server. I had SetiQ crash on me overnight a few times (see the stats page for the 0's). I'd lock the computer at the end of the day. When I'd come back the next morning SetiQ would be dead. It didn't make a difference if it was minimized in the system tray or open. I installed it as a service and it was fine last night. There are instructions on the SetiQ web page telling how to do that.
My clients are all running 3.03 (who'd have guessed). Here are some approximate averages as tracked by SetiQ:
Celeron 400 with Win2K Server (running SetiQ, Outlook 2000 and other office stuff during the day): 16 hr 25 minutes
PIII Xeon (733 I think) with Win2K Server (doing various web and similar server things): 7 hr 10 min
PIII 933 (various tasks, Seti running in the background 24x7 most of the time): 6 hr 45 min to 7 hr 0 min
PIII 866 (testing during the day, Seti not running): 6 hr 46 min to 7 hr 20 min
Note that some of these machines haven't returned more than a few WU's yet. I've got a few machines at home that I'll get up and running in the near future (PIII450, PIII450@600 (4.5x133), PII233, K6-2 400 (6x66)). No times on them yet, though.
Any questions?
.
Comment