"Martin 53N 1W" <ml_news@ddnospamddml1dd.co.uk.dd> wrote in message 
news:tcQ3f.766$WI4.170@newsfe4-gui.ntli.net...

Sarah wrote:

In WinXP Sp2 I've tried setting the Base Priority for SETI to Normal. The 
result that I'm expecting is faster crunching times. Everytime I restart 
the Base Priority defaults to Low. boincmgr remains at Normal. Is there 
any way to set it permanently to Normal or any other priority that I want 
to?

No, that's not supported by the client(s) (yet).

I'm sure its been requested before, but it is a very low priority feature 
to code up compared to the other work being done at present.

(OK, bad pun on the priorities :-O )

Each time the client starts a new WU, then that process is started at the 
usual low priority. If you have no other tasks running, then this is not a 
problem. s@h is /intended/ not to slow normal working. If there is no 
other work, then increasing the priority for Boinc will have little effect 
because there is no more CPU time available other than the 100% already 
being used by Boinc.

on windows i came accross a problem with seti and dcplusplus
when dcplusplus (DC++) 'hashs' files, i assume crc checks or some such seti 
is set higher than the hashing thread/process, so the hashing never gets 
done while seti is running, or takes an insane amount of time...

only noticed as my mate was moaning about it :)