Win 2000 can't see large Disk... (but used to)...?

Howdy,

I run Win 2000 Pro SP4 on one of my systems, and had in it a
250 gig Western Digital disk that failed.

I replaced it with a 500 gig drive, but Windows can only see
127 gig on that disk.

Here are the things I am sure of:

The bios (the most recent available) sees the disk as 500
gig.

The registry has the appropriate 48-Bit LBA Support for
ATAPI Disk Drives. I have checked that both by simply
viewing the appropriate registry key, and also by running a
tool that looks in the registry to see if the key is set
correctly.

I have partitioned and formatted the disk.

I have tried to add another partition, but (beyond the 127
gigs) there is no extra space available for such a
modification. I made this attempt using the Western Digital
supplied tools, and also using Acronis Disk Director. The
results were the same.

Also, after too many calls to Western Digital Tech "Support"
I thought that the disk itself may be defective.

I replaced it with another, and the results are exactly the
same.

Might you have some suggestions about an appropriate next
step?

Sincere thanks,
--
Kenneth

If you email... Please remove the "SPAMLESS."

On Sun, 01 Jun 2008 16:19:22 -0400, Kenneth
<usenet@soleSPAMLESSassociates.com> wrote:

>
>Howdy,
>
>I run Win 2000 Pro SP4 on one of my systems, and had in it a
>250 gig Western Digital disk that failed.
>
>I replaced it with a 500 gig drive, but Windows can only see
>127 gig on that disk.

What part of Windows are you talking about? Windows Explorer? Disk
Management? Windows setup?

>
>Here are the things I am sure of:
>
>The bios (the most recent available) sees the disk as 500
>gig.
>
>The registry has the appropriate 48-Bit LBA Support for
>ATAPI Disk Drives. I have checked that both by simply
>viewing the appropriate registry key, and also by running a
>tool that looks in the registry to see if the key is set
>correctly.

Does Disk Management show the correct capacity for the drive?
Caveat: if the drive is fully partitioned, Disk Management will show
its full capacity even though Windows 2000 may not be configured to
access past 137GB.

>
>I have partitioned and formatted the disk.

Using what software?

>
>I have tried to add another partition, but (beyond the 127
>gigs) there is no extra space available for such a
>modification. I made this attempt using the Western Digital
>supplied tools, and also using Acronis Disk Director. The
>results were the same.
>
>Also, after too many calls to Western Digital Tech "Support"
>I thought that the disk itself may be defective.
>
>I replaced it with another, and the results are exactly the
>same.
>
>Might you have some suggestions about an appropriate next
>step?

Partitioning or recognition of disk capacity during Windows 2000
setup: regardless of BIOS capability or Service Pack level incorported
in the Windows 2000 CD, only 131,000 MB will be recognized.

Once Windows 2000 has been installed on the hard drive: in order for
Windows 2000 to see past 137GB on the disk, Service Pack 3 or 4 must
be installed, and EnableBigLba = 1 has to be added to the registry.

The proper way to install Windows 2000 on a large disk is to start
with an unpartitioned disk. Create a single partition during Windows
setup, and install Windows. Once Windows 2000 is installed, apply SP4
and EnableBigLba in the registry. Then use Disk Management to create
additional partition(s) on the disk.

Once the 500GB disk is fully partitioned, Windows 2000 setup won't
work properly, because it can't correctly recognize the partition(s)
on the disk. With a 250GB disk, it typically isn't a problem.

>
>Sincere thanks,

On Sun, 01 Jun 2008 17:05:43 -0700, Andy <1@2.3> wrote:

Hi Andy,

Please see my responses to your comments inline below...


>On Sun, 01 Jun 2008 16:19:22 -0400, Kenneth
><usenet@soleSPAMLESSassociates.com> wrote:
>
>>
>>Howdy,
>>
>>I run Win 2000 Pro SP4 on one of my systems, and had in it a
>>250 gig Western Digital disk that failed.
>>
>>I replaced it with a 500 gig drive, but Windows can only see
>>127 gig on that disk.
>
>What part of Windows are you talking about? Windows Explorer? Disk
>Management? Windows setup?
>

Disk Management does not "see" the full capacity of the
drive.


>>
>>Here are the things I am sure of:
>>
>>The bios (the most recent available) sees the disk as 500
>>gig.
>>
>>The registry has the appropriate 48-Bit LBA Support for
>>ATAPI Disk Drives. I have checked that both by simply
>>viewing the appropriate registry key, and also by running a
>>tool that looks in the registry to see if the key is set
>>correctly.
>
>Does Disk Management show the correct capacity for the drive?
>Caveat: if the drive is fully partitioned, Disk Management will show
>its full capacity even though Windows 2000 may not be configured to
>access past 137GB.

No, the BIOS does show the drive as 500 gig, but Disk
Management has it as 137 gig.

