Originally posted by: Vagrant
Bozo Galore, thanks for the link, I will try a new battery, multi meter says the old one is putting out 3 volts, as labled, but that is a no load reading.
Zepper, MSI call it "instant power on" dont' know why they did it, but as soon as you conect power, the fans and diagnostic lights start up for about a second, then turn off. Nothing was changed from last time I ran it, apart from removing the burner.
That's interesting. I was just at the QDI (mobo) site today, reading their FAQ entries, and they had one that mentioned the system *automatically* powering on for a split-second after flashing the BIOS on a particular mobo. Their explaination was that the system was auto-starting, briefly, to "detect" the PSU.
Personally, I think that sounds a bit bizarre to me, I've never heard anything like that. But it's possible that the act of flashing the BIOS clears the CMOS, and on that (and perhaps others, like the MSI board in question?), triggers auto-power on due to the CMOS settings, and it powers on enough to adjust the settings/clear the checksum/etc. Something like that, anyways, that would prevent any further auto-power-ons. (Perhaps when the RTC gets power, when it counts the next second, it triggers a compare on the stored power-on-alarm values, and since the CMOS was reset, it triggers a power-on event, but then the BIOS POST recognizes that the CMOS checksum is invalid or otherwise cleared out, and then disables the RTC alarm setting, and possible sets the CMOS checksum, or something, etc. so it doesn't happen again, and then powers back down.)
I would still think that would cause the system to at least partially POST (bootblock early initialization) if that were true, so I don't think that's the correct explaination. It wouldn't be safe for the HDs either, to power-on for such a short period of time that they don't get to fully spin up and run internal firmware diagnostics, which often write to an internal error/event log stored on a non-host-accesable sector on the HD. Cutting the power to the drive (at least on IBM's Deskstars), while writing, could semi-permanently damage the low-level format of the drive and possibly the on-media firmware. (Never had that problem with WDs though.)
Edit: Oops, sorry, O-C disorder kicking in, following is actually diagnostics for a board that fails to start up, not starts up when power is plugged in to the supply, although it could explain why it suddenly powers off a split-second later. Personally, I suspect a buggered mobo though, period.
Edit: Also, most (half-decent) ATX PSUs, will auto-shutdown if they: 1) have a short, 2) have issues with the properly loading/operation of the switching regulator circuits, 3) overheat, 4) PSU fan failure, or other things.
I would also double-check that the ATX mobo power connector is properly connected, and that there isn't anything blocking one of the pins, and/or or that non of the pins are loose and got "pushed" back into the connector, resulting in no load on that voltage plane/regulator in the PSU. Likewise for drive molex power connectors, sometimes they fray, and one little wire strand pops out of the connector, and touches another one, an accident waiting to happen. Seems to happen most often when using cheapo aftermarket power-molex Y-splitters.
Oh yeah, one last "duh" thing, make sure that you have a fan with RPM/tach feedback plugged into the appropriate connector in the mobo, usually the CPU fan. Some boards were famous for not powering up due to not recieving a tach signal, to prevent CPU overheating/burn. A later BIOS for my old Abit BX6-r2 board was that way. If the CMOS is cleared, either manually or due to a a dead/flaky battery, it could reset that internal setting to default which was "ON" for that particular board/BIOS version.