2.76 and win 2000

[zzzz]

Has anybody tried the seti 2.76 client with win 2000? I was getting times of around 5 hours in win 98. Then I thought I will try win2k and the units seems to take foreware. The first unit was completed something like 40 % after 10 hours, so I thought may be I will try other. The second unit also showed simillar behaviour.(I use seti manager to cache units)
duron 600@1000
KT7
256Mb Ram

 

[ctll]

just a thought: you could assign it a higher priority in task manager. i don't know if your times indicate a lack of something or not... also you could try the NT command line client for seti in w2k. but i'm not up on seti, probably somebody else knows more...

 

[zzzz]

I just noticed a weird thing. My win2k task manager shows 33% cpu utilization at the same time the system idle processes show 99 % cpu.
I think it is related.Does anybody have a solution?

 

[mindless]

If its not using the CPU and the idle is then I would bump up the priority a notch, but be careful changing priorities can take down a system, and if you take it too high everything but SETI will run slow because SETI will not give up the CPU. On second though forget what I said about that last part, take it up as high as it will go while keeping the system stable, you dont need the CPU for anything else anyway

 

[PhotoLenny]

I've run Seti as high as priority "Normal" without too much weirdness, the occaisional one second mouse delay, but I usually run it on "Low". Do you have a dual machine - one instance only brings me to 50% on my dually.....