SETI and recompressing again

[V_D_O]

Since my HTPC is the most powerful PC in the house, and is free from work much if the time, I thought it'd be the perfect platform to run another Seti@Home client on. Turns out I was wrong.

As has been discovered by some, recompressions don't even start when SETI is running - no matter how high I make the BatchProcessor thread, the Low SETI thread always beats it and hogs all the CPU. The moment I end SETI, the recompession starts.

Through the course of my searches, I have heard various people say that it is possible to edid the PVSAPP.ini file to raise the priorities of PVS's internal recompression threads, but have been completely unable to find just where that particular post has gone (the boards' search function is called into question yet again). I have given the concerned file a cursory glance, but am way out of my depth here. I believe the workaround may have been posted by PBMax, but am not sure.

In any case, I would be extremely grateful if anyone could point me in the direction if this fix, or even suggest another instead of this (I am using 3.3, BTW). I suppose it is possible for me to stop SETI during the recopression hours, but this would be hugely inconvenient and I see no reason why I should have to.

Much obliged.

[RobertH]

you just gotta know how to use the search feature its much more usable if you know who did the post:

http://discuss2.snapstream.com/vb/sh...light=priority

search was:
keyword: priority
written by: pbmax

[V_D_O]

Thanks Robert!