This thread is a bit of a brain dump for me and hopefully others will contribute so that I can pick this back up again when I get to it..............
After looking at Grinler's Tutorial I decided to install XPMODE to see how it compared to VMPlayer and Virtualbox.
If you decide to follow the tutorial:
Firstly, be aware that there are issues with the links to downloads - I think MS moved stuff.
Secondly, there are 2 files you can download for XPMODE and no explanation as to the difference between them, The one with an extra 'N' in the name didn't work for me so I downloaded the other one which did. I thought the 'N' might stand for New but eventually found it stands for something else (I forget what but I think it has something removed?).
The interesting thing (for me) is that you don't get asked to activate XP when running XPMODE under MS Virtual PC.
In the info I found for W7 Ultimate, it says it has all the features of W7 Enterprise, which includes licences for 4 VMs, so either this is the reason for this or else it's pre-activated (somehow).
However, when I ran the standalone converter to run the same XP image under VMPlayer it immediately asks for activation - different virtual drivers I guess - so be aware of this.
Why did I do this - due to the 100% CPU issue with SVC Host which I tried to troubleshoot myself.
It occurs to me that anybody looking to virtualize their XP system may face the same issue with having to re-activate XP (at least under VMware or Virtualbox - not sure about Virtual PC).
However, the thing that I discovered by accident, as a result of the Windows Update / SVC Host / 100% CPU issue was that my XP VM is only using a single core of my CPU capacity whether I run it under MS Virtual PC (XPMODE) or VMware VMPlayer.
It looks like this is due to how MS built the XPMODE image and is either done so that the image runs on all machines including those with a single processor - or else they want people to buy an XP licence to run anything of significance under a VM (see below).
When I next get access to the other machine I'll try these resources which I assume will resolve the issue with running on a single core (due to the HAL) :
What I don't know (yet) is whether this change will trigger a request for re-activation of XP and whether this will affect both MS Viual PC and VMware.
** NOTE **
This is an issue where the initial XP Install detects a Single Processor and the XP image is moved to a system with multi-processors or a processor is upgraded.
I would expect that a new install from media to a system with Multi-Processors fitted would detect them and install the correct component setting.
Stuff to do, back to this later...................
Edited by SteveOC, 01 January 2014 - 09:18 AM.