HP Remote Graphics 4.2.0 User's Guide

PC Speaker Sounds Not Working:

The Sender will capture all audio information sent through the mixer. This includes most audio alerts, MIDI, Direct Sound and Direct Music. Sounds generated by the PC Speaker are not captured by the sender and will not be transmitted.

Audible Pops and Glitches in Sound:

Most likely this is because the network bandwidth and or system resources are starving the audio streaming from continuous play.

∙Try a lower audio quality setting to reduce network bandwidth usage.

∙Be sure you system is not doing something so computationally intensive that it is starving RGS from keeping up with graphics and audio processing.

Enabling Audio Causes Continuous Network Traffic:

When the sender detects an audio signal, that signal is sent to the receiver. If the audio device on the sender is silent, there should not be any network traffic due to audio. If the audio device is generating a large amount of noise, that noise may get interpreted as an audio signal and get sent to the receiver. This may occur when something is connected to the "Line In" port of the audio device. Reducing volume levels or disconnecting these external devices may help reduce the interference.

4.Network Timeout Issues:

The Remote Display Window repeatedly dims out and displays a connection warning message:

This is likely caused by frequent network disruptions between the Receiver and Sender. The dimming of the display serves as a notification to the end- user that the Remote Display Window may reflect stale information. If frequent notifications are annoying and the network issues do not improve, then the user should refer to the section “Using Timeouts” and adjust the Receiver’s warning timeout value found on the Receiver Control Panel or the property Rgreceiver.Network.Timeout.Warning.

The Remote Display Window dims, the Receiver disconnects, and it displays a “Connection closed” error dialog, but the user can often immediately connect in again:

Most likely network connectivity between the Receiver and Sender was temporarily lost for some reason. Other possibilities include

∙the Sender has ungracefully terminated

∙the Sender system experienced some sort of failure

∙the Sender system’s cpu utilization prevented the Sender from making progress, or

∙the length of this connectivity loss exceeds the Receiver’s error timeout value, controlled by the Receiver’s

130