i still get the same message. "Searching for Boot Record from IDE-0...OK"i might try using a new IDE cable &trying CHKDSK, Fixboot &/or Fixmbr (or Fdisk /MBR) after posting here.

but i'd like to get your opinion first...i tried this 'problem hard disk', using the same IDE cable, in another PC ---- before AND after trying it in the 'problem PC'..... it worked normally, the other PC boots ok..is it safe to say that the problem lies in the 'problem PC'?perhaps, the BIOS chip or the motherboard is broken/dead?any suggestions/advice?

I have a feeling there's something missing to your story. This is the original drive that was in the system, right? It's not a transplant from another PC?

Unless you were getting some sort of message about the CMOS battery, changing it was probably a waste of time. Also, when you change the battery, it automatically resets all the BIOS settings to the defaults, so "loading default settings" wasn't necessary because it was already done. You have to realize that defaults are NOT good performance settings, they are just a starting point. You need to double check the settings & correct any that are out of whack.

Check the master/slave jumper on the rear of the drive to make sure it's set correctly. If you have two drives on the same IDE cable, the HDD with Windows MUST be the master & the other drive MUST be the slave. If the HDD is a Western Digital, there *may* be separate jumper settings for master (single) or master (with slave), so make sure you get it right.

If the drives are being properly recognized in the BIOS, try fixmbr & fixboot like you mentioned.

i apologize for an impulsive post.it was also late at night when i posted.

i bought a used Seagate barracuda 120 gb (model? 3120022a ) from a friend.i reformatted it, installed Windows XP Pro . this was on the 'other PC' (let's call it 'PCa'). it did ok with an 80- & 40-conductor IDE cable.

the plan is to use this hard disk on my PC (the 'problem PC'; call it 'PCb').so i transferred the hard disk to PCb, using PCb's 80-conductor IDE cable.(during this process, no other hard disks were installed, on both PC's)like i told u, & to my surprise, it did not boot ok on PCb.... giving me the message "Searching for Boot Record from IDE-0...OK"

after a few re-boots, it still showed the same message. then i noticed in the BIOS setup:1. the hard disk shows up as number 2 in the "boot device priority" menu, number 1 is "Disabled". i put the hard disk on number 1, the rest i put on 'disabled'. (Note that on POST, the hard disk shows up as 'Primary Master')2. later on, i noticed the date/time on BIOS setup is outdated. this made me think, & with viewing other articles on the web, that it possibly is a sign that the CMOS battery is dead/dying (remember, PCb is 5-6yrs old now).so i decided to replace it yesterday with a new one. {after my post last night, & reading mickliq's post, i realized that changing the CMOS batt & 'loading default settings' was like 'doing the same thing differently'.}

changing the CMOS batt & 'loading default settings' --- these were solutions mentioned on the web. it did not help, in my case.

to confirm my hunch, i transferred the hard disk, using PCb's IDE cable, back to PCa....-i did not do any changes (jumper, etc).-i did not removed the IDE part connected on the hard disk.my hunch was confirmed: the hard disk does work on PCa. (this is what i meant with "I tried this 'problem hard disk', using the same IDE cable, in another PC ---- before AND after trying it in the 'problem PC'..... it worked normally, the other PC boots ok.").in other words, using 3 IDE cables (1 40-conductor & 2 80-conductor IDE cables), the hard disk worked in PCa.

having said that, these are the other possible solutions/conclusions:-i bought a new IDE cable. will try that later.-change the jumper settings.-the asrock mobo has 2 IDE 'sockets'. i'll try connecting the IDE on 'IDE socket 2'.-like in my first post, i think it's possible that the hard disk is not the problem, but the BIOS chip or motherboard. there were articles that talk about reflashing the BIOS as solution, but i think it might just worsen the problem, &/or it's more practical to buy a new mobo or PC.

any other thoughts/solutions?thank you very much everyone, mickliq & OtheHill!God bless!

OtheHill,if i reinstall Windows XP on the 120gb HD,will the 120gb capacity be reduced?will the data inside the HD be deleted?

"You can't install WinXP on a hard drive installed in one PC then move the hard drive to another PC and expect it to boot. This is by Microsoft design."im confused.how come another HD i tried before has booted ok on my PC (the 'problem PC'; 'PCb')?

First off, Microsoft doesn't want you to use the same copy of Windows on multple PCs.

Second, the hardware on PCa is different than PCb, causing the boot failure for lack of correct drivers.

If you do get a hard drive to boot after migrating it from one PC to another it is most likely because the core components are very similar. Don't confuse booting to a hard drive with installing a second hard drive and booting.

There is something called 28 bit LBA compliance and also 48 bit LBA compliance.

Hard drives have gotten progressively larger capacity since the first PC version. The two most recent standards for capacity involve the afore mentioned compliance.

Both the BIOS and the operating system must be 48 bit LBA compliant. WinXP original was only 28 bit LBA compliant.

Finally, hard drive manufacturers advertise capacity using the formula that 1000 kb = 1 MB. In actuality the formula is 1024kb = 1MB. This results in a shortfall in actual capacity. The rule of thumb is to multiply the stated capacity (120GB) by .93 to get the approximate usable capacity.

Assuming you configure the 120GB correctly it should work fine for you and show as about 111GB. Look at the link below for more on 48 bit LBA.

The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this
site. Computing.Net and Compnet Ventures, LLC hereby disclaim all responsibility
and liability for the content of Computing.Net and its accuracy.