New
#11
Shouldn't there be a partition, regardless of the drive letter, that is listed in Disk Management as "Boot, Page File, Crash Dump" also?
Shouldn't there be a partition, regardless of the drive letter, that is listed in Disk Management as "Boot, Page File, Crash Dump" also?
[QUOTE=dsperber;3016378]Yes, it is a little tight, I usually make them 30GB for simple installs. I try to keep the C partition for Windows only, and all other data on other partitions. With hibernation disabled and the pagefile on a diff partition , you can keep the root drive quite small. Biggest issue is the Winsxs folder keeps growing.
That's not a Windows system partition!! That's simply "system reserved" for Boot Manager. Standard 100MB size for that.
Windows on that drive is located (apparently) on what shows as G in the current screenshots. That's 20GB.
The third partition on that drive (H) is apparently a "data" partition.
OP didn't spread the columns for DISKMGMT, so we can't see the text in the crucial cells. But C (on DISK0) is where the true Windows lives in this other special setup where the problem drive has simply been temporarily connected as DISK1. Hence why its partitions appear to be "normal" partitions on a second drive, although we really know what they really are when the drive is used as a true primary boot drive.
Mexman,
Your specs show an SSD in the primary machine, along with two WD black spinners. Is this correct?
You also say this problem drive (80GB?) is connected with IDE cable?? Not SATA? Which drive would this be in your specs story?
Have you tried using PW's "align all partitions" operation on DISK1 (with the current setup where the problem drive is connected as a second drive in the other machine)?
It's certainly unheard of in my own experience for the BIOS to be in any way impacted by a disk drive format, so that it doesn't "post" and complete. Sure, it might not actually be able to boot (if say the boot sequence is wrong, or if there is no "active" partition found, etc.), but the BIOS itself should certainly complete and shouldn't hang in the middle.
Well, I gots to be stubborn.
I have never seen a screenshot of Disk Management that had a partition that contained Windows on it that simply said "Healthy, Primary Partition".
Mexman so these folks can have a proper look please complete this tutorial by Golden. I think it just might reveal some things if done properly.
Disk Management - Post a Screen Capture Image
On the boot drive, sure.
But on a second drive that contains a "residual" partition that actually is what once was a Windows partition? Why wouldn't it just be a "healthy" partition that is non-empty? It's just "residual" data on it, which happens to have been a usable Windows system partition at one time.
At this very moment it's not even in the Boot Manager menu on the current machine primary drive, so it's not even seen in any way as an available second bootable OS (which might be what possibly makes it show up as a second "system" partition in your comment, in addition to the currently booted Windows C partition which for sure shows as "system").
Now I'm a bit more confused. Is this a THIRD machine you're now talking about?
Your screenshot as posted shows two drives, one of which could be a 160GB drive as DISK0, with the problem 80GB drive as DISK1. I see no 1200GB boot drive?? Did you mean 120GB instead? And I still don't see that either.
Anyway, your forum "specs" show some machine with Kingston 64GB SSD and two WD Black spinners. Is that true or not? Is it either of the machines we're currently discussing, or yet some other machine?