Author Topic: Close-Up: Windows 7 XP Mode : Old Habits Die Hard  (Read 1076 times)

Offline javajolt

  • Administrator
  • Hero Member
  • *****
  • Posts: 36193
  • Gender: Male
  • I Do Windows
    • windows10newsinfo.com
Close-Up: Windows 7 XP Mode : Old Habits Die Hard
« on: July 25, 2009, 08:16:38 AM »
1. Old Habits Die Hard

We delve into the nitty-gritty of Windows 7's XP Mode. Getting it set up can be a bit glitchy, but after that—ah, sweet familiarity.

Most of us remember Windows Vista's debut—along with the hype, anticipation, and incompatibility with legacy applications that went with it. Is it any wonder that at the beginning of this year, two whole years after Vista’s launch, that enterprise adoption of the OS still hovered at the 10% mark—while nearly all other Windows deployments were with XP?



And beyond compatibility, let’s be honest, there just wasn’t much about Vista that could turn heads. The much-lauded Aero interface was a total dud. Who in their right mind would pay $100 to $300 for opaque edges plus a bit of glow and be happy about needing to pay more for beefier graphics hardware in order to support the user interface?

Well, we could spend all day beating the Vista piñata. But at the end of the day, legions of users, corporate and consumer alike, have made do with XP and still have no complaints about doing so. Now we have Windows 7 around the corner, which looks much the same under the hood as its predecessor. If you’re still using XP because of incompatibility problems with Vista, the new boss will be met much like the old boss—with a cold shoulder.

Say what you like about Microsoft, but the company rarely makes the same mistake twice. Microsoft has too much riding on the Windows 7 launch for business users to take another pass. That’s why we now have the arrival of Windows XP Mode (XPM), an add-on for Windows 7 that delivers a virtual Windows XP experience.

2. What You Need

XPM is available in Windows 7 Professional, Enterprise, and Ultimate versions, but not with the Home edition. (This is likely a market positioning move designed to accommodate business users while not-so-subtly forcing the consumer masses to the newer, more secure platform.) You can download the Windows XP Mode beta here. The plug-in is essentially some desktop-sharing support along with a copy of Windows XP SP3 licensed for use on the approved versions of Windows 7. The end result isn’t just that you can run Windows XP applications in a special OS emulator window, like an operating system picture-in-picture. Instead, you can actually run XP apps in regular app windows. While the window style has that XP look rather than Aero, the feel of these two blended platforms is surprisingly seamless.

The only system requirement for XPM is a processor with hardware-based virtualization support. Specifically, XPM requires either AMD's AMD-V or Intel’s VT-x. AMD has integrated AMD-V ever since its launch of the Athlon 64 and Athlon 64 X2. Intel VT-x came with the Pentium 4 662 and 672 models. But be careful. There are plenty of CPUs since these first releases that don’t support virtualization acceleration. For example, all Sempron and most Celeron devices omit virtualization support, and none of Intel’s Atom processors for nettops or netbooks support VT-x. Again, these omissions were more about market segmentation than any technical necessity. Until XPM, there was very little need for virtualization in the PC mainstream.



As of this writing, no major review outlets appear to have posted benchmark tests pitting applications running on XPM against native, non-Windows 7. While this is sure to be remedied soon, the outcome in general would seem predictable: the inner translations necessary to make a virtualized environment will inevitably take a toll on application performance. At heart, a hypervisor is a translator, and just like with human linguists, some translations and translators take longer than others to run. The amount of memory and specific CPU features will be factors. The degree to which the application(s) lean on non-CPU components, such as a network connection or the GPU’s 3D engine, will also be significant because these items are not generally accelerated for virtualization today. Said differently, we expect XPM to be great for those with only one or two 2D apps to support under Windows 7. Performance results will take a marginal hit, but that’s a lot better than not running at all. However, if you want to run 3D games side-by-side under XP and Windows 7, expect to be disappointed. XPM is a Band-Aid, not a multitasking panacea.

3. Four Warnings

In preparing a test system for this article, we encountered a few glitches worth pointing out so your installation won’t be as problematic as ours was.

1. You must use the Windows 7 Release Candidate or a more recent version. Microsoft’s PR agency had supplied us with a build 7000 beta disc in late April, which allegedly was sufficient for our needs. We no longer believe this to be true. The beta version will let you install XPM, but the add-in will not show up in the Start menu.

2. You must install Virtual PC beta for Windows 7 before installing Windows XP Mode. There is one sentence in fine print on the XPM download page that tells you this, and if you miss it, as we originally did, XPM will not work, no matter how many times you install it.



3. When we installed Win7 beta, we did so with a USB flash drive inserted in our Intel DX58SO motherboard, and the installation went fine. Once we downloaded the Windows 7 RC and burned its ISO image to disc, the installation routine kept delivering a message about how “Setup was unable to create a system partition.” Normally, this error strikes users trying to install to RAID volumes. However, when we removed the flash drive and tried installing again, the message and problem vanished.

4. You must have AMD-V or Intel VT enabled in your motherboard’s BIOS. Most boards ship with virtualization support disabled, ostensibly for security reasons. Finding this feature is easier on some boards than on others, and you may have to consult your manual and/or engage in some aggressive Web searching in order to find it. We found one bit of Microsoft documentation saying that Intel TXT must be disabled in the BIOS of Intel platform boards, but we never could find this on our DX58SO.

