Windows won't boot if any partition extends past 120 GB on 250 GBdrive

[Will Pittenger]

Isn't that what this thread is about? Also, as previously noted, the
partition manager portion of Windows does see the correct size.

 

[Andy]

When a disk is fully partitioned, Disk Management uses the partition
information on the disk to show the capacity of the disk. That's why
it would say 232GB even if Windows were not configured to to see past
137GB.

When Partition Magic runs under Windows, and it says that the capacity
of the disk drive is only 137GB, that means that Windows does not have
the ability to see past 137GB.

For these reasons, plus the fact that HDD Tune also says the capacity
of the disk is only 137GB, I still contend that the Windows
installation lacks the ability to see past 137GB on that disk.

An earlier message mentioned a Promise controller. If the 250GB disk
is attached to it, then the only thing that matters regarding fully
accessing the disk is the Windows driver for the Promise controller.
48-bit LBA capability in SP1 or SP2 applies only to the disk
controller in the motherboard chipset.

Try connecting a large, *unpartitioned* disk to the same controller as
the 250GB drive. Disk Management would say that the capacity would be
only 128GB.

 

[JS]

And as I mentioned earlier he may need to get the latest BIOS update from
Promise (date of purchase for the Promise card does not guaranty that BIOS
supports 48Bit LBA).

JS

 

[Will Pittenger]

Either the driver update or the bios update did it. (I did both.)
Thank you so much.

 

[Will Pittenger]

This problem is solved! Thank you! Even Partition Magic now runs.

 

[Will Pittenger]

BTW: Given what fixed the problem, why didn't the Linux based utilities
that I used (including an installation of Ubuntu) have the same problems
(or something equivalent) that the Windows based stuff had?

 

[JS]

You're welcome.

JS

Either the driver update or the bios update did it. (I did both.) Thank
you so much.