timetc1 said:
Correction --
"An exception occured while trying to run "C:\windows\system32\Shell32.dll,
Contro_RunDLL "C:\Windows\System32\inetcpl.cpl",
Q: What happens if you try to Run... (e.g. press Win-R and enter
control inetcpl.cpl
(That would eliminate the Control Panel itself from your symptom
description.)
If you get a similar symptom or are not able to use the Internet Options
dialog you could try to just Run...
regsvr32 /n /i inetcpl.cpl
Note to lurkers of other OS: Non-XP OS allow an IE Repair (ref KB194177)
which includes the equivalent of that re-registration in its FixIE.inf file.
For NT5x: an IE Repair includes many other re-registrations as well,
though not one for shell32.dll, even for W2K where it would be valid.
See the list in KB831429 which includes that one. (Ignore msjava.dll
if you don't have it.)
XPsp2 has a weaker substitute for IE Repair which needs to be modified
to be most effective. Here's an excerpt from a previous reply which
explains that
<excerpt>
Actually there was an attempt to provide a substitute for IE Repair
in XPsp2 by (e.g.) Run...
iexplore.exe /rereg
but some errors were made in the ieuinit.inf file that is used by it.
If you would like to try it there are four lines which need to be modified.
Specifically I found the following errors on mine (mostly to do with whether
there is a DllRegisterServer entry point or just a DllInstall entry point
in each of the following modules:
%11%\comctl32.dll,NI
%11%\digest.dll,NI
%11%\inetcpl.cpl,NI (I deleted the first and left this.)
;%11%\msapsspc.dll (I actually deleted this line.)
To be clear the above lines are my corrections. In order to make them
in your copy simply open %windir%\System32\ieuinit.inf in Notepad,
find each module name and make the appropriate change.
To summarize I appended ,NI to the lines which contain comctl32 and digest;
I deleted the line which contained inetcpl.cpl without the switches
and I deleted the line which contained msapsspc. If you prefer you could convert
both deletions to comments by inserting a semicolon (
in column 1 of those two lines
(as I was forced to do for my last example.)
Making those four changes allowed the whole section to execute cleanly.
BTW in view of the fact that the KB194177 repair is always
done during a boot when no other interference is possible I think it
should be advisable to stop as many other applications (if not services)
as well first but the command does nothing to encourage such an ideal.
Perhaps doing it after a safe mode boot would be a simple, effective
compromise.
HTH
Robert Aldwinckle
---