>
>>
>>I have partitioned and formatted the disk.
>
>Using what software?

I have tried three different approaches:

Windows itself, the Western Digital Installation software,
and Acronis Disk Director. All of these run under Windows,
and all see the disk as 137 gig.

>
>>
>>I have tried to add another partition, but (beyond the 127
>>gigs) there is no extra space available for such a
>>modification. I made this attempt using the Western Digital
>>supplied tools, and also using Acronis Disk Director. The
>>results were the same.
>>
>>Also, after too many calls to Western Digital Tech "Support"
>>I thought that the disk itself may be defective.
>>
>>I replaced it with another, and the results are exactly the
>>same.
>>
>>Might you have some suggestions about an appropriate next
>>step?
>
>Partitioning or recognition of disk capacity during Windows 2000
>setup: regardless of BIOS capability or Service Pack level incorported
>in the Windows 2000 CD, only 131,000 MB will be recognized.
>
>Once Windows 2000 has been installed on the hard drive: in order for
>Windows 2000 to see past 137GB on the disk, Service Pack 3 or 4 must
>be installed, and EnableBigLba = 1 has to be added to the registry.
>
>The proper way to install Windows 2000 on a large disk is to start
>with an unpartitioned disk. Create a single partition during Windows
>setup, and install Windows. Once Windows 2000 is installed, apply SP4
>and EnableBigLba in the registry. Then use Disk Management to create
>additional partition(s) on the disk.
>
>Once the 500GB disk is fully partitioned, Windows 2000 setup won't
>work properly, because it can't correctly recognize the partition(s)
>on the disk. With a 250GB disk, it typically isn't a problem.

Of course, I should have made this clear in my original
post, but I am NOT trying to install Windows to the large
disk. I have Windows installed on a small (20 gig) drive,
and it is running fine.

The large disk if for data only.

Thanks again for any further thoughts,
--
Kenneth

If you email... Please remove the "SPAMLESS."

>>> I have partitioned and formatted the disk.

>> Using what software?

> I have tried three different approaches:
>
> Windows itself, the Western Digital Installation software,
> and Acronis Disk Director. All of these run under Windows,
> and all see the disk as 137 gig.

You can produce a boot disc with Acronis. I would curious to see if
Disk Director would be as short-sighted when booted free of Windows.

On Mon, 02 Jun 2008 01:16:50 GMT, Grinder
<grinder@no.spam.maam.com> wrote:

>>>> I have partitioned and formatted the disk.
>
>>> Using what software?
>
>> I have tried three different approaches:
>>
>> Windows itself, the Western Digital Installation software,
>> and Acronis Disk Director. All of these run under Windows,
>> and all see the disk as 137 gig.
>
>You can produce a boot disc with Acronis. I would curious to see if
>Disk Director would be as short-sighted when booted free of Windows.

Hmmmm, I had not thought of that...

But when I launch Disk Director Suite and click on Bootable
Media Builder, nothing happens.

Checking the helpfile also yields nothing.

I know how to create a boot disk from True Image, but that
would not seem relevant to this issue.

I will check the Acronis forum and see what I can learn
about a Disk Director Bootable Disk...

Thanks again,
--
Kenneth

If you email... Please remove the "SPAMLESS."

On Sun, 01 Jun 2008 22:08:32 -0400, Kenneth
<usenet@soleSPAMLESSassociates.com> wrote:

>On Mon, 02 Jun 2008 01:16:50 GMT, Grinder
><grinder@no.spam.maam.com> wrote:
>
>>>>> I have partitioned and formatted the disk.
>>
>>>> Using what software?
>>
>>> I have tried three different approaches:
>>>
>>> Windows itself, the Western Digital Installation software,
>>> and Acronis Disk Director. All of these run under Windows,
>>> and all see the disk as 137 gig.
>>
>>You can produce a boot disc with Acronis. I would curious to see if
>>Disk Director would be as short-sighted when booted free of Windows.
>
>Hmmmm, I had not thought of that...
>
>But when I launch Disk Director Suite and click on Bootable
>Media Builder, nothing happens.
>
>Checking the helpfile also yields nothing.
>
>I know how to create a boot disk from True Image, but that
>would not seem relevant to this issue.
>
>I will check the Acronis forum and see what I can learn
>about a Disk Director Bootable Disk...
>
>Thanks again,

Hi again,

Well, I have the Bootable Media Builder thing sorted out,
but won't be able to burn a disk until tomorrow.

I'll let you know.

Many thanks for the idea,
--
Kenneth

If you email... Please remove the "SPAMLESS."

On Sun, 01 Jun 2008 20:43:32 -0400, Kenneth
<usenet@soleSPAMLESSassociates.com> wrote:

