Sound Support Cygwin/X
Hi all, I am sorry, if the question is off-topic. I've checked all related FAQs and archives but could not find a solution to my problem: I am using a Linux box and connect to it my Windows XP notebook as X-Server running Cygwin/X. I connect with XDMCP and it all works fine. After login when KDE is starting up I see a message that the /dev/dsp device could not be initialised. Is it true, that Cygwin/X does not support sound forwarding? Are there any other solutions? My goal is to to run a SIP Phone on the Linux box and use my Windows box for display/mic/speakers. Thanks and best regards, Gerhard __ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html
dell inspiron 8600 for 110
try: a href=http://www.booneo.com;http://www.booneo.com/a for these deals
Re: Sound Support Cygwin/X
Gerhard Zweimüller wrote: I am using a Linux box and connect to it my Windows XP notebook as X-Server running Cygwin/X. I connect with XDMCP and it all works fine. After login when KDE is starting up I see a message that the /dev/dsp device could not be initialised. Firstly, I think that this is a permissions problem. Take a look at /dev/dsp and make sure that the user you log in as has permissions to write to this device. This is usually done by adding the user to the audio group or something similar Is it true, that Cygwin/X does not support sound forwarding? Are there any other solutions? I have not gotten XDMCP working properly (you are further along than I am) but I am fairly sure that if you can get esound or arts to forward the sound you can figure out some way to get it through the XDMCP session. LB
Re: Sound Support Cygwin/X
On Tue, 17 Feb 2004, Loren H. Burlingame wrote: Gerhard Zweimüller wrote: I am using a Linux box and connect to it my Windows XP notebook as X-Server running Cygwin/X. I connect with XDMCP and it all works fine. After login when KDE is starting up I see a message that the /dev/dsp device could not be initialised. Firstly, I think that this is a permissions problem. Take a look at /dev/dsp and make sure that the user you log in as has permissions to write to this device. This is usually done by adding the user to the audio group or something similar Is it true, that Cygwin/X does not support sound forwarding? Are there any other solutions? I have not gotten XDMCP working properly (you are further along than I am) but I am fairly sure that if you can get esound or arts to forward the sound you can figure out some way to get it through the XDMCP session. With some magic you can configure esound to connect to the same machine as the xserver. The hostname is available from the DISPLAY variable. After stripping the trailing :0.0 you can set the the variable for esound (I'm not sure how it is called, i think ESD_SPEAKER or similar) to the hostname. But I'm not sure if esound is available on windows. For availibility of arts you may ask the people from the [EMAIL PROTECTED] list. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
no interaction in xterm, but it works in a cygwin shell
I'm using a Lisp-based computer algebra system called REDUCE. Basically it is started by a call of the form: #!/usr/bin/bash -v /cygdrive/c/devred/lisp/psl/win32/psl/bpsl -td 1600 -f 'C:\devred\lisp\psl\win32\red\reduce.img' The -v option is for printing the executed commands on the screen. The second line calls the Lisp (bpsl.exe) with the memory size (16Mb) and an image file (reduce.img). The binary bpsl.exe was compiled under Windows. In a Cygwin shell, i can have an interactive session without problems, e.g.: - start - [EMAIL PROTECTED] /cygdrive/d $ reduce #!/usr/bin/bash -v # Run Windows PSL REDUCE. /cygdrive/c/devred/lisp/psl/win32/psl/bpsl -td 1600 -f 'C:\devred\lisp\psl\w in32\red\reduce.img' Loading image file :C:\devred\lisp\psl\win32\red\reduce.img REDUCE Development Version, 10-Dec-03 ... 1: factorial 40; 8159152832478977343456112695961158942720 2: factorial 50; 30414093201713378043612608166064768844377641568960512 3: quit; Quitting [EMAIL PROTECTED] /cygdrive/d $ -- end - Now, if I do the same in an xterm, the following happens: There is no output on the screen from REDUCE. But I can enter line by line: factorial 40; factorial 50; quit; As soon as the quit; is entered, all the missing output is flushed to the screen, see this screenshot of an xterm session: - start - [EMAIL PROTECTED] ~ $ reduce #!/usr/bin/bash -v # Run Windows PSL REDUCE. /cygdrive/c/devred/lisp/psl/win32/psl/bpsl -td 1600 -f 'C:\devred\lisp\psl\w in32\red\reduce.img' factorial 40; factorial 50; quit; Loading image file :C:\devred\lisp\psl\win32\red\reduce.img REDUCE Development Version, 10-Dec-03 ... 1: 8159152832478977343456112695961158942720 2: 30414093201713378043612608166064768844377641568960512 3: Quitting [EMAIL PROTECTED] ~ $ - end - So my question is: Can somebody explain this behaviour, is there a solution? (E.g. the command line version of Maple works nicely both in xterm and a Cygwin shell.) Ciao, Andreas. -- http://www.fmi.uni-passau.de/~seidl
Re: no interaction in xterm, but it works in a cygwin shell
On Tue, 17 Feb 2004, Andreas Seidl wrote: I'm using a Lisp-based computer algebra system called REDUCE. Basically it is started by a call of the form: #!/usr/bin/bash -v /cygdrive/c/devred/lisp/psl/win32/psl/bpsl -td 1600 -f 'C:\devred\lisp\psl\win32\red\reduce.img' The -v option is for printing the executed commands on the screen. The second line calls the Lisp (bpsl.exe) with the memory size (16Mb) and an image file (reduce.img). The binary bpsl.exe was compiled under Windows. In a Cygwin shell, i can have an interactive session without problems, e.g.: - start - [EMAIL PROTECTED] /cygdrive/d $ reduce #!/usr/bin/bash -v # Run Windows PSL REDUCE. /cygdrive/c/devred/lisp/psl/win32/psl/bpsl -td 1600 -f 'C:\devred\lisp\psl\w in32\red\reduce.img' Loading image file :C:\devred\lisp\psl\win32\red\reduce.img REDUCE Development Version, 10-Dec-03 ... 1: factorial 40; 8159152832478977343456112695961158942720 2: factorial 50; 30414093201713378043612608166064768844377641568960512 3: quit; Quitting [EMAIL PROTECTED] /cygdrive/d $ -- end - Now, if I do the same in an xterm, the following happens: There is no output on the screen from REDUCE. But I can enter line by line: factorial 40; factorial 50; quit; As soon as the quit; is entered, all the missing output is flushed to the screen, see this screenshot of an xterm session: - start - [EMAIL PROTECTED] ~ $ reduce #!/usr/bin/bash -v # Run Windows PSL REDUCE. /cygdrive/c/devred/lisp/psl/win32/psl/bpsl -td 1600 -f 'C:\devred\lisp\psl\win32\red\reduce.img' factorial 40; factorial 50; quit; Loading image file :C:\devred\lisp\psl\win32\red\reduce.img REDUCE Development Version, 10-Dec-03 ... 1: 8159152832478977343456112695961158942720 2: 30414093201713378043612608166064768844377641568960512 3: Quitting [EMAIL PROTECTED] ~ $ - end - So my question is: Can somebody explain this behaviour, is there a solution? (E.g. the command line version of Maple works nicely both in xterm and a Cygwin shell.) Ciao, Andreas. Andreas, Just a WAG, but could it be that lisp detects that it's running on a console and uses a different (interactive) input mode? As far as Windows programs are concerned, a pty is nothing but a pipe, so you may have to force interactive mode somehow (via a flag?). Or it could be a CRLF vs. LF issue (i.e., the program waiting for CRLF to complete the line, but getting LFs, and then, once it gets the EOF, parsing the whole input), but I doubt it. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
Re: Clipboard related failure
I'm seeing the problem as well. Just highlight text in an xterm, paste into anything (e.g., notepad), and the program being pasted into stalls. Very unfortunate. Moreover, when I tried to exit Xwin after this (via the systray icon), the Xwin closing confirmation dialog also stalled! (Hence, no xwin.log.) I can't reproduce the problem, but I'll try and keep an eye out for it. -JT
