hysandrew wrote:
> Hi Paul,
> Thanks for your advice.
> I've now used a different PSU, as theone sold only has a peak of 500w
> and therfore there was no quarantee that it may be sufficient to power
> the PC. The one I have in question now is a Jeantech 700w Storm PSU
> after spending another £35!. With this PSU there is a wattage meter on
> the back, so when I turn the PC I can monitor the wattage, which when I
> do turn the PC it only gives a reading of 25w.
> The lights on the D bracket are reading just the number 3 LED which
> according to MSI means "ASSIGN RESOURCES TO ALL ISA." Do you or anybody
> else know, in plain English what this means?????
> If anyone can help you can email me direct at
>
Using the "ASSIGN RESOURCES TO ALL ISA", I ended up here. This
guy had a problem with his video card. So the LEDs and the source
of the problem, don't have to be related :-(
http://forum.msi.com.tw/index.php?topic=70813.msg498333
This page shows the LED values. The LEDs are not error indicators as
such, but progress markers. (They are about as useful as a Port 80
POST card.)
http://forum.msi.com.tw/index.php?topic=34535.0
ISA used to be a bus in the computer. Maybe something like a
serial port, is referred to as an ISA resource ? In any case,
I doubt the text string associated with the display value is
that meaningful by itself.
http://en.wikipedia.org/wiki/ISA_bus
The fact that the power consumption is only 25W is a bit
puzzling. Based on measurements I've made here with a couple
PCs, I find while in the BIOS, the processor runs at about
half power. If system clocks were cranked to their normal
levels, you'd think the power would be higher than that.
Maybe the resolution of the Jeantech meter isn't that good ?
I would try removing hardware from the computer, and watch
how the D-bracket and the system speaker respond. Obviously,
with missing memory or a missing video card, you should get
some indication they are missing. The very fact that the
D-bracket code value is advancing ("counting up"), tells you
that the processor is executing some BIOS code. The question
is, what motherboard resource, or plugin hardware, is causing
a problem ?
Paul