And this goes to say.. most problems are easily corrected by a format, but formatting isn't always the best or quickest move.

Waiting a day or two and asking around could solve you a week of backing up+reformatting+reinstalling windows+reinstalling your apps+restoring files

Appreciate what you say about re-formatting, but as the problem is occuring when doing this, it is very pertinent to this thread, in fact, it is the crux.

OK - I have spent hours on this, and I am certain I know the problem, but unfortunately, not the solution. According to Microsoft Knowledge Base, the error comes up after Verify DMI Pool when you try to load XP onto an IBM Hard Drive over 33GB, where the BIOS is Award 4.5. I now think this applies to ANY Hard Drive over 33GB. I have now used a combination FOUR Mobos, and THREE Hard Drives - an IBM 10gB, IBM 60gB and Maxtore 80gB (you see what I mean by hours). 3 Mobos are Award BIOS, one is AMI (American Megatrends). I was able to successfully load the following combinations - Awards BIOS and 10gB, and AMI BIOS and 60gb and 80gb. 3 x Award boards gave the error whether it was with the 60 or 80. Furthermore, when I tried to UPGRADE after loading ME first, it still failed, and when I re-formatted, the FDISK read the drive as 30GB, not 60gB. Even trying to use the 60GB with an Award boar after having successfully loaded XP using AMI, I still got the error.

The only way to fix this for yourselves, and I stand by this, is to get a MOBO running BIOS other than Award, or to use a 30GB or less HDD. Alternatively, does anyone know the number for the Award people The MS KB seems to think it's an IBM problem - I disagree.

I'm using Windows XP, Award BIOS on some systems, and drives in excess of 32Gb with no problems.

Are these drives being partitioned and formatted FAT32 with FDISK? If so, why? The Windows XP CD will partition and format the drives, and use NTFS as well. IF FDISK is used to create partitions over 32Gb, then problems can result, as XP doesn't like FAT32 volumes in excess of 32GB, and rightfully so, as they are innappropriate to use.

In this particular instance, Windows XP is quite possibly having problems starting as well because of the change in drive controller. Was the XP installation reset first to use generic IDE controllers, before the controller card was installed and the drive connected to it?

Can't you flash the BIOS to the latest version that has it in its fix list?

This thread is better than going and reading some maddox, really quite entertaining.

Well, I have another suggestion. Grab and install Smart BootManager, an open source boot manager. Smart BootManager features an option for "Toggled Extended Int 13H". Extended Int 13H lets us get past some HD Size barriers.

Its easy to install Smart BootManager; download the two files (sbminst.exe and cwsdpmi.exe) and place them on a startup disk. Boot up on the disk, and run the command:
Answer yes to the question asking you if you want to install, and you're set. Just reboot the PC and right after your BIOS loads, Smart BootManager will display.

I had the same problem and just changed in BIOS the IDE Access MODE to LHA, before it was AUTO (LARGE).

The funny think is that I had Windows installed on that Hard Disk (Seagate 80GB) and just tried to install the same Windows but in spanish...

Hi Zagith

My 20gb Master Hdd fell over not long ago and just bought a Maxtor drive and I put it in to be the Master. Then I set it up and then it had to do the first reboot and after doing the dmi Data Pool it said Error Loading Operating System. I have tried everything under the sun to fix it and I am now looking on the internet.

wow your dmi datapool told you?? sorry, but the dmi data pool doesn't tell you, post tests are telling you theres an error with the dmi data pool..

Clearing CMOS worked for me...