WIA and hibernation again
in [Windows XP Basics]
|
Prev: Pressing Change Password -button in WIN XP causes reboot
Next: Microsoft caught pirating somebody's patent again!!!
From: Unknown on 8 Apr 2010 11:00 How does your NORTON program get updated? Is it automatic? "William B. Lurie" <billurie(a)nospam.net> wrote in message news:%23vUXUSy1KHA.3744(a)TK2MSFTNGP04.phx.gbl... > > >>>>> >> John, the next test was inconclusive because I may not have >> waited quite 2 hours, but it is already beginning to look as >> though the length of time to test with DCOM plus each succeeding service, >> and then the next one plus each of the rest, will end >> some time in the next decade, not this one. I'll pursue this tack >> a bit further, but it seems to me that *somebody*, maybe another >> one of the excellent MVPs, might know which 'service' has a one >> hour time clock built into it. > > I've snipped everything out because I think we're at a decision- > making point. I just don't think that the try-each-service approach > is going to be practical. Just too many services, too many possible > combinations, too little known about each, too long to make just one > test. I agree it's logical and sensible and proper scientific > technique, but it's like counting the grains of sand on the beach. > > Getting back to the 1 hour/2 hour problem, I feel we have eliminated > any running application program as a source, by just not loading them. > If they don't load, they don't execute, and if they don't execute, > they can't influence hibernation. > > So what *is* running? The system and its big-brother-given 'services'. > Rereading my last comment above, I hope I didn't offend anybody, but we > have to realize how enormously complex the XP system is, and it's too > much to expect any MVP to be intimately familiar with the inner workings > of all of its services. That's approaching the problem from the bottom > up. The question, down from the top, is, can we pick enough MVPs' brains > hard enough to find out which of the services is capable of preventing > the supposedly idle system from hibernating after 2 hours, but not after > only 1 hour.
From: William B. Lurie on 8 Apr 2010 13:23 Unknown wrote: > How does your NORTON program get updated? Is it automatic? No, I *never* allow any software supplier to do automatic stuff. Norton has automatic live update, which I keep turned off. I do manual live update periodically. That goes especially for Windows as well. John, I'd be willing to look at that what's-running-monitor, how do I grab it? > "William B. Lurie" <billurie(a)nospam.net> wrote in message > news:%23vUXUSy1KHA.3744(a)TK2MSFTNGP04.phx.gbl... >> >>> John, the next test was inconclusive because I may not have >>> waited quite 2 hours, but it is already beginning to look as >>> though the length of time to test with DCOM plus each succeeding service, >>> and then the next one plus each of the rest, will end >>> some time in the next decade, not this one. I'll pursue this tack >>> a bit further, but it seems to me that *somebody*, maybe another >>> one of the excellent MVPs, might know which 'service' has a one >>> hour time clock built into it. >> I've snipped everything out because I think we're at a decision- >> making point. I just don't think that the try-each-service approach >> is going to be practical. Just too many services, too many possible >> combinations, too little known about each, too long to make just one >> test. I agree it's logical and sensible and proper scientific >> technique, but it's like counting the grains of sand on the beach. >> >> Getting back to the 1 hour/2 hour problem, I feel we have eliminated >> any running application program as a source, by just not loading them. >> If they don't load, they don't execute, and if they don't execute, >> they can't influence hibernation. >> >> So what *is* running? The system and its big-brother-given 'services'. >> Rereading my last comment above, I hope I didn't offend anybody, but we >> have to realize how enormously complex the XP system is, and it's too >> much to expect any MVP to be intimately familiar with the inner workings >> of all of its services. That's approaching the problem from the bottom >> up. The question, down from the top, is, can we pick enough MVPs' brains >> hard enough to find out which of the services is capable of preventing >> the supposedly idle system from hibernating after 2 hours, but not after >> only 1 hour. > >
From: William B. Lurie on 8 Apr 2010 13:26 John John - MVP wrote: > William B. Lurie wrote: >> >> >>>>>> >>> John, the next test was inconclusive because I may not have >>> waited quite 2 hours, but it is already beginning to look as >>> though the length of time to test with DCOM plus each succeeding >>> service, and then the next one plus each of the rest, will end >>> some time in the next decade, not this one. I'll pursue this tack >>> a bit further, but it seems to me that *somebody*, maybe another >>> one of the excellent MVPs, might know which 'service' has a one >>> hour time clock built into it. >> >> I've snipped everything out because I think we're at a decision- >> making point. I just don't think that the try-each-service approach >> is going to be practical. > > No, it isn't, that is why it's best to do it in batches of 10 services > or so... I'd love to be able to do 10 at a shot, especially since there are over 100 to do, John. But In 2 tries, at doing only one at a time, one was acceptable and the second single blew. I have no reason to expect that 10 would play... (remember, my first bank of 10 was successful, the next one failed). How do I see Sysinternals' Process Monitor? >> [snip...} > >> So what *is* running? > > Sysinternals' Process Monitor will tell you that... > > John
From: John John - MVP on 8 Apr 2010 14:02 William B. Lurie wrote: > John John - MVP wrote: >> William B. Lurie wrote: >>> >>> >>>>>>> >>>> John, the next test was inconclusive because I may not have >>>> waited quite 2 hours, but it is already beginning to look as >>>> though the length of time to test with DCOM plus each succeeding >>>> service, and then the next one plus each of the rest, will end >>>> some time in the next decade, not this one. I'll pursue this tack >>>> a bit further, but it seems to me that *somebody*, maybe another >>>> one of the excellent MVPs, might know which 'service' has a one >>>> hour time clock built into it. >>> >>> I've snipped everything out because I think we're at a decision- >>> making point. I just don't think that the try-each-service approach >>> is going to be practical. >> >> No, it isn't, that is why it's best to do it in batches of 10 services >> or so... > > I'd love to be able to do 10 at a shot, especially since there > are over 100 to do, John. But In 2 tries, at doing only one at > a time, one was acceptable and the second single blew. I have > no reason to expect that 10 would play... (remember, my first bank of > 10 was successful, the next one failed). You don't need to put all the services on Automatic start! Just do the necessary ones, leave all the others to Manual. I already gave you a list of 10 services which you should keep Disabled. I don't know what you run on your computer but of the remaining list set these to Automatic and see what happens: Cryptographic Services DCOM Server Process Launcher DHCP Client Event Log Plug and Play Print Spooler Protected Storage Remote Procedure Call (RPC) Security Accounts Manager Shell Hardware Detection System Event Notification System Restore Service Task Scheduler Themes ** Windows Audio Windows Management Instrumentation Workstation ** If you are using Themes, if you use Classic look only you don't need this on Automatic. Of course, depending on what you do with your computer, you're probably going to need to have a few other services set to start automatically but the above list is all that is needed for most users who run standalone machines. > How do I see Sysinternals' Process Monitor? http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx John
From: William B. Lurie on 8 Apr 2010 14:14
John John - MVP wrote: > William B. Lurie wrote: >> John John - MVP wrote: >>> William B. Lurie wrote: >>>> >>>> >>>>>>>> >>>>> John, the next test was inconclusive because I may not have >>>>> waited quite 2 hours, but it is already beginning to look as >>>>> though the length of time to test with DCOM plus each succeeding >>>>> service, and then the next one plus each of the rest, will end >>>>> some time in the next decade, not this one. I'll pursue this tack >>>>> a bit further, but it seems to me that *somebody*, maybe another >>>>> one of the excellent MVPs, might know which 'service' has a one >>>>> hour time clock built into it. >>>> >>>> I've snipped everything out because I think we're at a decision- >>>> making point. I just don't think that the try-each-service approach >>>> is going to be practical. >>> >>> No, it isn't, that is why it's best to do it in batches of 10 >>> services or so... >> >> I'd love to be able to do 10 at a shot, especially since there >> are over 100 to do, John. But In 2 tries, at doing only one at >> a time, one was acceptable and the second single blew. I have >> no reason to expect that 10 would play... (remember, my first bank of >> 10 was successful, the next one failed). > > You don't need to put all the services on Automatic start! Just do the > necessary ones, leave all the others to Manual. > > I already gave you a list of 10 services which you should keep Disabled. > I don't know what you run on your computer but of the remaining list > set these to Automatic and see what happens: > > Cryptographic Services > DCOM Server Process Launcher > DHCP Client > Event Log > Plug and Play > Print Spooler > Protected Storage > Remote Procedure Call (RPC) > Security Accounts Manager > Shell Hardware Detection > System Event Notification > System Restore Service > Task Scheduler > Themes ** > Windows Audio > Windows Management Instrumentation > Workstation > > ** If you are using Themes, if you use Classic look only you don't need > this on Automatic. > > Of course, depending on what you do with your computer, you're probably > going to need to have a few other services set to start automatically > but the above list is all that is needed for most users who run > standalone machines. > > >> How do I see Sysinternals' Process Monitor? > > http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx > > John Okay, John, I'll set those to Automatic. But that still leaves about 70 more. BTW, what about RPC (Locator)? And do I really want to make Event Log Automatic? |