C
Colin Barnhorst
I have been running tests today with an upgrade edition product key. It
turns out that an upgrade edition product key is sufficient for setting up
dual boot systems. I must admitted I am surprised that an installation
using an upgrade edition product key to a target volume other than the OS
being upgraded is tolerated.
The results of x86 scenarios with upgrade disabled (yellow dots in the
upgrade matrix) so far are:
Dual drive system with Windows 2000 Professional SP4 on drive 0, drive 1
empty. 768MB ram.
Ran Vista x86 Setup with an upgrade edition pk for VHP from the W2k desktop.
Disk Options are not available, therefore modifications to the disks are not
possible from Setup (no ability to format the target from within Setup).
Any modifications need to be made in W2k prior to running Vista Setup.
Upgrade option disabled. Custom option permits a choice of disk 0 or disk
1. Selection of disk 1 results in installation of Vista to drive E: and a
dual boot options menu. Both W2k and VHP boot as expected.
Dual drive system with Windows XP Professional SP2 on drive 0, drive 1 is
empty. 512MB of ram.
Ran Vista x86 Setup with an upgrade edition pk for VHP from the XP desktop.
As expected, disk options are not available, yada yada yada. Again the
custom option permits a choice of target volume and selection of drive 1
results in a dual boot system with both XP and Vista fully functional.
This appears to violate the EULA since it permits the continued use of the
legacy system, but it is not blocked.
I am about to switch to the upgrade-enabled scenarios (green dots) to check
if there is any difference. I am also going to spend some time on the x64
scenarios to see what additional tools are available and to investigate the
very discouraging results using an x86 upgrade pk with XP Pro x64 and Vista
x64 as the legacy systems. I am not using virtual machines because of the
licensing issue so this all takes some time.
turns out that an upgrade edition product key is sufficient for setting up
dual boot systems. I must admitted I am surprised that an installation
using an upgrade edition product key to a target volume other than the OS
being upgraded is tolerated.
The results of x86 scenarios with upgrade disabled (yellow dots in the
upgrade matrix) so far are:
Dual drive system with Windows 2000 Professional SP4 on drive 0, drive 1
empty. 768MB ram.
Ran Vista x86 Setup with an upgrade edition pk for VHP from the W2k desktop.
Disk Options are not available, therefore modifications to the disks are not
possible from Setup (no ability to format the target from within Setup).
Any modifications need to be made in W2k prior to running Vista Setup.
Upgrade option disabled. Custom option permits a choice of disk 0 or disk
1. Selection of disk 1 results in installation of Vista to drive E: and a
dual boot options menu. Both W2k and VHP boot as expected.
Dual drive system with Windows XP Professional SP2 on drive 0, drive 1 is
empty. 512MB of ram.
Ran Vista x86 Setup with an upgrade edition pk for VHP from the XP desktop.
As expected, disk options are not available, yada yada yada. Again the
custom option permits a choice of target volume and selection of drive 1
results in a dual boot system with both XP and Vista fully functional.
This appears to violate the EULA since it permits the continued use of the
legacy system, but it is not blocked.
I am about to switch to the upgrade-enabled scenarios (green dots) to check
if there is any difference. I am also going to spend some time on the x64
scenarios to see what additional tools are available and to investigate the
very discouraging results using an x86 upgrade pk with XP Pro x64 and Vista
x64 as the legacy systems. I am not using virtual machines because of the
licensing issue so this all takes some time.