From: John John - MVP on
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.

Is the machine still connected to the internet or to a LAN? Disconnect
from both while you troubleshoot the problem!

John
From: William B. Lurie on
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 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.
>
> Is the machine still connected to the internet or to a LAN? Disconnect
> from both while you troubleshoot the problem!
>
> John
John, I thought I made that clear. On each and every test run,
I restart the computer in order to reboot to the the test system,
and while it is booting, I physically disconnect the phone line
as it enters the modem from the wall outlet. As for LAN.......
I am a poor single-line homeowner with only one line of access
to the world of information, other than Comcast cable for TV.

And as for Ci which we discussed earlier, I can't put my finger on it;
please tell me again what to disable to stop it from cataloguing
system volume information at what appears to be random odd times.

I have another overnight run to report later, showing that
same intervention.
Bill
From: William B. Lurie on
William B. Lurie wrote:
(snip)
>>>> 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.
>>
>> Is the machine still connected to the internet or to a LAN?
>> Disconnect from both while you troubleshoot the problem!
>>
>> John
> John, I thought I made that clear. On each and every test run,
> I restart the computer in order to reboot to the the test system,
> and while it is booting, I physically disconnect the phone line
> as it enters the modem from the wall outlet. As for LAN.......
> I am a poor single-line homeowner with only one line of access
> to the world of information, other than Comcast cable for TV.
>
> And as for Ci which we discussed earlier, I can't put my finger on it;
> please tell me again what to disable to stop it from cataloguing
> system volume information at what appears to be random odd times.
>
> I have another overnight run to report later, showing that
> same intervention.
> Bill

But continuing on, another few bits of news.
I Disabled Indexing Service at 5:55 A.M. this morning and rebooted.
At 0700 screen was still black, power light still flashing, and I
thought maybe it would go the full 2 hours......only had 55 minutes
to go. At 0745 on came the desktop, followed by the "Preparing to
standby" message, and I figured I wouldn't wait another 100 minutes
to see if it would hibernate. More important to report what the Events
were. I filed the following from the Log:

> Type Date Time Source Category Event User Computer
> Warning 4/9/2010 5:56:51 AM EventSystem (54) 4353 N/A COMPAQ-2006
> Warning 4/9/2010 5:56:51 AM EventSystem (52) 4356 N/A COMPAQ-2006
> Warning 4/9/2010 5:56:51 AM EventSystem (54) 4353 N/A COMPAQ-2006
> Warning 4/9/2010 5:56:51 AM EventSystem (52) 4356 N/A COMPAQ-2006
> Information 4/9/2010 5:56:47 AM ASP.NET 2.0.50727.0 None 1076 N/A COMPAQ-2006
> Warning 4/9/2010 5:52:17 AM EventSystem (54) 4353 N/A COMPAQ-2006
> Warning 4/9/2010 5:52:17 AM EventSystem (52) 4356 N/A COMPAQ-2006
> Warning 4/9/2010 5:52:17 AM EventSystem (54) 4353 N/A COMPAQ-2006
> Warning 4/9/2010 5:52:17 AM EventSystem (52) 4356 N/A COMPAQ-2006
> Information 4/9/2010 5:52:11 AM ASP.NET 2.0.50727.0 None 1076 N/A COMPAQ-2006
> Information 4/9/2010 1:18:32 AM Ci CI Service 4103 N/A COMPAQ-2006
> Information 4/8/2010 9:55:34 PM Ci CI Service 4137 N/A COMPAQ-2006
>
> Event Type: Information
> Event Source: ASP.NET 2.0.50727.0
> Event Category: None
> Event ID: 1076
> Date: 4/9/2010
> Time: 5:56:47 AM
> User: N/A
> Computer: COMPAQ-2006
> Description:
> State server starts listening with 3 listeners
>
> Type Date Time Source Category Event User Computer
> Error 4/9/2010 5:56:07 AM ntfs Disk 55 N/A COMPAQ-2006
> Error 4/9/2010 5:56:04 AM ntfs Disk 55 N/A COMPAQ-2006
> Information 4/9/2010 5:56:04 AM Tcpip None 4201 N/A COMPAQ-2006
> Information 4/9/2010 5:56:24 AM eventlog None 6005 N/A COMPAQ-2006
> Information 4/9/2010 5:56:24 AM eventlog None 6009 N/A COMPAQ-2006
> Information 4/9/2010 5:55:11 AM eventlog None 6006 N/A COMPAQ-2006
> Error 4/9/2010 5:51:31 AM ntfs Disk 55 N/A COMPAQ-2006
> Error 4/9/2010 5:51:29 AM ntfs Disk 55 N/A COMPAQ-2006
> Information 4/9/2010 5:51:28 AM Tcpip None 4201 N/A COMPAQ-2006
> Information 4/9/2010 5:51:49 AM eventlog None 6005 N/A COMPAQ-2006
> Information 4/9/2010 5:51:49 AM eventlog None 6009 N/A COMPAQ-2006
> Information 4/9/2010 5:24:36 AM eventlog None 6006 N/A COMPAQ-2006
>

