Run diferent versions of IE on same machine
... without using VMWare etc.
The fact that you can load the 'old' dlls and use a .local file doesn't mean that IE isn't coupled very tightly to the OS it just means that you can use the .local file for its intended purpose... The 'latest' dll which the OS and the tightly coupled browser both need is still used by the OS and the latest version of the browser. The .local file simply allows the old version of the browser to find your local copy of the old version of the dll...
Len Holgate (www.lenholgate.com)
name not available
Why is a browser tightly coupled? One reason may be why should I care if the resource is local or (o what kind of resource it is) not when I want to look at it. Shouldn't I be able to be looking at my filesystem and type a location in the address bar and just see the resource? Modern Linux desktop managers have answered this question with a yes. If anything windows doesn't go far enough. I should be able to see, use, or work with the contents of any known file inside of my browser. I get to do that for the most part with Konqueror and would like to see windows catch up.
The browser coupling is not a case of predatory practices, in my opinion (ducks thrown tomatoes).
> Of course, that begs the question, why does a browser need to be so tightly coupled... <
Fog Creek Home