Its the latest service packs to XP, they have disabled popups.
....
have you tried going to add/remove in control panel and attempting to
remove IE, you'll get the option to repair it.
Steve,
Is this is a feature of XPsp2 <eg>? AFAIK IE Repair is only available to
XP users who had IE6sp1 *before* they installed XPsp1. In that case once
XPsp1 is installed setupwbv.dll would remain but the the normal Add/Remove
UI for IE6sp1 was removed. Hence, unless IE Repair is a new feature with
XPsp2 the most that I would expect him to be able to do on this tack is
Run... (e.g. press Win-R and enter
rundll32 setupwbv.dll,IE6Maintenance
Alternatively, I have been suggesting to XP users that they could simulate
the IE Repair that W2K users can do by making a list of all the references
to DllInstall and DllRegisterServer in FixIE.inf
For example, here is the list that W2K use of that file would imply:
(excerpt from previous post)
<excerpt>
regsvr32 /i browseui.dll
regsvr32 /i shdocvw.dll
regsvr32 /i mshtml.dll
regsvr32 mshtmled.dll
regsvr32 actxprxy.dll
regsvr32 /i urlmon.dll
What that represents is the set of re-registrations which
FixIE.inf indicates would be done for Base.W2K.AddReg
N.B. that neither mshtmled.dll nor actxprxy.dll have an entry point
called DllInstall and hence the /i option can not be used for them.
Neither msjava.dll nor shell32.dll are referred to by FixIE.inf
but those are two other modules which are often suggested to XP users
as needing re-registration for repairing in various circumstances.
Note that such re-registrations are normally done by an IE Repair
during a boot while nothing is running so at the very least I think
that it would be best to ensure that iexplore.exe is not active in your
task list. (Close all visible IE windows and then check that the
iexplore.exe is not in the list of Processes in Task Manager.
Ctrl-Shift-Esc,Ctrl-Tab,i,i,...)
</excerpt>
Related to this, recently some OE users have discovered
that there is a need to re-register inetcomm.dll. (We're not sure
why but there is some speculation that use of a Norton product
may be a common factor.)
I suspect that we could create a much more comprehensive FixIE.cmd
(or perhaps even a new FixIE.inf) to substitute for this relatively limited
set of .dll re-registrations. I wish Microsoft would drop the pretense
that WFP is a panacea that means IE Repair is no longer necessary.
Robert Aldwinckle
