Prev: Adobe Acrobat Reader 8 Clipboard Error
Next: Error connecting to the NON TS servers..
From: hein on 12 Mar 2007 15:47
Hi,

My original problem was that beeps to te system speaker are not redirected.
But you correct that system beeps are redirected to the ts client.
I have resolved the problem you described i possibly had and now the system
beeps
And the delay is very acceptable. Near null.
So I'm very glad!!

Now i hope to find someone what wants to re-program the software to a
windows environment.

Thanks everybody for there help!

Greeting from Holland, Hendrik Mosterman

"Vera Noest [MVP]" wrote:

> I agree with Jeff that converting the program to a Windows
> application would obviously be the best solution. But there might
> be reasons why that isn't possible, at least on a short notice.
>
> About your original problem: no beeps, that's a bit funny.
> On Windows 2003 RTM, system beeps were not transferred to the
> clients.
> Because a lot of users complained about that (they needed exactly
> the same functionality as you), system beeps are redirected to the
> TS clients after installing 2003 SP1.
> Then *other users* started to complain about the system beeps, so
> Microsoft created a hotfix and a registry change to disble the
> system beeps again in TS clients.
> Maybe you have that hotfix and the registry change on the Terminal
> Server? In that case, you should be able to enable system beeps
> again.
>
> More information here:
>
> 901115 - A Terminal Services client computer may make beep sounds
> after you connect to a Windows Server 2003 Service Pack 1-based
> computer
> http://support.microsoft.com/?kbid=901115
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> Jeff Pitsch <Jeff(a)Jeffpitschconsulting.com> wrote on 11 mar 2007
> in microsoft.public.windows.terminal_services:
>
> > I doubt there is much you can do but what sound quality are you
> > specifying? the higher the quality the more bandwidth and more
> > time it will take to get the sound.
> >
> > I have to ask this but since you can get the programmer to make
> > that change, why not have them reprogram it for windows?
> >
> > hein wrote:
> >> Hi,
> >>
> >> First my situation;
> >>
> >> I have a windows 2003 server with a old Dos program.
> >> That dos-program makes use of the pc-system speaker.
> >> The pc-speaker sounds are not redirected to the clients logged
> >> on the server with remote desktop.
> >>
> >> I have asked the programmer to come up with a solution.
> >> Now he has programmed the dos-application that when it's needed
> >> he is playing a wavfile with the command:
> >>
> >> sndrec32 /embedding /play /close chimes.wav
> >>
> >>
> >> That does the trick and it redirected to the client who is
> >> connected with a remote desktop connection.
> >>
> >>
> >>
> >> But there is a delay in playing the sound. It very annoying.
> >>
> >> Is there a way / program / command line to play the sound
> >> quicker on the client?
> >>
> >> English isn't my language so when something isn't clear to you
> >> i can give you more feedback
> >>
> >> greetings from Holland , hendrik
>

From: Vera Noest [MVP] on 12 Mar 2007 18:01
Great! I'm glad that your immediate problem is solved, but sooner
or later, you are going to run into others with such an old
program. So yes, you'd better plan to rewrite it.

Vriendelijke groeten,
Vera
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?aGVpbg==?= <hein(a)discussions.microsoft.com> wrote on 12
mar 2007 in microsoft.public.windows.terminal_services:

> Hi,
>
> My original problem was that beeps to te system speaker are not
> redirected. But you correct that system beeps are redirected to
> the ts client. I have resolved the problem you described i
> possibly had and now the system beeps
> And the delay is very acceptable. Near null.
> So I'm very glad!!
>
> Now i hope to find someone what wants to re-program the software
> to a windows environment.
>
> Thanks everybody for there help!
>
> Greeting from Holland, Hendrik Mosterman
>
> "Vera Noest [MVP]" wrote:
>
>> I agree with Jeff that converting the program to a Windows
>> application would obviously be the best solution. But there
>> might be reasons why that isn't possible, at least on a short
>> notice.
>>
>> About your original problem: no beeps, that's a bit funny.
>> On Windows 2003 RTM, system beeps were not transferred to the
>> clients.
>> Because a lot of users complained about that (they needed
>> exactly the same functionality as you), system beeps are
>> redirected to the TS clients after installing 2003 SP1.
>> Then *other users* started to complain about the system beeps,
>> so Microsoft created a hotfix and a registry change to disble
>> the system beeps again in TS clients.
>> Maybe you have that hotfix and the registry change on the
>> Terminal Server? In that case, you should be able to enable
>> system beeps again.
>>
>> More information here:
>>
>> 901115 - A Terminal Services client computer may make beep
>> sounds after you connect to a Windows Server 2003 Service Pack
>> 1-based computer
>> http://support.microsoft.com/?kbid=901115
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> Jeff Pitsch <Jeff(a)Jeffpitschconsulting.com> wrote on 11 mar
>> 2007 in microsoft.public.windows.terminal_services:
>>
>> > I doubt there is much you can do but what sound quality are
>> > you specifying? the higher the quality the more bandwidth
>> > and more time it will take to get the sound.
>> >
>> > I have to ask this but since you can get the programmer to
>> > make that change, why not have them reprogram it for windows?
>> >
>> > hein wrote:
>> >> Hi,
>> >>
>> >> First my situation;
>> >>
>> >> I have a windows 2003 server with a old Dos program.
>> >> That dos-program makes use of the pc-system speaker.
>> >> The pc-speaker sounds are not redirected to the clients
>> >> logged on the server with remote desktop.
>> >>
>> >> I have asked the programmer to come up with a solution.
>> >> Now he has programmed the dos-application that when it's
>> >> needed he is playing a wavfile with the command:
>> >>
>> >> sndrec32 /embedding /play /close chimes.wav
>> >>
>> >>
>> >> That does the trick and it redirected to the client who is
>> >> connected with a remote desktop connection.
>> >>
>> >>
>> >>
>> >> But there is a delay in playing the sound. It very annoying.
>> >>
>> >> Is there a way / program / command line to play the sound
>> >> quicker on the client?
>> >>
>> >> English isn't my language so when something isn't clear to
>> >> you i can give you more feedback
>> >>
>> >> greetings from Holland , hendrik
From: TP on 14 Mar 2007 03:48
Hi Vera,

