se serve a qlc...
There is three things you can do to get this fixed, you will need the winxp cd for all of em, here they are:
1) Go to the controle panel, add remove programs, windows components, and uncheck Internet Explorer, then press OK. Restart once its gone, and recheck IE, it will then install again.
2) Go to the start menu, open run and put this in exactly:
rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 %windir%\Inf\ie.inf
If you dont have run, right click the start button, go to properties, click customize, check display run.
Failing those 2 steps, you can actually check and see what file is wrong with IE or causing the problem, and replace it from the XP CD, here is how.
1) On the XP cd, close the auto run, open the cd and browse to the cdrom:\SUPPORT\TOOLS
run setup.exe . Now, browse to the directory on your HD where you installed the tools to.
Find this file " depends.exe " and double click it to run it.
Now, in the dependency walker, go to file, open, and browse to /Program Files/Internet Eplorer/and double click iexplore.exe
This opens up the actual executable and checks the file structure for all the files that are reqired for IE to work (you can do this with ANY program, and create no cd hacks for your software,if you dont like putting in the cd each time).
You should be looking at a tree of files, on the right there wont be much till you click on something, and at the bottom is all the module's in use.
What we are looking for is ANYTHING that is hilighted in pink/red. We then need to find out where that file is on your computer, and replace it.
The file will NOT have the exact same name on the windows CD. They will usually be in the i386 directory, and if for example its mpr.dll that is red/pink then on the windows cd it will be mpr.dl_ -- NOTE THE UNDERSCORE.
for most files, they have an underscore instead of the last character in the file extension. If the file you need to replace is in the system32 folder, or any other active windows folder, boot into safe mode, and put the new folder into system32/dllcache/ and the system will take it from the cache on reboot. This WILL fix your problem if done properly. If it is not done properly, you have the potential to fry your current windows installation and you will have to reformat and re-install everything.