10 Sep
2014
10 Sep
'14
5:02 p.m.
You don't get any sort of beep code out of it? I
gather these 255/300s are
supposed to beep at you like a PC does, given certain states where it can't
produce a display (or, I guess, console output).
It cycles through the lights then stops there.
Based on your comments I pulled the NVRAM battery and then I get a 1-2-1
beep code that the manual calls "Real-time clock (BQ3287) failure, or the
real-time clock interrupt
did not occur." and the LED cycle stops at XX0X 0XX0 which it calls
"Interrupts test failed"
Still no output on Com 1 or on the video card (an S3 based VGA card).
My next thought is a new CR2032 and see if it get past that in the startup
sequence.
Any other ideas?
Best,
Sean
>On Wed, Sep 10, 2014 at 3:59 PM, Sean Caron <scaron at umich.edu> wrote:
>
> Hi William,
> Does it cycle through other LED states before it
reaches 0xD1? Or does it
> just start there at power-on and sit forever? That is pretty odd; not
quite
> sure what to make of that. You tried the console
with and without a
> null-modem?
No null modem at hand. Just have a straight through cable and an Esprit
350C terminal.
Thanks,
William
--
Live like you will never die, love like you've never been hurt, dance
like no-one is watching.
Alex White l