Forum - DLL-files.com

John John - MVP wrote:
> William B. Lurie wrote:
>> William B. Lurie wrote:
>> <snip>
>>> I just finished what might be the most positive indicating
>>> run yet. Same conditions as last run, except this time I did
>>>
>>> Clean Boot
>>> Disabled Auto Live Update
>>> Disabled WIA and started at 9:12 P.M.
>>>
>>> 2.5 hours later, it had not hibernated, but I think
>>> there is just one reason clearly shown. I'll send you
>>> the files in the morning to look at, John.
>>>
>>> What I see is just *one* event, but it happened at 10:35 .....
>>> Tcpip... Type 4201 ......."SCM" I think.
>>>
>>> Bill
>> See these:
>>
>>> Type Date Time Source Category Event User Computer
>>> Information 4/14/2010 9:05:01 PM Automatic LiveUpdate
>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>> Information 4/14/2010 9:04:02 PM Automatic LiveUpdate
>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>> Information 4/14/2010 9:04:02 PM Automatic LiveUpdate
>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>> Information 4/14/2010 9:04:02 PM Automatic LiveUpdate
>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>> Information 4/14/2010 6:03:02 PM Automatic LiveUpdate
>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>> Information 4/14/2010 6:03:02 PM Automatic LiveUpdate
>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>
>> Type Date
>> Success Audit 4/14/2010 11:34:34 PM Security System
>> Event 513 SYSTEM COMPAQ-2006
>> Success Audit 4/14/2010 11:34:28 PM Security
>> Logon/Logoff 551 Compaq_Owner COMPAQ-2006
>> Success Audit 4/14/2010 9:11:04 PM Security Privilege
>> Use 576 NETWORK SERVICE COMPAQ-2006
>> Success Audit 4/14/2010 9:11:04 PM Security
>> Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006
>> Success Audit 4/14/2010 9:10:24 PM Security Privilege
>> Use 576 NETWORK SERVICE COMPAQ-2006
>> Success Audit 4/14/2010 9:10:24 PM Security
>> Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006
>> Success Audit 4/14/2010 9:10:24 PM Security System
>> Event 515 SYSTEM COMPAQ-2006
>> Success Audit 4/14/2010 9:10:22 PM Security Policy
>> Change 850 SYSTEM COMPAQ-2006
>> Success Audit 4/14/2010 9:10:22 PM Security Policy
>> Change 850 SYSTEM COMPAQ-2006
>> Success Audit 4/14/2010 9:10:22 PM Security Policy
>> Change 850 SYSTEM COMPAQ-2006
>>
>>> Type Date Time Source Cate
>>> Information 4/14/2010 11:34:34 PM eventlog None
>>> 6006 N/A COMPAQ-2006
>>> Information 4/14/2010 11:34:33 PM Service Control Manager
>>> None 7036 N/A COMPAQ-2006
>>> Information 4/14/2010 11:30:33 PM Tcpip None 4201
>>> N/A COMPAQ-2006
>>> Information 4/14/2010 10:35:53 PM Tcpip None 4201
>>> N/A COMPAQ-2006
>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>> None 7036 N/A COMPAQ-2006
>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>> None 7036 N/A COMPAQ-2006
>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>> None 7036 N/A COMPAQ-2006
>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>> None 7035 SYSTEM COMPAQ-2006
>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>> None 7035 Compaq_Owner COMPAQ-2006
>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>> None 7036 N/A COMPAQ-2006
>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>> None 7036 N/A COMPAQ-2006
>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>> None 7035 SYSTEM COMPAQ-2006
>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>> None 7036 N/A COMPAQ-2006
>>>
>>> Event Type: Information
>>> Event Source: Tcpip
>>> Event Category: None
>>> Event ID: 4201
>>> Date: 4/14/2010
>>> Time: 10:35:53 PM
>>> User: N/A
>>> Computer: COMPAQ-2006
>>> Description:
>>> The system detected that network adapter
>>> \DEVICE\TCPIP_{D5E50A75-4A1C-4421-A5B4-569C9FE131B8} was connected to
>>> the network, and has initiated normal operation over the network
>>> adapter.
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>> Data:
>>> 0000: 00 00 00 00 02 00 50 00 ......P.
>>> 0008: 00 00 00 00 69 10 00 40 ....i..@
>>> 0010: 02 00 00 00 00 00 00 00 ........
>>> 0018: 00 00 00 00 00 00 00 00 ........
>>> 0020: 00 00 00 00 00 00 00 00 ........
>>
>> I think that 10:35 PM event was the killer........
>> Our old friend Tcpip again. I have the feeling that, if I let it
>> run on past 11:30. it would repeat every hour or so.
>>
>> I'm ready to clean out the Event Logs on the Clone
>> system, and Clean Boot, and do whatever you tell me to,
>> John, to track it down. I don't know what Network Adapter they're
>> referring to in the Event Description.....
>
> Please do the clean boot.
>
> John
That last run *was* from squeaky cleanest clean boot,
John. I can clear out the ancient history just to make
the Event Logs look smaller, but that isn't going to change anything.
As I see it, we have the Tcpip 10:35 PM Event Type 4201 which I
expanded out and posted......and that needs blocking or whatever.
Bill

