|The things that I've seen damaged by a failing PS of about 15 failures are, in order of frequency, floppy drives 3 or 4, CD drives 2, 1 on each of 2 computers, cards in slots 2 on 1 computer (video and modem), and one mboard that would not boot - probably the mboard, not the cpu.|
For other cases I've heard about the onboard video or cards in slots may be damaged, usually the hard drive is okay physically but it may have damaged data (none of my 15 cases did any damage to the hard drives), only one case where the hard drive was fried, occasionally the cpu is damaged but that's less likely than the mboard is damaged - maybe 1 in 10 for a mboard. I don't recall hearing of many cases of fried ram, but that's certainly possible. There was one case where some of the usb controllers and a usb connected network adapter were fried.
If the PS shorted (a snap! sound) before it died, it is more likely it killed the mboard, and/or less likely, the cpu.
If a PS capacitor exploded (a pop! sound) it is less likely to have done that.
If a capacitor exploded there are loose pieces of it inside the PS, and often only wire stubs where it was.
The fact that you get the single beep and the mboard boots as far as it does is somewhat encouraging - that means the mboard itself is more likely to be okay. Sometimes if a CD drive or hard drive or floppy drive is damaged there will be a LONG delay while booting, and you may or may not get an error message.
Go into your bios Setup and turn off any setting for HALT on xxxx error(s).Try booting to see if the boot gets any further.
When you boot do you see the usual counting of the ram at the beginning, assuming the logo screen does not cover that up? If you do, is it the proper amount?
Sometimes the ram count is not visible because a logo screen is displayed overtop of it while booting. In that case, go into your bios Setup while booting. You could try disabling the display of the logo screen if there is such a setting, or disabling fast boot or similar, which often disables the logo screen.
Sometimes your monitor is not warmed up enough when you boot and you can't see anything at first - try pressing Reset, or Alt-Ctrl-Del at the same time, after you can see the display, to reboot.
Remove the power to the case, look for evidence of a short or shorts - zapped connections, zapped contacts on ram or cards. If you see nothing like that, remove, replace the ram modules and cards one at a time, make sure the ram and cards are all the way down in their slots. Remove the data cables to hard and cd drives on the mboard end and the power connectors to the drives.
Restore power to the PS, try booting to see if the boot gets any farther. If no change, the cpu may be damaged, or less likely, the ram.
Try booting with a bootable floppy disk, but the drive may be damaged. If the floppy led does not come on the drive is damaged - disconnect it's data and power connectors. If it does come on while booting, the drive may still be damaged and will not be able to read a disk (that was the case with all of the cases of a damaged floppy drive I mentioned).
If in doubt, try a known working floppy drive from another computer, with the data cable from that computer.
To check for the possibility the ram is fried, remove the power to the case, remove the ram, restore power to the case.
If the ram was damaged but nothing else is wrong, you will get a beep pattern that indicates no ram is installed. E.g. for many mboards with an Award bios, a beep lasting about a second, silence for a second, a beep lasting about a second, etc., continuously.
If the ram does not work in another mboard, that does not necessarily prove it is bad because the ram has to be compatible with the mboard you install it in - it might not be, more likely if it is DDR ram - in the worst cases the mboard will not boot when it is installed. If it DOES work in another mboard, that proves it also works in that other mboard and it is okay.
You can check your floppy, hard, and CD drives by connecting them to another computer. Don't connect a hard drive as master on the primary IDE (or primary SATA if that's what the bios is set to boot from) for the time being.
You could check the cpu by installing it in another mboard that it is compatible with, or by taking it to some place where they can do that for you, and they could test the mboard at the same time.