G
Greg Clark
I'm hoping someone has a solution to my problem. Here are some details of
the problem that I'm experiencing...
I have a Shuttle SV25 that I want to use as a "headless" media server, for
audio file streaming/storage accessable by other computers in my home, and
audio devices.
The problem I encounter is that the audio device is not loading properly
unless I connect locally to the machine prior to a RDC. If I login via RDC
prior to logging in locally, the audio control panel shows all options
grayed out, even though the device drivers say they are loaded correctly.
No audio devices appear in the control panel. If I connect locally, then
without logging out locally, connect via RDC, the sound works fine. This
defeats the purpose of wanting the machine to be "headless", as I need it to
live in a location where a monitor/keyboard/mouse is not feasable to attach
every time I reboot the box.
I've noticed on a few other groups online that other people have experienced
this issue, though most just make sure they log onto the remote box locally
first as a workaround. For me, this is an unworkable solution.
Can anyone point me to a better explanation of the cause of this issue, and
how I might work around it? I've tried using both onboard sound and a
SBLive card, both with the same result.
Thanks in advance for your feedback.
-Greg
the problem that I'm experiencing...
I have a Shuttle SV25 that I want to use as a "headless" media server, for
audio file streaming/storage accessable by other computers in my home, and
audio devices.
The problem I encounter is that the audio device is not loading properly
unless I connect locally to the machine prior to a RDC. If I login via RDC
prior to logging in locally, the audio control panel shows all options
grayed out, even though the device drivers say they are loaded correctly.
No audio devices appear in the control panel. If I connect locally, then
without logging out locally, connect via RDC, the sound works fine. This
defeats the purpose of wanting the machine to be "headless", as I need it to
live in a location where a monitor/keyboard/mouse is not feasable to attach
every time I reboot the box.
I've noticed on a few other groups online that other people have experienced
this issue, though most just make sure they log onto the remote box locally
first as a workaround. For me, this is an unworkable solution.
Can anyone point me to a better explanation of the cause of this issue, and
how I might work around it? I've tried using both onboard sound and a
SBLive card, both with the same result.
Thanks in advance for your feedback.
-Greg