4. XP Mode Setup

As we mentioned above, begin with configuring your BIOS settings, installing Virtual PC beta for Windows 7, then installing the Windows XP Mode add-on. For Virtual PC, you’ll have to decide between 64-bit and x86 versions (most users will want the latter), and XPM will prompt you make a similar choice between 32- and 64-bit options.







Once you’re into the actual Virtual Windows XP installation and have tended to any unforeseen configuration issues (see prior page), it’s pretty smooth sailing—mostly a lot of clicking Next menu options. Accept the license agreement and specify a password. (No, you can’t leave it blank. Yes, you want Windows to remember your credentials.) Decide if you want to turn on Automatic Updates, then kick back while XP installs—if only the native XP SP3 installation was this smooth.



Eventually, setup will complete and you’ll be dropped into a Virtual Windows XP window featuring the new old desktop, complete with the whole set of annoying XP taskbar pop-ups. Could Microsoft have tweaked this edition just enough to know that you really don’t need a tour of Windows XP when installed as a virtual machine? Apparently not. This is the authentic experience, right down to having to run through the initial file-associations setup in Windows Media Player 9.

5. Using XP Mode

Feel free to expand the XP virtual machine to full screen because if you leave the window too small, you’ll probably run into a pop-up message soon enough informing you that there isn’t enough room to display the application you’re running. From here, you can start loading your applications via Web download, My Computer, or whatever method you please. Our system had no trouble accessing a SATA-based DVD burner or USB flash drive, although it’s noteworthy that while Microsoft FrontPage 2002 installed fine from disc, 3DMark 2003 inexplicably did not. We had to use Task Manager to force the installation to close, which did not cause any additional system problems.



When you install a program under XP, you can access it straight from Windows 7's Start menu under the All Programs > Windows Virtual PC > Virtual Windows XP Applications group. When launched from here, the app pops up right on the Windows 7 desktop without any virtual machine window shell. Note that when given a choice of installing an XP application for one user or all users, you want to pick all users. This is necessary in order to enable execution without the XP environment shell. To illustrate, we installed Firefox under XP, then again under Windows 7, and ran them side-by-side. If not for the difference between XP’s visual style and Aero, you wouldn’t be able to tell them apart. This seamless blending between virtual environment and native Windows 7 is one of XP Mode’s most appealing features.



In practice, though, XP Mode can get a bit confusing. Specifically, when you close the virtual environment, it doesn’t outright shut down. It merely hibernates. So say you open the virtual environment, close it, then try to open a Start menu item from the XP Applications group straight into the Windows 7 desktop. You can’t. Effectively, you’re trying to run two instances of the same environment.


6. XP Mode Alternatives



Maybe you’ve got an older system or one with low-end specs, such as a netbook. You can’t run XPM, and the thought of seeing what the Windows 7 UI does to your hardware makes your stomach lurch. There are a few ways to throttle back Windows 7 so that it has a lower system impact and perhaps looks a bit more familiar.

First off, go to the Start menu and in the Search field enter"SystemPropertiesPerformance." Under the Visual Effects tab, you can fine-tune exactly which bits and pieces of the Aero UI get applied. Each one needs its own bit of graphics processing horsepower, and cumulatively they can take a real toll on humbler GPUs. You can go straight for the jugular by applying Adjust for best performance, which will give you something much more akin to Windows 2000 than XP, or you can tinker. The option with the most dramatic effect is "Use visual styles on windows and buttons."



Another option to help improve performance is to revert back to XP-class system searching, meaning taking Microsoft’s new indexing engine offline. Vista is notorious for excessive drive activity that integrated search indexing causes. If you happen to be gifted with your file and folder organization and don’t need indexing, then go into All Control Panel Items > Performance Information and Tools > Adjust indexing options > Modify button. Make sure that all locations are unchecked, thus giving the indexer nothing to do or maintain.


7. XPM’s Significance

On its surface, XP Mode is not revolutionary. Business users could pick their favorite desktop hypervisor, install Windows XP under it, and be backward compatible even without XP Mode. It might not look as pretty as XPM, but it would work. The biggest appeal for business users may be the licensing situation. With the Enterprise version of Windows, users have typically been allowed to run multiple virtual machines (up to four with Vista) at no additional cost, but with all other versions, the user must pony up for another license. For example, if you want to run Windows XP as a virtual machine within Windows Vista Professional, you’d need to pay for an XP license. Today, Windows XP Professional SP3 sells for about $140. With Windows 7 and XP Mode, that extra license cost disappears.



In a different way, XP Mode sets an interesting precedent. With Intel’s Nehalem microarchitecture, we saw the move from a one-design-fits-all approach, in which chips could be differentiated simply by disabling features, to real modularity. If you don’t need an extra two cores in the chip, you simply remove them from the design at the outset. Microsoft seems to have taken modularity to heart with the Windows 7/XMP setup. Not everyone needs XP compatibility. Sure, Microsoft could have built it into Windows 7, but that would have bloated the code and package and perhaps made Windows 7 a lesser product out of the box performance- and security-wise. This way, XP support is kept modular, and there’s good reason to think we’ll see other such modules for Windows 7 and/or future Windows versions.
« Last Edit: July 25, 2009, 08:24:13 AM by javajolt »