Win2000 Fdisk function partitions a 200G as a131G

[ollie]

Hello Yall,
I just put a new system together with Asus A7N8X-VM/400
motherboard and installed Win2000 with Service pack 4.
During the setup I noticed the 200G hard drive was being
recognized as a 131G HD. I called Asus and they told me
to create a 30G partition, finish the installation, then
windows would see the full partion, that did not happen.
Windows still thinks it is a 131G HD. I appreciate any
suggestions.

Thanks a lot

Ollie

 

[Andy]

If your goal is to have a single 200GB partition, you have to use
software such as Partition Magic that can nondestructively resize the
131GB partition.

 

[Roger Parr]

Hello Yall,
I just put a new system together with Asus A7N8X-VM/400
motherboard and installed Win2000 with Service pack 4.
During the setup I noticed the 200G hard drive was being
recognized as a 131G HD. I called Asus and they told me
to create a 30G partition, finish the installation, then
windows would see the full partion, that did not happen.
Windows still thinks it is a 131G HD. I appreciate any
suggestions.

There is a short registry fix from Microsoft which is required if
Windows 2000 is to support more than 131GB. Search the MS support
web-site for 48-bit LBA. Although I think this is incorporated into
SP4, it would be worth checking.

Also, check what your BIOS is reporting - with such a modern board as
that, I would have expected it to support >131GB out-of-the-box, but are
there any BIOS settings that might prevent the drive being properly
recognised?

Are there any jumper settings on the drive? You used to see "32GB"
clipping jumper options a few years ago, when drives of greater than
that size first came out. I wonder if maybe your drive has a similar
option to get round the 131GB limit? I have never seen this option, but
there again, I haven't had this problem.

As several other recent posters have had similar problems, it would be
helpful to others if you could post what the solution turns out to be.

HTH

 

[Bjorn Landemoo]

Ollie

You need to edit the registry, there is a value EnableBigLba that needs to
be enabled even if SP3 or later is installed. See this MS Knowledge Base
article:

http://support.microsoft.com/?id=305098

Best regards

Bjorn