>On Sun, 01 Jun 2008 17:05:43 -0700, Andy <1@2.3> wrote:
>
>Hi Andy,
>
>Please see my responses to your comments inline below...
>
>
>>On Sun, 01 Jun 2008 16:19:22 -0400, Kenneth
>><usenet@soleSPAMLESSassociates.com> wrote:
>>
>>>
>>>Howdy,
>>>
>>>I run Win 2000 Pro SP4 on one of my systems, and had in it a
>>>250 gig Western Digital disk that failed.
>>>
>>>I replaced it with a 500 gig drive, but Windows can only see
>>>127 gig on that disk.
>>
>>What part of Windows are you talking about? Windows Explorer? Disk
>>Management? Windows setup?
>>
>
>Disk Management does not "see" the full capacity of the
>drive.
>
>
>>>
>>>Here are the things I am sure of:
>>>
>>>The bios (the most recent available) sees the disk as 500
>>>gig.
>>>
>>>The registry has the appropriate 48-Bit LBA Support for
>>>ATAPI Disk Drives. I have checked that both by simply
>>>viewing the appropriate registry key, and also by running a
>>>tool that looks in the registry to see if the key is set
>>>correctly.
>>
>>Does Disk Management show the correct capacity for the drive?
>>Caveat: if the drive is fully partitioned, Disk Management will show
>>its full capacity even though Windows 2000 may not be configured to
>>access past 137GB.
>
>No, the BIOS does show the drive as 500 gig, but Disk
>Management has it as 137 gig.

Disk Management showing the drive capacity as only 128GB is sufficient
proof that your Windows 2000 installation is not properly configured
to support 48-bit LBA.

>
>>
>>>
>>>I have partitioned and formatted the disk.
>>
>>Using what software?
>
>I have tried three different approaches:
>
>Windows itself, the Western Digital Installation software,
>and Acronis Disk Director. All of these run under Windows,
>and all see the disk as 137 gig.

This means that your Windows 2000 installation is limited to 28-bit
LBA.

>
>>
>>>
>>>I have tried to add another partition, but (beyond the 127
>>>gigs) there is no extra space available for such a
>>>modification. I made this attempt using the Western Digital
>>>supplied tools, and also using Acronis Disk Director. The
>>>results were the same.
>>>
>>>Also, after too many calls to Western Digital Tech "Support"
>>>I thought that the disk itself may be defective.
>>>
>>>I replaced it with another, and the results are exactly the
>>>same.
>>>
>>>Might you have some suggestions about an appropriate next
>>>step?
>>
>>Partitioning or recognition of disk capacity during Windows 2000
>>setup: regardless of BIOS capability or Service Pack level incorported
>>in the Windows 2000 CD, only 131,000 MB will be recognized.
>>
>>Once Windows 2000 has been installed on the hard drive: in order for
>>Windows 2000 to see past 137GB on the disk, Service Pack 3 or 4 must
>>be installed, and EnableBigLba = 1 has to be added to the registry.
>>
>>The proper way to install Windows 2000 on a large disk is to start
>>with an unpartitioned disk. Create a single partition during Windows
>>setup, and install Windows. Once Windows 2000 is installed, apply SP4
>>and EnableBigLba in the registry. Then use Disk Management to create
>>additional partition(s) on the disk.
>>
>>Once the 500GB disk is fully partitioned, Windows 2000 setup won't
>>work properly, because it can't correctly recognize the partition(s)
>>on the disk. With a 250GB disk, it typically isn't a problem.
>
>Of course, I should have made this clear in my original
>post, but I am NOT trying to install Windows to the large
>disk. I have Windows installed on a small (20 gig) drive,
>and it is running fine.
>
>The large disk if for data only.
>
>Thanks again for any further thoughts,

"Kenneth" <usenet@soleSPAMLESSassociates.com> wrote in message
news:fj064459vfvnr6lcsgvlb4aho2s281rl95@4ax.com...
>
> Howdy,
>
> I run Win 2000 Pro SP4 on one of my systems, and had in it a
> 250 gig Western Digital disk that failed.
>
> I replaced it with a 500 gig drive, but Windows can only see
> 127 gig on that disk.

Are you sure you are on SP4? I encountered a similar problem on a fresh
install of Windows 2000 and the solution was to upgrade to SP4.
--
Brian Cryer
www.cryer.co.uk/brian

Hi Andy,

Please see my comments inline below...



On Sun, 01 Jun 2008 22:46:40 -0700, Andy <1@2.3> wrote:

>On Sun, 01 Jun 2008 20:43:32 -0400, Kenneth

