Den 2011-03-15 17:48 skrev Long, Phillip GOSS:
Dale:
We use UltraVNC on our Windows machines, and it's free as far as I
know (I'm not involved in licensing and that kind of noise). I
have had better luck with the UVNC server than with the Real one,
but the vncviewer works about the
Den 2009-09-24 18:29 skrev Jon Watte:
Peter Rosin wrote:
Den 2009-09-24 01:41 skrev Jon Watte:
In SetColourMapEntries, are the color values high-justified (most
significant bits) or left-justified (least significant bits -- if so,
how many?)
Huh? All 16 bits are significant.
Which means
Den 2009-09-24 01:41 skrev Jon Watte:
In SetColourMapEntries, are the color values high-justified (most
significant bits) or left-justified (least significant bits -- if so,
how many?)
My guess is high-justified, but the spec leaves this up to the
imagination, so I thought I'd check to make
Den 2009-09-14 21:37 skrev Christophe Lohr:
So, I wonder if a protocol extension could be interesting. Isn't it?
Look here:
http://www.tigervnc.org/cgi-bin/rfbproto
And search for ExtendedDesktopSize. I don't know what implementations
support that extension though...
Cheers,
Peter
Den 2009-03-13 13:01 skrev Pierre Ossman:
Hi,
We've been working on client initiated screen size changes and need to
extend the protocol to do that.
In order to minimise the number of extensions, we'd also like to
accommodate multi-head configurations with this new protocol.
So we'd like your
Den 2009-03-16 11:45 skrev Pierre Ossman:
On Mon, 16 Mar 2009 10:44:07 +0100
Peter Rosin wrote:
Hi Pierre!
There is also the WMVi pseudo-encoding (0x574d5669, or WMVi in FourCC)
to consider. A problem with this new proposal is that *both* WMVi and
this multihead scheme are better than
Den 2009-03-16 15:00 skrev Pierre Ossman:
On Mon, 16 Mar 2009 13:29:38 +0100
Peter Rosin wrote:
Den 2009-03-16 11:45 skrev Pierre Ossman:
That would be very against the RFB mentality, yes. But the wiki entry
you pointed to suggests that these encodings are just used for
offline rendering
Den 2009-03-16 18:15 skrev Pierre Ossman:
On Mon, 16 Mar 2009 16:54:20 +0100
Peter Rosin wrote:
Den 2009-03-16 15:00 skrev Pierre Ossman:
Annoying. Do they also rely on putting the conversion requirements on
the client?
Yes. If a client claims support for WMVi, it has to support all pixfmts
Den 2008-12-17 11:53 skrev Daniel P. Berrange:
On Wed, Dec 17, 2008 at 08:56:02AM +0100, Peter Rosin wrote:
*snip*
1. Is there any compelling reason to *not* sasl_encode/sasl_decode
the 6.1.3 SecurityResult message when there is a SSF layer? I think
using sasl_encode/sasl_decode
Hi again!
Sigh, sorry to reply to self, I guess the best was to find bugs is
to make a public statement of some sort...
Den 2008-12-17 08:56 skrev Peter Rosin:
--- README.sasl.orig2008-12-17 07:19:28.046875000 +0100
+++ README.sasl.new 2008-12-17 07:21:50.43750 +0100
@@ -174,5
Hi!
Den 2008-12-14 17:53 skrev Daniel P. Berrange:
I have defined a mapping of the SASL authentication scheme into the RFB
authentication protocol. Please could you allocate an official security
type code for use with this auth scheme, under the name SASL.
*snip*
I looked a bit at this and
On Tue, Jan 08, 2008 at 10:20:50AM -, James Weatherall wrote:
In practice desktop names are currently ASCII-only, but new standard RFB
protocol elements all use UTF-8 for string data. I'd recommend that
third-party encodings, etc also use UTF-8 for string data for consistency.
So, Peter,
On Mon, Jan 07, 2008 at 05:02:25PM +0100, Peter Estrand wrote:
NumberName
-306 DesktopName pseudo-encoding
Bzzzt -307 :-)
Here's the description:
A client which requests the DesktopName pseudo-encoding is declaring that
it is capable of coping with a change of the desktop name.
On Wed, Dec 12, 2007 at 01:50:38PM -, James Weatherall wrote:
Hi Anon,
This is a know limitation of the Refresh Screen option in VNC Free Edition
VNC Free Edition-based software, which isn't safe to use if the VNC Viewer
might be changing pixel format at a later point.
Nice to see it
On Thu, Dec 13, 2007 at 10:09:07AM -, James Weatherall wrote:
Hi Anon Peter,
The VNC Personal Enterprise Editions use a new scheme that does not have
this limitation.
You won't hit problems with the VNC Free Edition system unless you send
multiple outstanding update requests (as is
On Thu, Dec 13, 2007 at 12:40:11PM -, James Weatherall wrote:
Peter,
It is a limitation of the RFB 3.x protocol, which requires that update
requests are required to be matched 1-to-1 by framebuffer updates, although
this isn't strictly required if the pixel format isn't going to change.
On Tue, Dec 04, 2007 at 04:09:56PM -0800, Dave Stoft wrote:
My conclusion has been that I have misunderstood the syntax or
application
of the syntax with the command-line method but I have been unable to
locate
explicit examples to show where I made the error(s). Can you point to
the
On Mon, Aug 06, 2007 at 12:03:02AM -0400, Boyd Campbell wrote:
Good evening all,
I'm using VNC to connect to a specific server on a remote LAN from many
different clients at many different locations. However, using the same
machine on one network vs. another, I'm either able to get into
guessing.
Cheers,
Peter
Anyone else with thoughts? I'd very much like to hear from the VNC
community. Thank you.
-Original Message-
From: Peter Rosin [mailto:[EMAIL PROTECTED]
Sent: Monday, August 06, 2007 5:11 AM
To: Boyd Campbell
Cc: vnc-list@realvnc.com
Subject: Re: Inconsistent
On Fri, Feb 02, 2007 at 12:30:49PM -, James Weatherall wrote:
Hi Noriaki-san,
I've had encoding number 17 allocated to Hitachi ZYWRLE - using this
encoding number will ensure compatibility with standard VNC and
VNC-compatible releases. The next release of the VNC codebase will
Hi!
I have a working version of an RFB protocol extension, one of the
things missing before I publish is what numbers I should use.
I need one pseudo-encoding, one server-client message and one
client-server message, all can go under the name gii (General
Input Interface) in the protocol spec.
On Tue, May 15, 2007 at 08:13:29AM +0700, Constantin Kaplinsky wrote:
Hello Peter,
Peter Rosin wrote:
While implementing some vnc software I noticed a problem in the RFB
spec (version 3.8, 5 October 2006). It fails to mention that there is
no security result for authentication method
On Tue, May 15, 2007 at 11:00:00AM +0100, James Weatherall wrote:
Peter Rosin wrote:
Side note: a certain Windows only VNC client is a true pest when you
are implementing a server and want to be compatible, that for sure
took some workarounds (Oh great, you can do 3.8, then I want 3.4,
oh
Hi list!
While implementing some vnc software I noticed a problem in the
RFB spec (version 3.8, 5 October 2006). It fails to mention that
there is no security result for authentication method 'None'
for protocol version 3.3. As this differs from at least version
3.8 I think there should be some
On Fri, Feb 16, 2007 at 11:22:45AM +0100, Corne Beerse wrote:
Dhillon, Gurjit wrote:
I have set up vnc as a daemon mode through xinetd, it is working fine.
Great.
User give ipaddress and the predefined port number to connect the vnc
server. The only difference is now user doesn't
On Thu, Feb 15, 2007 at 01:03:24PM -0600, Matt Campbell wrote:
Hello James:
I have implemented the encoding, and so far, it seems to work well,
though I'll admit I'm testing on fast CPU's (at least 2 GHz). Please
allocate an encoding number for this encoding.
Also, a clarification on
On Mon, Jan 29, 2007 at 10:11:20AM +0800, lizhong wrote:
Peter Rosin wrote:
[1]
http://www.ggi-project.org/documentation/libggi/current/display-vnc.7.html
[2] http://www.ggi-project.org/
[3] http://sourceforge.net/cvs/?group_id=16307
It's strange that the first two web links in your
On Fri, Jan 26, 2007 at 05:44:40PM +0800, lizhong wrote:
Hi all,
As we know, vnc is used to send desktop to a client from the
server. I've dig into the emails of vnc mail list, and found a
single application vnc server called VNC CD Player. This program
was never published, and I just
28 matches
Mail list logo
