Question: is an installation of Windows 7 Pro valid if (1) the drive is partitioned into two "primary" partitions, and (2) Win7 is installed on the second partition, which Win7 designates as Drive C, instead of the first partition, which Win 7 designates as Drive D?
Of course, if that arrangement did not work then I doubt that I could run MSIE to post this question.
However, what problems -- if any -- might ensue if I do not re-install Win7 on the first partition of the drive? For example, can malware install itself on the other primary partition, change the MBR to designate it as the boot partition, then load itself into memory before booting Win 7?
Can I change the designation of the first partition as a "primary" partition to another status?
Not that this outcome was deliberately intended. ....
Recently I bought a 250GB Samsung EVO SSD and installed it in my computer (which I built myself at the end of April 2011). There haven't been any problems with it of which I am aware.
So I decided to perform a fresh Windows 7 Pro installation rather than attempt to "migrate" any of the content of the 500 GB Western Digital HDD to it. Windows has become "sluggish" since it was re-installed (for the same reason) about 18 months ago. Before installing Win7 on the SSD, I disconnected the HDD -- on which Win7 was installed on Partition 0 designated as Drive C -- until after Win7 was installed and fully updated on the SSD, and I was ready to run the software installers archived on the HDD.
Whether it matters, before partitioning the SSD I installed an AHCI driver for the Gigabyte GA-890FXA-UD5 motherboard SATA III 6 GB/s controller. Originally I installed AHCI for the WD HDD because the CPU is an AMD Phenom II X4 910e (four cores). Of course, I obtained the most recent AHCI update before the Win7 install on the SSD.
The first Win7 installation did not go very well. Some updates failed to install and were not downloaded again. Then Win7 either ignored some driver updates which I installed, or declared that they did not install correctly and either reverted to the Windows 7 default or to an outdated driver that had been installed from the Win7 disc or during an update. There were enough of these "exceptions" to my expectations that, eventually, I decided to risk wiping the SSD drive and try again. I used the Samsung Magician utility "Secure Erase" process. Evidently, it succeeded, there hasn't been any problem with the SSD that has become evident to me since. But we should not do that except as the last resort, when truly necessary.
During the second installation, I partitioned the SSD into one 107 GB partition and one 125 GB partition, which I created and formatted respectively in that order. Thus partition 0 should be and is 107 GB and partition 1 should have been and was 125 GB. The Windows 7 installer also created a 100 MB "System" partition at the "start" of the SSD although, in my experience, less than about 100 KB or so is ever used.
After Win 7 was installed for the second time, after many hours of downloading and installing all of the OS updates (about 300+ of them!), I successfully updated the drivers which Win 7 had not installed or updated, and installed some software.
Considering and investigating what I need to do with the partitions on the HDD, I ran the Admin Tools Disk Management utility.
Lo and behold: on the SSD, partition 0 is Drive D, which has 107 GB. Partition 1 is Drive C. Windows 7 is installed on Drive C, of course. After using ~ 23 GB for Overprovisioning, which Samsung Magician created at the "end" of the drive, Partition 1 (Drive C) is now a bit more than 100 GB. (Overprovisioning was done immediately after the Win7 install per se completed, before any Win7 updates.)
Okay, I forgot this possibility. It happened once when I installed Windows 7 for the second or third time on the 500 GB Western Digital HDD after I assembled the components to create the computer. Windows tech support advised me to wipe the HDD and repeat the Win 7 installation.
After all this time and effort, though, there are no evident problems with the fact that Windows 7 is installed on partition 1 / Drive C. Admin Tools Disk Management reports:
(1) "Volume" C has a simple layout, basic type, NTFS and is "Healthy (Boot, Page File, Crash Dump, Primary Partition)."
(2) Volume D is reported to have the same attributes and as a "Healthy (Primary Partition)" without any other characterization.
If memory serves, when I created the first partition during the installation, Win7 reported it as a "Primary" partition, and when I created the second partition, it was also reported to be a "Primary" partition. I am not sure what I did that was any different than what I have done during other Win7 installations, i.e., if I did anything differently. I have no idea what I needed to do to prevent the second partition from being created as a "Primary" partition, if that is the reason for the installation outcome.
Regardless, it is passing peculiar that the Win7 installer evidently (1) created the System partition, then (2) created partition 0 with the size that I specified for the first partition, and (3) created partition 1 with the size that I specified for the second partition, then (4) decided that partition 0 would be Drive D and partition 1 would be Drive C. It seems to me that it should make the first partition after the System partition the boot partition and designate it as Drive C, then designate the next partition as Drive D.
Insofar as a "Primary" partition is ordinarily a prospective boot partition, I suppose that someone could want to create two (or more) Primary partitions and install a different OS on each one, then select the OS when the hardware boots. That isn't what I intended to do, but if partitioning the drive with multiple Primary partitions does not affect whether Windows (or an alternative OS) can boot from the one where it is installed, then I don't perceive any reason to re-install Windows 7 for the third time. ...
Even if the third time is a charm. :-)