Absolutely right !!  Now all i need to find out is why it was not processing
work units till I made the SetiStash interface visible and "Told" it to
process work units.  One thing: it was set for "0" CPU's .... could that
have been incorrect?  This is a single P4 1.6GHz machine...

Since changing it to "1" CPU , it has been processing work units and
Motherboard Monitor shows the CPU maxed out all the time.

I'm on dial up here, and I noticed that Yahoo pager or whatever it is ...
can occupy all the CPU cycles by itself ... under some circumstances !!

-RS-

"Linus Das" <linus_das@yahoo.co.uk> wrote in message
news:1072479163.20963.0@eunomia.uk.clara.net...

"RS" <rbs747X@Xhotmail.com> wrote:

Is there any intrinsic problem running SetiStash 2.1 on WinXP Home?

I have never got it to run properly. Task Manager shows it running but
consuming 0% of the CPU.

If I double click on the SetiStash.exe, something opens and immediately
closes .... configuration is thus impossible.

It also shows as 0% on Windows 2000 - that's normal.  If SETIStash
has actually started a WU, that WU will show as a separate process
in the Task Manager (e.g. seti.exe 99%).  If it appears to open and
close immediately, it has been set to hide into the system tray.  If it
doesn't appear in the tray, the invisible icon option may have been
selected. Hover your mouse over an "empty" bit of the tray to find it.