Yes, you CAN get post errors with no CPU in it. So, yes I AM thinking for myself. If you like I can give you details on how post works, go right into the bootstrap and then into when it signs of to let the o/s take over. DMI Pooling can cause a computer to look up during post. Has happened before. Have seen it with experience. When post is done checking configuration and its minimal "jump start" to pass onto the bootstrap on the HDD very FIRST locale (0,0,1), JUST PRIOR to the DMI Pooling. The reason it would look up there was due to corrupted MBR data, so post NEVER finished.
ANYHOW it wont BOOT UP, but that was NOT the point. The point was getting a BEEP CODE and that was what we were discussing. Anyhow, looks like problem was solved.
Here are the reasons for my suggestions:
1. Power supply burned up. Could of killed the MBD and would of more than likley hit the processor AND memory... but lets start CHEAP first and things that are easier to do. Thats like changing out the power supply when a computer has no power before seeing if its plugged in! Start simple, and cheaper.
2. No post AND no video. Hmm. Well, power is GETTING there. Since no video, logical step one is to check each internal device. Vid card, IDE, PCI cards, the whole thing. If he got no post (and looks like that) to begin with, remove EVERYTHING but the HDD and see if you can GET a post. Then we know its something else.
3. As far as the CPU, no it WONT boot up. However, you CAN get a beep code PRIOR to that. THAT is what we are talking about. Or how about this error: CPU is missing or unworkable: these are legitimate error codes as are the bios beep codes (that we were talking about) for a misseated cpu. Soooo, YES... it IS possible. Yes, it has happened before.
By the preet2u, that is a kick a$$ desktop
