Lentil McBean wrote:

Not looking to be a massive Seti@Home cruncher, but I would like it to work!

I have an XP Pro machine and the GUI client installed.  Seti@Home is
selected as screen saver but I just get a flash and it goes away.

Installed as an Administrator ok?
Can you select it from the screen properties screensavers selection?

Note that for some systems, the 'preview' will only flash a single screensaver frame because of extraneous mouse activity immediately clearing the preview.

I've cleared about everything I can from the task manager just to see if I
can clear it, but No Joy.

That will have no effect whatsoever, unless you actually have some other unwanted screen saver operating.

Better research is to look at what services you can switch off. This also makes your system less flaky and slightly more secure also.

For services details, see:
http://www.blackviper.com/WinXP/servicecfg.htm

For general tips, see:
http://www.teamlambchop.com/tips.htm

I've looked at the 'run command line as service' option, but I don't want
the overhead.

What overhead?!

You can have s@h run with 100% CPU utilisation, and still have instant response for anything else you want to do. Whatever higher priority tasks you have just steal whatever CPU time they need away from the *low priority* s@h process.

CPUs can switch between tasks in less than a microsecond, constantly!!!

    Suggestions on how to debug the GUI?  Common culprits, etc?  Yes I read
the FAQ, and it didn't help.

The GUI works fine. Read further, or give a few more clues...


Good luck,
Martin

(Mandrake 9.1 Linux (;-))