posted on July 16, 2009 by Bryant Zadegan
Rafael Rivera, as he usually does, put a massive amount of research into discovering workarounds for downloading Internet Explorer on Windows 7 E. He found and posted a rather ingenious workaround for users stuck in Europe with Windows 7 E(U-gimped). The trick, which you can read over at Within Windows, definitely succeeds in winning the “clever” label applied by Rafael, but what Rafael didn’t mention is that Windows 7 (or at least Windows Media Player) still has the Trident rendering engine somewhere within the stripped OS. This means a number of things:
- Bad: Upgrading from Windows Vista to Windows 7 E shouldn’t be a problem whatsoever, despite what Microsoft may say. This, unfortunately, doesn’t do much for Microsoft’s image in Europe (unless Steven can come and tell us specifically why Windows Vista can’t be upgraded to Windows 7 E)
- Good: Windows really does rely on Trident for at least a few non-browsing-related functions, which makes sense given how useful HTML can be for creating a UI. It also gives a sense of validity to Microsoft’s claims with regards to the EU.
- Bad (for browser peddlers, Microsoft, and the user. Good for the EU): The EU, in its limited comprehension of how a browser works, might now use this as “evidence” of Microsoft being deceitful.
- Good: Your shiny new better-than-Snow-Leopard OS won’t be as gimped as you originally thought.
This also means that any applications which use Trident for rendering any HTML to present an interface to the user will still work without needing a browser, which means that application developers should still be happy.
You can catch Rafael’s guide here. While you’re at it, if you’re a native of an EU-governed state, please email them a few one-fingered salutes on behalf of the rest of the world.
Update: Paul would like to note that Microsoft has been “very upfront” about Windows 7 E having the Trident rendering engine. The fact is, Microsoft hasn’t really done a good job at pushing this note around, and given Microsoft’s other communication issues (again, noted by Paul), I’m inclined to say that the existence of Trident actually is news.
In fact, Microsoft also posted about it on their legal blog… in typical legalese. The official statement is:
Most importantly, the E versions of Windows 7 will continue to provide all of the underlying platform functionality of the operating system—applications designed for Windows will run just as well on an E version as on other versions of Windows 7.
To those of us who assume things in the most unrealistically general sense, “underlying platform functionality” includes Trident, but this by no means makes it obvious that Trident will still be in Windows 7 E, thereby proving Paul’s previous point about communication being a problem.
posted on May 8, 2009 by Bryant Zadegan
Stan Schroeder over at Mashable decided to argue in favor of Mozilla and Opera’s complaints reegarding Internet Explorer 8 becoming the default browser when the user upgrades to Windows 7 RC via Express settings. It took me a few reads to realize he was serious, so I’ll spare you the hassle of reading through his post and summarize it for you:
wwwaaaaaaaaahhhhhhhhh!
Let’s look at a logic chain here:
- User installs third party browser and makes it the default on Windows Vista.
- User upgrades to Windows 7 down the road, chooses express upgrade options.
- IE8 replaces the Vista default as the new default browser.
So, Mozilla and Opera are arguing that a new Microsoft browser which was installed onto Microsoft’s OS shouldn’t become default when the user just wants to install Windows and be done with it? Think about it this way: A user chooses to go with express configuration settings because the user doesn’t want to deal with setting anything up on his/her own. The user, therefore, consents to using Microsoft’s default settings, and Microsoft’s defaults include setting up Internet Explorer 8 as the default browser. If the user really wanted to customize any settings, the user would go ahead and do so without any problems. Keep in mind that installing Windows 7 also means, by extension, installing Internet Explorer 8.
There is no problem here; all I see is whining, and it’s getting ridiculous. Mozilla and Opera should work on creating a compelling product, and while I agree that Opera is better than Internet Explorer 8 in many ways including memory management (Mozilla’s RAM issues prevent me from considering it for anything), the point is that Windows belongs to Microsoft, and thus, Microsoft can do whatever they want with it. These “dominant market position” arguments don’t fly because Mozilla and Opera are both using the argument selectively; you don’t see them making nearly as much noise about Apple and the iPhone/iPod touch/Mac.
posted on March 4, 2009 by Bryant Zadegan
For those of you visiting from the recent Associated Press article, feel free to follow me on Twitter and stick around on the forums as well. In addition, for those of you looking for where this article falls on the grand timeline of things (most people miss the date published at the bottom of the article), this post was posted on the 4th of March at 12:03 AM Eastern Time, coinciding with Chris’s post just over one hour prior.
Thanks for stopping by, and welcome to AeroXperience. ~Bryant
Thanks exclusively and entirely to efforts between Chris Holmes and me, we discovered that Internet Explorer 8 can be removed from at least Windows 7 build 7048, which is a good sign for regulatory overlords in the EU and in the States. Given that this change doesn’t exist in Beta 1, the odds that this change will persist through to RC are quite high. Don’t believe this can be done? Well, how about a Windows Features dialog below for proof?

There is a catch: For now, this only seems to wipe the actual executable running Internet Explorer 8 (iexplore.exe), but given that many of the most vocal proponents of choice were just looking for an option to functionally remove IE8, this might’ve been the only way to do it without killing the rest of Windows. In addition, this actually takes two reboots and a configuration step to complete, so there’s definitely something going on behind the scenes (likely a remapping of where IE-related functions can be found for other elements in Windows so that Windows doesn’t complain about IE’s nonexistence).
You can catch the steps, as well as final screenshots of the somewhat-obliterated product, after the break.
Read More »