William B. Lurie wrote:
> John John - MVP wrote:
>> William B. Lurie wrote:
>>> William B. Lurie wrote:
>>> <snip>
>>>> I just finished what might be the most positive indicating
>>>> run yet. Same conditions as last run, except this time I did
>>>>
>>>> Clean Boot
>>>> Disabled Auto Live Update
>>>> Disabled WIA and started at 9:12 P.M.
>>>>
>>>> 2.5 hours later, it had not hibernated, but I think
>>>> there is just one reason clearly shown. I'll send you
>>>> the files in the morning to look at, John.
>>>>
>>>> What I see is just *one* event, but it happened at 10:35 .....
>>>> Tcpip... Type 4201 ......."SCM" I think.
>>>>
>>>> Bill
>>> See these:
>>>
>>>> Type Date Time Source Category Event User Computer
>>>> Information 4/14/2010 9:05:01 PM Automatic LiveUpdate
>>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>>> Information 4/14/2010 9:04:02 PM Automatic LiveUpdate
>>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>>> Information 4/14/2010 9:04:02 PM Automatic LiveUpdate
>>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>>> Information 4/14/2010 9:04:02 PM Automatic LiveUpdate
>>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>>> Information 4/14/2010 6:03:02 PM Automatic LiveUpdate
>>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>>> Information 4/14/2010 6:03:02 PM Automatic LiveUpdate
>>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>>
>>> Type Date
>>> Success Audit 4/14/2010 11:34:34 PM Security System
>>> Event 513 SYSTEM COMPAQ-2006
>>> Success Audit 4/14/2010 11:34:28 PM Security
>>> Logon/Logoff 551 Compaq_Owner COMPAQ-2006
>>> Success Audit 4/14/2010 9:11:04 PM Security Privilege
>>> Use 576 NETWORK SERVICE COMPAQ-2006
>>> Success Audit 4/14/2010 9:11:04 PM Security
>>> Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006
>>> Success Audit 4/14/2010 9:10:24 PM Security Privilege
>>> Use 576 NETWORK SERVICE COMPAQ-2006
>>> Success Audit 4/14/2010 9:10:24 PM Security
>>> Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006
>>> Success Audit 4/14/2010 9:10:24 PM Security System
>>> Event 515 SYSTEM COMPAQ-2006
>>> Success Audit 4/14/2010 9:10:22 PM Security Policy
>>> Change 850 SYSTEM COMPAQ-2006
>>> Success Audit 4/14/2010 9:10:22 PM Security Policy
>>> Change 850 SYSTEM COMPAQ-2006
>>> Success Audit 4/14/2010 9:10:22 PM Security Policy
>>> Change 850 SYSTEM COMPAQ-2006
>>>
>>>> Type Date Time Source Cate
>>>> Information 4/14/2010 11:34:34 PM eventlog None
>>>> 6006 N/A COMPAQ-2006
>>>> Information 4/14/2010 11:34:33 PM Service Control
>>>> Manager None 7036 N/A COMPAQ-2006
>>>> Information 4/14/2010 11:30:33 PM Tcpip None 4201
>>>> N/A COMPAQ-2006
>>>> Information 4/14/2010 10:35:53 PM Tcpip None 4201
>>>> N/A COMPAQ-2006
>>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>>> None 7036 N/A COMPAQ-2006
>>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>>> None 7036 N/A COMPAQ-2006
>>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>>> None 7036 N/A COMPAQ-2006
>>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>>> None 7035 SYSTEM COMPAQ-2006
>>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>>> None 7035 Compaq_Owner COMPAQ-2006
>>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>>> None 7036 N/A COMPAQ-2006
>>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>>> None 7036 N/A COMPAQ-2006
>>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>>> None 7035 SYSTEM COMPAQ-2006
>>>> Information 4/14/2010 9:11:40 PM Service Control Manager
>>>> None 7036 N/A COMPAQ-2006
>>>>
>>>> Event Type: Information
>>>> Event Source: Tcpip
>>>> Event Category: None
>>>> Event ID: 4201
>>>> Date: 4/14/2010
>>>> Time: 10:35:53 PM
>>>> User: N/A
>>>> Computer: COMPAQ-2006
>>>> Description:
>>>> The system detected that network adapter
>>>> \DEVICE\TCPIP_{D5E50A75-4A1C-4421-A5B4-569C9FE131B8} was connected
>>>> to the network, and has initiated normal operation over the network
>>>> adapter.
>>>>
>>>> For more information, see Help and Support Center at
>>>> http://go.microsoft.com/fwlink/events.asp.
>>>> Data:
>>>> 0000: 00 00 00 00 02 00 50 00 ......P.
>>>> 0008: 00 00 00 00 69 10 00 40 ....i..@
>>>> 0010: 02 00 00 00 00 00 00 00 ........
>>>> 0018: 00 00 00 00 00 00 00 00 ........
>>>> 0020: 00 00 00 00 00 00 00 00 ........
>>>
>>> I think that 10:35 PM event was the killer........
>>> Our old friend Tcpip again. I have the feeling that, if I let it
>>> run on past 11:30. it would repeat every hour or so.
>>>
>>> I'm ready to clean out the Event Logs on the Clone
>>> system, and Clean Boot, and do whatever you tell me to,
>>> John, to track it down. I don't know what Network Adapter they're
>>> referring to in the Event Description.....
>>
>> Please do the clean boot.
>>
>> John
> That last run *was* from squeaky cleanest clean boot,
> John. I can clear out the ancient history just to make
> the Event Logs look smaller, but that isn't going to change anything.
> As I see it, we have the Tcpip 10:35 PM Event Type 4201 which I
> expanded out and posted......and that needs blocking or whatever.

