Computer HELP! New motherboard

[MagicFingers]

I installed a new MB and processor, P4, 2.66mhz, and new mem, ddr400
It sees my HD, and will boot to a win98 floppy, but it will not boot to the HD.
The HD is 60GB IBM, IDE, ATA 100?

Do I have to run the CD that came with the MB to get it to boot up?
The disk is GOOD! and I have reason to believe the new parts are good.
The OS is Win XP Pro, and I also have W2k Pro on the disk what fails with a stop error 7f, I think.

Any experts out there know what I can do to solve this?
Thanks.

 

[TBKahuna123]

If you have a good OS on the hard disk it should boot, unless it's not recognizing the HDD. There are a couple reasons this could be:

Your HDD is set to cable select and the cable is now calling it a slave instead of a master.
Your HDD cable isn't all the way in or the power cord isn't in.
You may need to go into the BIOS setup and make sure LBA support is enbabled if you have a big HDD.
You may need to specify your boot device in the bios. It may only be set to boot from Floppy or CD. Uncommon, but not unheard of.

I'd first chek your POST and see if the HDD is being recognized, then go from there.

 

[MagicFingers]

HDD is recognized ok

in the bios. I've tried LBA, LARGE, AUTO,
The boot devices are ok.
I've turned SMART on and off, tried another cable, and another disk with XP pro. I know it has something to do with the new MB not auto configuring the HDD??? maybe?

Oh, and I tried fdisk /mbr - no help

 

[DemonOuterverse]

Hang on BigKahuna, he mentioned "Stop Error 7F". I'm wondering if he's actually able to boot the computer, but getting a BSOD saying "stop error 7F,8 unexpected kernal mode trap".

If THAT's the case, it's usually an issue with the memory not being seated (According to Microsoft).

If it's saying that before it boots to Windows, then yeah I'd go with what you said.

 

[MagicFingers]

Actually, that was booting W2000 pro

Hang on BigKahuna, he mentioned "Stop Error 7F". I'm wondering if he's actually able to boot the computer, but getting a BSOD saying "stop error 7F,8 unexpected kernal mode trap".

If THAT's the case, it's usually an issue with the memory not being seated (According to Microsoft).

If it's saying that before it boots to Windows, then yeah I'd go with what you said.

It was a stop error 7b, innaccessable boot device, even though I know the disk and cable are good, and I've tried 2 MBs, 2 processors, 2 memories, 2 memory slots.

HELP!

 

[popcorn2721]

I installed a new MB and processor, P4, 2.66mhz, and new mem, ddr400
It sees my HD, and will boot to a win98 floppy, but it will not boot to the HD.
The HD is 60GB IBM, IDE, ATA 100?

Do I have to run the CD that came with the MB to get it to boot up?
The disk is GOOD! and I have reason to believe the new parts are good.
The OS is Win XP Pro, and I also have W2k Pro on the disk what fails with a stop error 7f, I think.

Any experts out there know what I can do to solve this?
Thanks.

I would check all your connections again...sounds like a serial (or IEE) cable isnt plugged in all the way. I think I would make sure its not an issue in the boot sector of your hard drive...Ive seen windows do some crazy shit when swapping drives from one puter to another. Put this drive in another puter and format (read FDISK) it...then just before the first boot (when windows reboots) swap it into this one. This is how I do it on PCs with no CD drive (Ive lost a few drives over the years)

 

[Weird Harold]

It sees my HD, and will boot to a win98 floppy, but it will not boot to the HD.
The HD is 60GB IBM, IDE, ATA 100?

What else is on the same controller as the HD? Both physically connected, and according to the BIOS.

This sounds like a device conflict -- i.e. two devices jumpered as master or drives, or two incompatible devices (HD and CD on the same cable.)

Are you sure that you have the BIOS configured to boot from that hard drive in the proper boot sequence. I've had problems with a Floppy/CD/HD boot sequence with the system hanging up trying to boot from a CD and never skipping on to the HD. Try setting the boot sequence to HD:0 only.

If you have another computer you can patch the drive into to compare how the BIOS should be set up with what the new MB is detecting, that might be helpful.

I suspect that you may wind up having to re-format the drive before it will boot unless you can figure out the BIOS settings and manually set them to match the parameters the drive was originally formatted under. The cylinders/sectors/heads informationin the BIOS is generally NOT what the drive physically has, it's a translation to a "virtual configuration" and won't always be the same with one BIOS as it is with another. That virtual configuration has to be the same as the drive was formatted under before the MB can find and read the boot sector.

First eliminated any device conflicts by disconnecting everything except the HD and see if it will boot.

Second, check the BIOS setting as detected by the new MB with the BIOS settings on a MB that the drive will boot from (if it will boot with any MB.)

