backtop


Print 53 comment(s) - last by .. on Aug 30 at 10:07 AM


Windows 7's XP Mode has been improved in a new release candidate. This innovative virtualization feature allows applications to be run within the XP guest OS and seamless integrate with the Windows 7 environment. The front browser is running in XP, while the back is running in Windows 7.  (Source: LILkillaBees Blog)
Windows fans are invited to test out the innovative new OS feature

One of Windows 7's most interesting features is going to be the Windows XP mode, available on Professional and Ultimate editions.  Typically, virtual machines are only supported via separately purchase software from vendors such as VMWare or Microsoft.  This limits virtualization's audience and appeal, leaving out many everyday users.  So Microsoft decided to do something unique and bundle Windows 7 with a virtual machine with Windows XP inside.  This allowed them not only to bring virtualization to the masses, but also to seamlessly integrate compatibility for legacy applications.

The feature, however, was only in rough form in the beta candidate and previous release candidate builds.  Yesterday Microsoft release a new release candidate that at last added a near-finalized version of this functionality.  The build is available here and runs Windows XP SP3. 

Aware of security risks, Microsoft has accompanied the build with a warning that users should install anti-malware and antivirus software to protect Windows XP.  It has been speculated that malicious users could exploit the virtual machine's lack of certain security features -- such as ASLR (Address Space Layout Randomization) or an Internet Explorer Protected Mode -- to perform guest-to-host attacks.  This problem is minimized by the fact that the install comes with a firewall and that Microsoft will be offering free antivirus support for XP as well as Vista and Windows 7 this fall (a second beta is expected to drop soon).

Brandon LeBlanc, a Windows communications manager at Microsoft comments on the new RC build, stating, "Windows XP Mode is specially designed for small and medium-sized businesses to help ease the migration process to Windows 7 by providing additional compatibility for their older productivity applications. The newly updated Windows XP Mode now works with the RC and RTM versions of the Windows 7 Professional, Ultimate and Enterprise SKUs."

The differences in functionality of the new XP Mode and the old are subtle, but significant. Windows XP applications running on the Windows 7 task bar can now be accessed by right clicking.  Disk sharing between Windows 7 and Windows XP mode can now be disabled and users can choose where there Windows XP differencing files are stored.  USB devices can now operate within Windows XP without needing to go into fullscreen mode, useful for accessing content from programs like Word 2003 running in XP Mode.  Finally, a tutorial about XP Mode is now included, a great feature for new users.

Tom Quillin, director of Intel vPro Ecosystem Development lauds the feature, praising that its not only a fun toy for home users, but a valuable asset to businesses.  He states, "The increasing prevalence worldwide of PCs based on Intel Core 2 processors with Intel Virtualization Technology is enabling a variety of new applications that provide business opportunities for greater manageability, security and cost reduction. Used with Windows XP Mode, Intel Virtualization Technology helps small- and medium-sized businesses migrate more efficiently from Windows XP to Windows 7.



Comments     Threshold


This article is over a month old, voting and posting comments is disabled

RE: Just a thought...
By Fox5 on 8/5/2009 9:59:54 AM , Rating: 0
Most of Vista's incompatibilities were due to hardware, so I don't see how XP mode solves things at all. On top of that, it doesn't even support hardware accelerated 3d (unless they've updated XP's RDP to send display lists like vista's does, and even that's limited support).

Sorry, but this is just another too-little, too-late feature by MS to sell the more expensive versions of Windows. There's already superior VM programs on the market, and VirtualBox is already free, and Vmware has a free version as well.
Not to mention VMware has accelerated 3d support (slow, but it exists), and Virtualbox is capable of fully exposing the graphics hardware to the virtual machine as soon as motherboard chipsets are released with the capability (sometime with the next 6 months).

It seems like the only ones getting excited about XP mode, are the people that don't realize it doesn't solve their problems, or that their problems don't exist with Vista/7.


RE: Just a thought...
By damianrobertjones on 8/5/2009 11:07:54 AM , Rating: 2
I'm excited as it's... free. Thank you Microsoft. Other than that, I'll use VMWare Workstation for the other installs. People complain if they do, complain if they don't.

I consider it to be nothing more than something you will or won't use and above that, I'm not bothered. Anyway, if it's that bad, then duel boot XP with Win7.


RE: Just a thought...
By Mojo the Monkey on 8/5/09, Rating: 0
RE: Just a thought...
By The0ne on 8/5/2009 2:07:36 PM , Rating: 2
RTM makes dual booting impossible for me. I've tried so many ways but none has worked so far. RTM doesn't offer you the Boot Loader any longer. It wipes away anything version of OS you have and keeps its own.

Hiding the drive didn't solve it either although there are workarounds for that. Installing on different partitions/drive wasn't successful as well.

I'm open to suggestions from anyone who has successfully configured this setup. Please note, however, that this is for Windows7 RTM (7600) and XP SP3. Yes, I've Googled.


RE: Just a thought...
By wetwareinterface on 8/5/2009 10:41:27 PM , Rating: 2
the simple trick is install xp sp3 first, then install win 7 and use the new boot manager. it will recognize older windows installs and automatically make an entry in the boot list for older windows versions. on that page you can select which (if you have more than 1) older os to boot to.

if that's not custom enough use easybcd to make changes to boot order and what is listed and how it's labeled from within win 7 after everythings installed.

