As a result, almost every OEM Win 7 system you will find shipped with Pro. Microsoft pricing to OEM's for Win 7 Home was virtually idebntical to Win 7 Pro, so almost all OEM's standardised on Pro. On Windwos 7, stick to using Virtual-PC to run your own XP image. Whilst it might look like you are getting 'XP for free', it defaults to 512Mb RAM and the Virtual machine file CAN'T BE MIGRATED to Win10 Hyper-V. The Windows 7 'XP-Mode' from MS is not recommended. Whilst multiple virtualisation software choices exists, the main (free) ones are: Microsoft (Virtual PC(win7) and Hyper-V(win8+)), VMware (VMware Player) and Oracle (VirtualBox) So 'all' you need to do is 'pack up' your XP styetem into the appropriate 'virtual disk' format file and load it into you chosen virtualisation software choice.įor Microsoft Virtual PC or Hyper-V you need VHD or VHDX, for VMWare it's VMDK (Virtual Machine Disk) and for Oracle VirtualBox it's VDI (Virtual Disk Image), although VirtualBox will also accept VDI, VHD and VMDK (which is good when the 'virtual disk' generators run at no more than 50Gb/hr) vhd (virtual drive) file and run it on a 64bit Windows 7 Pro (or later) 'Virtual Machine'.

Fortunately, it is still possible to pack-up your system into a. This means it's no longer possible to install (or run) Windows XP on new hardware. However most new machines made by Dell etc. The most modern motherboard comes equipped with 'UEFI Class 3' BIOS that will only support GPD disk partitions (which are unusable by XP) and only 64bit Operating Systems (they have chip sets for which only 64bit drivers exists = USB-3 being the most common device for there are no XP drivers) As of 2016 it was still possible to find motherboards with a BIOS with a SATA option that could be set to 'legacy' mode (aka 'ATA' or 'IDE' mode). Virtual XP XP is dead, but it's ghost can live on !

Diskvhd oracle