Another annoyance with Product activation --- If you run Windows XP as a guest OS under VMware sometimes the Activate Windows screen will pop up because you've changed the configuration -- Virtual Hardware configuration your machine.
You then get into all sorts of shenanigens with Microsoft because the guy / gal at the other end of the telephone hasn't got a clue about "Virtual Machines" and thinks because the hardware is so different you are trying to install on a different machine. I've read the EULA licence and it says clearly this copy of Windows is licensed to run on 1 computer -- It is only running on 1 computer -- why should I have trouble emulating 2 or 3 machines on the same pysical machine.
For example you can change memory / disk / cd / monitor configuaration with VMware -- an excellent way to test out a new OS. If I install something and it doesn't work I just trash that virtual machine.
I only do what most properly run businesses do -- test out an upgrade on a "test Machine" before using it as "production".
I use my computer in my business so I need to ensure upgrades work.
Don't you just get sick of Microsoft at times.
However it's quite a challenge to fiddle around with the VM configuration so that the Activate Windows doesn't pop up on a newly configured Virtual Machine.
By the way buying corporate Windows XP really gives meaning to the XP in Windows XP
Windows eXPensive :bigsmile: not an option unless you are IBM, Shell etc etc.
(Any gurus out there who are interested in playing around with Virtual Machine look at http://www.vmware.com ).
I don't work for them or have any commercial associations with them -- just purely technical interests.