it seems your problem is you are trying to install win 7 first and win xp second. the dual boot options are geared mostly for people who are moving from one os to the new one and assume you already have the older os installed on your machine. it's not geared to someone who wants both and is starting fresh. it will be doable but it just isn't how they thought out implementing it and who would be using it.

if you already have win 7 installed and lots of programs going under it and don't want to re-set it up...

you could get a trial version imaging program, make an image of win 7, re-do the partioning and install xp first on the second partition/drive, then put the imaged win 7 back on the first partition/drive and run easybcd to point to xp as an optional boot.

or use a third party boot manager like acronis disk director or linux's grub

or install xp on second partition/drive, use win 7 install disk to automatically repair installation, use easybcd to point to xp


RE: Just a thought...
By queuetrip on 8/18/2009 12:45:14 PM , Rating: 2
When installing new operation systems for dual boot, install each operating system to a new hard drive alone. (so it will be 'drive c'. )
if the os is not installed alone the drive letter will be other than 'c'.
after all of the os's have been installed alone, connect all the drives and use some 'BCDEDIT' magic and the drives GUID, that should allow the windows' dual boot.

now, if someone had 'WIN ninja os' skills, the drive letter could be changed but I don't know how.

I just use the 'install OS alone on HDD' then the BIOS boot menu to dual boot winXP and vista. (i use the vista boot screen to choose between win7rc and vista)



RE: Just a thought...
By LRonaldHubbs on 8/5/2009 1:05:53 PM , Rating: 3
I'm not sure that's such a good idea. Win7 would clearly win the fight, but what if XP got a decent shot in, your Win7 could end up crippled!


RE: Just a thought...
By omnicronx on 8/5/2009 11:15:49 AM , Rating: 3
quote:
Most of Vista's incompatibilities were due to hardware, so I don't see how XP mode solves things at all. On top of that, it doesn't even support hardware accelerated 3d (unless they've updated XP's RDP to send display lists like vista's does, and even that's limited support).
While this may have been the reason for many home users, I really don't believe this was the reason that Vista never really reached mass deployment (Home users are a tiny percentage of Windows Sales). It was software not hardware that was incompatible with Vista. There were many API and fundamental changes such as moving the user to mode 1 and having services run in mode 0. None of my works service based apps worked in Vista because of this.

As for home users, directshow was a big showstopper, and this is where many hardware manufacturers failed to step up to the plate. So if anything it was still the software as it was badly written drivers that were the main culprit. (I'm looking at you Creative)


RE: Just a thought...
By adiposity on 8/5/2009 1:10:33 PM , Rating: 3
After you get past the hardware problems (not really an issue on a new computer, of course), the software problems begin. We have about 10 "must have" apps that we use at my company, and two of them flat-out don't work on Vista and Windows7.

There are newer versions that DO work, but we have to pay about $50,000 (in the case of one of the apps) to upgrade our licenses to that version. In the case of the other app, the newer version is not 100% backwards compatible with the old version, so we have to make changes to our independently developed code to make it work.

Also, older AutoCAD versions are not compatible with Vista/Windows7. We have some of those licenses, which will require us to pay for upgrades (1000s).

In the case of AutoCAD, we probably would not use XP mode. But in the case of the $50,000 client which works fine under XP mode, we may just use XP mode.

quote:
It seems like the only ones getting excited about XP mode, are the people that don't realize it doesn't solve their problems, or that their problems don't exist with Vista/7.


Nope. I know what it does, and it saves me $50,000.

-Dan


RE: Just a thought...
By epobirs on 8/5/2009 5:42:05 PM , Rating: 2
You couldn't be more wrong.

First, consider the failure of logic in blaming hardware. Vista runs just fine on plenty of machines that were produced before Vista was in beta. The sole issue in most cases where it doesn't run well is memory consumption. Some older machines lacked the ability to take much RAM above the 512 MB that was common for several years, and thus are bad Vista candidates even though the memory upgrade itself would be quite cheap.

The vast majority of software incompatibility issues are due to Vista's more stringent requirement for programming practices. When XP was released, Microsoft also published a guide to their preferred programming practices for better reliability and security. They also promised that apps that followed these guidelines would be viable for a long time to follow. They kept that promise. Software that complies with the guidelines runs perfectly on Vista with very few exceptions.

After years of getting blamed for the results of third party developer's bad coding practices, MS made some major changes in Vista compared to XP. Several things which had previously been condemned but allowed to run were no longer given that allowance. Vista flat out says no, you can't do that crap here. This is why no version of QuickBooks before Vista's release would run. Intuit did some really rotten stuff with the registry as a hack to enable interaction with other software instead of creating a proper infrastructure for the purpose. This was a really bad practice and Microsoft was well overdue to stop iy being done.

A lot of other examples are in-house proprietary apps that are critical to the businesses that original contracted their creation. The use of bad coding practices was endemic among these and that meant Vista was a no-go unless they could run them under XP in a VM. Two big Vista deployment I worked in were at companies big enough that their licensing with Microsoft allowed this to be done without any great additional cost. But for smaller companies this is a significant expense and involves some complexity for the users.

XP Mode solves that very well. There is a critical app that is widely used by convalescent hospitals to produce their Medicare billing. It's pretty ugly and can't even install on Vista, never mind run on it. I've already tested it with the XP Mode beta and it works perfectly, integrating with the Win7 desktop in a way that require nearly no training of existing users.

For me and my clients, XP Mode is a huge WIN .


"We don't know how to make a $500 computer that's not a piece of junk." -- Apple CEO Steve Jobs

Related Articles













botimage
Copyright 2014 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki