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: John John - MVP on 8 Apr 2010 14:32 William B. Lurie wrote: > 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. Don't worry about those 70 other ones, at least not for now. Most of them can stay on Manual, the operating system will start them if they are needed. Being on manual doesn't mean that they can't be run, it just means that they won't start unless they are needed. There are a few others that you will probably want to have on Automatic but you can deal with those in the "second" batch of trial services, for the time being stick with the above. BTW, what about RPC (Locator)? Leave it on manual, that is the default setting for it when you install Windows, there is no need to have it set to Automatic. > And do I really want to make Event Log Automatic? Yes, ABSOLUTELY! Always! John
From: Unknown on 8 Apr 2010 15:41 Something is interfacing, calling or activating DCOM. If you cripple DCOM will you get a logging of an error? DCOM is not needed. "William B. Lurie" <billurie(a)nospam.net> wrote in message news:OJVWmA01KHA.3652(a)TK2MSFTNGP04.phx.gbl... > 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 17:48 John John - MVP wrote: > William B. Lurie wrote: >> 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. > > Don't worry about those 70 other ones, at least not for now. Most of > them can stay on Manual, the operating system will start them if they > are needed. Being on manual doesn't mean that they can't be run, it > just means that they won't start unless they are needed. There are a > few others that you will probably want to have on Automatic but you can > deal with those in the "second" batch of trial services, for the time > being stick with the above. > > > BTW, what about RPC (Locator)? > > Leave it on manual, that is the default setting for it when you install > Windows, there is no need to have it set to Automatic. > > >> And do I really want to make Event Log Automatic? > > Yes, ABSOLUTELY! Always! > > John For what it's worth, I have some new Events to report, but I'm not sure what all the settings were. But maybe they say something......: > Type Date Time Source Category Event User Computer > Information 4/8/2010 2:47:52 PM Ci CI Service 4137 N/A COMPAQ-2006 > Warning 4/8/2010 2:41:23 PM EventSystem (54) 4353 N/A COMPAQ-2006 > Warning 4/8/2010 2:41:23 PM EventSystem (52) 4356 N/A COMPAQ-2006 > Warning 4/8/2010 2:41:23 PM EventSystem (54) 4353 N/A COMPAQ-2006 > Warning 4/8/2010 2:41:23 PM EventSystem (52) 4356 N/A COMPAQ-2006 > Information 4/8/2010 2:41:20 PM ASP.NET 2.0.50727.0 None 1076 N/A COMPAQ-2006 > Information 4/8/2010 2:28:40 PM Ci CI Service 4137 N/A COMPAQ-2006 > Warning 4/8/2010 2:21:41 PM EventSystem (54) 4353 N/A COMPAQ-2006 > Warning 4/8/2010 2:21:41 PM EventSystem (52) 4356 N/A COMPAQ-2006 > Warning 4/8/2010 2:21:41 PM EventSystem (54) 4353 N/A COMPAQ-2006 > Warning 4/8/2010 2:21:41 PM EventSystem (52) 4356 N/A COMPAQ-2006 > Information 4/8/2010 2:21:35 PM ASP.NET 2.0.50727.0 None 1076 N/A COMPAQ-2006 > Success Audit 4/8/2010 2:41:22 PM Security Logon/Logoff 540 ANONYMOUS LOGON COMPAQ-2006 > Success Audit 4/8/2010 2:41:21 PM Security Privilege Use 576 NETWORK SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:41:21 PM Security Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:41:20 PM Security Privilege Use 576 NETWORK SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:41:20 PM Security Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:41:20 PM Security Privilege Use 576 LOCAL SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:41:20 PM Security Logon/Logoff 528 LOCAL SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:41:18 PM Security Privilege Use 576 NETWORK SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:41:18 PM Security Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:41:17 PM Security Privilege Use 576 LOCAL SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:41:17 PM Security Logon/Logoff 528 LOCAL SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:41:17 PM Security Privilege Use 576 LOCAL SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:41:17 PM Security Logon/Logoff 528 LOCAL SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:40:34 PM Security Privilege Use 576 Compaq_Owner COMPAQ-2006 > Success Audit 4/8/2010 2:40:34 PM Security Logon/Logoff 528 Compaq_Owner COMPAQ-2006 > Success Audit 4/8/2010 2:40:34 PM Security Account Logon 680 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:40:34 PM Security Logon/Logoff 538 Compaq_Owner COMPAQ-2006 > Success Audit 4/8/2010 2:40:34 PM Security Privilege Use 576 Compaq_Owner COMPAQ-2006 > Success Audit 4/8/2010 2:40:34 PM Security Logon/Logoff 528 Compaq_Owner COMPAQ-2006 > Success Audit 4/8/2010 2:40:34 PM Security Account Logon 680 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:40:34 PM Security System Event 515 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:40:33 PM Security Policy Change 806 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:40:33 PM Security System Event 515 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:40:30 PM Security Privilege Use 576 NETWORK SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:40:30 PM Security Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:40:30 PM Security System Event 518 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:40:30 PM Security System Event 515 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:40:30 PM Security System Event 515 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:40:30 PM Security System Event 515 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:40:30 PM Security System Event 514 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:40:30 PM Security System Event 514 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:40:30 PM Security System Event 514 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:40:30 PM Security System Event 514 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:40:30 PM Security System Event 514 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:40:30 PM Security System Event 514 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:40:29 PM Security System Event 514 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:33:33 PM Security System Event 513 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:33:25 PM Security Logon/Logoff 551 Compaq_Owner COMPAQ-2006 > Success Audit 4/8/2010 2:21:40 PM Security Logon/Logoff 540 ANONYMOUS LOGON COMPAQ-2006 > Success Audit 4/8/2010 2:21:38 PM Security Privilege Use 576 NETWORK SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:21:38 PM Security Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:21:35 PM Security Privilege Use 576 NETWORK SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:21:35 PM Security Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:21:35 PM Security Privilege Use 576 LOCAL SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:21:35 PM Security Logon/Logoff 528 LOCAL SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:21:28 PM Security Privilege Use 576 NETWORK SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:21:28 PM Security Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:21:28 PM Security Privilege Use 576 LOCAL SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:21:28 PM Security Logon/Logoff 528 LOCAL SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:21:27 PM Security Privilege Use 576 LOCAL SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:21:27 PM Security Logon/Logoff 528 LOCAL SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:21:16 PM Security Policy Change 806 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:21:16 PM Security Privilege Use 576 Compaq_Owner COMPAQ-2006 > Success Audit 4/8/2010 2:21:16 PM Security Logon/Logoff 528 Compaq_Owner COMPAQ-2006 > Success Audit 4/8/2010 2:21:16 PM Security Account Logon 680 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:21:15 PM Security Logon/Logoff 538 Compaq_Owner COMPAQ-2006 > Success Audit 4/8/2010 2:21:15 PM Security Privilege Use 576 Compaq_Owner COMPAQ-2006 > Success Audit 4/8/2010 2:21:15 PM Security Logon/Logoff 528 Compaq_Owner COMPAQ-2006 > Success Audit 4/8/2010 2:21:15 PM Security Account Logon 680 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:21:15 PM Security System Event 515 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:21:15 PM Security System Event 515 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:21:12 PM Security Privilege Use 576 NETWORK SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:21:12 PM Security Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 > Success Audit 4/8/2010 2:21:12 PM Security System Event 518 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:21:12 PM Security System Event 515 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:21:12 PM Security System Event 515 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:21:12 PM Security System Event 515 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:21:12 PM Security System Event 514 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:21:12 PM Security System Event 514 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:21:12 PM Security System Event 514 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:21:12 PM Security System Event 514 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:21:12 PM Security System Event 514 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:21:12 PM Security System Event 514 SYSTEM COMPAQ-2006 > Success Audit 4/8/2010 2:21:12 PM Security System Event 514 SYSTEM COMPAQ-2006 > > Type Date Time Source Category Event User Computer > Information 4/8/2010 2:40:05 PM Tcpip None 4201 N/A COMPAQ-2006 > Information 4/8/2010 2:40:29 PM eventlog None 6005 N/A COMPAQ-2006 > Information 4/8/2010 2:40:29 PM eventlog None 6009 N/A COMPAQ-2006 > Information 4/8/2010 2:33:33 PM eventlog None 6006 N/A COMPAQ-2006 > Error 4/8/2010 2:24:07 PM NetDDE None 206 N/A COMPAQ-2006 > Information 4/8/2010 2:20:52 PM Tcpip None 4201 N/A COMPAQ-2006 > Information 4/8/2010 2:21:11 PM eventlog None 6005 N/A COMPAQ-2006 > Information 4/8/2010 2:21:11 PM eventlog None 6009 N/A COMPAQ-2006 > > Event Type: Information > Event Source: Ci > Event Category: CI Service > Event ID: 4137 > Date: 4/8/2010 > Time: 2:47:52 PM > User: N/A > Computer: COMPAQ-2006 > Description: > CI has started for catalog c:\system volume information\catalog.wci. > John, what the above shows, time-wise, is that however I set it up, it was after I made that whole batch automatic. I walked away at 2:21, and at 2:28 and again at 2:40-ish something interfered, and of course it never ended up hibernating.
From: William B. Lurie on 8 Apr 2010 20:44 William B. Lurie wrote: > John John - MVP wrote: >> William B. Lurie wrote: >>> 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. >> >> Don't worry about those 70 other ones, at least not for now. Most of >> them can stay on Manual, the operating system will start them if they >> are needed. Being on manual doesn't mean that they can't be run, it >> just means that they won't start unless they are needed. There are a >> few others that you will probably want to have on Automatic but you >> can deal with those in the "second" batch of trial services, for the >> time being stick with the above. >> >> >> BTW, what about RPC (Locator)? >> >> Leave it on manual, that is the default setting for it when you >> install Windows, there is no need to have it set to Automatic. >> >> >>> And do I really want to make Event Log Automatic? >> >> Yes, ABSOLUTELY! Always! >> >> John > For what it's worth, I have some new Events to report, > but I'm not sure what all the settings were. But maybe they > say something......: > >> Type Date Time Source Category Event User Computer >> Information 4/8/2010 2:47:52 PM Ci CI Service 4137 >> N/A COMPAQ-2006 >> Warning 4/8/2010 2:41:23 PM EventSystem (54) 4353 >> N/A COMPAQ-2006 >> Warning 4/8/2010 2:41:23 PM EventSystem (52) 4356 >> N/A COMPAQ-2006 >> Warning 4/8/2010 2:41:23 PM EventSystem (54) 4353 >> N/A COMPAQ-2006 >> Warning 4/8/2010 2:41:23 PM EventSystem (52) 4356 >> N/A COMPAQ-2006 >> Information 4/8/2010 2:41:20 PM ASP.NET 2.0.50727.0 >> None 1076 N/A COMPAQ-2006 >> Information 4/8/2010 2:28:40 PM Ci CI Service 4137 >> N/A COMPAQ-2006 >> Warning 4/8/2010 2:21:41 PM EventSystem (54) 4353 >> N/A COMPAQ-2006 >> Warning 4/8/2010 2:21:41 PM EventSystem (52) 4356 >> N/A COMPAQ-2006 >> Warning 4/8/2010 2:21:41 PM EventSystem (54) 4353 >> N/A COMPAQ-2006 >> Warning 4/8/2010 2:21:41 PM EventSystem (52) 4356 >> N/A COMPAQ-2006 >> Information 4/8/2010 2:21:35 PM ASP.NET 2.0.50727.0 >> None 1076 N/A COMPAQ-2006 > >> Success Audit 4/8/2010 2:41:22 PM Security >> Logon/Logoff 540 ANONYMOUS LOGON COMPAQ-2006 >> Success Audit 4/8/2010 2:41:21 PM Security Privilege >> Use 576 NETWORK SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:41:21 PM Security >> Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:41:20 PM Security Privilege >> Use 576 NETWORK SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:41:20 PM Security >> Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:41:20 PM Security Privilege >> Use 576 LOCAL SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:41:20 PM Security >> Logon/Logoff 528 LOCAL SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:41:18 PM Security Privilege >> Use 576 NETWORK SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:41:18 PM Security >> Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:41:17 PM Security Privilege >> Use 576 LOCAL SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:41:17 PM Security >> Logon/Logoff 528 LOCAL SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:41:17 PM Security Privilege >> Use 576 LOCAL SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:41:17 PM Security >> Logon/Logoff 528 LOCAL SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:40:34 PM Security Privilege >> Use 576 Compaq_Owner COMPAQ-2006 >> Success Audit 4/8/2010 2:40:34 PM Security >> Logon/Logoff 528 Compaq_Owner COMPAQ-2006 >> Success Audit 4/8/2010 2:40:34 PM Security Account >> Logon 680 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:40:34 PM Security >> Logon/Logoff 538 Compaq_Owner COMPAQ-2006 >> Success Audit 4/8/2010 2:40:34 PM Security Privilege >> Use 576 Compaq_Owner COMPAQ-2006 >> Success Audit 4/8/2010 2:40:34 PM Security >> Logon/Logoff 528 Compaq_Owner COMPAQ-2006 >> Success Audit 4/8/2010 2:40:34 PM Security Account >> Logon 680 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:40:34 PM Security System >> Event 515 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:40:33 PM Security Policy >> Change 806 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:40:33 PM Security System >> Event 515 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:40:30 PM Security Privilege >> Use 576 NETWORK SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:40:30 PM Security >> Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:40:30 PM Security System >> Event 518 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:40:30 PM Security System >> Event 515 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:40:30 PM Security System >> Event 515 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:40:30 PM Security System >> Event 515 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:40:30 PM Security System >> Event 514 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:40:30 PM Security System >> Event 514 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:40:30 PM Security System >> Event 514 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:40:30 PM Security System >> Event 514 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:40:30 PM Security System >> Event 514 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:40:30 PM Security System >> Event 514 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:40:29 PM Security System >> Event 514 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:33:33 PM Security System >> Event 513 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:33:25 PM Security >> Logon/Logoff 551 Compaq_Owner COMPAQ-2006 >> Success Audit 4/8/2010 2:21:40 PM Security >> Logon/Logoff 540 ANONYMOUS LOGON COMPAQ-2006 >> Success Audit 4/8/2010 2:21:38 PM Security Privilege >> Use 576 NETWORK SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:21:38 PM Security >> Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:21:35 PM Security Privilege >> Use 576 NETWORK SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:21:35 PM Security >> Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:21:35 PM Security Privilege >> Use 576 LOCAL SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:21:35 PM Security >> Logon/Logoff 528 LOCAL SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:21:28 PM Security Privilege >> Use 576 NETWORK SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:21:28 PM Security >> Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:21:28 PM Security Privilege >> Use 576 LOCAL SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:21:28 PM Security >> Logon/Logoff 528 LOCAL SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:21:27 PM Security Privilege >> Use 576 LOCAL SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:21:27 PM Security >> Logon/Logoff 528 LOCAL SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:21:16 PM Security Policy >> Change 806 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:21:16 PM Security Privilege >> Use 576 Compaq_Owner COMPAQ-2006 >> Success Audit 4/8/2010 2:21:16 PM Security >> Logon/Logoff 528 Compaq_Owner COMPAQ-2006 >> Success Audit 4/8/2010 2:21:16 PM Security Account >> Logon 680 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:21:15 PM Security >> Logon/Logoff 538 Compaq_Owner COMPAQ-2006 >> Success Audit 4/8/2010 2:21:15 PM Security Privilege >> Use 576 Compaq_Owner COMPAQ-2006 >> Success Audit 4/8/2010 2:21:15 PM Security >> Logon/Logoff 528 Compaq_Owner COMPAQ-2006 >> Success Audit 4/8/2010 2:21:15 PM Security Account >> Logon 680 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:21:15 PM Security System >> Event 515 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:21:15 PM Security System >> Event 515 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:21:12 PM Security Privilege >> Use 576 NETWORK SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:21:12 PM Security >> Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 >> Success Audit 4/8/2010 2:21:12 PM Security System >> Event 518 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:21:12 PM Security System >> Event 515 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:21:12 PM Security System >> Event 515 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:21:12 PM Security System >> Event 515 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:21:12 PM Security System >> Event 514 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:21:12 PM Security System >> Event 514 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:21:12 PM Security System >> Event 514 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:21:12 PM Security System >> Event 514 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:21:12 PM Security System >> Event 514 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:21:12 PM Security System >> Event 514 SYSTEM COMPAQ-2006 >> Success Audit 4/8/2010 2:21:12 PM Security System >> Event 514 SYSTEM COMPAQ-2006 >> >> Type Date Time Source Category Event User Computer >> Information 4/8/2010 2:40:05 PM Tcpip None 4201 >> N/A COMPAQ-2006 >> Information 4/8/2010 2:40:29 PM eventlog None 6005 >> N/A COMPAQ-2006 >> Information 4/8/2010 2:40:29 PM eventlog None 6009 >> N/A COMPAQ-2006 >> Information 4/8/2010 2:33:33 PM eventlog None 6006 >> N/A COMPAQ-2006 >> Error 4/8/2010 2:24:07 PM NetDDE None 206 N/A >> COMPAQ-2006 >> Information 4/8/2010 2:20:52 PM Tcpip None 4201 >> N/A COMPAQ-2006 >> Information 4/8/2010 2:21:11 PM eventlog None 6005 >> N/A COMPAQ-2006 >> Information 4/8/2010 2:21:11 PM eventlog None 6009 >> N/A COMPAQ-2006 >> >> Event Type: Information >> Event Source: Ci >> Event Category: CI Service Event ID: 4137 >> Date: 4/8/2010 >> Time: 2:47:52 PM >> User: N/A >> Computer: COMPAQ-2006 >> Description: >> CI has started for catalog c:\system volume information\catalog.wci. >> > > John, what the above shows, time-wise, is that however I set it up, > it was after I made that whole batch automatic. I walked away at 2:21, > and at 2:28 and again at 2:40-ish something interfered, and of course it > never ended up hibernating. And now another run...... > Type Date Time Source Category Event User Computer > Information 4/8/2010 5:59:01 PM Ci CI Service 4137 N/A COMPAQ-2006 > Warning 4/8/2010 5:52:02 PM EventSystem (54) 4353 N/A COMPAQ-2006 > Warning 4/8/2010 5:52:02 PM EventSystem (52) 4356 N/A COMPAQ-2006 > Warning 4/8/2010 5:52:02 PM EventSystem (54) 4353 N/A COMPAQ-2006 > Warning 4/8/2010 5:52:02 PM EventSystem (52) 4356 N/A COMPAQ-2006 > Information 4/8/2010 5:51:56 PM ASP.NET 2.0.50727.0 None 1076 N/A COMPAQ-2006 > Started it at 5:52 and 7 minutes later in recorder an Information Event.....and then ran almost 2 hours before some unknown and unrecorded distrurbanc caused it to come alive, as evidenced by the desktop and icons coming on. I'll try this one again later this evening and record more.
From: John John - MVP on 8 Apr 2010 21:09
William B. Lurie wrote: >> Event Type: Information >> Event Source: Ci >> Event Category: CI Service Event ID: 4137 >> Date: 4/8/2010 >> Time: 2:47:52 PM >> User: N/A >> Computer: COMPAQ-2006 >> Description: >> CI has started for catalog c:\system volume information\catalog.wci. >> > > John, what the above shows, time-wise, is that however I set it up, > it was after I made that whole batch automatic. I walked away at 2:21, > and at 2:28 and again at 2:40-ish something interfered, and of course it > never ended up hibernating. That is the Indexing Service, Bill. This was discussed in an earlier post. Why is it on? Is it still set to Automatic start? John |