SCOUG-HELP Mailing List Archives
Return to [ 09 |
February |
2001 ]
<< Previous Message <<
>> Next Message >>
Content Type: text/plain
=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================
Peter,
I believe the cause is the video card (motherboard MAY have killed it???)
because my monitor is not getting a signal. The monitor is fine. I have a
KVM switch and I am using it on another system to type this. Second, I took
the ATi card back to West Tech in Mission Viejo where I bought it and they
tested it in one of their systems, said it was bad, and gave me a new one.
The Award web site says that the only beep code is one long and two short
beeps signifying a bad video card. Listening to it again, there ARE two
short beeps at the end although they are nearly run together.
I have tried the latest PCI video card in two different PCI slots, the one
next to the AGP slot and the one next to that. with the same results. I have
not had time yet to take out the rest of the cards. What I REALLY want is a
Matrox G450, but I'm afraid that if I spend the bucks and plug it into my
motherboard, that it will end up dead as well as the other two cards that I
have. I would like to get the system working again before I make that step.
Tom Brown
Peter Skye wrote:
> =====================================================
> If you are responding to someone asking for help who
> may not be a member of this list, be sure to use the
> REPLY TO ALL feature of your email program.
> =====================================================
>
> Tom Brown wrote:
> >
> > I got one long beeeeeeep
>
> Tom,
>
> You don't say why you think the cause is the video card, so apologies if
> the following is useless. :-)
> _____
>
> The motherboard's BIOS has a number of different "beep codes" (POST, or
> Power On Self Test, codes) to alert you when it can't complete its
> processing and thus can't continue on and boot your operating system.
>
> Unfortunately, different BIOS manufacturers have different codes.
>
> First: Check the documentation which came with your motherboard. It
> may list the "beep codes", including your "one long beep".
>
> Second: Go to the BIOS manufacturer's web site (okay, call a friend and
> have _them_ go to the BIOS web site) and download the doc file for your
> particular BIOS. Look up the beep codes.
>
> Third: Email the motherboard manufacturer's tech support and ask them
> what "one long beep" means.
>
> The last time I had a video card failure, the error beep code for that
> particular motherboard BIOS was two short beeps. (The motherboard was
> too old to handle my new Elsa card.)
> _____
>
> Gary's response of "reseat everything" is a good one. It's only a
> two-minute job, and frankly you might just want to pull out _everything_
> (including the video card _and_ your motherboard memory) and start
> putting things back in one at a time. (Power should be off when
> removing or inserting stuff.) The "beep code table" for your BIOS is in
> sequence by the tests done by that BIOS (at least mine are) so it's a
> good sequence in which to plug the stuff back in.
> _____
>
> Here are some BIOS urls from my home page (haven't checked 'em
> recently):
>
> American Megatrends, Inc.
> (AMI) (BIOS manufacturer)
>
> Award Software (BIOS
> manufacturer)
>
> Note: Sep98 Award merged with Phoenix
>
>
>
> Phoenix Technologies Ltd. (BIOS
> manufacturer)
>
> - Peter
>
> =====================================================
>
> To unsubscribe from this list, send an email message
> to "steward@scoug.com". In the body of the message,
> put the command "unsubscribe scoug-help".
>
> For problems, contact the list owner at
> "rollin@scoug.com".
>
> =====================================================
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 09 |
February |
2001 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
|