I dual (or triple) boot WinXP, Win7 and Win10. When I boot into any of these 3, in DiskManagement and FileExplorer the partition for that OS becomes the C: drive. These are hard drive partitions, all on the same hard drive. Win7's hard drive boot partition is called WD2TB B.
Recently I got interested in adding a SATA SSD to my system. To get the SSD to even show on my computer I (per instructions) first connected it via aSATA-USB cable. Then I can see it in DiskManagement of Win7. I created a primary (bootable) partition naming in SSD1 and giving it letter V:. I then used and imaging app, Macrium, to restore aback-up-image of harddrive-Win7 into my new SSD partition disk V:.
I then shut down and connected the SSD to SATA cable 5 and booted harddrive-Win7. InEasyBCD I created a new entry for the BCD booting menu, calling it"Win7 on SSD" and pointing it at disk V:
When I used "Win7on SSD" Win7 does boot, but there are anomalies. FileExplorer is showing C: as being WD2TB B, I expected (wanted) it to be SSD1 on the V: drive. When I uninstall a program while I'm booted to "Win7on SSD" it also disappears on the regular hard-drive Win7installation!
I suspect this happened when I added my new BCD entry in EasyBVD by simply pointing it at V:
"Win7 on SSD"does boot a bit more snappily, I think it's actually using the SSD,but somehow it's also tied into the hard drive partition for Win7somehow. And I DON'T want it to be.
Recently I got interested in adding a SATA SSD to my system. To get the SSD to even show on my computer I (per instructions) first connected it via aSATA-USB cable. Then I can see it in DiskManagement of Win7. I created a primary (bootable) partition naming in SSD1 and giving it letter V:. I then used and imaging app, Macrium, to restore aback-up-image of harddrive-Win7 into my new SSD partition disk V:.
I then shut down and connected the SSD to SATA cable 5 and booted harddrive-Win7. InEasyBCD I created a new entry for the BCD booting menu, calling it"Win7 on SSD" and pointing it at disk V:
When I used "Win7on SSD" Win7 does boot, but there are anomalies. FileExplorer is showing C: as being WD2TB B, I expected (wanted) it to be SSD1 on the V: drive. When I uninstall a program while I'm booted to "Win7on SSD" it also disappears on the regular hard-drive Win7installation!
I suspect this happened when I added my new BCD entry in EasyBVD by simply pointing it at V:
"Win7 on SSD"does boot a bit more snappily, I think it's actually using the SSD,but somehow it's also tied into the hard drive partition for Win7somehow. And I DON'T want it to be.