I have received several reports of SETI Driver's Set Affinity option causing
problems with XP systems running on HT enabled processors.  The problem
appears to be that the two instances of the SETI CLI client are deadlocking
the IO portion of the processor when Windows isn't allowed to float the CLI
between processors.  To avoid this issue, don't use the Set Affinity option
when running on HT enabled CPUs.  You can still run a CLI instance (Max
Processes) on each virtual CPU, i.e., 2 for a each HT enabled CPU.

Also, since it is known that the CLI runs at priority 4 and that off-line
folders in XP and Outlook appear to run at either priority 2 or 3, you
should upgrade to the latest version of SETI Driver (1.6.3.4) and use the
"Idle" processing option.  This will force the CLI to priority 1, which is
where the GUI client runs when it's in background.

Mike Ober.