G
Gene E. Bloch
Flightless Bird
This reminds me a lot of my post in this thread.
On 1/15/10, Michael Walraven posted:
> John,
> For future use:
> You could try enabling 1/2 of the items in a list. If the symptom persists
> then problem is in the enabled 1/2, otherwise in the disabled 1/2.
> Using the part that has the problem, divide again in 1/2 and repeat. It
> quickly results in the culprit ( if only one culprit that is).
> Advice too late for you this time but maybe next time :}
> Michael
> "John McGaw" <Nobody@Nowh.ere> wrote in message
> news:eF64n.94186$5n7.54127@en-nntp-09.dc1.easynews.com...
>> On 1/15/2010 4:14 PM, John McGaw wrote:
>>> On 1/15/2010 3:08 PM, Seth wrote:
>>>> "John McGaw" <Nobody@Nowh.ere> wrote in message
>>>> news:h024n.48827$oC1.8667@en-nntp-01.dc1.easynews.com...
>>>>>
>>>>> By way of restarting everything normally I told the system to restart
>>>>> and then went to get some lunch. I came back and the monitor was
>>>>> sleeping. But I was at login then and after logging on the monitor
>>>>> would no longer sleep. So that means that something is happening that
>>>>> doesn't happen at the login screen which is killing the monitor sleep
>>>>> function. I'm about ready to admit defeat for the moment and move on.
>>>>> I get the feeling that when (if?) the problem is identified it will be
>>>>> by luck and not logic.
>>>>
>>>>
>>>> OK, now we may be getting somewhere... Probably some app or utility
>>>> running in the user space that's causing it. The system doesn't know if
>>>> it's "inactive" if certain things that get monitored are constantly
>>>> being tickled.
>>>>
>>>> What's running out of your Startup group as well as HKCU and HKLM
>>>> \SOFTWARE\Microsoft\Windows\CurrentVersion\Run ?
>>>>
>>>> One of those items (or the app that runs on this machine) may be needing
>>>> an upgrade to a Win7 compliant version.
>>>>
>>>
>>> I don't doubt that you are right. It is something running after login.
>>> However enough is being autostarted on login that it is going to take a
>>> very long time to figure it out. Probably eliminating one at a time will
>>> be the only way accomplish it and I just don't have the time right now
>>> to tackle that project. At least it is narrowed down enough that an end
>>> is (distantly) in sight.
>>
>> Well, I finally worked it out. But the final answer still baffles me.
>>
>> I installed AutoRuns and then disabled every item that I could imagine no
>> use for and all of the ones from questionable sources. Then I set monitor
>> sleep to 1 minute and started testing. The first go-round I knew that
>> something good had happened since the monitor slept. So then it was a
>> matter of enabling one item at a time and rebooting and waiting. Long story
>> made short: on the ninth reboot I hit paydirt. A task called NB Agent was
>> the culprit. The surprising thing is that this is part of Nero's Backitup.
>> This is one of the companies I would have trusted pretty far and I disabled
>> it not realizing that it was their program. Needless to say I'm
>> uninstalling their backup program right away. No money lost though since
>> the gave it to me as a free bonus when I bought Nero 9.
>>
>> So ends the tale...
>>
--
Gene Bloch 650.366.4267 lettersatblochg.com
On 1/15/10, Michael Walraven posted:
> John,
> For future use:
> You could try enabling 1/2 of the items in a list. If the symptom persists
> then problem is in the enabled 1/2, otherwise in the disabled 1/2.
> Using the part that has the problem, divide again in 1/2 and repeat. It
> quickly results in the culprit ( if only one culprit that is).
> Advice too late for you this time but maybe next time :}
> Michael
> "John McGaw" <Nobody@Nowh.ere> wrote in message
> news:eF64n.94186$5n7.54127@en-nntp-09.dc1.easynews.com...
>> On 1/15/2010 4:14 PM, John McGaw wrote:
>>> On 1/15/2010 3:08 PM, Seth wrote:
>>>> "John McGaw" <Nobody@Nowh.ere> wrote in message
>>>> news:h024n.48827$oC1.8667@en-nntp-01.dc1.easynews.com...
>>>>>
>>>>> By way of restarting everything normally I told the system to restart
>>>>> and then went to get some lunch. I came back and the monitor was
>>>>> sleeping. But I was at login then and after logging on the monitor
>>>>> would no longer sleep. So that means that something is happening that
>>>>> doesn't happen at the login screen which is killing the monitor sleep
>>>>> function. I'm about ready to admit defeat for the moment and move on.
>>>>> I get the feeling that when (if?) the problem is identified it will be
>>>>> by luck and not logic.
>>>>
>>>>
>>>> OK, now we may be getting somewhere... Probably some app or utility
>>>> running in the user space that's causing it. The system doesn't know if
>>>> it's "inactive" if certain things that get monitored are constantly
>>>> being tickled.
>>>>
>>>> What's running out of your Startup group as well as HKCU and HKLM
>>>> \SOFTWARE\Microsoft\Windows\CurrentVersion\Run ?
>>>>
>>>> One of those items (or the app that runs on this machine) may be needing
>>>> an upgrade to a Win7 compliant version.
>>>>
>>>
>>> I don't doubt that you are right. It is something running after login.
>>> However enough is being autostarted on login that it is going to take a
>>> very long time to figure it out. Probably eliminating one at a time will
>>> be the only way accomplish it and I just don't have the time right now
>>> to tackle that project. At least it is narrowed down enough that an end
>>> is (distantly) in sight.
>>
>> Well, I finally worked it out. But the final answer still baffles me.
>>
>> I installed AutoRuns and then disabled every item that I could imagine no
>> use for and all of the ones from questionable sources. Then I set monitor
>> sleep to 1 minute and started testing. The first go-round I knew that
>> something good had happened since the monitor slept. So then it was a
>> matter of enabling one item at a time and rebooting and waiting. Long story
>> made short: on the ninth reboot I hit paydirt. A task called NB Agent was
>> the culprit. The surprising thing is that this is part of Nero's Backitup.
>> This is one of the companies I would have trusted pretty far and I disabled
>> it not realizing that it was their program. Needless to say I'm
>> uninstalling their backup program right away. No money lost though since
>> the gave it to me as a free bonus when I bought Nero 9.
>>
>> So ends the tale...
>>
--
Gene Bloch 650.366.4267 lettersatblochg.com