Thursday, July 12, 2007

Running multiple versions of IE on Vista

I recently began using windows Vista which comes pre loaded with Internet Explorer 7. As most web developers know, to produce a quality site that works on all current browsers you need to test on multiple versions of Internet Explorer. On XP you could use standalone versions of of older IE versions (including IE6 and down) along side of IE7. However, the standalone installations of IE do not work on Vista. I did find a solution but it is a bit more involved.

First off, if you are running XP and want the easy to install standalone versions of IE, check them out at evolt.

A solution:

The team at IE Blog have generously provided a hard disk image of a windows XP installation (with IE 6) which you can use.

  1. First download and install Microsoft virtual PC (its free)
  2. Next, head over to IEBlog and get the image here. The file is a whopping 450mb, so put your feet up and wait. If your on dial-up, give up.
  3. Run virtual PC and set up a new machine (the process is pretty self explanatory). Use the XP image you just downloaded.
  4. Run the system, you now have access to IE 6

Thats IE6 out of the way, what about the rest?

  • IE7 - Your on vista, so you have it!
  • IE6 - On your virtual PC
  • IE5/IE5.5 - Copy the standalone version (found at evolt) to your virtual PC (drag and drop, easy!)
  • Fix conditional comments on the virtual machine, by going start > run and typing regedit. Find HKLMSOFTWAREMicrosoftInternet ExplorerVersion Vector and rename the ‘IE’ key to ‘zIE’. Conditional comments will now function in the standalone versions.

Like I said, not the easiest, but it works!

~Billy Flaherty
Website Developer
www.billyswebdesign.com

Posted by Billy at 22:20:55
Comments

7 Responses to “Running multiple versions of IE on Vista”

  1. Kuba says:

    I get less then .5% of visitors using IE older than 6. But don’t forget Firefox 1.5, 2, Safari Tiger (2.04), Safari Panther (1.3.2).
    And, if you feel ambitious, Firefox 1, Safari 3 (win & mac), Mozilla, Opera, Kamino, and the Googlebot.
    That’s enough to make me want to throw the computer out the window. Then smash it. Or see will it blend. And then throw it out the window again.

  2. Billy says:

    Yeah, I really only test IE6 and up, Fx 1.5 and up, safari 3 for win & mac and i figure my bases are pretty much covered. I never test IE5 anymore (because I know it almost never works right).

  3. Anonymous says:

    Thanx, just what i needed

  4. Anonymous says:

    better solution: NEVER EVER install vista in your computer because is a pile of SHITE

  5. Anonymous says:

    Someday the world will be perfect!
    That will be the day when Microsoft and Mozilla finally wake up to real life and start doing their software the way Opera does it.

    Until there, I will only test my sites in Opera, FF and IE7, and that’s more than enough for me…

    If a client of mine wants more compatibility than that my price will go much more higher, and believe me, it really is a higher price!!

    Keep the standards alive! http://opera.com

  6. Anonymous says:

    thanks this is what i was looking for

  7. Anonymous says:

    Good advice on your part, bad advice from Mr #5; maybe he didn’t mean to come across arrogant buy my god… “That’s good enough for me!”

    Outside of my office there’s a world, and in that world people have different circumstances to my own and while I can’t accomodate everyone I can take on board the majority.

    I’d say IE6 is still a prominent browser in key circles, mainly corporate and educational so I wouldn’t be so fast to flip it the bird and simply say “Meh get IE 7 it’s more compatible!” The users in these environments are stuck with that browser and I am sure they would love to upgrade but they can’t… so share the love and spend an extra 30 mins getting your code right for the poor surfers stuck in these environments - who should be working ;0)

    At the end of the day, good code should work for itself with minimal tweaking - IE6 is a bugger but that’s why you can target its flaws using an IE conditional so note where the messups are during your testing and tweak for that browser.

    I’d say the cut off point is IE6 in the main stream and if the client has a specific need for anything lower, then argue your point with statistics (of their client base) or increase your fee; if you educate the client on their expectations they can take it on the chin or take it on the wallet.

Leave a Reply