Backwards application compatibility in Windows 7 and Linux

By apexwm, 16 September, 2010 13:05

Recently helping with Windows 7 migrations, I've taken a look at "XP Mode" in Windows 7. It was hyped up by everybody as offering backwards compatibility in Windows 7. Much to my surprise when I got it downloaded and installed, it's simply an XP virtual machine running with VirtualPC, with a very generic Windows XP Professional installation inside of it. I think it should really be called "XP VirtualMachine" instead of "XP Mode". XP Mode implies that it's more integrated into Windows 7, which it is not. It's a separate operating system, which requires its own updates, etc. I can see why it's offered, as it offers a completely separate environment because Windows 7 cannot run some older specific applications. Thankfully, "XP Mode" is free.

Windows does have a "compatibility mode" as well (simply right click on any executable, and under the Compatibility tab you can choose what version of Windows to emulate back to Windows 95, but I've had very mixed luck getting it to actually help applications or make any difference.

Migrating to any operating system is always going to be a challenge, it's just a matter of how much work it is. It could be minimal, or a lot, depending on the specific applications needed. There's been a lot of fuss and rumors about migrating from Windows to Linux, too. And I have to mention that there are a lot of similar issues for users migrating from Windows XP to 7, as there are from Windows XP to Linux. Both paths require a learning curve. Both have issues with application compatibility.

What many don't realize, is that Linux has TWO options for application compatiblity. Linux offers Wine, the Windows Emulator. It can run Windows applications, allowing each to use its own DLLs without affecting other applications, as well as run in whichever Windows version you specify for it. The best part of this is that it can all happen to the same filesystem structure (all files are stored in the user's home folder, in a directory called ".wine").

Linux also offers Virtual Machine capability, with a couple different products. The one that is most like "XP Mode" is probably Oracle VirtualBox. There are packages available for the main distributions for easy installation. VirtualBox can run a Windows virtual machine, allowing complete access to hardware and everything else. So if you need 100% XP compatibility, VirtualBox should be your answer. The drawback of this is the same as "XP Mode", where you will have to maintain updates because it's a separate operating system. Wine works well in a lot of cases too, and is much faster and doesn't require booting a VM as applications are opened on the fly, however compatibilty varies. Some applications simply don't work. Others work flawlessly. Check the Wine compatiblity website to check on compatiblity.

Talkback

I completely agree. Wine does work, but it can be hit or miss. When trying to run Windows applications through wine, you can submit your errors that you get and hopefully, if the wine team gets on it, they will issue the fix to get your piece of software working. Now this might not be a perfect solution, but as the author states, VirtualBox is definitely the answer to WinXP to Linux migration. If for some reason the software doesn't work in wine, VirtualBox will run no problem. (This applies to applications, not gaming, as I have never used the virtualbox for playing video games)
Nextwave 16 September, 2010 18:42
Report offensive content Reply

What are the licensing issues related to running XP in a virtual machine? I am asking this question because I honestly don't know. As I understand it, Microsoft (in their infinite generosity) is giving an XP license for free with Windows 7 "XP Mode" - but what versions of Windows 7 actually include this "XP Mode"? On the other side, when you want to run XP, or any other version of Windows as I understand it, in a virtual machine hosted by some other operating system such as Linux/Solaris/whatever, you actually do need to have a licensed copy of Windows to run in that VM, don't you? I also seem to recall some controversy a while back because Microsoft was trying to change the Windows End User License to make it illegal to run it in a VM? I'm not sure, and I don't recall how that came out, so I would like to know the actual current situation.

jw
J.A. Watson 17 September, 2010 13:52
Report offensive content Reply

Jamie : I also recall the fiasco where Microsoft started making a point that running XP in a VM requires a separate license. The last I heard, they made their statement and that was that. An XP retail install still requires activation, so I'm assuming those that have a retail version laying around should be free to install it in a VM of their own, and treat it like a separate PC. However, the tricky part will come in to play if somebody has an old vendor-purchased PC with an OEM XP license on it, in which case they may not be able to transfer the license over to a VM. Which, I am pretty sure will cover most people. I don't know of too many people that bought retail copies of Windows. In fact, an OEM copy of XP from Dell for example, probably won't install in a VM.

XP Mode is a free download and install on Windows 7. I believe that its license is included as part of Windows 7.

Every time I try to figure out Microsoft licensing I get a headache, so I try not to go there too often. I just assume that licenses are required, unless Microsoft states otherwise. Then again, personally I stay away from Microsoft products altogether on my own equipment.
apexwm 17 September, 2010 20:47
Edit Delete Report offensive content Reply