WIA and hibernation again
in [Windows XP Basics]
|
Prev: Pressing Change Password -button in WIN XP causes reboot
Next: Microsoft caught pirating somebody's patent again!!!
From: William B. Lurie on 26 Mar 2010 18:23 William B. Lurie wrote: > John John - MVP wrote: >> >> If I understand correctly, you have the machine set to hibernate after >> 2 hours of inactivity but it can't enter the hibernation state because >> something keeps it awake... >> >> This is what I would try: >> >> Reboot the machine and don't do anything whatsoever after it boots, >> leave it alone for the time set for hibernation and see if it does >> hibernate. >> >> If it doesn't hibernate I would then try a clean boot and once again >> not touch the machine for the set time and see if it does hibernate. >> >> http://support.microsoft.com/kb/310353 >> How to configure Windows XP to start in a "clean boot" state >> >> John > > John, I followed instructions. Touched NOTHING for 4 hours > (hibernate set at 2). Power-on light on tower was flashing > and it never went to hibernate. I'll read the Clean Boot instructions > again. Last time I thought it was quite an effort, but this is > this time. Maybe this evening. I took another small step, John. I like to try new things on my Clone system before I take a chance with my Main Drive......so I printed out KB310353 and followed its Method 2 on my clone system. It was very easy, and I did it and immediately went away for 2-3/4 hours ......and when I returned, the power light on my tower was blinking, the screen was on, and was not even in Screen Saver mode, which to me means that some Event occurred. It goes to Screen Saver at 10 minutes. I undid the msconfig changes and returned here, to my Master Drive. So I would judge that Clean Boot didn't show any difference. What's your next advice?
From: John John - MVP on 27 Mar 2010 01:11 William B. Lurie wrote: > William B. Lurie wrote: >> John John - MVP wrote: >>> >>> If I understand correctly, you have the machine set to hibernate >>> after 2 hours of inactivity but it can't enter the hibernation state >>> because something keeps it awake... >>> >>> This is what I would try: >>> >>> Reboot the machine and don't do anything whatsoever after it boots, >>> leave it alone for the time set for hibernation and see if it does >>> hibernate. >>> >>> If it doesn't hibernate I would then try a clean boot and once again >>> not touch the machine for the set time and see if it does hibernate. >>> >>> http://support.microsoft.com/kb/310353 >>> How to configure Windows XP to start in a "clean boot" state >>> >>> John >> >> John, I followed instructions. Touched NOTHING for 4 hours >> (hibernate set at 2). Power-on light on tower was flashing >> and it never went to hibernate. I'll read the Clean Boot instructions >> again. Last time I thought it was quite an effort, but this is >> this time. Maybe this evening. > > I took another small step, John. I like to try new things on my Clone > system before I take a chance with my Main Drive......so I printed > out KB310353 and followed its Method 2 on my clone system. It was very > easy, and I did it and immediately went away for 2-3/4 hours ......and > when I returned, the power light on my tower was blinking, the screen > was on, and was not even in Screen Saver mode, which to me means that > some Event occurred. It goes to Screen Saver at 10 minutes. I undid the > msconfig changes and returned here, to my Master Drive. > > So I would judge that Clean Boot didn't show any difference. What's > your next advice? Take a look in the Event Viewer and see if anything relevant is logged. Check the log on the clone too. John
From: William B. Lurie on 27 Mar 2010 07:44 John John - MVP wrote: > William B. Lurie wrote: >> William B. Lurie wrote: >>> John John - MVP wrote: >>>> >>>> If I understand correctly, you have the machine set to hibernate >>>> after 2 hours of inactivity but it can't enter the hibernation state >>>> because something keeps it awake... >>>> >>>> This is what I would try: >>>> >>>> Reboot the machine and don't do anything whatsoever after it boots, >>>> leave it alone for the time set for hibernation and see if it does >>>> hibernate. >>>> >>>> If it doesn't hibernate I would then try a clean boot and once again >>>> not touch the machine for the set time and see if it does hibernate. >>>> >>>> http://support.microsoft.com/kb/310353 >>>> How to configure Windows XP to start in a "clean boot" state >>>> >>>> John >>> >>> John, I followed instructions. Touched NOTHING for 4 hours >>> (hibernate set at 2). Power-on light on tower was flashing >>> and it never went to hibernate. I'll read the Clean Boot instructions >>> again. Last time I thought it was quite an effort, but this is >>> this time. Maybe this evening. >> >> I took another small step, John. I like to try new things on my Clone >> system before I take a chance with my Main Drive......so I printed >> out KB310353 and followed its Method 2 on my clone system. It was very >> easy, and I did it and immediately went away for 2-3/4 hours ......and >> when I returned, the power light on my tower was blinking, the screen >> was on, and was not even in Screen Saver mode, which to me means that >> some Event occurred. It goes to Screen Saver at 10 minutes. I undid the >> msconfig changes and returned here, to my Master Drive. >> >> So I would judge that Clean Boot didn't show any difference. What's >> your next advice? > > Take a look in the Event Viewer and see if anything relevant is logged. > Check the log on the clone too. > > John I'll have to do the clean boot again to be sure, but I don't think it told a noteworthy story. But, because I, too, am suspicious that the Norton AV software is a likely suspect, I made a different test overnight, on this Master system. I disabled all Norton/Symantec entries in the services.msc list, disconnected from the phone line, and let it try to go to sleep at 10 P.M...... and when I checked nine hours later, the power light on the tower was flashing. So I immediately copied and saved the 3 pages in the Events Log, and will paste them in below. I was disappointed in a way, at not seeing the every-hour intervention, and I don't know if it's good news or not. What's your take on it? (I'm sorry for the length of the post; I haven't worked out the free uploading thing yet). But the overnight Events Log is surprisingly bare; maybe that does point the accusing finger at the Norton software. I can repeat that test overnight with just that one difference. Note the usual 7026 error when booting at 6:50 this morning, that I've mentioned before, and nothing else. I really ought to do the clean boot thing again on the clone, and record the Events Log. > Type Date Time Source Category Event User Computer > Information 3/27/2010 6:49:21 AM Norton AntiVirus None 35 SYSTEM COMPAQ-2006 > Information 3/27/2010 6:49:19 AM Norton AntiVirus None 34 SYSTEM COMPAQ-2006 > Information 3/27/2010 6:45:45 AM SecurityCenter None 1800 N/A COMPAQ-2006 > Information 3/27/2010 6:44:02 AM Viewpoint Manager Service None 0 N/A COMPAQ-2006 > Information 3/27/2010 6:43:11 AM Norton Save and Restore Medium Priority 100 N/A COMPAQ-2006 > Information 3/27/2010 6:42:26 AM Norton AntiVirus None 35 SYSTEM COMPAQ-2006 > Information 3/27/2010 6:42:25 AM Norton AntiVirus None 34 SYSTEM COMPAQ-2006 Type Date Time Source Category Event User Computer Success Audit 3/27/2010 6:50:04 AM Security Policy Change 850 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 850 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 850 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 850 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 850 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 850 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 850 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 849 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:04 AM Security Policy Change 848 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:50:02 AM Security Privilege Use 576 LOCAL SERVICE COMPAQ-2006 Success Audit 3/27/2010 6:50:02 AM Security Logon/Logoff 528 LOCAL SERVICE COMPAQ-2006 Success Audit 3/27/2010 6:49:53 AM Security Privilege Use 576 NETWORK SERVICE COMPAQ-2006 Success Audit 3/27/2010 6:49:53 AM Security Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 Success Audit 3/27/2010 6:49:46 AM Security Privilege Use 576 NETWORK SERVICE COMPAQ-2006 Success Audit 3/27/2010 6:49:46 AM Security Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 Success Audit 3/27/2010 6:49:44 AM Security System Event 515 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:39 AM Security Privilege Use 576 LOCAL SERVICE COMPAQ-2006 Success Audit 3/27/2010 6:49:39 AM Security Logon/Logoff 528 LOCAL SERVICE COMPAQ-2006 Success Audit 3/27/2010 6:49:21 AM Security System Event 515 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:15 AM Security Logon/Logoff 540 ANONYMOUS LOGON COMPAQ-2006 Success Audit 3/27/2010 6:49:12 AM Security Privilege Use 576 LOCAL SERVICE COMPAQ-2006 Success Audit 3/27/2010 6:49:12 AM Security Logon/Logoff 528 LOCAL SERVICE COMPAQ-2006 Success Audit 3/27/2010 6:49:06 AM Security System Event 515 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:06 AM Security System Event 515 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:06 AM Security System Event 515 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:05 AM Security Policy Change 806 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:04 AM Security Privilege Use 576 Compaq_Owner COMPAQ-2006 Success Audit 3/27/2010 6:49:04 AM Security Logon/Logoff 528 Compaq_Owner COMPAQ-2006 Success Audit 3/27/2010 6:49:04 AM Security Account Logon 680 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:04 AM Security Logon/Logoff 538 Compaq_Owner COMPAQ-2006 Success Audit 3/27/2010 6:49:04 AM Security Privilege Use 576 Compaq_Owner COMPAQ-2006 Success Audit 3/27/2010 6:49:04 AM Security Logon/Logoff 528 Compaq_Owner COMPAQ-2006 Success Audit 3/27/2010 6:49:04 AM Security Account Logon 680 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:02 AM Security Privilege Use 576 LOCAL SERVICE COMPAQ-2006 Success Audit 3/27/2010 6:49:02 AM Security Logon/Logoff 528 LOCAL SERVICE COMPAQ-2006 Success Audit 3/27/2010 6:49:02 AM Security Privilege Use 576 NETWORK SERVICE COMPAQ-2006 Success Audit 3/27/2010 6:49:02 AM Security Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 Success Audit 3/27/2010 6:49:01 AM Security Privilege Use 576 NETWORK SERVICE COMPAQ-2006 Success Audit 3/27/2010 6:49:01 AM Security Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006 Success Audit 3/27/2010 6:49:01 AM Security System Event 515 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:01 AM Security System Event 518 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:01 AM Security System Event 515 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:01 AM Security System Event 515 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:01 AM Security System Event 515 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:01 AM Security System Event 514 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:01 AM Security System Event 514 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:01 AM Security System Event 514 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:01 AM Security System Event 514 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:01 AM Security System Event 514 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:01 AM Security System Event 514 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:49:01 AM Security System Event 514 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:47:55 AM Security System Event 513 SYSTEM COMPAQ-2006 Success Audit 3/27/2010 6:47:48 AM Security Logon/Logoff 551 Compaq_Owner COMPAQ-2006 Success Audit 3/26/2010 10:29:50 PM Security System Event 517 SYSTEM COMPAQ-2006 Type Date Time Source Category Event User Computer Information 3/27/2010 7:02:21 AM Service Control Manager None 7036 N/A COMPAQ-2006 Information 3/27/2010 7:02:20 AM Service Control Manager None 7035 SYSTEM COMPAQ-2006 Information 3/27/2010 7:00:55 AM Service Control Manager None 7036 N/A COMPAQ-2006 Information 3/27/2010 7:00:55 AM Service Control Manager None 7035 SYSTEM COMPAQ-2006 Information 3/27/2010 6:50:35 AM Service Control Manager None 7036 N/A COMPAQ-2006 Information 3/27/2010 6:50:35 AM Service Control Manager None 7036 N/A COMPAQ-2006 Information 3/27/2010 6:50:35 AM Service Control Manager None 7035 SYSTEM COMPAQ-2006 Information 3/27/2010 6:50:35 AM Service Control Manager None 7035 SYSTEM COMPAQ-2006 Information 3/27/2010 6:50:35 AM Service Control Manager None 7036 N/A COMPAQ-2006 Information 3/27/2010 6:50:35 AM Service Control Manager None 7036 N/A COMPAQ-2006 Information 3/27/2010 6:50:35 AM Service Control Manager None 7036 N/A COMPAQ-2006 Information 3/27/2010 6:50:35 AM Service Control Manager None 7035 SYSTEM COMPAQ-2006 Information 3/27/2010 6:50:35 AM Service Control Manager None 7035 Compaq_Owner COMPAQ-2006 Information 3/27/2010 6:50:35 AM Service Control Manager None 7036 N/A COMPAQ-2006 Information 3/27/2010 6:50:35 AM Service Control Manager None 7036 N/A COMPAQ-2006 Information 3/27/2010 6:50:35 AM Service Control Manager None 7035 SYSTEM COMPAQ-2006 Information 3/27/2010 6:50:35 AM Service Control Manager None 7036 N/A COMPAQ-2006 Information 3/27/2010 6:50:35 AM Service Control Manager None 7035 SYSTEM COMPAQ-2006 Information 3/27/2010 6:50:35 AM Service Control Manager None 7036 N/A COMPAQ-2006 Information 3/27/2010 6:50:35 AM Service Control Manager None 7035 SYSTEM COMPAQ-2006 Error 3/27/2010 6:50:35 AM Service Control Manager None 7026 N/A COMPAQ-2006 Information 3/27/2010 6:50:02 AM SRTSP None 2003 N/A COMPAQ-2006 Information 3/27/2010 6:48:47 AM Tcpip None 4201 N/A COMPAQ-2006 Information 3/27/2010 6:49:01 AM eventlog None 6005 N/A COMPAQ-2006 Information 3/27/2010 6:49:01 AM eventlog None 6009 N/A COMPAQ-2006 Information 3/27/2010 6:47:55 AM eventlog None 6006 N/A COMPAQ-2006 Information 3/27/2010 6:45:45 AM Service Control Manager None 7036 N/A COMPAQ-2006 Information 3/27/2010 6:45:45 AM Service Control Manager None 7035 Compaq_Owner COMPAQ-2006 Information 3/27/2010 6:44:02 AM Service Control Manager None 7036 N/A COMPAQ-2006 Information 3/27/2010 6:44:02 AM Service Control Manager None 7035 Compaq_Owner COMPAQ-2006 Information 3/27/2010 6:42:56 AM Service Control Manager None 7036 N/A COMPAQ-2006 Information 3/27/2010 6:42:56 AM Service Control Manager None 7035 Compaq_Owner COMPAQ-2006 Information 3/27/2010 6:42:49 AM Service Control Manager None 7035 SYSTEM COMPAQ-2006 Information 3/27/2010 6:42:26 AM Service Control Manager None 7036 N/A COMPAQ-2006 Information 3/27/2010 6:42:26 AM Service Control Manager None 7035 Compaq_Owner COMPAQ-2006 Information 3/27/2010 6:41:19 AM Service Control Manager None 7036 N/A COMPAQ-2006 Information 3/27/2010 6:41:19 AM Service Control Manager None 7035 SYSTEM COMPAQ-2006
From: William B. Lurie on 27 Mar 2010 08:55 John John - MVP wrote: > William B. Lurie wrote: >> William B. Lurie wrote: >>> John John - MVP wrote: >>>> >>>> If I understand correctly, you have the machine set to hibernate >>>> after 2 hours of inactivity but it can't enter the hibernation state >>>> because something keeps it awake... >>>> >>>> This is what I would try: >>>> >>>> Reboot the machine and don't do anything whatsoever after it boots, >>>> leave it alone for the time set for hibernation and see if it does >>>> hibernate. >>>> >>>> If it doesn't hibernate I would then try a clean boot and once again >>>> not touch the machine for the set time and see if it does hibernate. >>>> >>>> http://support.microsoft.com/kb/310353 >>>> How to configure Windows XP to start in a "clean boot" state >>>> >>>> John >>> >>> John, I followed instructions. Touched NOTHING for 4 hours >>> (hibernate set at 2). Power-on light on tower was flashing >>> and it never went to hibernate. I'll read the Clean Boot instructions >>> again. Last time I thought it was quite an effort, but this is >>> this time. Maybe this evening. >> >> I took another small step, John. I like to try new things on my Clone >> system before I take a chance with my Main Drive......so I printed >> out KB310353 and followed its Method 2 on my clone system. It was very >> easy, and I did it and immediately went away for 2-3/4 hours ......and >> when I returned, the power light on my tower was blinking, the screen >> was on, and was not even in Screen Saver mode, which to me means that >> some Event occurred. It goes to Screen Saver at 10 minutes. I undid the >> msconfig changes and returned here, to my Master Drive. >> >> So I would judge that Clean Boot didn't show any difference. What's >> your next advice? > > Take a look in the Event Viewer and see if anything relevant is logged. > Check the log on the clone too. > > John The scene changes again, John. I just heard from Symantec, that Norton AntiVirus does do Idle Time Scan. I had it set for "Quarterly" so it should not have interfered. But with their help, I reset it to *never* and maybe that will be the answer. I can live with no idle time scans. So put my other testing on hold while I find out if hibernate now works right.
From: Unknown on 27 Mar 2010 12:11
Have you looked into using MSE? "William B. Lurie" <billurie(a)nospam.net> wrote in message news:ugsTbITzKHA.1796(a)TK2MSFTNGP02.phx.gbl... > Dear Unk: > Thanks for working with me. I'll let John comment more on > your list, but Norton Anti-Virus is my main protection and > I don't leave home without it. I could, of course, disconnect from > the phone line and disable it to see if somehow that's the cause. > One thing at a time..... > > Unknown wrote: >> William; I compared my services with yours since my system does not fail >> to hibernate. >> I'll post the differences. Do a Google search for 'viewpoint manager >> services'. Looks suspicious. >> I would also suspect Norton AntiVirus. >> Differences (not on my system) are: >> LexBce Server >> lxct device >> Norton AntiVirus-------I would definately get rid of this. >> Pervasive PSQL Workgroup Engine >> Speed Disk Service------Part of Norton >> Viewpoint Manager Service >> >> >> "William B. Lurie" <billurie(a)nospam.net> wrote in message >> news:OPnYAYRzKHA.5940(a)TK2MSFTNGP02.phx.gbl... >>> John John - MVP wrote: >>>> If I understand correctly, you have the machine set to hibernate after >>>> 2 hours of inactivity but it can't enter the hibernation state because >>>> something keeps it awake... >>>> >>>> This is what I would try: >>>> >>>> Reboot the machine and don't do anything whatsoever after it boots, >>>> leave it alone for the time set for hibernation and see if it does >>>> hibernate. >>>> >>>> If it doesn't hibernate I would then try a clean boot and once again >>>> not touch the machine for the set time and see if it does hibernate. >>>> >>>> http://support.microsoft.com/kb/310353 >>>> How to configure Windows XP to start in a "clean boot" state >>>> >>>> John >>> John, I followed instructions. Touched NOTHING for 4 hours >>> (hibernate set at 2). Power-on light on tower was flashing >>> and it never went to hibernate. I'll read the Clean Boot instructions >>> again. Last time I thought it was quite an effort, but this is >>> this time. Maybe this evening. >> |