> Event Type: Information
> Event Source: Tcpip
> Event Category: None
> Event ID: 4201
> Date: 4/9/2010
> Time: 5:56:04 AM
> User: N/A
> Computer: COMPAQ-2006
> Description:
> The system detected that network adapter \DEVICE\TCPIP_

{D5E50A75-4A1C-4421-A5B4-569C9FE131B8} was connected to the network,

and has initiated normal operation over the network adapter.
>
> For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 00 00 00 00 02 00 50 00 ......P.
> 0008: 00 00 00 00 69 10 00 40 ....i..@
> 0010: 02 00 00 00 00 00 00 00 ........
> 0018: 00 00 00 00 00 00 00 00 ........
> 0020: 00 00 00 00 00 00 00 00 ........

Maybe there's some new evidence here. Things happening that I
of course don't understand. Note initiating operation over the network
adapter, but I rechecked and my phone line was indeed unplugged.
I only reconnect when I boot back to this main system.
From: John John - MVP on
William B. Lurie wrote:

>> Is the machine still connected to the internet or to a LAN?
>> Disconnect from both while you troubleshoot the problem!
>>
>> John
> John, I thought I made that clear. On each and every test run,
> I restart the computer in order to reboot to the the test system,
> and while it is booting, I physically disconnect the phone line
> as it enters the modem from the wall outlet. As for LAN.......
> I am a poor single-line homeowner with only one line of access
> to the world of information, other than Comcast cable for TV.

OK, being that your firewall and AV applications are not running while
you run these trials I just wanted to make sure that you weren't opening
your unprotected machine to the outside world.



> And as for Ci which we discussed earlier, I can't put my finger on it;
> please tell me again what to disable to stop it from cataloguing
> system volume information at what appears to be random odd times.

Let's try one last effort and see if we can get to the bottom of this.
I'm going to try another approach, I will try to configure your services
via scripts or batch files that you can run on your machine. We are
going to start from scratch again, I need you to do the following 2 tasks:

Task 1:

Copy the stuff between the ====== lines and save it as ServiceStat.vbs:


================================================================
Const ForWriting = 2
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objLogFile = objFSO.OpenTextFile("c:\services.txt", _
ForWriting, True)
objLogFile.Write _
("Service Name,Start Mode")
objLogFile.Writeline
strComputer = "."
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
Set colListOfServices = objWMIService.ExecQuery _
("Select * from Win32_Service")
For Each objService in colListOfServices
objLogFile.Write(objService.Name) & ","
objLogFile.Write(objService.StartMode) & ","
objLogFile.writeline
Next
objLogFile.Close
================================================================

Run ServiceState.vbs (double click on it) and after it runs look for the
file C:\services.txt, copy and paste the contents of the file to your
next post.


Task 2:

This one involves running a Sysinternals utility (Autorunsc) at the
command prompt.

Go here: http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx

and download the Autoruns and Autorunsc package (581 KB). Unzip the
package, there will be two executable in the package:

The GUI version: autoruns.exe

and the Command version: autorunsc.exe

Copy the command version (autorunsc.exe) to an easy to find location,
for example C:\, then at a Command Prompt run this command:

c:\autorunsc >c:\autostart.txt

Copy and paste the contents of the c:\autostart.txt to your next post.


Be patient after you post the files. I have a busy next few days ahead,
I might not be able to get back to you until much later, maybe not
before Sunday.

