200GB hard drive config-FIXED

[MojoKrunch]

On an ABIT KT7Raid board with 80GB primary, 80GB slave on High Point headers.
200GB is on ATA100 card header 1.

200GB WD in XP Pro(all SPs and updates) Computer Management only shows up as 128GB.
I used my snazzy glow in the dark cable instead of the included cable, but I'm pretty sure it is ATA100 capable.
Could this be the problem or is this something else?

First I installed the hd on the HP secondary header but then installed the ATA100 card after hd only showed as 128GB in Computer Management.
Instead, I'm getting same 128GB... according to the instructions from WD all I needed to do was install the card and drivers and all would be loverly.

I figured someone here could point me in the right direction.
Thanks.

EDIT:
Doh!
Egg on my face.
Talked to WD Tech Support(quick, friendly, effecient).
It seems I didn't install the Promise UltraATA drivers correctly... you have to force XP to use *not* use its drivers.

Thanks for the help guys.

brett

 

[rbV5]

Was it already formatted? If you are using XP SP1, you may have to just delete and recreate the partition within Computer Management if it was created without 48bit LBA.....as long as you are using NTFS.

 

[MojoKrunch]

Was it already formatted?

I believe it was.
I know I didn't format it and it was recognized in Computer Management as "unallocated".

If you are using XP SP1, you may have to just delete and recreate the partition within Computer Management if it was created without 48bit LBA.....as long as you are using NTFS.

Sounds good.
I'll give it a shot.

Ok, I created a new partition under Computer Management but it was only 128GB, so I deleted it.

Will I have to format it using the Data Lifeguard Tools disk supplied by WD?

Thanks
brett

 

[lobadobadingdong]

does your ata100 card support 48-bit addressing? it may be as simple as getting a different eide card.

 

[MojoKrunch]

does your ata100 card support 48-bit addressing? it may be as simple as getting a different eide card.

It was the card supplied with the drive, so I hope it does.

brett

 

[crisp82]

does the Bios see 200Gb of the drive?
Does the Mobo support over 137gb HDs?
Have you flashed the bios?
Is it seen in DiskPart as 2 seperate partitions, or 1 128gb and 72 unpartitioned space?

 

[MojoKrunch]

does the Bios see 200Gb of the drive?

Because the drive is attached to the ATA100 card, it isn't under the BIOS setup screen anywhere, but the ATA100 screen definitely shows it as 187GB.

Does the Mobo support over 137gb HDs?

This might be the problem.
It is an ABIT KT7Raid board and is over 3 years old, so....

Have you flashed the bios?

IIRC, I have the newest BIOS update installed... but that might not mean much.

Is it seen in DiskPart as 2 seperate partitions, or 1 128gb and 72 unpartitioned space?

No, only as one 128GB block.

I suspect I may be SOL because of the MB, so I'll need to look into this a bit more.

Thanks

brett

 

[EeyoreX]

does the Bios see 200Gb of the drive?

Because the drive is attached to the ATA100 card, it isn't under the BIOS setup screen anywhere, but the ATA100 screen definitely shows it as 187GB.

Does the Mobo support over 137gb HDs?

This might be the problem.
It is an ABIT KT7Raid board and is over 3 years old, so....

I suspect I may be SOL because of the MB, so I'll need to look into this a bit more.

The motherboard is certainly not the problem. Since you are bypassing the motherboard and using the ATA controller card. That is the entire point of the controller card in this case, to allow an older computer that does not support the large hard drive to use it via the card.

The 187GB the controller recognizes is correct, so the problem is obviously in the software, not hardware. The disk is being shown at its proper formatted size in the controllers BIOS. It seems your Windows is not properly updated to recognize 48-bit addressing. The Microsoft Knowledge base is a good place to look. Here is the pertinent article for ensuring 48-bit addressing is properly enabled in Windows XP.

\Dan

 

[MojoKrunch]

Dan, buddy, I think you're on to something!

It seems your Windows is not properly updated to recognize 48-bit addressing.

Which is odd because I'm showing SP 1 installed and I *know* I install every hot fix as it comes down the line.

The Microsoft Knowledge base is a good place to look. Here is the pertinent article for ensuring 48-bit addressing is properly enabled in Windows XP.

Checked out the article and sure enough I was using an "older" version of Atapi.sys.
So I DLed the app from Article 331958 and ran it.
Restarted and checked the Atapi.sys number and it was 5.1.2600.1135... just like it said it should be.

Unfortunately, this didn't fix the problem.
DM still only reads it as 128GB.

I did see this and checked the registry:
"For the original release of Windows XP Home Edition or Windows XP Professional, 48-bit LBA could be enabled for testing purposes by setting a registry value, named EnableBigLba, to 1 in the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Atapi\Parameters\"

EnableBigLba is *not* in the Parameters folder in my registry.
Can I/should I simply add this string to my registry?

The fix in the article looked way too complicated for me and I'm wondering if I need to get in touch with Microsoft.

This copy of XP Pro was from some discount promo package and came with a baseball and a bobblehead doll... so I'm wondering if maybe that doesn't have something to do with it.
lol

Thanks for the help.

brett