AHHHHHH! JUST GOT RMA MOBO BACK FROM NEWEGG...SAME PROBLEM!!!

[Loobusk]

If it's not a WD drive then it's most likely because you have a MSI board

That kind of comment is just about funny as your name DAPUNISHER (ie not funny at all)
so keep it to yourself and don't be misleading the guy any further for godsakes. MSI boards are just fine.

 

[Mavrick007]

Before you go cutting wires, try running the drive on cable select. I had a problem on my new nforce2 board with a WD 1200JB drive.
It would boot with the XP cd, and installed fine, although the post screen seemed to take forever (about 5 mins), and then on a reboot I got a disk boot error..
but with the cd in, it would boot back up. I was going to try the hd in another computer to see if it would boot from it but just before this I looked at
the drive and said to my friend "it should work on master, I don't have to use cable select do I?" cause we were both baffled, and it had arrived on
cable select but I have never jumpered a drive to cs before, I always used master or slave.

Well, to make a long story shorter, I put the drive back in and it booted no problem without a cd and the post was only about 10 seconds.

It might not help, but you would be surprised if it did.. I was.

You might have to manually set your cpu to 166fsb in your bios. Yes, there is a jumper for 133/166, but try doing this anyway.
If your cpu came up at 1250mhz then it would be the 12.5 multiplyer x 100mhz. At 133fsb x 12.5 = 1663mhz, ie. a 2000+ cpu.
It seems it didn't select the right fsb, so do it manually, no biggy.

 

[Dug]

Besides all that is mentioned, if you are running Windows XP there is a very good chance you won't be able to boot into it because of having so many different components. It will usually hang before getting anywhere.

You will have to boot to cd first and then reinstall Windows.

 

[m1ke101]

Originally posted by: Booty
I was just about to post the same thing, but figured I'd read through the whole thread to make sure someone else didn't catch it first. Niwi7, I think you need to take a little more time with your builds, pat attention to the details, read the manuals, and make sure you know what you're doing... especially before flipping out.

 

[DAPUNISHER]

Originally posted by: Loobusk

If it's not a WD drive then it's most likely because you have a MSI board

That kind of comment is just about funny as your name DAPUNISHER (ie not funny at all)
so keep it to yourself and don't be misleading the guy any further for godsakes. MSI boards are just fine.

Mislead him further? I told him why his board wouldn't boot with the HDD attached and provided him with both the explanation for why it happens and a very simple fix for the issue so STFU. Furthermore, my low estimation of MSI boards is based on my personal experience with them as a system builder and I will rip on them as the mood comes upon me. You've added nothing constructive to this conversation and I'll thank you not to address me again in the future as I can foresee nothing to be gained by it :evil:

 

[Mitzi]

Originally posted by: DAPUNISHER
If it's not a WD drive then it's most likely because you have a MSI board

I'd just like to add that in my personal experience I've had no problems with a number of MSI products, in fact my current machine is built around a KT3 Ultra and MSI GeForce4.

I certainly doubt the issues niwi7 was encountering were down to his choice in motherboard manufacturer.

 

[chocoruacal]

Originally posted by: niwi7
ok i changed the jumper with the 3 pins to the opposite setting and now it detects it as a 2600

ok thank god! i was so freaked out sorry bout my noobishness


now....any1 have any idea on how to fix my hard drive problem????? maybe ill buy a new one

Uh....some friendly advice...stop being such a pu**y and try "modifying" the stupid IDE cable. And you might want to try reading your motherboard manual before putting a system together, especially since this appears to be your first time performing major PC surgery.

Hmm, so let me get this straight, you are running a CPU with a 166 MHz FSB with RAM that is only rated for 100 MHz (of course these speeds are 333 and 200 DDR respectively). Am I the only one that sees an obvious problem here? Because somehow, I doubt the board has a memory divider that low.

Oh no...you weren't the only one who noticed