John
From: Unknown on
What is the status of "speed disk" when failing to hibernate?
"William B. Lurie" <billurie(a)nospam.net> wrote in message
news:u0EKbI%231KHA.3652(a)TK2MSFTNGP04.phx.gbl...
> William B. Lurie wrote:
> (snip)
>>>>> 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.
>>>
>>> Is the machine still connected to the internet or to a LAN? Disconnect
>>> from both while you troubleshoot the problem!
>>>
>>> John
>> John, I thought I made that clear. On each and every test run,
>> I restart the computer in order to reboot to the the test system,
>> and while it is booting, I physically disconnect the phone line
>> as it enters the modem from the wall outlet. As for LAN.......
>> I am a poor single-line homeowner with only one line of access
>> to the world of information, other than Comcast cable for TV.
>>
>> And as for Ci which we discussed earlier, I can't put my finger on it;
>> please tell me again what to disable to stop it from cataloguing
>> system volume information at what appears to be random odd times.
>>
>> I have another overnight run to report later, showing that
>> same intervention.
>> Bill
>
> But continuing on, another few bits of news.
> I Disabled Indexing Service at 5:55 A.M. this morning and rebooted.
> At 0700 screen was still black, power light still flashing, and I
> thought maybe it would go the full 2 hours......only had 55 minutes
> to go. At 0745 on came the desktop, followed by the "Preparing to standby"
> message, and I figured I wouldn't wait another 100 minutes
> to see if it would hibernate. More important to report what the Events
> were. I filed the following from the Log:
>
>> Type Date Time Source Category Event User Computer
>> Warning 4/9/2010 5:56:51 AM EventSystem (54) 4353 N/A COMPAQ-2006
>> Warning 4/9/2010 5:56:51 AM EventSystem (52) 4356 N/A COMPAQ-2006
>> Warning 4/9/2010 5:56:51 AM EventSystem (54) 4353 N/A COMPAQ-2006
>> Warning 4/9/2010 5:56:51 AM EventSystem (52) 4356 N/A COMPAQ-2006
>> Information 4/9/2010 5:56:47 AM ASP.NET 2.0.50727.0 None 1076 N/A
>> COMPAQ-2006
>> Warning 4/9/2010 5:52:17 AM EventSystem (54) 4353 N/A COMPAQ-2006
>> Warning 4/9/2010 5:52:17 AM EventSystem (52) 4356 N/A COMPAQ-2006
>> Warning 4/9/2010 5:52:17 AM EventSystem (54) 4353 N/A COMPAQ-2006
>> Warning 4/9/2010 5:52:17 AM EventSystem (52) 4356 N/A COMPAQ-2006
>> Information 4/9/2010 5:52:11 AM ASP.NET 2.0.50727.0 None 1076 N/A
>> COMPAQ-2006
>> Information 4/9/2010 1:18:32 AM Ci CI Service 4103 N/A COMPAQ-2006
>> Information 4/8/2010 9:55:34 PM Ci CI Service 4137 N/A COMPAQ-2006
>>
>> Event Type: Information
>> Event Source: ASP.NET 2.0.50727.0
>> Event Category: None
>> Event ID: 1076
>> Date: 4/9/2010
>> Time: 5:56:47 AM
>> User: N/A
>> Computer: COMPAQ-2006
>> Description:
>> State server starts listening with 3 listeners
>>
>> Type Date Time Source Category Event User Computer
>> Error 4/9/2010 5:56:07 AM ntfs Disk 55 N/A COMPAQ-2006
>> Error 4/9/2010 5:56:04 AM ntfs Disk 55 N/A COMPAQ-2006
>> Information 4/9/2010 5:56:04 AM Tcpip None 4201 N/A COMPAQ-2006
>> Information 4/9/2010 5:56:24 AM eventlog None 6005 N/A COMPAQ-2006
>> Information 4/9/2010 5:56:24 AM eventlog None 6009 N/A COMPAQ-2006
>> Information 4/9/2010 5:55:11 AM eventlog None 6006 N/A COMPAQ-2006
>> Error 4/9/2010 5:51:31 AM ntfs Disk 55 N/A COMPAQ-2006
>> Error 4/9/2010 5:51:29 AM ntfs Disk 55 N/A COMPAQ-2006
>> Information 4/9/2010 5:51:28 AM Tcpip None 4201 N/A COMPAQ-2006
>> Information 4/9/2010 5:51:49 AM eventlog None 6005 N/A COMPAQ-2006
>> Information 4/9/2010 5:51:49 AM eventlog None 6009 N/A COMPAQ-2006
>> Information 4/9/2010 5:24:36 AM eventlog None 6006 N/A COMPAQ-2006
>>
>
>> Event Type: Information
>> Event Source: Tcpip
>> Event Category: None
>> Event ID: 4201
>> Date: 4/9/2010
>> Time: 5:56:04 AM
>> User: N/A
>> Computer: COMPAQ-2006
>> Description:
>> The system detected that network adapter \DEVICE\TCPIP_
>
> {D5E50A75-4A1C-4421-A5B4-569C9FE131B8} was connected to the network,
>
> and has initiated normal operation over the network adapter.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 00 00 00 00 02 00 50 00 ......P.
>> 0008: 00 00 00 00 69 10 00 40 ....i..@
>> 0010: 02 00 00 00 00 00 00 00 ........
>> 0018: 00 00 00 00 00 00 00 00 ........
>> 0020: 00 00 00 00 00 00 00 00 ........
>
> Maybe there's some new evidence here. Things happening that I
> of course don't understand. Note initiating operation over the network
> adapter, but I rechecked and my phone line was indeed unplugged.
> I only reconnect when I boot back to this main system.