I have been doing a little experimentation with running SETI and Dnet at the same time.
On 2K, SETI CLI ver 3.0 is very dominant taking nearly 99% of the CPU cycles.
On a Win 95 box, SETI GUI ver 3.03 gets ~70% of the cycles, and Dnet the rest.
The good thing is that when the SETI client cannot get a WU, it 'shuts down' giving Dnet all the cycles. This way your machine won't go to waste if the SETI server is out of work.
viz