deleted

[KevinAr18]

deleted

 

[Nitrom]

Uhhh take it easy...too many questions.

First of all when you post with this type of problem U must list all the components of the system U R talking about.

List what is new and what is old in separate columns.

I did had the same problem U have and almost went crazy. Until I realize that the connections I made were not done properly. Once I made the proper connections (specially the power cable to the video card and the cables to the Hard drive and optical devices) I turn the machine ON again and still ...nothing...same problem...no video signal.
The trick was then to turn off the machine and TEAK..unplug and plug again every connection until I noticed that there was one connector that did not go all the way in.....
So...I turn the machine ON and BINGO...I had the BIOS screen in front of me...the rest is history.

This doesn't mean you are in the same situation. There are too many variables to consider. First list your components.

 

[endyen]

A great place for you to start, would be to read the post at the top of this forum. It is very informative. A few answers- yes, no , only if you hold your mouth right.
Different mobos treat errors diferently. There are some general truths. You need only a psu, and a mobo to get something out of a system speaker (okay, a speaker as well).
If there is a short anywhere in your system, the psu will imediately shut itself off. In that case, you dont have what is needed to get something out of the speaker.
A lot of mobos have a post reporter, which is a voice that tells you if you have no cpu, ram or if you have let the tea steep to long (well, maybe not the last, but I've heard they are working on that.)
The rest use a simple beep code. A medium length beep means everything is fine.

 

[Crashman]

The only reason a system won't make a beep at all is if it doesn't initialize the CPU. That can be caused by a few things, but the most common are 1.) you have a board that uses a 4-pin ATX12v connector, but the power supply doesn't have it, or you didn't connect it 2.) You're using an old unkeyed IDE cable, and it's connected the wrong way.

<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>

 

[Codesmith]

If something is connected wrong or some device is seriously defective (even a USB device you forgot to disconnect) it can be a showstopper.

Common culprits also include something not 100% inserted in a slot (VGA, PCI, RAM) so that a pin shorts two leads.

Without memory your motherboard should beep forever.
You also get a different beep without a video card.

Motherboards don't always beep when they should. I have seen motherboards what would do nothing without RAM rather than give the no RAM beep code listed in their manuals.

I would remove and disconnect everthing, then connect the CPU (& its fan), powersupply, case switches and internal speaker, AND NOTHING ELSE.

See if you get any beeps.

Then add the RAM and see if you get beeps. Be 100% certain it is inserted correctly.

Then add the video card and see if you get any beeps. Be 100% certain it is inserted correctly.

Also are you sure you mounted the motehrboard correctly. Many times I have been asked to help someone after a bad build only to find they didn't use any spacers and their motherboard was shorting against the case!

I usually try POSTing with the motherboad on a piece of cardboard prior to mounting it.

 

[Crashman]

Yes, having an IDE cable on backwards can prevent BIOS from doing anything (including starting the CPU).

<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>