No, Windows Vista and up always use C:
as the system drive.
For example, if you have two partitions, one with XP and the second with 7 so that you can dual-boot XP and 7, you will see that when you boot into XP, it will still be on C:
as before, but when you boot 7, it will also be on C:
. What happens is that the system is mapped to C:
while the partition that would have been C:
will be mapped to something else.
The same is true if you dual-boot Vista and 7 or 7 and another copy of 7; each system will assign C:
to its own boot-up partition and assign something else to the other partitions.
Further, A:
and B:
are special reserved letters that cannot be used as system drives, even in XP (though you can assign them to miscellaneous hard-drive partitions).
So in DiskPart, would it even make sense to assign drive letters pre-installation? – Kevin Hua – 2012-07-18T02:15:32.217
As @Synetech said, no it would not. – imtheman – 2012-07-18T02:18:56.927
How are you running DiskPart? If you are running it in the System Repair console or pre-installation, then the letters will only be visible in that context and then Windows will re-assign the drive letters as necessary during the initialization phase of the installation. When you boot into Windows, it will see whatever letters you assigned regardless of what you assigned in other copies of Windows. – Synetech – 2012-07-18T02:19:14.457
I discovered this behavior of Windows 7 when I installed 7 as a dual-boot to XP. I was pleasantly surprised to see that I did not have to manually re-assign any drive letters because 7 already claimed
C:
for itself.:-)
– Synetech – 2012-07-18T02:20:23.147That's convenient, I can simplify my preinstallation script now =) – Kevin Hua – 2012-07-18T02:20:54.037
Yes, definitely. Though if you really want/need to install 7 to a different drive, letter, this person suggested running the installation from an already booted copy of Windows (from
– Synetech – 2012-07-18T02:23:35.403C:
), but I suspect that once the installation has completed and the new copy boots, it will be onC:
and the existing copy will be remapped to something else.