><usenet@soleSPAMLESSassociates.com> wrote:
>
>>On Sun, 01 Jun 2008 17:05:43 -0700, Andy <1@2.3> wrote:
>>
>>Hi Andy,
>>
>>Please see my responses to your comments inline below...
>>
>>
>>>On Sun, 01 Jun 2008 16:19:22 -0400, Kenneth
>>><usenet@soleSPAMLESSassociates.com> wrote:
>>>
>>>>
>>>>Howdy,
>>>>
>>>>I run Win 2000 Pro SP4 on one of my systems, and had in it a
>>>>250 gig Western Digital disk that failed.
>>>>
>>>>I replaced it with a 500 gig drive, but Windows can only see
>>>>127 gig on that disk.
>>>
>>>What part of Windows are you talking about? Windows Explorer? Disk
>>>Management? Windows setup?
>>>
>>
>>Disk Management does not "see" the full capacity of the
>>drive.
>>
>>
>>>>
>>>>Here are the things I am sure of:
>>>>
>>>>The bios (the most recent available) sees the disk as 500
>>>>gig.
>>>>
>>>>The registry has the appropriate 48-Bit LBA Support for
>>>>ATAPI Disk Drives. I have checked that both by simply
>>>>viewing the appropriate registry key, and also by running a
>>>>tool that looks in the registry to see if the key is set
>>>>correctly.
>>>
>>>Does Disk Management show the correct capacity for the drive?
>>>Caveat: if the drive is fully partitioned, Disk Management will show
>>>its full capacity even though Windows 2000 may not be configured to
>>>access past 137GB.
>>
>>No, the BIOS does show the drive as 500 gig, but Disk
>>Management has it as 137 gig.
>
>Disk Management showing the drive capacity as only 128GB is sufficient
>proof that your Windows 2000 installation is not properly configured
>to support 48-bit LBA.
>
>>
>>>
>>>>
>>>>I have partitioned and formatted the disk.
>>>
>>>Using what software?
>>
>>I have tried three different approaches:
>>
>>Windows itself, the Western Digital Installation software,
>>and Acronis Disk Director. All of these run under Windows,
>>and all see the disk as 137 gig.
>
>This means that your Windows 2000 installation is limited to 28-bit
>LBA.

Well yes, that would appear to be correct, but...

The appropriate LBA reg key is where it should be, and also,
prior to putting in this large disk, I had another (250 gig)
in the bay working fine.


>
>>
>>>
>>>>
>>>>I have tried to add another partition, but (beyond the 127
>>>>gigs) there is no extra space available for such a
>>>>modification. I made this attempt using the Western Digital
>>>>supplied tools, and also using Acronis Disk Director. The
>>>>results were the same.
>>>>
>>>>Also, after too many calls to Western Digital Tech "Support"
>>>>I thought that the disk itself may be defective.
>>>>
>>>>I replaced it with another, and the results are exactly the
>>>>same.
>>>>
>>>>Might you have some suggestions about an appropriate next
>>>>step?
>>>
>>>Partitioning or recognition of disk capacity during Windows 2000
>>>setup: regardless of BIOS capability or Service Pack level incorported
>>>in the Windows 2000 CD, only 131,000 MB will be recognized.
>>>
>>>Once Windows 2000 has been installed on the hard drive: in order for
>>>Windows 2000 to see past 137GB on the disk, Service Pack 3 or 4 must
>>>be installed, and EnableBigLba = 1 has to be added to the registry.
>>>
>>>The proper way to install Windows 2000 on a large disk is to start
>>>with an unpartitioned disk. Create a single partition during Windows
>>>setup, and install Windows. Once Windows 2000 is installed, apply SP4
>>>and EnableBigLba in the registry. Then use Disk Management to create
>>>additional partition(s) on the disk.
>>>
>>>Once the 500GB disk is fully partitioned, Windows 2000 setup won't
>>>work properly, because it can't correctly recognize the partition(s)
>>>on the disk. With a 250GB disk, it typically isn't a problem.
>>
>>Of course, I should have made this clear in my original
>>post, but I am NOT trying to install Windows to the large
>>disk. I have Windows installed on a small (20 gig) drive,
>>and it is running fine.
>>
>>The large disk if for data only.
>>
>>Thanks again for any further thoughts,


All the best,
--
Kenneth

If you email... Please remove the "SPAMLESS."

On Mon, 2 Jun 2008 10:55:14 +0100, "Brian Cryer"
<not.here@localhost> wrote:

>"Kenneth" <usenet@soleSPAMLESSassociates.com> wrote in message
>news:fj064459vfvnr6lcsgvlb4aho2s281rl95@4ax.com.. .
>>
>> Howdy,
>>
>> I run Win 2000 Pro SP4 on one of my systems, and had in it a
>> 250 gig Western Digital disk that failed.
>>
>> I replaced it with a 500 gig drive, but Windows can only see
>> 127 gig on that disk.
>
>Are you sure you are on SP4? I encountered a similar problem on a fresh
>install of Windows 2000 and the solution was to upgrade to SP4.

Yup... It is SP4.

Thanks for any further thoughts,
--
Kenneth

If you email... Please remove the "SPAMLESS."