RE: RealVNC 4.1.2 does not work with MacOS 10.4.8
Alex, While you can do that, it's obviously only useful if you want to run X11 applications, not standard Mac applications. Cheers, Wez @ RealVNC Ltd. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Pelts Sent: 19 October 2006 21:58 To: [EMAIL PROTECTED] Cc: vnc-list@realvnc.com Subject: Re: RealVNC 4.1.2 does not work with MacOS 10.4.8 Since mac osx is bsd based you can easy compile the existing vnc server for unix. Regards, Alex [EMAIL PROTECTED] wrote: Just as a quick follow-up on my previous email: I found a good VNC server for Mac OSX (OSXvnc V1.71) here: www.redstonesoftware.com/products/vine/index.html (I couldn't find any on the RealVNC website) OSXvnc is probably derived from RealVNC because it works real well with the RealVNC 4.1.2 on my winXP machine. Thanks Freddy ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: RealVNC 4.1.2 does not work with MacOS 10.4.8
Hi Freddy, OSXvnc is based on our old VNC 3 system and appears to, like the VNC 4 system, have been developed to remain compatible with VNC 3. Regards, Wez @ RealVNC Ltd. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Freddy Jensen Sent: 19 October 2006 20:52 To: vnc-list@realvnc.com Cc: [EMAIL PROTECTED] Subject: Re: RealVNC 4.1.2 does not work with MacOS 10.4.8 Just as a quick follow-up on my previous email: I found a good VNC server for Mac OSX (OSXvnc V1.71) here: www.redstonesoftware.com/products/vine/index.html (I couldn't find any on the RealVNC website) OSXvnc is probably derived from RealVNC because it works real well with the RealVNC 4.1.2 on my winXP machine. Thanks Freddy ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: I have Desktop/Font resolution issues it seems
Has anyone seen this issue with fonts before? Jose Huerta United Stationers Email: [EMAIL PROTECTED] Office Phone: 847-627-2067 Cell Phone: 847-878-4961 Fax: 847-627-7067 From: Huerta, Jose Sent: Wednesday, October 18, 2006 1:20 PM To: vnc-list@realvnc.com Subject: I have Desktop/Font resolution issues it seems Hello, I have recently installed VNC 4.1 on an HP-UX 11.11 Unix server and also downloaded the Windows VIEWER version. I am able to get my desktop to display as you can see from my printscreen capture, but the FONTS/TEXT appears very out of shape, like I don't have the correct fonts. I did try to look on the message boards and found some suggested changes, like adding the font paths to the vncserver file, but no luck Any suggestions on what I may need to do? Do I need to have a .Xresources file under my Home Directory? Thanks, Jose Huerta United Stationers Email: [EMAIL PROTECTED] Office Phone: 847-627-2067 Cell Phone: 847-878-4961 Fax: 847-627-7067 [demime 1.01d removed an attachment of type image/jpeg which had a name of image001.jpg] ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
Driver not support Planar/chunky
I'm trying to get a vnc server (tight vnc) installed on a customer's machine so we can remote administer it. I am attempting to have the customer install it as we are a good distance from the customer. when I attempt to connect, the customer reports an error message popping up on their machine. it says driver not supported and then something about planar and chunky. the machine is running windows 98 ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
Re: RealVNC 4.1.2 does not work with MacOS 10.4.8
James, That is true. I did not think of that. I am not a mac person, but I thought they use some sort of X server as a foundation for UI. I guess not. Regards, Alex James Weatherall wrote: Alex, While you can do that, it's obviously only useful if you want to run X11 applications, not standard Mac applications. Cheers, Wez @ RealVNC Ltd. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Pelts Sent: 19 October 2006 21:58 To: [EMAIL PROTECTED] Cc: vnc-list@realvnc.com Subject: Re: RealVNC 4.1.2 does not work with MacOS 10.4.8 Since mac osx is bsd based you can easy compile the existing vnc server for unix. Regards, Alex [EMAIL PROTECTED] wrote: Just as a quick follow-up on my previous email: I found a good VNC server for Mac OSX (OSXvnc V1.71) here: www.redstonesoftware.com/products/vine/index.html (I couldn't find any on the RealVNC website) OSXvnc is probably derived from RealVNC because it works real well with the RealVNC 4.1.2 on my winXP machine. Thanks Freddy ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
Is anyone using VNCSERVER on AIX?
Has anyone installed and is using VNCSERVER on AIX? Jose Huerta United Stationers Email: [EMAIL PROTECTED] Office Phone: 847-627-2067 Cell Phone: 847-878-4961 Fax: 847-627-7067 ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: setting server rfb port to non-default - on the vncviewer
John,
vncviewer -geometry 1440x1062 -passwd z ipaddr::4918:19
/dev/null and that worked.
I think the ':19' after the port is immaterial. Try connecting to
ipaddr::4918:abcd or even ipaddr::4918abcd; it works. It makes
sense because you cannot have more than 1 display listening on a single
port (the second Xvnc will complain that it cannot bind to the given
port) unless using inetd.
-siva.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of John Lumby
Sent: Friday, October 20, 2006 4:33 PM
To: [EMAIL PROTECTED]; vnc-list@realvnc.com
Subject: RE: setting server rfb port to non-default - on the vncviewer
James Weatherall wrote
John,
No, you don't - the syntax you are specifying to your VNC Viewer
(host::port:display) is not valid. The two valid syntaxes are:
Host:port_or_display (display if 0-99, port otherwise) and
Host::port(always port)
i.e. you specify *either* a VNC display number *or* a TCP port number.
VNC display numbers 0-99 are just a short-hand for TCP port numbers
5900 to 5999.
I hate to argue with someone who has a realvnc email but my recent
experience is in direct contracdiction of what you have written:
1).I started my vncserver with options
vncserver :19 -geometry 1440x1062 -name x -rfbport 4918
(I can explain why but not relevant)
Here is the Xvnc process:
Xvnc :19 -desktop xx ... -geometry 1440x1062 ... -rfbwait 12
-rfbauth -rfbport 5919 -fp ... -rfbport 4918
NB the two -rfbport options. - the first (I assume) always
specified,
and the second from my vncserver option. And to show which one took
precedence:
here is netstat output to show which port it actually is
listening
on:
netstat -an | egrep -e 4918|5919
tcp4 0 0 *.4918 *.*
LISTEN
tcp4 0 0 ipaddr.4918 other_ipaddr.34849
ESTABLISHED
2)and now here is the command I used on my workstation to connect :
vncviewer -geometry 1440x1062 -passwd z ipaddr::4918:19 /dev/null
and that worked.
Does that convince you? If not - try it!
John
_
Experience Live Search from your PC or mobile device today.
http://www.live.com/?mkt=en-ca
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
Confidentiality Notice
This e-mail (including any attachments) is intended only for the recipients
named above. It may contain confidential or privileged information and should
not be read, copied or otherwise used by any other person. If you are not a
named recipient, please notify the sender of that fact and delete the e-mail
from your system.
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
Re: setting server rfb port to non-default - on the vncviewer
On Fri Oct 20, 2006 at 04:32:37PM -0400, John Lumby wrote: James Weatherall wrote John, No, you don't - the syntax you are specifying to your VNC Viewer (host::port:display) is not valid. The two valid syntaxes are: Host:port_or_display (display if 0-99, port otherwise) and Host::port(always port) i.e. you specify *either* a VNC display number *or* a TCP port number. VNC display numbers 0-99 are just a short-hand for TCP port numbers 5900 to 5999. I hate to argue with someone who has a realvnc email but my recent experience is in direct contracdiction of what you have written: 1).I started my vncserver with options vncserver :19 -geometry 1440x1062 -name x -rfbport 4918 (I can explain why but not relevant) The :19 there is telling it to start X server 19 which, by default, would start on port 5919 (hence you get that option in the Xvnc process). This is then overridden by the -rfbport option in your command line, hence the server listens on port 4918. 2)and now here is the command I used on my workstation to connect : vncviewer -geometry 1440x1062 -passwd z ipaddr::4918:19 /dev/null and that worked. Does that convince you? If not - try it! The X server you specify here is used purely to figure out which port to connect to - it's not used in any other way by the client. If you explicitly specify the port then it doesn't need that. Have you tried starting the viewer with just: vncviewer -geometry 1440x1062 -passwd z ipaddr::4918 Anything beyond the port number is (presumably) ignored by the vncviewer application (whether that's by design or purely coincidental I don't know). Cheers, Robin -- ___ ( ' } | Robin Hill[EMAIL PROTECTED] | / / ) | Little Jim says | // !! | He fallen in de water !! | [demime 1.01d removed an attachment of type application/pgp-signature] ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: setting server rfb port to non-default - on the vncviewer
John, I'm afraid that you are mistaken. In the example you give, either ipaddr::4918 Or ipaddr:4918 Are valid, and will work. ipaddr::4918:19 is not a valid server specification but happens to work because of the way VNC Viewer interprets the port/display number specification. Cheers, Wez @ RealVNC Ltd. -Original Message- From: John Lumby [mailto:[EMAIL PROTECTED] Sent: 20 October 2006 21:33 To: [EMAIL PROTECTED]; vnc-list@realvnc.com Subject: RE: setting server rfb port to non-default - on the vncviewer James Weatherall wrote John, No, you don't - the syntax you are specifying to your VNC Viewer (host::port:display) is not valid. The two valid syntaxes are: Host:port_or_display (display if 0-99, port otherwise) and Host::port(always port) i.e. you specify *either* a VNC display number *or* a TCP port number. VNC display numbers 0-99 are just a short-hand for TCP port numbers 5900 to 5999. I hate to argue with someone who has a realvnc email but my recent experience is in direct contracdiction of what you have written: 1).I started my vncserver with options vncserver :19 -geometry 1440x1062 -name x -rfbport 4918 (I can explain why but not relevant) Here is the Xvnc process: Xvnc :19 -desktop xx ... -geometry 1440x1062 ... -rfbwait 12 -rfbauth -rfbport 5919 -fp ... -rfbport 4918 NB the two -rfbport options. - the first (I assume) always specified, and the second from my vncserver option. And to show which one took precedence: here is netstat output to show which port it actually is listening on: netstat -an | egrep -e 4918|5919 tcp4 0 0 *.4918 *.* LISTEN tcp4 0 0 ipaddr.4918 other_ipaddr.34849 ESTABLISHED 2)and now here is the command I used on my workstation to connect : vncviewer -geometry 1440x1062 -passwd z ipaddr::4918:19 /dev/null and that worked. Does that convince you? If not - try it! John _ Experience Live Search from your PC or mobile device today. http://www.live.com/?mkt=en-ca ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: Driver not support Planar/chunky
Caleb, TightVNC is based on the old VNC 3 codebase, which required chunky pixels. If you upgrade the server to VNC 4, you shouldn't see this issue. Cheers, Wez @ RealVNC Ltd. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Caleb Cushing Sent: 20 October 2006 13:56 To: vnc-list@realvnc.com Subject: Driver not support Planar/chunky I'm trying to get a vnc server (tight vnc) installed on a customer's machine so we can remote administer it. I am attempting to have the customer install it as we are a good distance from the customer. when I attempt to connect, the customer reports an error message popping up on their machine. it says driver not supported and then something about planar and chunky. the machine is running windows 98 ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
