Windows can't see large disk... (but used to)...?

[Guest Kenneth]

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."

[Guest DL]

Re: Windows can't see large disk... (but used to)...?

 

Was this your boot disk or a slave you replaced?

 

"Kenneth" <usenet@soleSPAMLESSassociates.com> wrote in message

news:r216449jnn18k5vcmofrdjo4p0k007lb2t@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.

>

> 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."

[Guest Kenneth]

Re: Windows can't see large disk... (but used to)...?

 

On Sun, 1 Jun 2008 21:23:42 +0100, "DL" <address@invalid>

wrote:

>

>"Kenneth" <usenet@soleSPAMLESSassociates.com> wrote in message

>news:r216449jnn18k5vcmofrdjo4p0k007lb2t@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.

>>

>> 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."

>

>Was this your boot disk or a slave you replaced?

 

Howdy,

 

It is a slave, used only for data...

 

Thanks for any ideas,

--

Kenneth

 

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

[Guest nesredep egrob]

Re: Windows can't see large disk... (but used to)...?

 

On Sun, 01 Jun 2008 16:20: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.

>

>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,

 

If all is as you say it can only be the LBA. Despite you have what you see, it

may not be working, just try this, really it is your last way to make it work. I

say that as I had 320 GB working and a 750 was not working until I did this

trick:

 

Start/run/regedit

(if unsure export registry for safety)

select HKEY_LOCAL_MACHINE

navigate to system/services/atapi/parameters or

system/currentcontrolset/services/atapi/parameters

right click for new

Select Dword name it EnableBigLba (take note of case)

set value to 1

end regedit

reboot

 

B|rge in sunny Perth, Australia

[Guest Kenneth]

Re: Windows can't see large disk... (but used to)...?

 

On Mon, 02 Jun 2008 07:49:47 +0800, nesredep egrob <Long.

-31,48.21 Lat. 115,47.40> wrote:

>On Sun, 01 Jun 2008 16:20: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.

>>

>>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,

>

>If all is as you say it can only be the LBA. Despite you have what you see, it

>may not be working, just try this, really it is your last way to make it work. I

>say that as I had 320 GB working and a 750 was not working until I did this

>trick:

>

>Start/run/regedit

>(if unsure export registry for safety)

>select HKEY_LOCAL_MACHINE

>navigate to system/services/atapi/parameters or

>system/currentcontrolset/services/atapi/parameters

>right click for new

>Select Dword name it EnableBigLba (take note of case)

>set value to 1

>end regedit

>reboot

>

>Børge in sunny Perth, Australia

 

Hi Børge,

 

I thank you for your suggestion, but have already done just

what you describe.

 

Are you suggesting that I remove the key, and re-enter it?

 

Thanks again,

--

Kenneth

 

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

[Guest DL]

Re: Windows can't see large disk... (but used to)...?

 

If I read you correctly, you stated you created & formated a partition of

137gb, and after rebooting, only this partition was avilable & disk

management showed no free space to create a further parition.

If that is the case there is something other than big LBA going on - what I

cannot think

 

"DL" <address@invalid> wrote in message

news:%23UIkgVCxIHA.4492@TK2MSFTNGP02.phx.gbl...

> Was this your boot disk or a slave you replaced?

>

> "Kenneth" <usenet@soleSPAMLESSassociates.com> wrote in message

> news:r216449jnn18k5vcmofrdjo4p0k007lb2t@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.

>>

>> 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."

>

>

[Guest Kenneth]

Re: Windows can't see large disk... (but used to)...?

 

On Mon, 2 Jun 2008 07:52:14 +0100, "DL" <address@invalid>

wrote:

>If I read you correctly, you stated you created & formated a partition of

>137gb, and after rebooting, only this partition was avilable & disk

>management showed no free space to create a further parition.

>If that is the case there is something other than big LBA going on - what I

>cannot think

 

Hi DL,

 

Could you say something more about this...?

 

