Intel 850e and the 137 gig Limit

[wrathofall]

I recently had an HDD death and purchased a new Western Digital 500gig. During my quest to get XP pro SP1 running on the beast, I discovered that there is a 137 gig limit on the motherboard bios. I've searched the internet for answers, but I'm finding myself becoming more confused as I go. I know that flashing the bios is an option, but also that it could kill the motherboard. So, any ideas on how and if I can get XP loaded on a 500 gig HDD? All help and comments are very appreciated!

[jaclaz]

If there is a BIOS update for your specific motherboard, you should use it to update.

The procedure is less risky than probably a few things you do daily or weekly.

Newish motherboards (meaning anything produced since 1998 or 1999 ) have Bios Boot Recovery Block, thus even a bad flash (as said unlikely) can be recovered from.

If you need help on carrying on a Bios Flash, post a link to the motherborad page and/or Bios update, the procedure might be slightly different depending on the type of BIOS.

More info on the 137 Gb limit/LBA48 barrier:

http://www.pcguide.com/ref/hdd/bios/size.htm

http://www.pcguide.com/ref/hdd/bios/sizeGB128-c.html

http://www.pcguide.com/ref/hdd/bios/sizeHandling-c.html

http://www.48bitlba.com/

jaclaz

Edited March 7, 2009 by jaclaz

[wrathofall]

Can I update the bios without an O/S?

Thanks for the links, btw. But I need a "how-to-for dummies" type of thing : )

Edited March 7, 2009 by wrathofall

[submix8c]

Yes, but you have to have a bootable cd/floppy of the Win9x/ME variety. These can be obtained from nearly anywhere on the internet from many trusted sites (be sure it's trusted). One created from XP, even though the option is there to create one, does NOT work (I tried it). It just needs the IO.SYS, MSDOS.SYS, and COMMAND.COM files (delete all others). Then you copy the BIOS update files from the manufacturer and boot to it. Instructions are usually provided at the manufacturer's site.

And be aware that a BIOS update may not help at all (it's a 48-bit LBA problem) so you will need to use the Install CD for your HDD to allow for a Dang-nabbit special MBR DDO code that would be installed.

edit - scratch the Limit thing... 850e should support that (ATA100).

edit2 - boot floppies - http://www.bootdisk.com

edit3 - see jaclaz' post below; pretty good info in there and (FYI) additional links to other stuff.

HTH

Edited March 7, 2009 by submix8c

[jaclaz]

See if this thread is "for-dummies" enough :

http://www.msfn.org/board/index.php?showtopic=127593

jaclaz

[pointertovoid]

To my best knowledge, Xp can use Lba48 independently of the Bios. At least W2k can.

One way would be to install the "Intel Application Accelerator" driver after Xp is installed. It just means that the volume where Xp resides will be smaller than 128GiB - this is good practice anyway.

Another way would be to integrate the registry value EnableBigLba in the installation CD. Explained here for W2k Sp4 : http://home.arcor.de/jterlinden/w2ksp4_128.htm

Even better, use HfSlip to integrate both the Sp2 or Sp3 and the EnableBigLba on your installation CD. Little to do by yourself.

[puntoMX]

or take a look at pointertovoid topic, point (6).

Looks promising, did you try it before pointertovoid?

[pointertovoid]

Todavía no. I want to try it, as I've a W2k on a separate disk just for experiment purposes.

So I'll have observations for i815ep and J8080, which are P-Ata and bring the equivalent of Ncq - J8080 is very efficient on Ncq, it is Excelstor's name for a licensed fabrication of Hitachi's 1680, a 160GB platter with one 80GB face used. If UniAta switches Ncq properly, I'll see it with Atto and W2k.

On the other hand, I've no hardware to test it on S-Ata.

As for 128GiB, my W2k installation Cd are all HfSlip'ed with Sp4 (...and more!) and the EnableBigLba switch, so the driver's effect shouldn't be observable.

HfSlip is anyway the right method. I had to slip the Sp4 because W2k Sp0 installs on a Raid-0 only with certain stripe sizes... Real luck that the support at Silicon Image knew it!