Something is interfacing, calling or activating DCOM. If you cripple DCOM
will you get a logging of an error?
DCOM is not needed.
"William B. Lurie" wrote in message
...
Unknown wrote:
How does your NORTON program get updated? Is it automatic?

No, I *never* allow any software supplier to do automatic
stuff. Norton has automatic live update, which I keep
turned off. I do manual live update periodically. That goes especially
for Windows as well.

John, I'd be willing to look at that what's-running-monitor,
how do I grab it?

"William B. Lurie" wrote in message
...

John, the next test was inconclusive because I may not have
waited quite 2 hours, but it is already beginning to look as
though the length of time to test with DCOM plus each succeeding
service, and then the next one plus each of the rest, will end
some time in the next decade, not this one. I'll pursue this tack
a bit further, but it seems to me that *somebody*, maybe another
one of the excellent MVPs, might know which 'service' has a one
hour time clock built into it.
I've snipped everything out because I think we're at a decision-
making point. I just don't think that the try-each-service approach
is going to be practical. Just too many services, too many possible
combinations, too little known about each, too long to make just one
test. I agree it's logical and sensible and proper scientific
technique, but it's like counting the grains of sand on the beach.

Getting back to the 1 hour/2 hour problem, I feel we have eliminated
any running application program as a source, by just not loading them.
If they don't load, they don't execute, and if they don't execute,
they can't influence hibernation.

So what *is* running? The system and its big-brother-given 'services'.
Rereading my last comment above, I hope I didn't offend anybody, but we
have to realize how enormously complex the XP system is, and it's too
much to expect any MVP to be intimately familiar with the inner workings
of all of its services. That's approaching the problem from the bottom
up. The question, down from the top, is, can we pick enough MVPs' brains
hard enough to find out which of the services is capable of preventing
the supposedly idle system from hibernating after 2 hours, but not after
only 1 hour.