You are so sweet to help. Message number is 10005. DCOM may be
enabled because I have a crossover cable LAN (which isn't working, but
that's because of an update six months ago that killed it). It's a
weird kind of network setup -- NetBios over TCP? Is that what the
computer guy said?
I haven't installed any drivers for months. I don't host or create
websites or webpages.
What helped to reduce the problem was chkdsk /f. Reduced the number
of explorer auto-restarts to about 5 per hour.
I practice safe hex -- keep virus, adaware, pest patrol, and popup
stopper up to date and run them often. I've also run an online virus
scan. All appears okay.
I do get into the registry from time to time. I have a nagging
thought that there may be a registry error that is causing the shell
autorestart. Would that make any sense, or am I dreaming?
I don't have any restore points left from before the problem started.
Are there other MVP's that you could run this by? I hate to have you
spending hours and hours on it yourself.
I'm off to class--first day of summer school. I'll be the oldest one
there.
<*((((><{
(e-mail address removed)
On Sun, 23 May 2004 01:57:02 +0100, "John Barnett MVP"
|This looks like a task and a half.
|
|Well so far the only instances of the DCOM 1005 error message i have come
|across relates to Microsoft Operations Manager (which i doubt you have
|installed ot have any need for) and also IIS (Internet Information Services)
|The IIS isn't enabled by default but you would need it if you used say
|Microsoft frontpage or created your won website.
|
|DCOM itself (Distributed Component Object Model) basically enables software
|to communicate directly over a network. Now as you are using XP home and you
|haven't mention that you run a network i can't see DCOM being enabled being
|of any use.
|
|The problem with a lot of PC errors is, basically, that the solution is a
|trial and error affair. To be honest i have spent 4 or 5 hours searching the
|Microsoft Knowledge base and, other than the two problems outlined about, i
|can find absolutley no reference to your particular problem.
|
|However as DCOM keeps forming part of the equation perhaps we might try
|disabling it to see if a) we get an improvement or b) we solve the problem.
|
|I think i read somwhere in one of your posts that you had tried a Repair and
|got some joy out of it but it didn't solve the problem. I could suggest that
|you reformat your drive/partition and reinstall XP, but i won't. Well not
|yet.
|
|In your post to me you said it the problem started four days ago. Now i
|suppose you checked for virus activity? I also presume you checked for
|spyware too. Did you maske any alterations to your system prior to the
|problem occuring? I have asked if you installed any software/hardware or
|drivers but you didn't say whether you had or not and, if so, what you
|actually installed or altered. Have you tried a system restore to a few days
|prior to the problem starting? It might be worth a try.
|
|I notice also from a reply to one of your posts that someone had already
|mention Gibson research (grc.com) To save complicating matters, especially
|by editing the registry. I suggest you go to
www.grc.com/dcom and download
|the DCOMbobulator software. It is only about 250k in size. Run this
|application and Disable DCOM. As you can see from the grc website it is just
|as easy to re-enable it again afterwards if things don't improve.
|
|If disabling DCOM doesn't improve matters then try a system restore to a
|date prior to when your problem started and see if that helps. Obviously, if
|you have installed software/drivers etc during this time these will be lost
|when you do the system restore.
|
|Give these suggestions a try first and, in the meantime, as my time allows,
|i'll keep searching to see if i can come up with some answers.
