I should have also asked what maintenance level.
If XPsp2 you could do
iexplore /rereg
I would treat that one with the same care that I was suggesting
you give regsvr32 /i mshtml.dll since it is even closer to an
IE Repair (without the boot).
If you installed IE6sp1 before installing XPsp1
you would have setupwbv.dll and be able to do
a real IE repair with (adaptation of KB194177):
rundll32 setupwbv.dll,IE6Maintenance
Is it possible that the program I installed to mess
the type associations?
Yes. That's what I was assuming.
I noticed it updated some system files and required me to reboot.
Depending on how it was packaged that could be bad news.
However, provided the "system files" were protected by XP's WFP
(in %windir%\System32\dllcache) they would soon be replaced.
I don't know if they would be re-registered then though.
I also wonder if some kind of virus or malicious code could be
the cause of this problem
Possibly but I think that the package you installed is the more likely
culprit. If the repair works you can test by observing more closely
what your package does during its install.
One simple check you could do as a check on your associations
for before and after comparison is this command pipeline:
ftype | find /i "iexplore"
what exactly does IE Repair?
A whole bunch of regsvr32 commands during a boot while nothing
else is running. If you download IE6 you could extract fixie.inf
(or otherwise acquire that file). It is a mixture of the commands which
it would do for each OS but essentially any file listed with a DllRegisterServer
entry would be given the equivalent of a regsvr32 command
and any file listed with a DllInstall entry would be given the equivalent
of a regsvr32 /i command.
I suppose this (re)installs the IE core, doesn't it?
Were you paying attention? <g>
mshtml.dll is the rendering engine for IE so yes it is a core IE module
but regsvr32 /i just executes the DllInstall entry point which causes
a bunch of registry entries to be checked or rewritten.
With XPsp2's new /rereg switch XP's lack of an IE Repair may not
be as much of an issue any more. For XP users who are not yet at
that level I have been suggesting that they try the regsvr32 commands
listed in KB831429. (I'm still unclear that XP's sfc command does
anything to the registry with modules which it does not replace. That's
why I suggest that modification of the KB article's actual instructions.)
Robert
---