Vista - Screensaver doesn't kick in

This seems to be a problem that has been in Windows since at least Windows
2000. In my Vista Ultimate SP1 32-bit system the screensaver doesn't always
kick in after the specified time. It's so unreliable that I had been
remembering to modify the number of minutes every time I was going away from
my laptop as this used to be a way of making it kick in. But even that
method is unreliable and these days it seems that about 9 times out 10 the
screen saver just doesn't function.

Is there any way to fix this?

--
And loving it,

-Q
_________________________________________________
Qu0llSixFour@xxxxxx
(Replace the "SixFour" with numbers to email me)

Hi,

The fix is to figure out what software you are running that is interfering
with it kicking on. I've never had any Windows machine (or linux for that
matter) that the screensaver did not work on. Start by disabling background
applications, especially AV, P2P, IM, and distributed computing programs.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"Qu0ll" <Qu0llSixFour@xxxxxx> wrote in message
news:BB8BC3B4-E9B7-463A-85F7-CED4E273E2D2@xxxxxx

"Rick Rogers" <rick@xxxxxx> wrote in message
news:#elLNQnpIHA.2064@xxxxxx
Well I have never had a Windows machine of any flavour that had a
screensaver that worked ALL the time. My Linux machines have never had such
problems.

OK so I need to disable some background process... but what's the point of
disabling AV when everyone knows you cannot live without it? I don't use
any IM or P2P programs so what else could it be?

--
And loving it,

-Q
_________________________________________________
Qu0llSixFour@xxxxxx
(Replace the "SixFour" with numbers to email me)

Hi,

I just listed the most frequent causes, you're going to have to run the
gamut of software on your installation to figure it out. Look especially at
the autoloads section. Make sure you include any services they add as well,
not just the program.

I'm not suggesting you run without AV, but you do need to eliminate it as a
potential cause.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"Qu0ll" <Qu0llSixFour@xxxxxx> wrote in message
news:6532B499-D88E-47CC-9510-F5F59A14729F@xxxxxx