Typically you should only be seeing one (if ever) Event 4201 from TCPIP
when the computer is booted, or when the adapter is disabled or enabled.
Have you always been getting multiple Events 4201? If yes this might
be indicative of faulty or failing network hardware, bad cable, bad
switch, bad router, bad NIC... Try disabling the network adapter and
see what happens, to disable the adapter go in "Network Connections" and
right click on the connection. On your previous effort with a different
clone, did you ever at any time successfully hibernate at 2 hours?

John

John John - MVP wrote:
> William B. Lurie wrote:
>> John John - MVP wrote:
>>> William B. Lurie wrote:
>>>> William B. Lurie wrote:
>>>> <snip>
>>>>> I just finished what might be the most positive indicating
>>>>> run yet. Same conditions as last run, except this time I did
>>>>>
>>>>> Clean Boot
>>>>> Disabled Auto Live Update
>>>>> Disabled WIA and started at 9:12 P.M.
>>>>>
>>>>> 2.5 hours later, it had not hibernated, but I think
>>>>> there is just one reason clearly shown. I'll send you
>>>>> the files in the morning to look at, John.
>>>>>
>>>>> What I see is just *one* event, but it happened at 10:35 .....
>>>>> Tcpip... Type 4201 ......."SCM" I think.
>>>>>
>>>>> Bill
>>>> See these:
>>>>
>>>>> Type Date Time Source Category Event User
>>>>> Computer
>>>>> Information 4/14/2010 9:05:01 PM Automatic LiveUpdate
>>>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>>>> Information 4/14/2010 9:04:02 PM Automatic LiveUpdate
>>>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>>>> Information 4/14/2010 9:04:02 PM Automatic LiveUpdate
>>>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>>>> Information 4/14/2010 9:04:02 PM Automatic LiveUpdate
>>>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>>>> Information 4/14/2010 6:03:02 PM Automatic LiveUpdate
>>>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>>>> Information 4/14/2010 6:03:02 PM Automatic LiveUpdate
>>>>> Scheduler Devices 101 SYSTEM COMPAQ-2006
>>>>
>>>> Type Date
>>>> Success Audit 4/14/2010 11:34:34 PM Security System
>>>> Event 513 SYSTEM COMPAQ-2006
>>>> Success Audit 4/14/2010 11:34:28 PM Security
>>>> Logon/Logoff 551 Compaq_Owner COMPAQ-2006
>>>> Success Audit 4/14/2010 9:11:04 PM Security Privilege
>>>> Use 576 NETWORK SERVICE COMPAQ-2006
>>>> Success Audit 4/14/2010 9:11:04 PM Security
>>>> Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006
>>>> Success Audit 4/14/2010 9:10:24 PM Security Privilege
>>>> Use 576 NETWORK SERVICE COMPAQ-2006
>>>> Success Audit 4/14/2010 9:10:24 PM Security
>>>> Logon/Logoff 528 NETWORK SERVICE COMPAQ-2006
>>>> Success Audit 4/14/2010 9:10:24 PM Security System
>>>> Event 515 SYSTEM COMPAQ-2006
>>>> Success Audit 4/14/2010 9:10:22 PM Security Policy
>>>> Change 850 SYSTEM COMPAQ-2006
>>>> Success Audit 4/14/2010 9:10:22 PM Security Policy
>>>> Change 850 SYSTEM COMPAQ-2006
>>>> Success Audit 4/14/2010 9:10:22 PM Security Policy
>>>> Change 850 SYSTEM COMPAQ-2006
>>>>
>>>>> Type Date Time Source Cate
>>>>> Information 4/14/2010 11:34:34 PM eventlog None
>>>>> 6006 N/A COMPAQ-2006
>>>>> Information 4/14/2010 11:34:33 PM Service Control
>>>>> Manager None 7036 N/A COMPAQ-2006
>>>>> Information 4/14/2010 11:30:33 PM Tcpip None 4201
>>>>> N/A COMPAQ-2006
>>>>> Information 4/14/2010 10:35:53 PM Tcpip None 4201
>>>>> N/A COMPAQ-2006
>>>>> Information 4/14/2010 9:11:40 PM Service Control
>>>>> Manager None 7036 N/A COMPAQ-2006
>>>>> Information 4/14/2010 9:11:40 PM Service Control
>>>>> Manager None 7036 N/A COMPAQ-2006
>>>>> Information 4/14/2010 9:11:40 PM Service Control
>>>>> Manager None 7036 N/A COMPAQ-2006
>>>>> Information 4/14/2010 9:11:40 PM Service Control
>>>>> Manager None 7035 SYSTEM COMPAQ-2006
>>>>> Information 4/14/2010 9:11:40 PM Service Control
>>>>> Manager None 7035 Compaq_Owner COMPAQ-2006
>>>>> Information 4/14/2010 9:11:40 PM Service Control
>>>>> Manager None 7036 N/A COMPAQ-2006
>>>>> Information 4/14/2010 9:11:40 PM Service Control
>>>>> Manager None 7036 N/A COMPAQ-2006
>>>>> Information 4/14/2010 9:11:40 PM Service Control
>>>>> Manager None 7035 SYSTEM COMPAQ-2006
>>>>> Information 4/14/2010 9:11:40 PM Service Control
>>>>> Manager None 7036 N/A COMPAQ-2006
>>>>>
>>>>> Event Type: Information
>>>>> Event Source: Tcpip
>>>>> Event Category: None
>>>>> Event ID: 4201
>>>>> Date: 4/14/2010
>>>>> Time: 10:35:53 PM
>>>>> User: N/A
>>>>> Computer: COMPAQ-2006
>>>>> Description:
>>>>> The system detected that network adapter
>>>>> \DEVICE\TCPIP_{D5E50A75-4A1C-4421-A5B4-569C9FE131B8} was connected
>>>>> to the network, and has initiated normal operation over the network
>>>>> adapter.
>>>>>
>>>>> For more information, see Help and Support Center at
>>>>> http://go.microsoft.com/fwlink/events.asp.
>>>>> Data:
>>>>> 0000: 00 00 00 00 02 00 50 00 ......P.
>>>>> 0008: 00 00 00 00 69 10 00 40 ....i..@
>>>>> 0010: 02 00 00 00 00 00 00 00 ........
>>>>> 0018: 00 00 00 00 00 00 00 00 ........
>>>>> 0020: 00 00 00 00 00 00 00 00 ........
>>>>
>>>> I think that 10:35 PM event was the killer........
>>>> Our old friend Tcpip again. I have the feeling that, if I let it
>>>> run on past 11:30. it would repeat every hour or so.
>>>>
>>>> I'm ready to clean out the Event Logs on the Clone
>>>> system, and Clean Boot, and do whatever you tell me to,
>>>> John, to track it down. I don't know what Network Adapter they're
>>>> referring to in the Event Description.....
>>>
>>> Please do the clean boot.
>>>
>>> John
>> That last run *was* from squeaky cleanest clean boot,
>> John. I can clear out the ancient history just to make
>> the Event Logs look smaller, but that isn't going to change anything.
>> As I see it, we have the Tcpip 10:35 PM Event Type 4201 which I
>> expanded out and posted......and that needs blocking or whatever.
>
> Typically you should only be seeing one (if ever) Event 4201 from TCPIP
> when the computer is booted, or when the adapter is disabled or enabled.
> Have you always been getting multiple Events 4201? If yes this might
> be indicative of faulty or failing network hardware, bad cable, bad
> switch, bad router, bad NIC... Try disabling the network adapter and
> see what happens, to disable the adapter go in "Network Connections" and
> right click on the connection. On your previous effort with a different
> clone, did you ever at any time successfully hibernate at 2 hours?
>
> John
>
Can't say if I ever saw multiple 4201 from Tcpip, John. All I can do is
watch for it as we make more runs. I can repeat last run exactly, in the
clone, with Network Connections Disabled. As for ever seeing successful
hibernate at 2 hours, 'ever' is getting to be a long time, and I
really can't say if I ever saw it. I think yes, but really couldn't
swear to it. I'll look at and disable now in the clone, but, remember,
that system has no AV at all and I run it disconnected from the line.
Back at 12:30....
Bill

