Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><strong>Update:</strong> Microsoft now provide virtual machine images for various versions of IE that are ready to use on all of the major OS X virtualisation platforms (<a href="https://www.virtualbox.org" rel="nofollow noreferrer">VirtualBox</a>, <a href="http://www.vmware.com/products/fusion/overview.html" rel="nofollow noreferrer">VMWare Fusion</a>, and <a href="http://www.parallels.com/" rel="nofollow noreferrer">Parallels</a>).</p> <p>Download the appropriate image from: <a href="https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/" rel="nofollow noreferrer">https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/</a></p> <hr> <p>On an Intel based Mac you can run Windows within a virtual machine. You will need one virtual machine for each version of IE you want to test against.</p> <p>The instructions below include free and legal virtualisation software and Windows disk images.</p> <ol> <li>Download some virtual machine software. The developer disk images we're going to use are will work with either <a href="http://www.vmware.com/products/fusion/" rel="nofollow noreferrer">VMWare Fusion</a> or <a href="http://www.virtualbox.org/" rel="nofollow noreferrer">Sun Virtual Box</a>. VMWare has more features but costs $80, Virtual Box on the other hand is more basic but is free for most users (see <a href="http://www.virtualbox.org/wiki/Licensing_FAQ" rel="nofollow noreferrer">Virtual Box licensing FAQ</a> for details).</li> <li>Download the IE developer disk images, which are free from Microsoft: <a href="http://www.microsoft.com/downloads/details.aspx?FamilyId=21EABB90-958F-4B64-B5F1-73D0A413C8EF&amp;displaylang=en" rel="nofollow noreferrer">http://www.microsoft.com/downloads/...</a></li> <li>Extract the disk images using <a href="http://www.cabextract.org.uk/" rel="nofollow noreferrer">cabextract</a> which is available from <a href="http://www.macports.org" rel="nofollow noreferrer">MacPorts</a> or as source code (Thanks to <a href="https://stackoverflow.com/users/6262/clinton">Clinton</a>).</li> <li>Download Q.app from <a href="http://www.kju-app.org/" rel="nofollow noreferrer">http://www.kju-app.org/</a> and put it in your /Applications folder (you will need it to convert the disk images into a format VMWare/Virtual Box can use)</li> </ol> <p>At this point, the process depends on which VM software you're using.</p> <p><strong>Virtual Box users</strong></p> <ol> <li><p>Open a Terminal.app on your Mac (you can find it in /Applications/Utilities) and run the following sequence of commands, replacing <em>input.vhd</em> with the name of the VHD file you're starting from and <em>output.vdi</em> with the name you want your final disk image to have:</p> <pre><code>/Applications/Q.app/Contents/MacOS/qemu-img convert -O raw -f vpc "input.vhd" temp.bin VBoxManage convertdd temp.bin "output.vdi" rm temp.bin mv "output.vdi" ~/Library/VirtualBox/VDI/ VBoxManage modifyvdi "output.vdi" compact </code></pre></li> <li>Start Virtual Box and create a new virtual machine</li> <li>Select the new VDI file you've just created as the boot hard disk</li> </ol> <p><strong>VMWare fusion users</strong></p> <ol> <li><p>Open a Terminal.app on your Mac (you can find it in /Applications/Utilities) and run the following commands, replacing <em>input.vhd</em> and <em>output.vmdk</em> with the name of the VHD file you're working on and the name you want your resulting disk image to have:</p> <pre><code>/Applications/Q.app/Contents/MacOS/qemu-img convert -O vmdk -f vpc "input.vhd" "output.vmdk" mv "output.vmdk" ~/Documents/Virtual\ Machines.localized/ </code></pre> <p>This will probably take a while (It takes around 30 minutes per disk image on my 2.4GHz Core 2 Duo MacBook w/ 2Gb RAM).</p></li> <li>Start VMWare Fusion and create a new virtual machine</li> <li>In the advanced disk options select "use and existing disk" and find the VMDK file you just created</li> </ol>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload