Douglas Kosovic douglask at itee.uq.edu.au
Wed Oct 6 22:09:19 CDT 2004

Hi Randy,

> So you mean that in order for VenueVNC to work on Windows there needs to 
> be a server and viewer running on the same machine?

As there is no VenueVNC server for Windows (at least not yet?), what I do 
instead is start a VenueVNC server on Linux, then run rdesktop (full screen, 
no border decoration, 16 bit depth) and connect to a Windows XP or 2003 PC 
running Microsoft's Remote Desktop.

As Microsoft's Remote Desktop has much better hooks into Windows than any 
VNC server running on Windows, screen refreshes, scrolling etc is much 
better. Although, the latest TightVNC server is suppose to have better hooks 
into Windows than previous VNC versions, I don't know how it compares to 
Microsoft's Remote Desktop.

> Sorry, I feel a bit dense about this - I use VNC all the time, and 
> presumed
> that what I would be doing with the VenueVNC app was to start up a viewer
> that I could point to an arbitrary venue server out there.  Is this an
> incorrect assumption?

Yep, incorrect assumption, using the AGTk VenueClient GUI, you can only 
connect to a VenueVNC server, not an arbitary VNC server.

> Or is this the first step towards setting up a service that a node 
> presents to the world?

I guess so.

> If there's documentation that I should go and read (more than the readme) 
> please feel free to point me in that direction.

Okay, how about a bug report to read :-) , see:

As VenueVNC server hasn't been officially announced, I'm imagine there will 
be more documentation closer to or after the release date.


More information about the ag-tech mailing list