A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » The Basics
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

WIA and hibernation again



 
 
Thread Tools Display Modes
  #46  
Old March 31st 10, 10:31 PM posted to microsoft.public.windowsxp.basics
Unknown
external usenet poster
 
Posts: 6,007
Default WIA and hibernation again

Can you verify the default time is still 0x00093a80 in the registry. If it
is trying to sync your clock
too often then perhaps that would prevent hibernation. Savings time
changeover
would not be affected.
"William B. Lurie" wrote in message
...
Unknown wrote:
Curiosity question. Did you at any time alter the time interval for when
you sync your clock?
Check your registry at:
HKEY_LOCAL_MACHINE\System\currentcontrolset\servic es\w32Time\TimeProviders\NTPclient
in right pane special poll interval is a hexidecimal count in seconds.
For one week (XP default time) it is 0x00093a80 (604800)
"William B. Lurie" wrote in message


No, I've never been there. It of course did the Savings Time changeover
with no hitch at all. This problem goes back way beyond 10 days ago.......



Ads
  #47  
Old April 1st 10, 12:20 AM posted to microsoft.public.windowsxp.basics
William B. Lurie
external usenet poster
 
Posts: 811
Default WIA and hibernation again

Unknown wrote:
Can you verify the default time is still 0x00093a80 in the registry. If it
is trying to sync your clock
too often then perhaps that would prevent hibernation. Savings time
changeover
would not be affected.
"William B. Lurie" wrote in message
...
Unknown wrote:
Curiosity question. Did you at any time alter the time interval for when
you sync your clock?
Check your registry at:
HKEY_LOCAL_MACHINE\System\currentcontrolset\servic es\w32Time\TimeProviders\NTPclient
in right pane special poll interval is a hexidecimal count in seconds.
For one week (XP default time) it is 0x00093a80 (604800)
"William B. Lurie" wrote in message

No, I've never been there. It of course did the Savings Time changeover
with no hitch at all. This problem goes back way beyond 10 days ago.......



Just to check back with you, UNk, I checked and my
setting is indeed as you showed, for SpecialPollInterval.
Back to the drawing board.........
  #48  
Old April 1st 10, 03:57 PM posted to microsoft.public.windowsxp.basics
Unknown
external usenet poster
 
Posts: 6,007
Default WIA and hibernation again

Thanks. Without sitting at your machine and observing various items I can
only go through the process of elimination.
It seems something is calling for the internet about every hour. May I ask
what you mean when you say Norton fixes their Boo-boos by remote control?
"William B. Lurie" wrote in message
...
Unknown wrote:
Can you verify the default time is still 0x00093a80 in the registry. If
it is trying to sync your clock
too often then perhaps that would prevent hibernation. Savings time
changeover
would not be affected.
"William B. Lurie" wrote in message
...
Unknown wrote:
Curiosity question. Did you at any time alter the time interval for
when you sync your clock?
Check your registry at:
HKEY_LOCAL_MACHINE\System\currentcontrolset\servic es\w32Time\TimeProviders\NTPclient
in right pane special poll interval is a hexidecimal count in seconds.
For one week (XP default time) it is 0x00093a80 (604800)
"William B. Lurie" wrote in message
No, I've never been there. It of course did the Savings Time changeover
with no hitch at all. This problem goes back way beyond 10 days
ago.......



Just to check back with you, UNk, I checked and my
setting is indeed as you showed, for SpecialPollInterval.
Back to the drawing board.........



  #49  
Old April 1st 10, 04:23 PM posted to microsoft.public.windowsxp.basics
John John - MVP[_2_]
external usenet poster
 
Posts: 1,637
Default WIA and hibernation again

William B. Lurie wrote:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 6:40:36 AM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it. "
attempting to start the service MDM with arguments "" in order to run
the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 6:35:10 AM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it. "
attempting to start the service MDM with arguments "" in order to run
the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Ntfs
Event Category: Disk
Event ID: 55
Date: 4/1/2010
Time: 6:42:47 AM
User: N/A
Computer: COMPAQ-2006
Description:
The file system structure on the disk is corrupt and unusable. Please
run the chkdsk utility on the volume R:.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0d 00 00 00 02 00 4e 00 ......N.
0008: 02 00 00 00 37 00 04 c0 ....7..À
0010: 00 00 00 00 32 00 00 c0 ....2..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 4/1/2010
Time: 6:44:25 AM
User: N/A
Computer: COMPAQ-2006
Description:
The following boot-start or system-start driver(s) failed to load:
ftsata2
KLIF



Is that an updated and current list of started Windows services?


Yes, John, I generate it anew every time I make one
of these hibernation runs, so that you can see it right
with the Events.

You discussed about those two drivers with another poster not too long
ago.


Yes, and now I'll answer your queries:

ftsata2: Do you now, or did you at any time have a Promise controller
installed?


No, I do not now, and never did. This basic HP machine came with
one hard drive, and cabling and slots for two more, which I
added. I select which drive to run by interrupting boot process
and telling it.

KLIF: Do you now or did you at any time have Kaspersky AV software
installed on the machine?


No, I have used Norton AV steadily for at least 15 years. From
the days when Norton was impossible to work with, to the present,
where they fix boo-boos by Chat and remote control of their software.

The chkdsk message... What do you have stored on volume R?


Oh, I missed that it was referring to volume R. I have numerous
'restore points' of which that volume is one. I generate these
every month or so, using the Save & Restore feature of Norton
System Works, which used to be PowerQuest Partition Magic. I
keep these in case I have to recreate a system as it was as of
an earlier date). I'll chkdsk it routinely but I think we can
ignore that Event.


These system-start driver errors shouldn't affect the ability to
hibernate but you can change their startup type and get rid of the
errors if you want. You will have to change them in the registry at
their respective subkeys in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es key , set their
Start Value to 0x3 or 0x4. 0x3 is manual start, 0x4 is disabled.

Or, we can change them at the command prompt if you wish, I need the
results of the following command before I can give you the proper
commands to change the start type:

sc query state= all c:\sc.txt

Copy and paste the contents of the generated sc.txt file to your next
post, there will be lots of verbiage in the file, post it all.

John
  #50  
Old April 1st 10, 04:43 PM posted to microsoft.public.windowsxp.basics
William B. Lurie
external usenet poster
 
Posts: 811
Default WIA and hibernation again

Unknown wrote:
Thanks. Without sitting at your machine and observing various items I can
only go through the process of elimination.
It seems something is calling for the internet about every hour. May I ask
what you mean when you say Norton fixes their Boo-boos by remote control?


