I've bought a second-hand unit to use as my sibling's homework and research "computer". However, after setting it all up, I discovered that the sound output device fails to operate most of the time. I have tried putting a fan on it to cool it down, however this doesn't semt to solve the problem.
The computer I'm using (for now) is a windows 2003 R2 Enterprise Server in trial mode for 120 days (about 97 days left now, solely to make sure it isn't my winXP machine's fault for this) and other /normal/ computers can connect to it through remote desktop connection, with sound (although the sound recieved is a little delayed, but this is not unexpected).
Steps:
In an RDP session, start windows media player (or whatever, so long as it puts out sound) and begin playback.
Watching the network utilization, observe how much data is put through during non-sound output and with sound output.
Notice that after a short period of time playing, windows media player will stop playing, presumably to let the device "catch up" on outputting the sound. All other functions (screen writing etc) are working normally.
After a bit, windows media player will continue playback even though very little sound has been output (most of it is garbled garbage anyways. Not too pleasant). Notice that despite the fact that windows media player is "paused" (the status is still "playing" yet the tracker is stopped) the application is not frozen and any visualizer will continue to run, although as if the media being played is blank (ie the scope visualization will flatline) during periods of "waiting".
Tags: