Hello! I have run the VenueVNCServer successfully on Windows and Fedora Core 3. Works great so far. I did some minor changes e.g. the python script takes the Xvnc application form the local directory instead of the version from /usr/bin, but thats not necessary in general and only required to reflect our project internal needs.
On Windows I also put the winvnc4.exe (and dlls) into the same directory as the Python script. I think that makes it more handy, but thats my personal opinion. I am currently working on a windows installer based upon NSIS to have a easy way of distributing the Windows VNCServer among the partners in our project. If there is interest I can provide that installer for the public. I also planned to include a small windows app that allows me to launch the VenueVNC server based on the current users Venue-Bookmarks, so that in the end you don't have to use console commands at all to launch it. Cheers Michael ------------------ Dipl.-Inf. Michael Braitmaier HLRS - Visualization / Video Conferencing University of Stuttgart Germany Website: http://www.hlrs.de/organization/vis/people/braitmaier/ ----- Original Message ----- From: "Thomas D. Uram" <[email protected]> To: "Andrew Patrick" <[email protected]> Cc: <[email protected]> Sent: Wednesday, February 09, 2005 5:08 PM Subject: Re: [AG-TECH] VenueVNCServer available > Andrew: > > I have the VenueVNC client installed on Gentoo, Windows, and OSX as part > of the package. Which OS are you using? VenueVNC is different from the > other shared apps, in that having the client installed does not enable you > to start sessions. VenueVNC sessions are started only by the server; the > only indication that you have a client installed is when you try to join a > session, whether it succeeds or not. > > Let me know details and we'll sort it out. > > Tom > > > Andrew Patrick wrote: >> Although the VenueVNC client application is included in the AG2.3 >> software package, it is not installed by default and there is no .app >> file to support installing in the usual fashion using agpm. Perhaps >> someone could make available a small ZIP file containing the appropriate >> Python and .app file so the client can be installed properly? >> >> >> >> Thomas D. Uram wrote: >> >>> >>> The server component of the VenueVNC shared application is now available >>> for download: >>> >>> http://www.mcs.anl.gov/fl/research/accessgrid/software/releases/2.3/patches/VenueVNCServer.py >>> >>> This program is all Python code, so works similarly on the three >>> supported platforms: Windows, Linux, and OSX. Platform variations >>> are given here: >>> >>> * Windows >>> - Depends on RealVNC (http://realvnc.com/) >>> - Looks for server executable in the RealVNC install directory >>> (C:\Program Files\RealVNC\VNC4\WinVNC4.exe) >>> - Only the primary display can be shared >>> - Uses port 5900 for server >>> >>> * Linux >>> - Depends on tightvnc (http://www.tightvnc.com) (other vnc packages >>> may also work) >>> - Looks for server executable in /usr/bin/Xvnc >>> - Any virtual display can be shared via the '--display' option >>> - Uses port 5900+displaynumber for server (e.g. 5909 for display number >>> 9) >>> >>> * OSX >>> - Depends on OSXvnc (http://www.redstonesoftware.com/osxvnc/OSXvnc.html) >>> - Looks for server executable in /Applications/OSXvnc.app/OSXvnc-server >>> - Only the primary display can be shared >>> - Uses port 5900 for server >>> >>> Users should note the following with respect to security and VNC: >>> - VNC is regarded as a security risk >>> (refer to http://www.realvnc.com/faq.html#security) >>> - Firewall holes must be opened to allow access to the VNC server from >>> outside your network. Ports are identified above in the plaform >>> notes. >>> >>> >>> ** Execution >>> >>> VenueVNCServer.py will typically be executed as follows: >>> >>> python VenueVNCServer.py --venueUrl >>> https://someserver:8000/Venues/default >>> >>> On OSX, the environment settings file must be sourced into your >>> environment >>> before running VenueVNCServer.py (the file is >>> /Applications/AccessGridToolkit.app/Contents/Resources/setupenv.sh). >>> >>> A complete list of command-line options is available by passing the '-h' >>> option. >>> >>> Bugs should be filed in the AccessGrid bugzilla database at >>> http://bugzilla.mcs.anl.gov/accessgrid . >>> >> >
