I'm not clear about the advantage of the
Explorer window. The title bar is more
easily customizable? Don't they both just
show the current location (With IE also
showing the OEM string if there's one in
I wonder if you could recreate what you need
with an HTA or some such. I'm not familiar with
the WindowRegistered event and how you're
using it, but I imagine that MS probably made
the change as an update/security measure. IE
and Explorer have not actually been related since
WinME. Only Active Desktop systems have an
IE window in the folder view. (Even on AD systems
the connection between IE and Explorer is as much
marketing as it is actuality.)
As of XP, the Shell object model is really a
compatibility holdover. The design of ShellWindows,
returning Explorer *and* IE instances, never made much
sense, but at least there was actually an IE browser
window buried in Explorer instances when they wrote
that object. And it was possible to access the actual
browser window (though not directly through VBS).
Since XP there's really no connection at all. There's
no IE browser window in folders. (Even though each
Window item is officially an IE object, the IE.document
is just a dummy placeholder that really returns a
MS is just stuck with the IE/Explorer marketing tie-in
from the 90s and need to support old code.
In light of all that it seems to make sense that
MS has "cleaned out" unnecessary IE functionailty
from the Shell object, as much as they can. The Open
method, after all, is supposed to open an Explorer folder
window. There's no reason that one should be able to
jump from there to an IE instance.
...Which is to say that I doubt that functionality is
coming back. I'm still using IE5 and it's a pleasure.
I can do all sorts of things with it. But with later versions
of IE it doesn't seem realistic to use it for anything
> In the good old days of XP and IE 6, it used to be
> the case that Windows Explorer and Internet Explorer
> were pretty much the same thing with only minor
> (though significant) differences.
> In particular, if you wanted an Explorer flavour of IE,
> what you could do was to instantiate a
> Shell.Application object and use its Open property
> to kick off an instance of Windows Explorer.
> By using the WindowRegistered event handler
> function of the Shell.Application->windows object,
> you could trap for this newly created instance of
> Windows Explorer. At this point, you could then do
> Navigate2 "about:blank"
> on said Windows Explorer object and it would turn
> into an IE object. Tada.
> Now what happens under Vista (Business) and IE 8
> is that when you do the Navigate2 "about:blank" hack
> then all of a sudden, instead of Windows Explorer
> turning in IE, A new program (with a differently sized
> window) starts up, which might be Firefox, IE or some
> other browser, and Windows Explorer goes poof.
> Even if I set the default browser to IE 8, I get this
> same effect.
> My question: I don't suppose anyone knows of a
> way to get the XP / IE6 legacy style of behaviour.
> Perhaps there is some obscure flag or such. My
> interest in this is that the title bar of Window explorer
> is much more amenable for the functionality that I
> have in mind, which is that I want to use "Windows
> Explorer/IE" as a canvas to host my own script
> Thanks for any thoughts,
> Csaba Gabor from Vienna