|22 Oct 2012||#1|
| || |
Win7 Disk Management - What criteria does W7 use to id Disk0 vs Disk1
I have just done a fresh install of Windows 7 Pro 32-bit, replacing my XP install.
I am running a 2 HDD setup. The 2 HDD's are connected across 2 SATA ports; port 0 and port 1. I use the first HDD for Windows install and the second HDD for user data.
Paragon's Partition Manager sees HDD0 (which holds the Windows 7 install) and HDD1 (which contains just a volume of data).
If I only connect HDD0 (and appropriately only identify it as connected in the BIOS), Windows 7's <Computer Management> <Disk Management> identifies it as Disk0.
But, when I connect both HDD0 and HDD1 up (and configure as such in the BIOS), Windows 7 now refers to the Windows 7 install disk as Disk1 and the 2ndary HDD as Disk0.
All seems to be working, but is this normal?
I would of thought, especially after only connecting one HDD and Windows recognizing it as Drive 0, that when connecting a second HDD it would of for sure kept what was being Drive 0 as Drive 0, AND the newly connected drive as Drive 1.
What criteria does Windows 7 employ in identifying Disk 0 and Disk 1?
Many thanks for all responses ... Bill
|My System Specs|
|Similar help and support threads for2: Win7 Disk Management - What criteria does W7 use to id Disk0 vs Disk1|
|Disk Management (Snap in) shows swaped Disk0=D and Disk1=C||Hardware & Devices|
|BCD setting for win7 ult x64 disk0 & xp pro sp3 x32 disk1||Installation & Setup|
|Disk Management - Extending/spanning a Striped Dynamic Disk, how?||General Discussion|
|hard disk changed to dynamic type after using disk management||General Discussion|
|Partition not Showing in Win7 After Rescan in Disk Management||General Discussion|
|Need quick help about new hard disk partition on win 7 disk management||Hardware & Devices|
|HDD listing in Disk Management in Win7||Hardware & Devices|