Re: WinXP screen saver password

From: Anando [MS-MVP] (anando_at_mvps.org)
Date: 07/12/04 

Date: Mon, 12 Jul 2004 20:59:21 +0530

Hi Andrew,

Make sure that you account is password protected to start off with. Secondly, only if the
screensaver starts on its own, will it prompt you for a password once you try to resume. 

-- 
Anando
Microsoft MVP- Windows Shell/User
http://www.microsoft.com/mvp
http://www.mvps.org
Folder customizations
http://newdelhi.sancharnet.in/minku
Protect your PC!
http://www.microsoft.com/protect
"Andrew" <anonymous@discussions.microsoft.com> wrote in message 
news:2b45701c46823$c0885240$a401280a@phx.gbl...
>I am running WinXP Professional on both my home and office
> computers, and I am trying to set password protection on
> my screen saver.  When I right-click on the desktop, I
> click on "Properties," then go to the "Screen Saver" tab.
> There is a check-box that reads "On resume, password
> protect," and I click on that, and a little check mark
> appears in the box.  According to the Win XP on-line help,
> that should set the password protection.
>
> The problem is the password prompt never appears.  On
> previous versions of Windows, clicking on the "Preview"
> button will start the screen saver, and it would prompt
> for a password, but not in WinXP.  I just move my mouse,
> and the desktop appears as usual.  When I set the screen
> saver to start after just one minute on inactivity, same
> result.  No matter what I try, I can't seem to enable the
> password protection on the screen saver.
>
> Yes, I know there is a way to lock the computer via Task
> Manager, but I'd gotten used to the convenience of putting
> a shortcut to my favorite screen saver on the Taskbar or
> the desktop, and just clicking on it to start the password-
> protected screen saver.
>
> I do need this at work, for obvious security reasons.  If
> I'm missing something, or if anybody has any ideas, I
> would appreciate it.  BTW, I am the administrator on my
> home PC, but not my office PC, if that helps, but it
> doesn't make any difference for this problem, because it
> is the same on both my home and office PCs.  Thanks.