Strange, I have not seen a 2003 SP1 server emit system beeps
to the TS client. Longhorn server does send beeps, but they
can be disabled via the registry setting you posted.

Do any of your 2003 SP1 servers send beeps?

-TP

Vera Noest [MVP] wrote:
> I agree with Jeff that converting the program to a Windows
> application would obviously be the best solution. But there might
> be reasons why that isn't possible, at least on a short notice.
>
> About your original problem: no beeps, that's a bit funny.
> On Windows 2003 RTM, system beeps were not transferred to the
> clients.
> Because a lot of users complained about that (they needed exactly
> the same functionality as you), system beeps are redirected to the
> TS clients after installing 2003 SP1.
> Then *other users* started to complain about the system beeps, so
> Microsoft created a hotfix and a registry change to disble the
> system beeps again in TS clients.
> Maybe you have that hotfix and the registry change on the Terminal
> Server? In that case, you should be able to enable system beeps
> again.
>
> More information here:
>
> 901115 - A Terminal Services client computer may make beep sounds
> after you connect to a Windows Server 2003 Service Pack 1-based
> computer
> http://support.microsoft.com/?kbid=901115
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
From: Vera Noest [MVP] on 14 Mar 2007 11:52
Yes, they did, all of them. I had to apply the KB901115 hotfix to
get rid of the beeps.
It happened a long time ago (directly after installing SP1), so I'm
not 100% sure what exactly caused those beeps, it might have been
some "wait" command in a batch job.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"TP" <tperson.knowspamn(a)mailandnews.com> wrote on 14 mar 2007 in
microsoft.public.windows.terminal_services:

> Hi Vera,
>
> Strange, I have not seen a 2003 SP1 server emit system beeps
> to the TS client. Longhorn server does send beeps, but they
> can be disabled via the registry setting you posted.
>
> Do any of your 2003 SP1 servers send beeps?
>
> -TP
>
> Vera Noest [MVP] wrote:
>> I agree with Jeff that converting the program to a Windows
>> application would obviously be the best solution. But there
might
>> be reasons why that isn't possible, at least on a short notice.
>>
>> About your original problem: no beeps, that's a bit funny.
>> On Windows 2003 RTM, system beeps were not transferred to the
>> clients.
>> Because a lot of users complained about that (they needed
exactly
>> the same functionality as you), system beeps are redirected to
the
>> TS clients after installing 2003 SP1.
>> Then *other users* started to complain about the system beeps,
so
>> Microsoft created a hotfix and a registry change to disble the
>> system beeps again in TS clients.
>> Maybe you have that hotfix and the registry change on the
Terminal
>> Server? In that case, you should be able to enable system beeps
>> again.
>>
>> More information here:
>>
>> 901115 - A Terminal Services client computer may make beep
sounds
>> after you connect to a Windows Server 2003 Service Pack 1-based
>> computer
>> http://support.microsoft.com/?kbid=901115
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>
From: TP on 14 Mar 2007 13:16
Thanks.

Not sure why I have never seen this with the ones I have done. I
have SP1 servers that were originally RTM, some that were originally
SP1, and others that are R2, both x86 and x64. Just in the past several
weeks I have built 4 fresh R2s and none of them have the beeps.

I would have noticed the beeps; when using Longhorn it is one of the
first annoyances that jumps out after installation.

I guess I am just weird (surprise!). :-)

This reminds me of some of the common issues that people have with
TS. There are many that I have never experienced--I know I am doing
something different than these people that avoids the problems, but I
am unable to tell you what.

Same thing happens often when people ask me to fix their computer. If
I am physically present (or on the phone) then their computer seems to
work fine...until I leave.

-TP

Vera Noest [MVP] wrote:
> Yes, they did, all of them. I had to apply the KB901115 hotfix to
> get rid of the beeps.
> It happened a long time ago (directly after installing SP1), so I'm
> not 100% sure what exactly caused those beeps, it might have been
> some "wait" command in a batch job.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Adobe Acrobat Reader 8 Clipboard Error
Next: Error connecting to the NON TS servers..