....
Has been like this for a long time. And I'm getting sick of it.
It doesn't help turing off all security either (no prompting).
Instead of "no prompting" have you tried maximal prompting?
E.g. using Security tab, Custom Level... Security Settings dialog
change all settings which are currently Enable (green dot)
to Prompt. E.g. essentially type P, look for green dot beside Enable
and press Spacebar; repeat to end of options. Do that on both
systems, the one which works properly and the one which is failing.
Open the problem page on both systems, taking note of the number
and sequence of prompts. Compare results. If necessary,
you can do exactly the same thing with the Advanced Privacy Settings
dialog to ensure you are getting prompts for accepting Cookies too.
Even better if you have a script debugger would be tracing the scripts
as they are encountered. Unfortunately I haven't found a way just
to *record* the traced execution so that analysis can get a bit tedious.
Seems like it doesn't even try downloading any ActivX'es.
And I can't find where this setting is (have tried to compare
registry with the laptop where ActiveX still can be downloaded).
Reminds me of trying to debug why I can't use the the Windows Update
Catalog--keep getting Administrators Only symptom and there is no
attempt as far as I can see to even check properly.
However, "compare registry" may not be the most effective way to do
such a comparison. What I would do is use RegMon and FileMon
and compare their traces on the two cases. To try to make the analysis
manageable you could start by using some fairly restrictive filtering,
e.g perhaps just checking to see which .dlls are being referenced.
Another thing to be aware of is that FileMon may only show you accesses
of the .dlls being loaded, so to be sure that you are capturing all such accesses
you probably will want to start the traces before any iexplore.exe is running.
If you have a specific scenario to trace others could try tracing it too
and see what common clues they come up with for it. E.g. if your
list of .dlls being loaded is different from their list that could be used
as a signal to see if that .dll is registerable and if so try re-registering it.
Etc.
HTH
Robert Aldwinckle
---