display depth changing when using remote desktop and -multiwindow option, unable to set depth manually with -multiwindow
Hello. I use Cygwin/X on my office computer to run a program called Cadence (using 24-bit display), but have limited Cygwin functionality when I use remote desktop to work from home. Displays are set to 32-bit on both computers, and the Windows XP remote-desktop protocol (RDP) version I am using on both supports 32-bit displays. If I start Cygwin at the office and then use RDP to connect from home, everything continues working perfectly. However, if I log in remotely and then start a new Cygwin session, I get the following: *ERROR* Failed to find either 24-bit TrueColor or 8-bit PseudoColor Visual. *WARNING* Failed to find either 24-bit TrueColor or 8-pbit PseudoColor Visual. And my application will not start. I am using the following to start cygwin: run XWin -multiwindow -clipboard -silent-dup-error run xterm -e /usr/bin/bash -l I believe that Cygwin is detecting the optimal display settings on startup and determining it to be less than 32-bit when initiated through remote desktop. I would use the -depth command line option to manually set the depth to 32 bits, but this does not work with multiwindow enabled. Is there another way that I can manually set the display depth? Or somehow ensure that Cygwin determines that 32-bits are optimal when started through a remote desktop session? I have tried modifying the .inputrc file for 8-bit mode as follows, but had the same problem. set meta-flag on set convert-meta off set output-meta on Many thanks, Jason cygcheck_original.out Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: display depth changing when using remote desktop and -multiwindow option, unable to set depth manually with -multiwindow
Jason May schrieb: > I believe that Cygwin is detecting the optimal display settings on > startup and determining it to be less than 32-bit when initiated > through remote desktop. I would use the -depth command line option to > manually set the depth to 32 bits, but this does not work with > multiwindow enabled. Is there another way that I can manually set the > display depth? You can't set Xwins display depth larger than the Desktop it is running on. Usually that would be 16 Bit with rdp sessions. Did you ever check on the rdp Windows Desktop that you really get 32 Bit in Windows? Because i get 16 Bit even if i request 24 Bit. > I have tried modifying the .inputrc file for 8-bit mode as follows, > but had the same problem. That has no influence on Xwin. A possible solution would be a ssh connection and tunneling X11 through it. Cygwin provides a ssh daemon for windows. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: display depth changing when using remote desktop and -multiwindow option, unable to set depth manually with -multiwindow
Thanks Holger for the response. - You can't set Xwins display depth larger than the Desktop it is running on. Usually that would be 16 Bit with rdp sessions. Did you ever check on the rdp Windows Desktop that you really get 32 Bit in Windows? Because i get 16 Bit even if i request 24 Bit. - I'm using a new beta version of microsoft's RDP which should support 32-bit displays (http://support.microsoft.com/kb/925876), but I will have to check whether it is actually working as advertised. - A possible solution would be a ssh connection and tunneling X11 through it. Cygwin provides a ssh daemon for windows. I am currently using SSH (putty) with tunneling to connect from the office PC to a linux server. The network administrators have not opened any ports on the linux server for outside access, I believe I can only enter the network via RDP on my office computer. I will see if they will allow me to open another port on my computer for SSH port forwarding, it should indeed solve the problem if I can bypass the office computer directly. Jason -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/