Screen Saver does not start

Desktop, 64-bit Win 7 Pro. No wireless keyboard or mouse.

Any ideas?

Thanks,


--
Andrew Hall
(Now reading Usenet in alt.windows7.general...)

Start Task Manager, Show processes for all users. see what's keeping it
awake.

On 5/21/2012 10:02 AM, wrote:
>
> Desktop, 64-bit Win 7 Pro. No wireless keyboard or mouse.
>
> Any ideas?
>
> Thanks,
>
>

On Mon, 21 May 2012 18:24:45 -0500, Bob I <> wrote:

>On 5/21/2012 10:02 AM, wrote:
>>
>> Desktop, 64-bit Win 7 Pro. No wireless keyboard or mouse.
>>
>> Any ideas?
>
>Start Task Manager, Show processes for all users. see what's keeping it
>awake.

I'm curious... How would you be able to tell which process is the one
that's preventing the screen saver from starting?

--

Char Jackson

<> wrote:

> Desktop, 64-bit Win 7 Pro. No wireless keyboard or mouse.

Speculation: you are using a Microsoft-supplied desktop theme.

If you configure the system to set up a screensaver and later select a
Microsoft theme, the theme will quietly turn off the screensaver.

I ran into that when I was designing the Win7 configuration for my POE.

Joe

"Char Jackson" <> wrote:
> Bob I <> wrote:
>>On 5/21/2012 10:02 AM, wrote:

>>> Desktop, 64-bit Win 7 Pro. No wireless keyboard or mouse.

>>Start Task Manager, Show processes for all users. see what's keeping it
>>awake.

> I'm curious... How would you be able to tell which process is the one
> that's preventing the screen saver from starting?

One way would be process of elimination. Start with nothing running but the
base system; if the screensaver pops start adding the other tasks until the
screensaver no longer comes up.

There is a defined API by which a process can suppress idle detection,
intended for situations where interruption would impact the user
experience - video and audio playback, for example. At one point (some time
back) I looked for but didn't find a way to turn off the suppression from an
external process, and at this instant I can't even recall the API name.

Joe

"Joe Morris" <> writes:

> "Char Jackson" <> wrote:
>> Bob I <> wrote:
>>>On 5/21/2012 10:02 AM, wrote:
>
>>>> Desktop, 64-bit Win 7 Pro. No wireless keyboard or mouse.
>
>>>Start Task Manager, Show processes for all users. see what's keeping it
>>>awake.
>
>> I'm curious... How would you be able to tell which process is the one
>> that's preventing the screen saver from starting?

I had the same thought, but tried to see if I could tell anything.
Sure enough the only process that took any CPU time while I sat on
my hands was the Wacom Tablet. I had a wacom mouse sitting on the
tablet, and every 10-20 seconds there was a 1% CPU use from the Wacom
process. I put the mouse away from the pad, and the screen saver
is working again.

Thanks all!

> One way would be process of elimination. Start with nothing running but the
> base system; if the screensaver pops start adding the other tasks until the
> screensaver no longer comes up.
>

> There is a defined API by which a process can suppress idle detection,
> intended for situations where interruption would impact the user
> experience - video and audio playback, for example. At one point (some time
> back) I looked for but didn't find a way to turn off the suppression from an
> external process, and at this instant I can't even recall the API name.
>
> Joe


--
Andrew Hall
(Now reading Usenet in alt.windows7.general...)

wrote:
> "Joe Morris"<> writes:
>
>> "Char Jackson"<> wrote:
>>> Bob I<> wrote:
>>>> On 5/21/2012 10:02 AM, wrote:
>>
>>>>> Desktop, 64-bit Win 7 Pro. No wireless keyboard or mouse.
>>
>>>> Start Task Manager, Show processes for all users. see what's keeping it
>>>> awake.
>>
>>> I'm curious... How would you be able to tell which process is the one
>>> that's preventing the screen saver from starting?
>
> I had the same thought, but tried to see if I could tell anything.
> Sure enough the only process that took any CPU time while I sat on
> my hands was the Wacom Tablet. I had a wacom mouse sitting on the
> tablet, and every 10-20 seconds there was a 1% CPU use from the Wacom
> process. I put the mouse away from the pad, and the screen saver
> is working again.
>
> Thanks all!
>
>> One way would be process of elimination. Start with nothing running but the
>> base system; if the screensaver pops start adding the other tasks until the
>> screensaver no longer comes up.
>>
>
>> There is a defined API by which a process can suppress idle detection,
>> intended for situations where interruption would impact the user
>> experience - video and audio playback, for example. At one point (some time
>> back) I looked for but didn't find a way to turn off the suppression from an
>> external process, and at this instant I can't even recall the API name.
>>
>> Joe
>
>

Thanks for letting us know what fixed it!

--
JD..

I thought that part was obvious, if the CPU is showing something running
up the usage that's the offender.

On 5/21/2012 8:10 PM, Char Jackson wrote:
> On Mon, 21 May 2012 18:24:45 -0500, Bob I<> wrote:
>
>> On 5/21/2012 10:02 AM, wrote:
>>>
>>> Desktop, 64-bit Win 7 Pro. No wireless keyboard or mouse.
>>>
>>> Any ideas?
>>
>> Start Task Manager, Show processes for all users. see what's keeping it
>> awake.
>
> I'm curious... How would you be able to tell which process is the one
> that's preventing the screen saver from starting?
>

On Tue, 22 May 2012 18:12:59 -0500, Bob I <> wrote:

>On 5/21/2012 8:10 PM, Char Jackson wrote:
>> On Mon, 21 May 2012 18:24:45 -0500, Bob I<> wrote:
>>
>>> On 5/21/2012 10:02 AM, wrote:
>>>>
>>>> Desktop, 64-bit Win 7 Pro. No wireless keyboard or mouse.
>>>>
>>>> Any ideas?
>>>
>>> Start Task Manager, Show processes for all users. see what's keeping it
>>> awake.
>>
>> I'm curious... How would you be able to tell which process is the one
>> that's preventing the screen saver from starting?
>>
>I thought that part was obvious, if the CPU is showing something running
>up the usage that's the offender.

I believe that's a bad assumption.

--

Char Jackson

"" <> wrote in message
news::

> Desktop, 64-bit Win 7 Pro. No wireless keyboard or mouse.
>
> Any ideas?

Others have already suggested looking for some application that is
preventing the screen saver. (Macro processors like Macro Express often
do this. What's the point of playing back keystrokes on a screen
displaying a screen saver?)

If that doesn't fix it, it could also be due to a corrupted user
profile.

http://beingpc.com/2011/02/how-to-re...-in-windows-7/




-- Steven L.