On Thu, 2010-11-04 at 11:37 -0400, John A. Sullivan III wrote:
Hello, all. We were thinking of using the Windows 3.0.1-2 client to experiment with using vcxsrv as the Windows X Server rather than Xming. I remember that there was an enormous performance improvement in our systems when we moved from -2 to -4. Indeed, we found -2 unusable and -4 just about as fast as Linux. Was the only change including a built-in Xming as per http://www.freedesktop.org/wiki/Xming/Building or were there other changes as well? Thanks - John <snip> Oops! I should have thought to read the change logs in http://x2go.obviously-nice.de/deb/ rather than wasting everyone's time. I see:
- windows:
- Start own build of X Server
- Start one X server per x2goclient
- Start own build of PulseAudio
- Start one PulseAudio server per x2goclient
- Start one sshd per x2goclient
- printing and viewing pdf in windows using ShellExec
- make x2goclient work if username have spaces and unicode symbols
as well as:
- set x2goagents dpi option
- fixed rsa/dsa keys with password
- session limit error message
- warning by terminating session
- fixed help message
- save pulseaudio client.conf and cookie on server
- in session directory not in ~/.pulse/client.conf
- (do not owerwrite local pulse settings for remote user)
- copy pulse cookie-file to remote system
- try to load module-native-protocol-tcp
- dependency for openssh-server in deb
- set keyboard layout by default
- add ssh option ServerAliveInterval=300
- check if port free when starting tunnel for nxproxy
I was hoping it would be as simple as rewriting the NSIS script to install vcxsrv as an option rather than needing to rebuild the Windows binary as I've not been able to do that successfully yet. We'll have to see how we can approach it. Sorry for the unnecessary question - John