J
Jack
We are experimenting with a program for voice comms over our LAN/WAN.
As most people are in an open-plan office environment the use of headsets
is preferred to speakers and desktop microphones but they do not need to
wear them permanently - i.e. only when in conversation.
The app. allows for an incoming call to flagged by sending ring-tone to the
speakers (which hardly anyone ever hears via the headset when not being
worn) or to beep the basic PC speaker [ i.e. the chassis-mounted one -
_not_ the sound card/chip one].
The majority of our machines use DFI mobos with Award BIOS and no provision
is made for the use of the basic speaker (although there are pin-outs for it
which are wired to the chassis speaker ).
I'm assuming that the problem is due to the Award bios not being programmed
to use the chassis speaker because there is a small *buzzer* type device on
the m/board for signalling BIOS beeps.
Can anyone think of a work-around ?
Do these on-board *buzzers* use standard addresses? etc.
TIA
Craig
As most people are in an open-plan office environment the use of headsets
is preferred to speakers and desktop microphones but they do not need to
wear them permanently - i.e. only when in conversation.
The app. allows for an incoming call to flagged by sending ring-tone to the
speakers (which hardly anyone ever hears via the headset when not being
worn) or to beep the basic PC speaker [ i.e. the chassis-mounted one -
_not_ the sound card/chip one].
The majority of our machines use DFI mobos with Award BIOS and no provision
is made for the use of the basic speaker (although there are pin-outs for it
which are wired to the chassis speaker ).
I'm assuming that the problem is due to the Award bios not being programmed
to use the chassis speaker because there is a small *buzzer* type device on
the m/board for signalling BIOS beeps.
Can anyone think of a work-around ?
Do these on-board *buzzers* use standard addresses? etc.
TIA
Craig