Question about 137GB limitations and such

[sprockkets]

I came across a very weird issue with Windows 2k and XP. My sister recently bought a 160GB hdd for her computer. Currently it is an Intel 845G ATX board with a 1.8ghz P4 Northwood.

I put in the hdd, yet her computer, while realizing it was a 160GB hdd, couldn't read it. It kept saying it was not formated, but that isn't true since I formated it on my computer and was just fine. I already did the fix for XP for enabling the 48 bit LBA, and updated the BIOS as well. What is odd is that there is no issue with doing anything else on the other hdd.

Using Linux on that same computer with Knoppix was ok, it has no issues with the HDD.
I tried installing Windows XP w/ sp2 yet it also said while it could see the hdd, it couldn't format it for use.

Oddly enough, the solution to the issue was just to install the Intel AA Drivers, or in other words the IDE drivers for windows. Then all was ok.

But this brings up my question then. How can you install windows to that 160GB disk? You wouldn't use a raid driver, right? Do I add the Intel AA drivers somehow? No where is this discussed, as far as I can tell.

This also brings up another issue. Since linux has the kernel module or library "PIIX" to work with the latest chipsets from Intel, it doesn't have this issue. But does this mean that accessing any drive bigger than 137GB requires special drivers so it can work? Does this mean that legacy access or legacy low level drivers which enable any OS to work with any chipset IDE controller only works up to 137GB?

 

[sprockkets]

bump

 

[DAPUNISHER]

I have seen WD list the IAA fix for older Intel chipsets before. Some options for initial setup include-

1. Slipstreaming the drivers into the install CD. Obviously having another system with burner is needed to accomplish that since we haven't done the build yet.

2. The HDD maker should have a FDD bootable utility that allows you to format and partition the drive, thus preparing it for the windows install.

3. Use/keep a cheapo PCI ATA controller in your "bag of tricks" for just such occassions.

 

[BadThad]

Why not just partition the drive and end all your problems?

 

[stevty2889]

If you wanted to install windows to the 160gb drive, and have it fully recognized, you would need to have a windows xp cd with service pack 1 or 2. Otherwise you could probably partition and format it using the hard drive manufactures utilites prior to installing windows, or you could make a slipstreamed windows cd with one of the service packs. For win2k I think it's service pack 4 that enables the large drive support.

 

[Blake]

I think you need a board that supports 48-bit Logical Block Addressing (LBA) for drives larger than 137GB. Some boards may allow you to update to newer bios that supports 48-bit Logical Block Addressing (LBA).

I had an Intel board with an 845 chipset that I wanted to use for a 2005 Windows Media Center Edition Computer with a 320 gig harddrive. The 845 board didn't support 48-bit Logical Block Addressing (LBA) so I used an Asus P4P 800-E Deluxe that had support for the 48-bit Logical Block Addressing (LBA). The large harddrive worked with no problem.

 

[BadThad]

Originally posted by: Blake
I think you need a board that supports 48-bit Logical Block Addressing (LBA) for drives larger than 137GB. Some boards may allow you to update to newer bios that supports 48-bit Logical Block Addressing (LBA).

I had an Intel board with an 845 chipset that I wanted to use for a 2005 Windows Media Center Edition Computer with a 320 gig harddrive. The 845 board didn't support 48-bit Logical Block Addressing (LBA) so I used an Asus P4P 800-E Deluxe that had support for the 48-bit Logical Block Addressing (LBA). The large harddrive worked with no problem.

Exactly! Good post! :thumbsup: