SCOUG-HELP Mailing List Archives
Return to [ 19 |
December |
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.
=====================================================
Sandy Shapiro wrote:
> >> When I installed my new PCI AOpen sound card, AW320, it apparantly
> >> disabled my system speaker.
> Even
> when I removed the sound card completely, the speaker volume was still
> barely audible. Even the POST beep on boot up can only be heard if I put
> my ear up to the speaker.
Hi Sandy,
Since you can hear a faint "beep" the system is generating a beep signal
and thus it isn't a software problem.
Check that you have the speaker plugged onto the _proper_ pins on the
motherboard. You might, for example, have it plugged in "one pin over"
or you might have a bent motherboard pin. Check the motherboard manual
for the pin layout, the labeling on the motherboards is sometimes rather
cryptic. And make _sure_ you pull the connector and plug it back in so
you have a "fresh" mechanical connection.
Then put your system into a "beep loop" and wiggle the speaker
connectors and wire. You might have a loose connection. (Sometimes you
get these if you remove a connector by pulling on its wires instead of
the connector body.) If you have Graham Utilities it contains a
BEEP.EXE program, or you can use the Rexx BEEP function.
If you have a spare system (even an old one) plug its speaker connector
into the motherboard and see if you get a beep. This will check for a
bad connector, broken wire or open speaker coil. The chance of the
actual speaker failing is just about nil but it will check for that
too. Radio Shack or similar may sell spare PC speakers with the proper
cable attached, or you can borrow one from somebody.
It's possible for the motherboard's speaker driver transistor to have
failed but it's much more likely that you have a bad connection
somewhere. About the only thing that would cause the transistor to fail
would be a prolonged short of its output while it was beeping, and even
that situation wouldn't necessarily cause a failure. (I think there's
an onboard series resistor to guard against this possibility.)
- 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".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 19 |
December |
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.
|