Dalibor wrote:

I get around 3h30min average with GUI on a AMD XP 1700@2200+
(1836MHz), 333Mhz fsb, 2x256MB 333DDR.
With the CLI client, it around 2h50min-3h00min..

That makes me think there is something wrong with my machine's set-up.
It is a Celeron 1700, 400 FSB, with 384 MB PC133, running XP Home and CLI
3.08 under SETIGate 1.94
and WUs are averaging around 9 hours.

Task Manager shows SETI gets about 99% of the CPU, but does this really
measure what it looks like?
Are some system overheads shared out amongst the processes?
When it was newly installed, XP's Universal Plug and Play service was unable
to cope with something and gradually hogged more and more resources, so I
disabled it (thanks Black Viper and others).

SETISpy reports CpF of ~15 which looks pathetic.

Sisoft Sandra reports there are 'features' which seem to have been disabled
in the BIOS, but there is nothing I can see to change apart from CAS Latency
values, and thats too scary for me to change without guidance.
The on-board temperature sensor seems to be stuck permanently on 51C.

Any ideas?
---------------------------
585 WUs