> I just cleaned my RAM and tried with three separate sticks. Two that
> were in my current PC and one that came from a working PC. Still no
> luck. I put the third stick in the original working PC and it is
> working so I'm sure at least one stick of the three is functional.
> Thanks for the suggestion! I'll keep trying.
Avoid the noon_day sun, wear pith helmut.
Life's a =bitch=
then the 'sounds' get louder,
then it quits .
I shy away from alcohol cleaner(s)... too many additives.
Mite try torpedo fuel if I could find some
TomG hadnt drunk it all.
> >> The BIOS error codes are all over the place
> >> 02
> >> 83
> >> 9f
> >> 8c
'Above' are BIOS post codes, so_called,
technically(weasel word) begin at [01h] , end at [FFh].
*IF* you can make the BIOS POST pgm spit out =all= it's (completed} POST
they'll be all over the place , but usually 'sequentially' spit.
*IF* you 'see' one ...
thats a successful POST "step" completion ...
which "step cmpln msg" can be an [err], or not.
POST code 'step' errors are typically translated into
(few) "Beep Codes" ...
the booting PC is almost screenless, but the speaker works ...
"is" why 'they' sell the POST CODE diagnostic "show" card.
If your 'post' got to [9Fh] ,
you got a long way thru the POST .
I'm not quite sure if you can boot from flpy ... ???
.... mobo, et al, still in the case.
If "so" , you're a potential winner .
Try disconnecting =all/any= storage devices =except= flpy .
.... NIC, sound, et al too ...
Leave kybd & CRT.
A PIA for sure, worth the efort.
Qed. >> Stay informed about: No boot on Abit AV8