Sure. I go to their website and find tech support, for which one option
is one-on-one online chat with their 'analyst'. I describe the problem,
he (she) asks for permission to connect to my machine remotely, I give
it, then he takes control of my cursor as tho' he was sitting in my
chair, clicks and clacks, even downloads new upgrades software,
installs, he and I check that he has fixed the problem, and I terminate
the 'chat' session. The wait isn't usually long, typically 5 to 15
minutes. It's calling for *something* after one hour, which is why it
doesn't reach the 2-hour hibernate, but as for calling the Internet, I
don't know if we've proven that........

"William B. Lurie" wrote in message
...
Unknown wrote:
Can you verify the default time is still 0x00093a80 in the registry. If
it is trying to sync your clock
too often then perhaps that would prevent hibernation. Savings time
changeover
would not be affected.
"William B. Lurie" wrote in message
...
Unknown wrote:
Curiosity question. Did you at any time alter the time interval for
when you sync your clock?
Check your registry at:
HKEY_LOCAL_MACHINE\System\currentcontrolset\servic es\w32Time\TimeProviders\NTPclient
in right pane special poll interval is a hexidecimal count in seconds.
For one week (XP default time) it is 0x00093a80 (604800)
"William B. Lurie" wrote in message
No, I've never been there. It of course did the Savings Time changeover
with no hitch at all. This problem goes back way beyond 10 days
ago.......

Just to check back with you, UNk, I checked and my
setting is indeed as you showed, for SpecialPollInterval.
Back to the drawing board.........



  #51  
Old April 1st 10, 04:51 PM posted to microsoft.public.windowsxp.basics
William B. Lurie
external usenet poster
 
Posts: 811
Default WIA and hibernation again

John John - MVP wrote:
William B. Lurie wrote:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 6:40:36 AM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it. "
attempting to start the service MDM with arguments "" in order to
run the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 6:35:10 AM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it. "
attempting to start the service MDM with arguments "" in order to
run the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Ntfs
Event Category: Disk
Event ID: 55
Date: 4/1/2010
Time: 6:42:47 AM
User: N/A
Computer: COMPAQ-2006
Description:
The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume R:.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0d 00 00 00 02 00 4e 00 ......N.
0008: 02 00 00 00 37 00 04 c0 ....7..À
0010: 00 00 00 00 32 00 00 c0 ....2..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 4/1/2010
Time: 6:44:25 AM
User: N/A
Computer: COMPAQ-2006
Description:
The following boot-start or system-start driver(s) failed to load:
ftsata2
KLIF


Is that an updated and current list of started Windows services?


Yes, John, I generate it anew every time I make one
of these hibernation runs, so that you can see it right
with the Events.

You discussed about those two drivers with another poster not too
long ago.


Yes, and now I'll answer your queries:

ftsata2: Do you now, or did you at any time have a Promise
controller installed?


No, I do not now, and never did. This basic HP machine came with
one hard drive, and cabling and slots for two more, which I
added. I select which drive to run by interrupting boot process
and telling it.

KLIF: Do you now or did you at any time have Kaspersky AV software
installed on the machine?


No, I have used Norton AV steadily for at least 15 years. From
the days when Norton was impossible to work with, to the present,
where they fix boo-boos by Chat and remote control of their software.

The chkdsk message... What do you have stored on volume R?


Oh, I missed that it was referring to volume R. I have numerous
'restore points' of which that volume is one. I generate these
every month or so, using the Save & Restore feature of Norton
System Works, which used to be PowerQuest Partition Magic. I
keep these in case I have to recreate a system as it was as of
an earlier date). I'll chkdsk it routinely but I think we can
ignore that Event.


These system-start driver errors shouldn't affect the ability to
hibernate but you can change their startup type and get rid of the
errors if you want. You will have to change them in the registry at
their respective subkeys in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es key , set their
Start Value to 0x3 or 0x4. 0x3 is manual start, 0x4 is disabled.

Or, we can change them at the command prompt if you wish, I need the
results of the following command before I can give you the proper
commands to change the start type:

sc query state= all c:\sc.txt

Copy and paste the contents of the generated sc.txt file to your next
post, there will be lots of verbiage in the file, post it all.

John


Okay, John. I'll do it now on my Master system, saves some time in
rebooting, doing sc on clone, rebooting to Master. Here it is:


