On Wed, 04 Aug 2004 12:55:32 GMT, Martin 53N 1W
<ml_news@ddnospamddml1dd.co.uk.dd> wrote:

Bob Simon wrote:
[...]

installed BOINC on a PC running Windows XP HE.

"Windows XP HE": Win XP Home?

Yes; I have XP Home Edition.

When I've got my
screen saver set to "on resume, password protect" I get a message that
says: 
Secure Windows Desktop Detected  
This configuration is currently not supported

Likely meaning that the BOINC screen saver doesn't support password 
protected resume...

What does this mean "doesn't support"?  I see work units are still
getting uploaded (occasionally) and the computer successfully locks
with a password.  So what are the consequences of using a
non-supported config?

I have a teenage son at home all day and would really prefer to lock
my computer when I'm not there.  If I simply ignore the error message,

Let him grow up a little? Educate him further??

Actually, he has his own computer and downloads lots of stuff which
repeatedly makes his system unstable.  He's had to reload XP at least
twice due to viruses and malware but he's very impulsive and hasn't
learned to avoid executables in email.  When his computer is down, he
would likely use mine if I don't password protect it.

You could run s@h without running its screen saver. Better still would 
be to run the much faster CLI version. For your 'screen saver', just 
select "Blank Screen" screen saver (no CPU wasting) which should support 
password protection.

Thanks for the tip re the CLI version.  I will check this out.

If you're using s@h "classic", find the 'blank screen' option in there. 
Then set s@h to 'always run' and from the desktop screen properties, 
select the "blank" screen saver from there also.

Look up the CLI version and associated addons. I found SetiSpy to be 
best for summarising progress.

In a few days, check out BOINC.

What's going to happen in a few days?

Good luck,

Thanks!

--
Bob Simon
remove x from domain to reply