Check your ICH5R Southbridge for burn marks.
http://onfinite.com/libraries/179057/2ea.jpg
Whenever an ICH5/ICH5R machine fails to do much of anything,
start by assuming a "latchup failure" on the USB subsystem. That
causes a large current to flow between the power input points
of the USB pads on the Southbridge chip. If the bond wires hold
up while the current is flowing, the top of the ICH5/ICH5R is
burned as shown.
Perhaps the last thing you did, was plug a USB device into the
(relatively floating) USB port on the front of the computer ? Using
the rear USB ports on an ICH5/ICH5R motherboard may extend the life,
but at least a few posters with this problem, didn't have a
clearly associated ESD (electrostatic discharge) event correlating
with boot failure.
When a latchup failure occurs, a heavy current flows until the power
source is disabled, and the rail voltage drops to zero. Latchup
failure forms a PNPN junction, otherwise known as an SCR. If a user
was immediately aware latchup had occurred, they'd have a second or
two to remove power. And this information is of no real use in the
real world, because you're not hyper-tuned to expecting it, and
even if you were, you might still not make it in time to stop it.
It's like a "melt down". For most users, a minute or two pass, before
the realization it's broken.
My P4C800-E Deluxe still works, but is a backup machine now. I never wired
the front USB ports, and haven't used USB too much on it (mainly because
I didn't have a lot of USB stuff to begin with).
If you had a lot of add-in PCI cards, you could strip the machine down
a bit, and remove excess hardware, and check for different symptoms.
You could also attempt a "beep test", by removing all memory sticks
and the AGP video card, forcing the computer to "beep an error code".
If it doesn't beep, then you're getting closer to concluding the
processor simply cannot execute code any more. A burned Southbridge
prevents access to the bytes of code stored in the BIOS EEPROM. To
"beep", you really need a working Northbridge, hub bus, Southbridge,
and interface to the EEPROM, to suck in bytes of code. A burned
Southbridge stops that. A missing ATX12V power cable would give
similar symptoms (try re-plugging it).
Paul