SERVICE_NAME: Alerter
DISPLAY_NAME: Alerter
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: ALG
DISPLAY_NAME: Application Layer Gateway Service
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: AppMgmt
DISPLAY_NAME: Application Management
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: aspnet_state
DISPLAY_NAME: ASP.NET State Service
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Ati HotKey Poller
DISPLAY_NAME: Ati HotKey Poller
TYPE : 110 WIN32_OWN_PROCESS (interactive)
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: ATI Smart
DISPLAY_NAME: ATI Smart
TYPE : 110 WIN32_OWN_PROCESS (interactive)
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: AudioSrv
DISPLAY_NAME: Windows Audio
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Automatic LiveUpdate Scheduler
DISPLAY_NAME: Automatic LiveUpdate Scheduler
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: BITS
DISPLAY_NAME: Background Intelligent Transfer Service
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Browser
DISPLAY_NAME: Computer Browser
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: CiSvc
DISPLAY_NAME: Indexing Service
TYPE : 120 WIN32_SHARE_PROCESS (interactive)
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: ClipSrv
DISPLAY_NAME: ClipBook
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: clr_optimization_v2.0.50727_32
DISPLAY_NAME: .NET Runtime Optimization Service v2.0.50727_X86
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: COMSysApp
DISPLAY_NAME: COM+ System Application
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: CryptSvc
DISPLAY_NAME: Cryptographic Services
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: DcomLaunch
DISPLAY_NAME: DCOM Server Process Launcher
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Dhcp
DISPLAY_NAME: DHCP Client
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: dmadmin
DISPLAY_NAME: Logical Disk Manager Administrative Service
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: dmserver
DISPLAY_NAME: Logical Disk Manager
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Dnscache
DISPLAY_NAME: DNS Client
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: ERSvc
DISPLAY_NAME: Error Reporting Service
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Eventlog
DISPLAY_NAME: Event Log
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(NOT_STOPPABLE,NOT_PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: EventSystem
DISPLAY_NAME: COM+ Event System
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: FastUserSwitchingCompatibility
DISPLAY_NAME: Fast User Switching Compatibility
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Fax
DISPLAY_NAME: Fax
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: FontCache3.0.0.0
DISPLAY_NAME: Windows Presentation Foundation Font Cache 3.0.0.0
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: GEARSecurity
DISPLAY_NAME: GEARSecurity
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: helpsvc
DISPLAY_NAME: Help and Support
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: HidServ
DISPLAY_NAME: Human Interface Device Access
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: HTTPFilter
DISPLAY_NAME: HTTP SSL
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: IDriverT
DISPLAY_NAME: InstallDriver Table Manager
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: idsvc
DISPLAY_NAME: Windows CardSpace
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Imapi Helper
DISPLAY_NAME: Imapi Helper
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: ImapiService
DISPLAY_NAME: IMAPI CD-Burning COM Service
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: lanmanserver
DISPLAY_NAME: Server
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: lanmanworkstation
DISPLAY_NAME: Workstation
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: LexBceS
DISPLAY_NAME: LexBce Server
TYPE : 110 WIN32_OWN_PROCESS (interactive)
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: LiveUpdate
DISPLAY_NAME: LiveUpdate
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: LmHosts
DISPLAY_NAME: TCP/IP NetBIOS Helper
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: lxct_device
DISPLAY_NAME: lxct_device
TYPE : 110 WIN32_OWN_PROCESS (interactive)
STATE : 4 RUNNING
(STOPPABLE,PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: MBAMService
DISPLAY_NAME: MBAMService
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: MDM
DISPLAY_NAME: Machine Debug Manager
TYPE : 110 WIN32_OWN_PROCESS (interactive)
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Messenger
DISPLAY_NAME: Messenger
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: mnmsrvc
DISPLAY_NAME: NetMeeting Remote Desktop Sharing
TYPE : 110 WIN32_OWN_PROCESS (interactive)
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: MSIServer
DISPLAY_NAME: Windows Installer
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: NetDDE
DISPLAY_NAME: Network DDE
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: NetDDEdsdm
DISPLAY_NAME: Network DDE DSDM
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Netlogon
DISPLAY_NAME: Net Logon
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Netman
DISPLAY_NAME: Network Connections
TYPE : 120 WIN32_SHARE_PROCESS (interactive)
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: NetTcpPortSharing
DISPLAY_NAME: Net.Tcp Port Sharing Service
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Nla
DISPLAY_NAME: Network Location Awareness (NLA)
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Norton AntiVirus
DISPLAY_NAME: Norton AntiVirus
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Norton Save and Restore
DISPLAY_NAME: Norton Save and Restore
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: NProtectService
DISPLAY_NAME: Norton UnErase Protection
TYPE : 110 WIN32_OWN_PROCESS (interactive)
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: NtLmSsp
DISPLAY_NAME: NT LM Security Support Provider
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: NtmsSvc
DISPLAY_NAME: Removable Storage
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: ose
DISPLAY_NAME: Office Source Engine
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: PlugPlay
DISPLAY_NAME: Plug and Play
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(NOT_STOPPABLE,NOT_PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: PolicyAgent
DISPLAY_NAME: IPSEC Services
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: ProtectedStorage
DISPLAY_NAME: Protected Storage
TYPE : 120 WIN32_SHARE_PROCESS (interactive)
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: psqlWGE
DISPLAY_NAME: Pervasive PSQL Workgroup Engine
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: RasAuto
DISPLAY_NAME: Remote Access Auto Connection Manager
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: RasMan
DISPLAY_NAME: Remote Access Connection Manager
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: RDSessMgr
DISPLAY_NAME: Remote Desktop Help Session Manager
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: RemoteAccess
DISPLAY_NAME: Routing and Remote Access
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: RpcLocator
DISPLAY_NAME: Remote Procedure Call (RPC) Locator
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: RpcSs
DISPLAY_NAME: Remote Procedure Call (RPC)
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: RSVP
DISPLAY_NAME: QoS RSVP
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: SamSs
DISPLAY_NAME: Security Accounts Manager
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: SCardSvr
DISPLAY_NAME: Smart Card
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Schedule
DISPLAY_NAME: Task Scheduler
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: seclogon
DISPLAY_NAME: Secondary Logon
TYPE : 120 WIN32_SHARE_PROCESS (interactive)
STATE : 4 RUNNING
(STOPPABLE,PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: SENS
DISPLAY_NAME: System Event Notification
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: SharedAccess
DISPLAY_NAME: Windows Firewall/Internet Connection Sharing (ICS)
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: ShellHWDetection
DISPLAY_NAME: Shell Hardware Detection
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Speed Disk service
DISPLAY_NAME: Speed Disk service
TYPE : 110 WIN32_OWN_PROCESS (interactive)
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Spooler
DISPLAY_NAME: Print Spooler
TYPE : 110 WIN32_OWN_PROCESS (interactive)
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: srservice
DISPLAY_NAME: System Restore Service
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: SSDPSRV
DISPLAY_NAME: SSDP Discovery Service
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: stisvc
DISPLAY_NAME: Windows Image Acquisition (WIA)
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: SwPrv
DISPLAY_NAME: MS Software Shadow Copy Provider
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Symantec RemoteAssist
DISPLAY_NAME: Symantec RemoteAssist
TYPE : 110 WIN32_OWN_PROCESS (interactive)
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: SysmonLog
DISPLAY_NAME: Performance Logs and Alerts
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: TapiSrv
DISPLAY_NAME: Telephony
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: TermService
DISPLAY_NAME: Terminal Services
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Themes
DISPLAY_NAME: Themes
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: TrkWks
DISPLAY_NAME: Distributed Link Tracking Client
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: upnphost
DISPLAY_NAME: Universal Plug and Play Device Host
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: UPS
DISPLAY_NAME: Uninterruptible Power Supply
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: Viewpoint Manager Service
DISPLAY_NAME: Viewpoint Manager Service
TYPE : 110 WIN32_OWN_PROCESS (interactive)
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: VSS
DISPLAY_NAME: Volume Shadow Copy
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: W32Time
DISPLAY_NAME: Windows Time
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: WebClient
DISPLAY_NAME: WebClient
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: winmgmt
DISPLAY_NAME: Windows Management Instrumentation
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: WmdmPmSN
DISPLAY_NAME: Portable Media Serial Number Service
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: WmiApSrv
DISPLAY_NAME: WMI Performance Adapter
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: WMPNetworkSvc
DISPLAY_NAME: Windows Media Player Network Sharing Service
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: wscsvc
DISPLAY_NAME: Security Center
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: wuauserv
DISPLAY_NAME: Automatic Updates
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: WudfSvc
DISPLAY_NAME: Windows Driver Foundation - User-mode Driver Framework
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: WZCSVC
DISPLAY_NAME: Wireless Zero Configuration
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

SERVICE_NAME: xmlprov
DISPLAY_NAME: Network Provisioning Service
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

  #52  
Old April 1st 10, 04:57 PM posted to microsoft.public.windowsxp.basics
Unknown
external usenet poster
 
Posts: 6,007
Default WIA and hibernation again

You stated after the hibernation time (2 hours) your HD light is flashing?
At that point did you open task manager and check what processes is running
and whether or not
an application is running?
Also have you compared the services when starting to hibernate against the
services after one hour?
"William B. Lurie" wrote in message
...
Unknown wrote:
Thanks. Without sitting at your machine and observing various items I can
only go through the process of elimination.
It seems something is calling for the internet about every hour. May I
ask what you mean when you say Norton fixes their Boo-boos by remote
control?


Sure. I go to their website and find tech support, for which one option
is one-on-one online chat with their 'analyst'. I describe the problem,
he (she) asks for permission to connect to my machine remotely, I give
it, then he takes control of my cursor as tho' he was sitting in my chair,
clicks and clacks, even downloads new upgrades software, installs, he and
I check that he has fixed the problem, and I terminate the 'chat' session.
The wait isn't usually long, typically 5 to 15 minutes. It's calling for
*something* after one hour, which is why it
doesn't reach the 2-hour hibernate, but as for calling the Internet, I
don't know if we've proven that........

"William B. Lurie" wrote in message
...
Unknown wrote:
Can you verify the default time is still 0x00093a80 in the registry. If
it is trying to sync your clock
too often then perhaps that would prevent hibernation. Savings time
changeover
would not be affected.
"William B. Lurie" wrote in message
...
Unknown wrote:
Curiosity question. Did you at any time alter the time interval for
when you sync your clock?
Check your registry at:
HKEY_LOCAL_MACHINE\System\currentcontrolset\servic es\w32Time\TimeProviders\NTPclient
in right pane special poll interval is a hexidecimal count in
seconds.
For one week (XP default time) it is 0x00093a80 (604800)
"William B. Lurie" wrote in message
No, I've never been there. It of course did the Savings Time
changeover
with no hitch at all. This problem goes back way beyond 10 days
ago.......

Just to check back with you, UNk, I checked and my
setting is indeed as you showed, for SpecialPollInterval.
Back to the drawing board.........



  #53  
Old April 1st 10, 05:01 PM posted to microsoft.public.windowsxp.basics
William B. Lurie
external usenet poster
 
Posts: 811
Default WIA and hibernation again

John John - MVP wrote:
William B. Lurie wrote:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 6:40:36 AM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it. "
attempting to start the service MDM with arguments "" in order to
run the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 6:35:10 AM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it. "
attempting to start the service MDM with arguments "" in order to
run the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Ntfs
Event Category: Disk
Event ID: 55
Date: 4/1/2010
Time: 6:42:47 AM
User: N/A
Computer: COMPAQ-2006
Description:
The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume R:.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0d 00 00 00 02 00 4e 00 ......N.
0008: 02 00 00 00 37 00 04 c0 ....7..À
0010: 00 00 00 00 32 00 00 c0 ....2..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 4/1/2010
Time: 6:44:25 AM
User: N/A
Computer: COMPAQ-2006
Description:
The following boot-start or system-start driver(s) failed to load:
ftsata2
KLIF


Is that an updated and current list of started Windows services?


Yes, John, I generate it anew every time I make one
of these hibernation runs, so that you can see it right
with the Events.

You discussed about those two drivers with another poster not too
long ago.


Yes, and now I'll answer your queries:

ftsata2: Do you now, or did you at any time have a Promise
controller installed?


No, I do not now, and never did. This basic HP machine came with
one hard drive, and cabling and slots for two more, which I
added. I select which drive to run by interrupting boot process
and telling it.

KLIF: Do you now or did you at any time have Kaspersky AV software
installed on the machine?


No, I have used Norton AV steadily for at least 15 years. From
the days when Norton was impossible to work with, to the present,
where they fix boo-boos by Chat and remote control of their software.

The chkdsk message... What do you have stored on volume R?


Oh, I missed that it was referring to volume R. I have numerous
'restore points' of which that volume is one. I generate these
every month or so, using the Save & Restore feature of Norton
System Works, which used to be PowerQuest Partition Magic. I
keep these in case I have to recreate a system as it was as of
an earlier date). I'll chkdsk it routinely but I think we can
ignore that Event.


These system-start driver errors shouldn't affect the ability to
hibernate but you can change their startup type and get rid of the
errors if you want. You will have to change them in the registry at
their respective subkeys in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es key , set their
Start Value to 0x3 or 0x4. 0x3 is manual start, 0x4 is disabled.

Or, we can change them at the command prompt if you wish, I need the
results of the following command before I can give you the proper
commands to change the start type:

sc query state= all c:\sc.txt

Copy and paste the contents of the generated sc.txt file to your next
post, there will be lots of verbiage in the file, post it all.

John


I don't mess with registry unless it has to be messed with.
And if those commands and errors are innocuous, I see no need to
mess with them via command prompt. And the chkdsk request was
a blind alley, and to be sure, I deleted that 2+ year old backup
anyway.

But what to do next? With all this time spent on the hibernate
problem, I hate to give up. Who knows, the answer may be just around
the next bend in the road.
  #54  
Old April 1st 10, 05:10 PM posted to microsoft.public.windowsxp.basics
William B. Lurie
external usenet poster
 
Posts: 811
Default WIA and hibernation again

Unknown wrote:
You stated after the hibernation time (2 hours) your HD light is flashing?
At that point did you open task manager and check what processes is running
and whether or not
an application is running?


No, but I will next time around. What I see there most often, during
these test runs, is nothing related to the user except HpBootOpt, but
plenty of System and Local Service with many many 'svchost.exe',
none of which are under my control.

The sequence is, first desktop; then Screen Saver: then Monitor shutoff
(never), then HD shutoff (20 minutes), then System Standby (25 min.)
and finally hibernate (2 hours). After 2 hours or more have elapsed,
the mintor is in reduced power, the power-on light is flashing, and
that's all. It never goes to hibernate, which would be indicated by
the power-on light turning off.

Also have you compared the services when starting to hibernate against the
services after one hour?
"William B. Lurie" wrote in message
...
Unknown wrote:
Thanks. Without sitting at your machine and observing various items I can
only go through the process of elimination.
It seems something is calling for the internet about every hour. May I
ask what you mean when you say Norton fixes their Boo-boos by remote
control?

Sure. I go to their website and find tech support, for which one option
is one-on-one online chat with their 'analyst'. I describe the problem,
he (she) asks for permission to connect to my machine remotely, I give
it, then he takes control of my cursor as tho' he was sitting in my chair,
clicks and clacks, even downloads new upgrades software, installs, he and
I check that he has fixed the problem, and I terminate the 'chat' session.
The wait isn't usually long, typically 5 to 15 minutes. It's calling for
*something* after one hour, which is why it
doesn't reach the 2-hour hibernate, but as for calling the Internet, I
don't know if we've proven that........

"William B. Lurie" wrote in message
...
Unknown wrote:
Can you verify the default time is still 0x00093a80 in the registry. If
it is trying to sync your clock
too often then perhaps that would prevent hibernation. Savings time
changeover
would not be affected.
"William B. Lurie" wrote in message
...
Unknown wrote:
Curiosity question. Did you at any time alter the time interval for
when you sync your clock?
Check your registry at:
HKEY_LOCAL_MACHINE\System\currentcontrolset\servic es\w32Time\TimeProviders\NTPclient
in right pane special poll interval is a hexidecimal count in
seconds.
For one week (XP default time) it is 0x00093a80 (604800)
"William B. Lurie" wrote in message
No, I've never been there. It of course did the Savings Time
changeover
with no hitch at all. This problem goes back way beyond 10 days
ago.......
Just to check back with you, UNk, I checked and my
setting is indeed as you showed, for SpecialPollInterval.
Back to the drawing board.........


  #55  
Old April 1st 10, 05:40 PM posted to microsoft.public.windowsxp.basics
Unknown
external usenet poster
 
Posts: 6,007
Default WIA and hibernation again

Do a Google search for 'power on light flashing' Lots of info there.
"William B. Lurie" wrote in message
...
Unknown wrote:
You stated after the hibernation time (2 hours) your HD light is
flashing?
At that point did you open task manager and check what processes is
running and whether or not
an application is running?


No, but I will next time around. What I see there most often, during
these test runs, is nothing related to the user except HpBootOpt, but
plenty of System and Local Service with many many 'svchost.exe',
none of which are under my control.

The sequence is, first desktop; then Screen Saver: then Monitor shutoff
(never), then HD shutoff (20 minutes), then System Standby (25 min.)
and finally hibernate (2 hours). After 2 hours or more have elapsed,
the mintor is in reduced power, the power-on light is flashing, and that's
all. It never goes to hibernate, which would be indicated by
the power-on light turning off.

Also have you compared the services when starting to hibernate against
the services after one hour?
"William B. Lurie" wrote in message
...
Unknown wrote:
Thanks. Without sitting at your machine and observing various items I
can only go through the process of elimination.
It seems something is calling for the internet about every hour. May I
ask what you mean when you say Norton fixes their Boo-boos by remote
control?
Sure. I go to their website and find tech support, for which one option
is one-on-one online chat with their 'analyst'. I describe the problem,
he (she) asks for permission to connect to my machine remotely, I give
it, then he takes control of my cursor as tho' he was sitting in my
chair, clicks and clacks, even downloads new upgrades software,
installs, he and I check that he has fixed the problem, and I terminate
the 'chat' session. The wait isn't usually long, typically 5 to 15
minutes. It's calling for *something* after one hour, which is why it
doesn't reach the 2-hour hibernate, but as for calling the Internet, I
don't know if we've proven that........

"William B. Lurie" wrote in message
...
Unknown wrote:
Can you verify the default time is still 0x00093a80 in the registry.
If it is trying to sync your clock
too often then perhaps that would prevent hibernation. Savings time
changeover
would not be affected.
"William B. Lurie" wrote in message
...
Unknown wrote:
Curiosity question. Did you at any time alter the time interval for
when you sync your clock?
Check your registry at:
HKEY_LOCAL_MACHINE\System\currentcontrolset\servic es\w32Time\TimeProviders\NTPclient
in right pane special poll interval is a hexidecimal count in
seconds.
For one week (XP default time) it is 0x00093a80 (604800)
"William B. Lurie" wrote in message
No, I've never been there. It of course did the Savings Time
changeover
with no hitch at all. This problem goes back way beyond 10 days
ago.......
Just to check back with you, UNk, I checked and my
setting is indeed as you showed, for SpecialPollInterval.
Back to the drawing board.........




  #56  
Old April 1st 10, 06:28 PM posted to microsoft.public.windowsxp.basics
John John - MVP
external usenet poster
 
Posts: 780
Default WIA and hibernation again

William B. Lurie wrote:
John John - MVP wrote:
William B. Lurie wrote:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 6:40:36 AM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it. "
attempting to start the service MDM with arguments "" in order to
run the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 6:35:10 AM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it. "
attempting to start the service MDM with arguments "" in order to
run the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Ntfs
Event Category: Disk
Event ID: 55
Date: 4/1/2010
Time: 6:42:47 AM
User: N/A
Computer: COMPAQ-2006
Description:
The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume R:.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0d 00 00 00 02 00 4e 00 ......N.
0008: 02 00 00 00 37 00 04 c0 ....7..À
0010: 00 00 00 00 32 00 00 c0 ....2..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 4/1/2010
Time: 6:44:25 AM
User: N/A
Computer: COMPAQ-2006
Description:
The following boot-start or system-start driver(s) failed to load:
ftsata2
KLIF


Is that an updated and current list of started Windows services?

Yes, John, I generate it anew every time I make one
of these hibernation runs, so that you can see it right
with the Events.

You discussed about those two drivers with another poster not too
long ago.

Yes, and now I'll answer your queries:

ftsata2: Do you now, or did you at any time have a Promise
controller installed?

No, I do not now, and never did. This basic HP machine came with
one hard drive, and cabling and slots for two more, which I
added. I select which drive to run by interrupting boot process
and telling it.

KLIF: Do you now or did you at any time have Kaspersky AV software
installed on the machine?

No, I have used Norton AV steadily for at least 15 years. From
the days when Norton was impossible to work with, to the present,
where they fix boo-boos by Chat and remote control of their software.

The chkdsk message... What do you have stored on volume R?

Oh, I missed that it was referring to volume R. I have numerous
'restore points' of which that volume is one. I generate these
every month or so, using the Save & Restore feature of Norton
System Works, which used to be PowerQuest Partition Magic. I
keep these in case I have to recreate a system as it was as of
an earlier date). I'll chkdsk it routinely but I think we can
ignore that Event.


These system-start driver errors shouldn't affect the ability to
hibernate but you can change their startup type and get rid of the
errors if you want. You will have to change them in the registry at
their respective subkeys in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es key , set their
Start Value to 0x3 or 0x4. 0x3 is manual start, 0x4 is disabled.

Or, we can change them at the command prompt if you wish, I need the
results of the following command before I can give you the proper
commands to change the start type:

sc query state= all c:\sc.txt

Copy and paste the contents of the generated sc.txt file to your next
post, there will be lots of verbiage in the file, post it all.

John


I don't mess with registry unless it has to be messed with.
And if those commands and errors are innocuous, I see no need to
mess with them via command prompt. And the chkdsk request was
a blind alley, and to be sure, I deleted that 2+ year old backup
anyway.

But what to do next? With all this time spent on the hibernate
problem, I hate to give up. Who knows, the answer may be just around
the next bend in the road.


I don't see the KLIF or ftsata2 driver on the sc query list that you
supplied... could be that they are on the clone but not on the
production machine, or that the sc command doesn't see these as
services. You can try these and see what it returns:

sc query klif
sc query ftsata2


We could also get the list of drivers with a different command:

driverquery c:\drivers.txt

If you want to solve the problem you need to keep on investigating until
you find what it is that is running or starting and that prevents
hibernation, I don't know of an easy way to figure this out. Sometimes
you need dogged determination to get to the bottom of some of these
problems.

John
  #57  
Old April 1st 10, 07:40 PM posted to microsoft.public.windowsxp.basics
William B. Lurie
external usenet poster
 
Posts: 811
Default WIA and hibernation again

John John - MVP wrote:
William B. Lurie wrote:
John John - MVP wrote:
William B. Lurie wrote:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 6:40:36 AM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it
is disabled or because it has no enabled devices associated with
it. " attempting to start the service MDM with arguments "" in
order to run the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 6:35:10 AM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it
is disabled or because it has no enabled devices associated with
it. " attempting to start the service MDM with arguments "" in
order to run the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Ntfs
Event Category: Disk
Event ID: 55
Date: 4/1/2010
Time: 6:42:47 AM
User: N/A
Computer: COMPAQ-2006
Description:
The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume R:.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0d 00 00 00 02 00 4e 00 ......N.
0008: 02 00 00 00 37 00 04 c0 ....7..À
0010: 00 00 00 00 32 00 00 c0 ....2..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 4/1/2010
Time: 6:44:25 AM
User: N/A
Computer: COMPAQ-2006
Description:
The following boot-start or system-start driver(s) failed to load:
ftsata2
KLIF


Is that an updated and current list of started Windows services?

Yes, John, I generate it anew every time I make one
of these hibernation runs, so that you can see it right
with the Events.

You discussed about those two drivers with another poster not too
long ago.

Yes, and now I'll answer your queries:

ftsata2: Do you now, or did you at any time have a Promise
controller installed?

No, I do not now, and never did. This basic HP machine came with
one hard drive, and cabling and slots for two more, which I
added. I select which drive to run by interrupting boot process
and telling it.

KLIF: Do you now or did you at any time have Kaspersky AV software
installed on the machine?

No, I have used Norton AV steadily for at least 15 years. From
the days when Norton was impossible to work with, to the present,
where they fix boo-boos by Chat and remote control of their software.

The chkdsk message... What do you have stored on volume R?

Oh, I missed that it was referring to volume R. I have numerous
'restore points' of which that volume is one. I generate these
every month or so, using the Save & Restore feature of Norton
System Works, which used to be PowerQuest Partition Magic. I
keep these in case I have to recreate a system as it was as of
an earlier date). I'll chkdsk it routinely but I think we can
ignore that Event.

These system-start driver errors shouldn't affect the ability to
hibernate but you can change their startup type and get rid of the
errors if you want. You will have to change them in the registry at
their respective subkeys in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es key , set their
Start Value to 0x3 or 0x4. 0x3 is manual start, 0x4 is disabled.

Or, we can change them at the command prompt if you wish, I need the
results of the following command before I can give you the proper
commands to change the start type:

sc query state= all c:\sc.txt

Copy and paste the contents of the generated sc.txt file to your next
post, there will be lots of verbiage in the file, post it all.

John


I don't mess with registry unless it has to be messed with.
And if those commands and errors are innocuous, I see no need to
mess with them via command prompt. And the chkdsk request was
a blind alley, and to be sure, I deleted that 2+ year old backup
anyway.

But what to do next? With all this time spent on the hibernate
problem, I hate to give up. Who knows, the answer may be just around
the next bend in the road.


I don't see the KLIF or ftsata2 driver on the sc query list that you
supplied... could be that they are on the clone but not on the
production machine, or that the sc command doesn't see these as
services. You can try these and see what it returns:

sc query klif
sc query ftsata2

They're both there, John. One of them is:


SERVICE_NAME: ftsata2
TYPE : 1 KERNEL_DRIVER
STATE : 1 STOPPED

(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 31 (0x1f)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
The other one reads the same but I misplaced it.....the
same except it said klif and one other change
(I think TYPE -------CONTROL).


We could also get the list of drivers with a different command:

driverquery c:\drivers.txt


It didn't recognize that command.

If you want to solve the problem you need to keep on investigating until
you find what it is that is running or starting and that prevents
hibernation, I don't know of an easy way to figure this out. Sometimes
you need dogged determination to get to the bottom of some of these
problems.


Oh, you're right, John. We've both invested too much
time and intellect in it, and I'd hate to drop it,
either. But, as I said, what next?


  #58  
Old April 1st 10, 08:03 PM posted to microsoft.public.windowsxp.basics
William B. Lurie
external usenet poster
 
Posts: 811
Default WIA and hibernation again

William B. Lurie wrote:
John John - MVP wrote:
William B. Lurie wrote:
John John - MVP wrote:
William B. Lurie wrote:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 6:40:36 AM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it
is disabled or because it has no enabled devices associated with
it. " attempting to start the service MDM with arguments "" in
order to run the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 6:35:10 AM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it
is disabled or because it has no enabled devices associated with
it. " attempting to start the service MDM with arguments "" in
order to run the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Ntfs
Event Category: Disk
Event ID: 55
Date: 4/1/2010
Time: 6:42:47 AM
User: N/A
Computer: COMPAQ-2006
Description:
The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume R:.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0d 00 00 00 02 00 4e 00 ......N.
0008: 02 00 00 00 37 00 04 c0 ....7..À
0010: 00 00 00 00 32 00 00 c0 ....2..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 4/1/2010
Time: 6:44:25 AM
User: N/A
Computer: COMPAQ-2006
Description:
The following boot-start or system-start driver(s) failed to load:
ftsata2
KLIF


Is that an updated and current list of started Windows services?

Yes, John, I generate it anew every time I make one
of these hibernation runs, so that you can see it right
with the Events.

You discussed about those two drivers with another poster not too
long ago.

Yes, and now I'll answer your queries:

ftsata2: Do you now, or did you at any time have a Promise
controller installed?

No, I do not now, and never did. This basic HP machine came with
one hard drive, and cabling and slots for two more, which I
added. I select which drive to run by interrupting boot process
and telling it.

KLIF: Do you now or did you at any time have Kaspersky AV
software installed on the machine?

No, I have used Norton AV steadily for at least 15 years. From
the days when Norton was impossible to work with, to the present,
where they fix boo-boos by Chat and remote control of their
software.

The chkdsk message... What do you have stored on volume R?

Oh, I missed that it was referring to volume R. I have numerous
'restore points' of which that volume is one. I generate these
every month or so, using the Save & Restore feature of Norton
System Works, which used to be PowerQuest Partition Magic. I
keep these in case I have to recreate a system as it was as of
an earlier date). I'll chkdsk it routinely but I think we can
ignore that Event.

These system-start driver errors shouldn't affect the ability to
hibernate but you can change their startup type and get rid of the
errors if you want. You will have to change them in the registry at
their respective subkeys in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es key , set their
Start Value to 0x3 or 0x4. 0x3 is manual start, 0x4 is disabled.

Or, we can change them at the command prompt if you wish, I need the
results of the following command before I can give you the proper
commands to change the start type:

sc query state= all c:\sc.txt

Copy and paste the contents of the generated sc.txt file to your
next post, there will be lots of verbiage in the file, post it all.

John

I don't mess with registry unless it has to be messed with.
And if those commands and errors are innocuous, I see no need to
mess with them via command prompt. And the chkdsk request was
a blind alley, and to be sure, I deleted that 2+ year old backup
anyway.

But what to do next? With all this time spent on the hibernate
problem, I hate to give up. Who knows, the answer may be just around
the next bend in the road.


I don't see the KLIF or ftsata2 driver on the sc query list that you
supplied... could be that they are on the clone but not on the
production machine, or that the sc command doesn't see these as
services. You can try these and see what it returns:

sc query klif
sc query ftsata2

They're both there, John. One of them is:


SERVICE_NAME: ftsata2
TYPE : 1 KERNEL_DRIVER
STATE : 1 STOPPED

(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 31 (0x1f)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
The other one reads the same but I misplaced it.....the
same except it said klif and one other change
(I think TYPE -------CONTROL).xxxxxx SEE BELOW!!!!
xxxxxxxx

We could also get the list of drivers with a different command:

driverquery c:\drivers.txt


It didn't recognize that command.

If you want to solve the problem you need to keep on investigating
until you find what it is that is running or starting and that
prevents hibernation, I don't know of an easy way to figure this out.
Sometimes you need dogged determination to get to the bottom of some
of these problems.


Oh, you're right, John. We've both invested too much
time and intellect in it, and I'd hate to drop it,
either. But, as I said, what next?


Here's the other one.....from the Clone; both are
on both drives:


SERVICE_NAME: klif
TYPE : 2 FILE_SYSTEM_DRIVER
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 31 (0x1f)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

  #59  
Old April 1st 10, 08:41 PM posted to microsoft.public.windowsxp.basics
John John - MVP
external usenet poster
 
Posts: 780
Default WIA and hibernation again

William B. Lurie wrote:
John John - MVP wrote:
William B. Lurie wrote:
John John - MVP wrote:
William B. Lurie wrote:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 6:40:36 AM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it
is disabled or because it has no enabled devices associated with
it. " attempting to start the service MDM with arguments "" in
order to run the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 6:35:10 AM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it
is disabled or because it has no enabled devices associated with
it. " attempting to start the service MDM with arguments "" in
order to run the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Ntfs
Event Category: Disk
Event ID: 55
Date: 4/1/2010
Time: 6:42:47 AM
User: N/A
Computer: COMPAQ-2006
Description:
The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume R:.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0d 00 00 00 02 00 4e 00 ......N.
0008: 02 00 00 00 37 00 04 c0 ....7..À
0010: 00 00 00 00 32 00 00 c0 ....2..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 4/1/2010
Time: 6:44:25 AM
User: N/A
Computer: COMPAQ-2006
Description:
The following boot-start or system-start driver(s) failed to load:
ftsata2
KLIF


Is that an updated and current list of started Windows services?

Yes, John, I generate it anew every time I make one
of these hibernation runs, so that you can see it right
with the Events.

You discussed about those two drivers with another poster not too
long ago.

Yes, and now I'll answer your queries:

ftsata2: Do you now, or did you at any time have a Promise
controller installed?

No, I do not now, and never did. This basic HP machine came with
one hard drive, and cabling and slots for two more, which I
added. I select which drive to run by interrupting boot process
and telling it.

KLIF: Do you now or did you at any time have Kaspersky AV
software installed on the machine?

No, I have used Norton AV steadily for at least 15 years. From
the days when Norton was impossible to work with, to the present,
where they fix boo-boos by Chat and remote control of their
software.

The chkdsk message... What do you have stored on volume R?

Oh, I missed that it was referring to volume R. I have numerous
'restore points' of which that volume is one. I generate these
every month or so, using the Save & Restore feature of Norton
System Works, which used to be PowerQuest Partition Magic. I
keep these in case I have to recreate a system as it was as of
an earlier date). I'll chkdsk it routinely but I think we can
ignore that Event.

These system-start driver errors shouldn't affect the ability to
hibernate but you can change their startup type and get rid of the
errors if you want. You will have to change them in the registry at
their respective subkeys in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es key , set their
Start Value to 0x3 or 0x4. 0x3 is manual start, 0x4 is disabled.

Or, we can change them at the command prompt if you wish, I need the
results of the following command before I can give you the proper
commands to change the start type:

sc query state= all c:\sc.txt

Copy and paste the contents of the generated sc.txt file to your
next post, there will be lots of verbiage in the file, post it all.

John

I don't mess with registry unless it has to be messed with.
And if those commands and errors are innocuous, I see no need to
mess with them via command prompt. And the chkdsk request was
a blind alley, and to be sure, I deleted that 2+ year old backup
anyway.

But what to do next? With all this time spent on the hibernate
problem, I hate to give up. Who knows, the answer may be just around
the next bend in the road.


I don't see the KLIF or ftsata2 driver on the sc query list that you
supplied... could be that they are on the clone but not on the
production machine, or that the sc command doesn't see these as
services. You can try these and see what it returns:

sc query klif
sc query ftsata2

They're both there, John. One of them is:


SERVICE_NAME: ftsata2
TYPE : 1 KERNEL_DRIVER
STATE : 1 STOPPED

(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 31 (0x1f)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
The other one reads the same but I misplaced it.....the
same except it said klif and one other change
(I think TYPE -------CONTROL).


At the command prompt do:

sc config klif start= demand
sc config ftsata2 start= demand

You should get a ChangeServiceConfig message indicating success or failure.



We could also get the list of drivers with a different command:

driverquery c:\drivers.txt


It didn't recognize that command.


Another utility that is included in XP Pro but not in XP Home...


If you want to solve the problem you need to keep on investigating
until you find what it is that is running or starting and that
prevents hibernation, I don't know of an easy way to figure this out.
Sometimes you need dogged determination to get to the bottom of some
of these problems.


Oh, you're right, John. We've both invested too much
time and intellect in it, and I'd hate to drop it,
either. But, as I said, what next?


Make sure that you don't have a 3D screen saver running.

Disconnect the network cable and see if things change, maybe something
from 'outside' is keeping the machine alive.

See what shows up in the Event Log, if there is nothing to be found in
the Event Log start investigating the Loaded Modules.

John
  #60  
Old April 1st 10, 11:06 PM posted to microsoft.public.windowsxp.basics
William B. Lurie
external usenet poster
 
Posts: 811
Default WIA and hibernation again

John John - MVP wrote:
William B. Lurie wrote:
John John - MVP wrote:
William B. Lurie wrote:
John John - MVP wrote:
William B. Lurie wrote:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 6:40:36 AM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it
is disabled or because it has no enabled devices associated with
it. " attempting to start the service MDM with arguments "" in
order to run the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 6:35:10 AM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it
is disabled or because it has no enabled devices associated with
it. " attempting to start the service MDM with arguments "" in
order to run the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Ntfs
Event Category: Disk
Event ID: 55
Date: 4/1/2010
Time: 6:42:47 AM
User: N/A
Computer: COMPAQ-2006
Description:
The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume R:.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0d 00 00 00 02 00 4e 00 ......N.
0008: 02 00 00 00 37 00 04 c0 ....7..À
0010: 00 00 00 00 32 00 00 c0 ....2..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 4/1/2010
Time: 6:44:25 AM
User: N/A
Computer: COMPAQ-2006
Description:
The following boot-start or system-start driver(s) failed to load:
ftsata2
KLIF


Is that an updated and current list of started Windows services?

Yes, John, I generate it anew every time I make one
of these hibernation runs, so that you can see it right
with the Events.

You discussed about those two drivers with another poster not too
long ago.

Yes, and now I'll answer your queries:

ftsata2: Do you now, or did you at any time have a Promise
controller installed?

No, I do not now, and never did. This basic HP machine came with
one hard drive, and cabling and slots for two more, which I
added. I select which drive to run by interrupting boot process
and telling it.

KLIF: Do you now or did you at any time have Kaspersky AV
software installed on the machine?

No, I have used Norton AV steadily for at least 15 years. From
the days when Norton was impossible to work with, to the present,
where they fix boo-boos by Chat and remote control of their
software.

The chkdsk message... What do you have stored on volume R?

Oh, I missed that it was referring to volume R. I have numerous
'restore points' of which that volume is one. I generate these
every month or so, using the Save & Restore feature of Norton
System Works, which used to be PowerQuest Partition Magic. I
keep these in case I have to recreate a system as it was as of
an earlier date). I'll chkdsk it routinely but I think we can
ignore that Event.

These system-start driver errors shouldn't affect the ability to
hibernate but you can change their startup type and get rid of the
errors if you want. You will have to change them in the registry
at their respective subkeys in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es key , set
their Start Value to 0x3 or 0x4. 0x3 is manual start, 0x4 is
disabled.

Or, we can change them at the command prompt if you wish, I need
the results of the following command before I can give you the
proper commands to change the start type:

sc query state= all c:\sc.txt

Copy and paste the contents of the generated sc.txt file to your
next post, there will be lots of verbiage in the file, post it all.

John

I don't mess with registry unless it has to be messed with.
And if those commands and errors are innocuous, I see no need to
mess with them via command prompt. And the chkdsk request was
a blind alley, and to be sure, I deleted that 2+ year old backup
anyway.

But what to do next? With all this time spent on the hibernate
problem, I hate to give up. Who knows, the answer may be just around
the next bend in the road.

I don't see the KLIF or ftsata2 driver on the sc query list that you
supplied... could be that they are on the clone but not on the
production machine, or that the sc command doesn't see these as
services. You can try these and see what it returns:

sc query klif
sc query ftsata2

They're both there, John. One of them is:


SERVICE_NAME: ftsata2
TYPE : 1 KERNEL_DRIVER
STATE : 1 STOPPED

(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 31 (0x1f)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
The other one reads the same but I misplaced it.....the
same except it said klif and one other change
(I think TYPE -------CONTROL).


At the command prompt do:

sc config klif start= demand
sc config ftsata2 start= demand

You should get a ChangeServiceConfig message indicating success or failure.


Okay, I'll try those.


We could also get the list of drivers with a different command:

driverquery c:\drivers.txt


It didn't recognize that command.


Another utility that is included in XP Pro but not in XP Home...


If you want to solve the problem you need to keep on investigating
until you find what it is that is running or starting and that
prevents hibernation, I don't know of an easy way to figure this
out. Sometimes you need dogged determination to get to the bottom of
some of these problems.


Oh, you're right, John. We've both invested too much
time and intellect in it, and I'd hate to drop it,
either. But, as I said, what next?


Make sure that you don't have a 3D screen saver running.


Only screen saver is garden variety generic via StartDisplayScreen
Saver that came with XP.

Disconnect the network cable and see if things change, maybe something
from 'outside' is keeping the machine alive.


I was testing that way for a while, didn't show any improvement (then).

See what shows up in the Event Log, if there is nothing to be found in
the Event Log start investigating the Loaded Modules.


By Loaded Modules, I assume you mean everything that shows
in the Task Manager list, including about 15 executables
that are not user-generated...... SvcHosts, for example.
I don't think I'm up to doing that, but I have the other
items above to look into.

May I digress with an adaptation of a prayer?
Lord, give me the strength to change what I can change.
And the grace to accept what I cannot change.
And the wisdom to know the difference between the two.
Bill

John

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 12:28 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.