Finally, if all else fails, do a complete FDISK and unconditional format as if it was an empty drive.

 

[TBKahuna123]

Lots of good info here.

Here's a question we haven't asked: Does thsi new board support ATA 100? You didn't mention if it was a brand new board or just a replacement.

RAM seating could be a problem. Here is how I usually do this. Strip the machine. Start by trying to boot with just a processor and RAM. Obviously this won't get you far but you'll at least get a POST beep. Then start adding components one at a time until you get a conflict. This will rule everything out for device conflicts.

Now that might be going too far because youa re getting past the POST screen. Have you tried booting to a bootable CD? Next try removing the CDROM and FDD and just having your HDD> That will tell you if it's a device conflict.

 

[litdude]

You're pretty close to screwed. It was an unwise course of action. Motherboards swaps out are a turd of a problem because: you have now given the OS a new hard drive controller underneath, but the code that it had for the old motherrboard's hdctlr is different than your new. I've seen this even when putting the same model motherboard in, but having just a rev B to rev C difference in an IO chip on it.

Solution1: mount your hard drive in some other pc as a second drive and pull off all your pertinent data. then back to the original and reformat and load fresh.

For a teeny bit of hope...
(after you read everything, and have your data backed up maybe as in solution 1, try solution 2)

Solution 2: look up doing the repair reinstalls - which is booting your winxp cd and hitting R at the appropriate points. I believe this does works but I forget the exact specifics of whether you have to load the new controller codes at the point when asked (in the beginning).

 

[MagicFingers]

Thanks, popcorn

I would check all your connections again...sounds like a serial (or IEE) cable isnt plugged in all the way. I think I would make sure its not an issue in the boot sector of your hard drive...Ive seen windows do some crazy shit when swapping drives from one puter to another. Put this drive in another puter and format (read FDISK) it...then just before the first boot (when windows reboots) swap it into this one. This is how I do it on PCs with no CD drive (Ive lost a few drives over the years)

I'd really like to hear more about this, as I've heard something similar before.
HOWEVER, if I fdisk it, all data will be wiped out and that's what I was trying to avoid. (Good thing I have backed up my ~1gb or porn and stories to CDs!)
Did you really mean it to sound like this, or is there another way to get this old dick to boot without wiping it out?

 

[MagicFingers]

Thanks, litdude

You're pretty close to screwed. It was an unwise course of action. Motherboards swaps out are a turd of a problem because: you have now given the OS a new hard drive controller underneath, but the code that it had for the old motherrboard's hdctlr is different than your new. I've seen this even when putting the same model motherboard in, but having just a rev B to rev C difference in an IO chip on it.

Solution1: mount your hard drive in some other pc as a second drive and pull off all your pertinent data. then back to the original and reformat and load fresh.

For a teeny bit of hope...
(after you read everything, and have your data backed up maybe as in solution 1, try solution 2)

Solution 2: look up doing the repair reinstalls - which is booting your winxp cd and hitting R at the appropriate points. I believe this does works but I forget the exact specifics of whether you have to load the new controller codes at the point when asked (in the beginning).

You should post more often than once every 2 months. You have some good knowledge.

Well, I haven't posted because I've been down, and working hard too. I tried fdisk /mbr and that didn't work. I managed to borrow a 40gb HDD and an XP-PRO cd and it loaded and ran with no problems. So, WH and TBKahuna, thanks for your suggestions, but I had tried most of them before posting without success. I had put it back into my old MB and it worked fine, so I knew it was good. And I went to Fry's and demanded they replace all their garbage with upopened garbage (if you know what I mean here).

SO, the problem is as litdude suggests, that the drivers are so different from my old motherboard to the new one that it won't even boot up enough to get to the point where it loads the new ones automatically. I even tried the CD that came with the MB but it wouldn't boot either! IT ONLY WORKS WITH WINDOWS! Can you believe it? The drivers are all there but I can't get them into the HDD!

So I have this borrowed disk with bare Win XP on it and my old HDD hooked up as the slave. I can see everything on it just fine. I really hate to rebuild everything onto a new drive but that's what I'm looking at doing right now. My friend said I could KEEP the disk he let me borrow to test it! He's my new best friend! I got all the Windows updates, anti-virus, anti-malware programs, Office, Lit & Xnews running, so I have the basics of life. lol

I have thought of doing the Repair-Install, but am afraid to do it. I have tried something like this before and it wiped out everything. If you know that it will work with XP-Pro, I can do it. I do have the official CDs for it.
Any more info on this process?
Thanks to you all for your kind and thoughtful replies. I know of no better place to go to for help than right here.
Gracius, merci, Kob khun krap, etc.