When the news got out that Windows 7 would get a “Classic”-like virtual environment for running Windows XP applications that would otherwise not run on Windows 7, we hoped it would mark the beginning of Microsoft moving backwards compatibility into a VM. This would then allow them to cut major cruft out of the operating system. However, with more and more information trickling out about Windows XP Mode, it becomes more and more clear this new feature has little to do with cutting backwards compatibility (as I already said when we covered this subject during our latest podcast). Update: Paul Thurrot states you can install other operating systems into Windows XP Mode’s virtual machine as well. This is a great selling point for us enthusiasts.
Jammer, maar helaas
Microsoft has published several blog entries and press releases about Windows XP Mode, and in each and every one of them, the company is accentuating that Windows XP Mode is targeted towards small businesses, to help them move from Windows XP to Windows 7. For larger companies, Microsoft advocates Enterprise Desktop Virtualization 2.0 (MED-V). There is no indication that XPM is a first step in a push towards moving all backwards compatibility in Windows towards a VM.
Of course, sharp folk had already realised this by looking at who would get Windows XP Mode for free: users of Windows 7 Professional and up. If XPM had really been the future of Windows’ backwards compatibility across the board, everyone would be able to download it.
So, it seems that our initial enthusiasm has been a bit, well, premature. I guess all the excitement about XPM on OSNews and other parts of the web illustrates all the more the longing there is among Windows users towards a world where backwards compatibility does not hold back Windows’ development. It would be great if Microsoft made a clear statement about this subject.
How XPM works
A lot of information on how Windows XP Mode works has also made it to the web. For instance, Rafael Rivera explained how the application publishing (the “coherence” or “unity” technology of XPM) works. It makes use of some key RDP technologies: Remote Applications and Application Publishing. The basic gist of the story is that these technologies normally allow you to install applications on client machines (complete with file type associations and shortcuts), but have them run on a server machine in the network.
XPM allows you to do the same, but then with the virtual XP machine acting as the server, and the Windows 7 host as the client. Some additional services within the XP virtual machine monitor the “All users” Start menu, and pushes those applications down to the host Windows 7 machine.
Currently, XPM does hit a limitation thanks to Terminal Server licensing. “Only one user or channel can be open at any given time,” Rivera explains, “This means you cannot execute Internet Explorer 6 while running maintenance tasks within the virtual machine, like installing updates from Windows Update.” There are tricks to get around this one, though.
It sort of sounds like Microsoft invented a swiss army knife, but only wanted people to use the tweezers. Now that the public has discovered all of the other uses, they’re continuing to emphasize the tweezer’s usefullness. Worse, with the concurrent user cap, its like they’re soldering the rest of the tools into the body to prevent their use.
If only the decision makers would realize they built a tool that could save the company’s life! With the eventual arrival of Midori ( a non win32 managed code Kernel), they need a way of maintaining backwards compatibility while encouraging adoption & development in the new api & methodology. This would be perfect for that.
Sort of reminds me of Intel’s posturing when it was revealed that they were working on a 64 bit x86 chip that they said would have limited usefulness, but still claiming that Itanium was the future for everyone.
The Rafael Rivera link is pointing to a page on HP’s online store.