William B. Lurie wrote:
> This is a new thread. See old stuff for history.

Does everyone realize that at this point in the troubleshooting procedure -
if time is money (and for many people it is) and even if it is not a *lot*
of money (let's go with $1.00 / hour - U.S.) that this problem has gone on
long enough now to afford a replacement computer with likely more CPU power,
more hard drive space and a better video device without all the current
trouble by now, eh?

I mean - really - this computer could be defective.

Just throwing that out there... *grin*

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Shenan Stanley wrote:
> William B. Lurie wrote:
>> This is a new thread. See old stuff for history.
>
> Does everyone realize that at this point in the troubleshooting procedure -
> if time is money (and for many people it is) and even if it is not a *lot*
> of money (let's go with $1.00 / hour - U.S.) that this problem has gone on
> long enough now to afford a replacement computer with likely more CPU power,
> more hard drive space and a better video device without all the current
> trouble by now, eh?
>
> I mean - really - this computer could be defective.
>
> Just throwing that out there... *grin*
>
You are 99-44/100 percent right, but the other 0.56% is the
spirit of the scientist who wants to know *why*. I would be
willing to drop the issue any time John wants to throw in
the towel, and I will thank him a thousand-fold for his
invaluable assistance, perseverance, and resourcefulness.

Meanwhile, we are quite close to the solution, as my posting later
this morning will indicate. Getting the Network thing and also
the ever-intrusive Norton background scans out of the way has
given me, overnight, two runs which ran two hours before going
into hibernation.

William B. Lurie wrote:
> Shenan Stanley wrote:
>> William B. Lurie wrote:
>>> This is a new thread. See old stuff for history.
>>
>> Does everyone realize that at this point in the troubleshooting
>> procedure - if time is money (and for many people it is) and even if
>> it is not a *lot* of money (let's go with $1.00 / hour - U.S.) that
>> this problem has gone on long enough now to afford a replacement
>> computer with likely more CPU power, more hard drive space and a
>> better video device without all the current trouble by now, eh?
>>
>> I mean - really - this computer could be defective.
>>
>> Just throwing that out there... *grin*
>>
> You are 99-44/100 percent right, but the other 0.56% is the
> spirit of the scientist who wants to know *why*. I would be
> willing to drop the issue any time John wants to throw in
> the towel, and I will thank him a thousand-fold for his
> invaluable assistance, perseverance, and resourcefulness.
>
> Meanwhile, we are quite close to the solution, as my posting later
> this morning will indicate. Getting the Network thing and also
> the ever-intrusive Norton background scans out of the way has
> given me, overnight, two runs which ran two hours before going
> into hibernation.

To make the successful runs on my Clone system, John, I did
not do Clean Boot, but I Disabled the Networks Connection from Control
Panel, and turned off all Norton Anti Virus (disconnecting from
the line, of course). Oh, I unplugged printer and camera but I
don't expect that is pertinent. I'll see to the Norton part, but
what's your take on the 'Networks Connection' thing? Isn't that
vital to communicating with he web?

William B. Lurie wrote:
> William B. Lurie wrote:
>> Shenan Stanley wrote:
>>> William B. Lurie wrote:
>>>> This is a new thread. See old stuff for history.
>>>
>>> Does everyone realize that at this point in the troubleshooting
>>> procedure - if time is money (and for many people it is) and even if
>>> it is not a *lot* of money (let's go with $1.00 / hour - U.S.) that
>>> this problem has gone on long enough now to afford a replacement
>>> computer with likely more CPU power, more hard drive space and a
>>> better video device without all the current trouble by now, eh?
>>>
>>> I mean - really - this computer could be defective.
>>>
>>> Just throwing that out there... *grin*
>>>
>> You are 99-44/100 percent right, but the other 0.56% is the
>> spirit of the scientist who wants to know *why*. I would be
>> willing to drop the issue any time John wants to throw in
>> the towel, and I will thank him a thousand-fold for his
>> invaluable assistance, perseverance, and resourcefulness.
>>
>> Meanwhile, we are quite close to the solution, as my posting later
>> this morning will indicate. Getting the Network thing and also
>> the ever-intrusive Norton background scans out of the way has
>> given me, overnight, two runs which ran two hours before going
>> into hibernation.
>
> To make the successful runs on my Clone system, John, I did
> not do Clean Boot, but I Disabled the Networks Connection from Control
> Panel, and turned off all Norton Anti Virus (disconnecting from
> the line, of course). Oh, I unplugged printer and camera but I
> don't expect that is pertinent. I'll see to the Norton part, but
> what's your take on the 'Networks Connection' thing? Isn't that
> vital to communicating with he web?

Yes, the web is a network and all your network traffic flows through
your network adapter, without it you will not be able to get on the web.

So what happens if you keep all your Norton stuff turned off and enable
the adapter?

Also make sure that power saving is not enabled on the adapter. Right
click on the network adapter and select "Properties" then click on the
"Configure" button for the adapter then click on the "Power Management"
tab and make sure that the "Allow the computer to turn off this device
to save power" is *not* selected.

John

John John - MVP wrote:
> William B. Lurie wrote:
>> William B. Lurie wrote:
>>> Shenan Stanley wrote:
>>>> William B. Lurie wrote:
>>>>> This is a new thread. See old stuff for history.
>>>>
>>>> Does everyone realize that at this point in the troubleshooting
>>>> procedure - if time is money (and for many people it is) and even if
>>>> it is not a *lot* of money (let's go with $1.00 / hour - U.S.) that
>>>> this problem has gone on long enough now to afford a replacement
>>>> computer with likely more CPU power, more hard drive space and a
>>>> better video device without all the current trouble by now, eh?
>>>>
>>>> I mean - really - this computer could be defective.
>>>>
>>>> Just throwing that out there... *grin*
>>>>
>>> You are 99-44/100 percent right, but the other 0.56% is the
>>> spirit of the scientist who wants to know *why*. I would be
>>> willing to drop the issue any time John wants to throw in
>>> the towel, and I will thank him a thousand-fold for his
>>> invaluable assistance, perseverance, and resourcefulness.
>>>
>>> Meanwhile, we are quite close to the solution, as my posting later
>>> this morning will indicate. Getting the Network thing and also
>>> the ever-intrusive Norton background scans out of the way has
>>> given me, overnight, two runs which ran two hours before going
>>> into hibernation.
>>
>> To make the successful runs on my Clone system, John, I did
>> not do Clean Boot, but I Disabled the Networks Connection from Control
>> Panel, and turned off all Norton Anti Virus (disconnecting from
>> the line, of course). Oh, I unplugged printer and camera but I
>> don't expect that is pertinent. I'll see to the Norton part, but
>> what's your take on the 'Networks Connection' thing? Isn't that
>> vital to communicating with he web?
>
> Yes, the web is a network and all your network traffic flows through
> your network adapter, without it you will not be able to get on the web.
>
> So what happens if you keep all your Norton stuff turned off and enable
> the adapter?
>
> Also make sure that power saving is not enabled on the adapter. Right
> click on the network adapter and select "Properties" then click on the
> "Configure" button for the adapter then click on the "Power Management"
> tab and make sure that the "Allow the computer to turn off this device
> to save power" is *not* selected.
>
> John
That will be my next step, this morning, and thank you, John.

You give up too easily.
"Shenan Stanley" <newshelper@gmail.com> wrote in message
news:OJKqWTP3KHA.556@TK2MSFTNGP04.phx.gbl...
> William B. Lurie wrote:
>> This is a new thread. See old stuff for history.
>
> Does everyone realize that at this point in the troubleshooting
> procedure - if time is money (and for many people it is) and even if it is
> not a *lot* of money (let's go with $1.00 / hour - U.S.) that this problem
> has gone on long enough now to afford a replacement computer with likely
> more CPU power, more hard drive space and a better video device without
> all the current trouble by now, eh?
>
> I mean - really - this computer could be defective.
>
> Just throwing that out there... *grin*
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>

This last set of comments comes at a funny time, namely, I believe
we have just solved the problem. First on my clone, and now on my
Master drive, I got the system to hibernate at two hours by making
what I believe are *only* two changes.

First, Network Connections.....>>Power Options....
Do *not* allow it to turnoff device.........

Second, in Norton Anti-Virus, set it for 'Silent Mode'
(whatever that means) and set its 'Idle Time Scan' for the
maximum it allows, namely six hours.

It has hibernated at 2 hours twice so far, and I intend to give it
more opportunities........

But that Norton 'feature' to me is something I'm going to complain
to them about. If I don't want it to scan except when I want it to,
I should have that privilege! They really do too many things that
way...you know, the 'Big Brother knows best' syndrome.

Unknown wrote:
> You give up too easily.
> "Shenan Stanley" <newshelper@gmail.com> wrote in message
> news:OJKqWTP3KHA.556@TK2MSFTNGP04.phx.gbl...
>> William B. Lurie wrote:
>>> This is a new thread. See old stuff for history.
>> Does everyone realize that at this point in the troubleshooting
>> procedure - if time is money (and for many people it is) and even if it is
>> not a *lot* of money (let's go with $1.00 / hour - U.S.) that this problem
>> has gone on long enough now to afford a replacement computer with likely
>> more CPU power, more hard drive space and a better video device without
>> all the current trouble by now, eh?
>>
>> I mean - really - this computer could be defective.
>>
>> Just throwing that out there... *grin*
>>
>> --
>> Shenan Stanley
>> MS-MVP
>> --
>> How To Ask Questions The Smart Way
>> http://www.catb.org/~esr/faqs/smart-questions.html
>>
>
>

Probably only one? Norton Idle Time Scan. Guessed it was Norton from the
beginning.
Great you found it.
"William B. Lurie" <billurie@nospam.net> wrote in message
news:%23BKLtpb3KHA.4964@TK2MSFTNGP05.phx.gbl...
> This last set of comments comes at a funny time, namely, I believe
> we have just solved the problem. First on my clone, and now on my
> Master drive, I got the system to hibernate at two hours by making
> what I believe are *only* two changes.
>
> First, Network Connections.....>>Power Options....
> Do *not* allow it to turnoff device.........
>
> Second, in Norton Anti-Virus, set it for 'Silent Mode'
> (whatever that means) and set its 'Idle Time Scan' for the
> maximum it allows, namely six hours.
>
> It has hibernated at 2 hours twice so far, and I intend to give it
> more opportunities........
>
> But that Norton 'feature' to me is something I'm going to complain
> to them about. If I don't want it to scan except when I want it to,
> I should have that privilege! They really do too many things that
> way...you know, the 'Big Brother knows best' syndrome.
>
> Unknown wrote:
>> You give up too easily.
>> "Shenan Stanley" <newshelper@gmail.com> wrote in message
>> news:OJKqWTP3KHA.556@TK2MSFTNGP04.phx.gbl...
>>> William B. Lurie wrote:
>>>> This is a new thread. See old stuff for history.
>>> Does everyone realize that at this point in the troubleshooting
>>> procedure - if time is money (and for many people it is) and even if it
>>> is not a *lot* of money (let's go with $1.00 / hour - U.S.) that this
>>> problem has gone on long enough now to afford a replacement computer
>>> with likely more CPU power, more hard drive space and a better video
>>> device without all the current trouble by now, eh?
>>>
>>> I mean - really - this computer could be defective.
>>>
>>> Just throwing that out there... *grin*
>>>
>>> --
>>> Shenan Stanley
>>> MS-MVP
>>> --
>>> How To Ask Questions The Smart Way
>>> http://www.catb.org/~esr/faqs/smart-questions.html
>>>
>>
>>
>

John John - MVP wrote:

> Yes, the web is a network and all your network traffic flows through
> your network adapter, without it you will not be able to get on the web.
>
> So what happens if you keep all your Norton stuff turned off and enable
> the adapter?
>
> Also make sure that power saving is not enabled on the adapter. Right
> click on the network adapter and select "Properties" then click on the
> "Configure" button for the adapter then click on the "Power Management"
> tab and make sure that the "Allow the computer to turn off this device
> to save power" is *not* selected.
>
> John

In retrospect on this project, John, now that it's just about finished,
I hope we all learned something from it, including people who have
been watching silently.

I've thought about your early comments that there are a few dozen
'services' that are active but will never be used, and wondered if
it would speed things up to disable them. I could start with one
of the lists you created, but I'm more inclined to say we now have
it where it ain't broke, so I shouldn't fix it.

And just once more: Thank you for all your efforts.

Bill

a clean boot should work

PSQLWGE (your services) is Window Workgroup Engine. That and
'lanmanworkstation' indicate to me that other computers have access to your
computer.