Quick question on WinXP mode in Win7...
I'm familiar with other virtualization technologies out there like VMWare and VirtualBox.
What intrigues me about Win7's XP mode is that it appears to me from googling that:
- WinXP licensing is included with your Win7 license. No extra licenses required just for an app or two
- The WinXP instance doesn't need to run like a full blown OS on a virtual machine. No dedicated page file, hiberfil, set of user IDs or SIDs, passwords, AV software, policies etc... It's meant much more for launching one app... This would be a distinct advantage in my books over VMWare, VBox etc...
I have a number of devices, such as a Nikon Coolscan 5000ED 35mm film scanner, for which Nikon has only grudgingly put out Vista support and only x86 at that. There are workarounds for x64 which I'm using, but nonetheless they seem to have more or less decided that they're not going to support the device at all going forward.
As with many other cases under Win7, I do not necessarily anticipate a lot of problems running software apps under Win7, but I do forsee driver problems such as this one.
Can anyone in-the-know describe briefly whether XP Mode can indeed address driver issues, how drivers are loaded in the XP space, and can only applications running in XP space access the XP drivers? I presume that even in Win7 x64 the XP Mode is x86, correct? Is the WinXP mode indeed application-oriented instead of boot-a-whole-OS oriented? This is a disadvantage for sandboxes, but an advantage for the average Joe with an old app. (Speaking of sandboxes, I guess that means x64 users could get Sandboxie back, as kludgy as it is implemented kernel-wise. Run IE in XPM w/ sandboxie.).
Thanks,
I'm familiar with other virtualization technologies out there like VMWare and VirtualBox.
What intrigues me about Win7's XP mode is that it appears to me from googling that:
- WinXP licensing is included with your Win7 license. No extra licenses required just for an app or two
- The WinXP instance doesn't need to run like a full blown OS on a virtual machine. No dedicated page file, hiberfil, set of user IDs or SIDs, passwords, AV software, policies etc... It's meant much more for launching one app... This would be a distinct advantage in my books over VMWare, VBox etc...
I have a number of devices, such as a Nikon Coolscan 5000ED 35mm film scanner, for which Nikon has only grudgingly put out Vista support and only x86 at that. There are workarounds for x64 which I'm using, but nonetheless they seem to have more or less decided that they're not going to support the device at all going forward.
As with many other cases under Win7, I do not necessarily anticipate a lot of problems running software apps under Win7, but I do forsee driver problems such as this one.
Can anyone in-the-know describe briefly whether XP Mode can indeed address driver issues, how drivers are loaded in the XP space, and can only applications running in XP space access the XP drivers? I presume that even in Win7 x64 the XP Mode is x86, correct? Is the WinXP mode indeed application-oriented instead of boot-a-whole-OS oriented? This is a disadvantage for sandboxes, but an advantage for the average Joe with an old app. (Speaking of sandboxes, I guess that means x64 users could get Sandboxie back, as kludgy as it is implemented kernel-wise. Run IE in XPM w/ sandboxie.).
Thanks,