Appendix E: Informational Notes
337
Audio in a Linux Environment
The following are known issues when using the audio feature in a Linux
®
environment.
Linux
®
users, use the default audio device for playback. Sound may
not come through if a non-default sound card is selected.
SuSE 11 clients require Javas_1_6_0-sun-alsa (ALSA support for
java-1_6_0-sun) to be installed via YAST.
For Logitech
®
headsets with a built in a mic, only the Mono Capture
option is available.
In order to display the device, if you are running SUSE 11 and an
ALSA driver, log out of KX III, then log back in.
Additionally, if you connect and disconnect the audio device a
number of times, the device may be listed several times vs. just once
as it should.
Using the audio feature with a Fedora Core
®
13 target set to mono
16 bit, 44k may cause considerable interference during playback.
Audio in a Windows Environment
On Windows
®
64-bit clients, only one playback device is listed on the
Connect Audio panel when accessing the device through the Virtual
KVM Client (VKC).
The audio device is the default device, and is listed on the Connect
Audio panel as Java Sound Audio Engine.
Smart Card Notes
Virtual KVM Client (VKC) Smart Card Connections to Fedora
Servers
If you are using a smart card to connect to a Linux
®
Fedora
®
server via
Virtual KVM Client (VKC) upgrade the pcsc-lite library to 1.4.102-3 or
above.
CC-SG Notes
Virtual KVM Client Version Not Known from CC-SG Proxy Mode
When the Virtual KVM Client (VKC) is launched from CommandCenter
Secure Gateway (CC-SG) in proxy mode, the VKC version is unknown.
In the About Raritan Virtual KVM Client dialog, the version is displayed
as “Version Unknown”.
Содержание dominion kx III
Страница 12: ......
Страница 103: ...Chapter 4 KX III Administrator Help 91 3 Click OK ...
Страница 159: ...Chapter 4 KX III Administrator Help 147 ...
Страница 283: ...Chapter 7 KX III Local Console KX III End User Help 271 ...
Страница 391: ......