I ask because it seems to me that Windows is "ignoring" the

LBA key.

 

Is that what you meant when saying something else is going

on?

 

(I will add that minutes ago, I looked at the reg key yet

again, and it looked fine. But then, I changed it from "1"

to "0" and ran a tool that "tests" then entry. The tool

showed a "failure" and gave the option to correct the

setting. I did that to allow the tool to modify the entry

[thinking that somehow, I might be entering something

incorrectly], but its entry looked just like mine. In any

case, I still have the problem.)

 

Thanks again,

--

Kenneth

 

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

[Guest Kenneth]

Re: Windows can't see large disk... (but used to)...?

 

On Sun, 01 Jun 2008 20:08:11 -0400, Kenneth

<usenet@soleSPAMLESSassociates.com> wrote:

 

Hello again,

 

I eventually spoke with a grown-up tech at Western

Digital...

 

He listened to my detailed description and then said:

 

"I'd suggest that you look for a driver update for your ATA

controller."

 

I did that and am now formatting all of the 500 gig drive.

 

(I still don't understand how I was successfully using the

250 gig drive that I had in the box last week, but that is

not the important thing right now.)

 

Thanks to all who helped,

--

Kenneth

 

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

[Guest DL]

Re: Windows can't see large disk... (but used to)...?

 

Glad its sorted

 

"Kenneth" <usenet@soleSPAMLESSassociates.com> wrote in message

news:2ap744t4crhbcteo4pl93a3jkqkr08ptu5@4ax.com...

> On Mon, 2 Jun 2008 07:52:14 +0100, "DL" <address@invalid>

> wrote:

>

>>If I read you correctly, you stated you created & formated a partition of

>>137gb, and after rebooting, only this partition was avilable & disk

>>management showed no free space to create a further parition.

>>If that is the case there is something other than big LBA going on - what

>>I

>>cannot think

>

> Hi DL,

>

> Could you say something more about this...?

>

> I ask because it seems to me that Windows is "ignoring" the

> LBA key.

>

> Is that what you meant when saying something else is going

> on?

>

> (I will add that minutes ago, I looked at the reg key yet

> again, and it looked fine. But then, I changed it from "1"

> to "0" and ran a tool that "tests" then entry. The tool

> showed a "failure" and gave the option to correct the

> setting. I did that to allow the tool to modify the entry

> [thinking that somehow, I might be entering something

> incorrectly], but its entry looked just like mine. In any

> case, I still have the problem.)

>

> Thanks again,

> --

> Kenneth

>

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

[Guest nesredep egrob]

Re: Windows can't see large disk... (but used to)...?

 

On Sun, 01 Jun 2008 20:08:11 -0400, Kenneth <usenet@soleSPAMLESSassociates.com>

wrote:

>On Mon, 02 Jun 2008 07:49:47 +0800, nesredep egrob <Long.

>-31,48.21 Lat. 115,47.40> wrote:

>

>>On Sun, 01 Jun 2008 16:20: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.

>>>

>>>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,

>>

>>If all is as you say it can only be the LBA. Despite you have what you see, it

>>may not be working, just try this, really it is your last way to make it work. I

>>say that as I had 320 GB working and a 750 was not working until I did this

>>trick:

>>

>>Start/run/regedit

>>(if unsure export registry for safety)

>>select HKEY_LOCAL_MACHINE

>>navigate to system/services/atapi/parameters or

>>system/currentcontrolset/services/atapi/parameters

>>right click for new

>>Select Dword name it EnableBigLba (take note of case)

>>set value to 1

>>end regedit

>>reboot

>>

>>B|rge in sunny Perth, Australia

>

>Hi B|rge,

>

>I thank you for your suggestion, but have already done just

>what you describe.

>

>Are you suggesting that I remove the key, and re-enter it?

>

>Thanks again,

 

 

If it still does not work, is seems not to be too daft an option

 

B|rge in sunny Perth, Australia