Nicholas, VNC Viewer will only run when there are incoming updates to be processed. This will be the case if your remote desktop is changing rapidly, for example. VNC Viewer 3.3.7 will tend to consume more CPU, because it uses a less efficient method to draw the changes.
Xvnc does not need to use polling to detect changes - since it is the X server, it is implicitly aware of all the changes that are taking place. To reiterate: - The only reason that VNC Viewer would use CPU cycles is if it is processing incoming updates, i.e. if things are changing on the VNC Server's desktop. - If your laptop is overheating then there is something fundamentally wrong with either its power management drivers or its hardware. Application software cannot cause a healthy system to overheat! Regards, Wez @ RealVNC Ltd. > -----Original Message----- > From: Nicholas Keown [mailto:[EMAIL PROTECTED] > Sent: 02 March 2005 11:47 > To: James Weatherall > Cc: vnc-list@realvnc.com > Subject: Re: CPU overloading in WinVNC connecting to Linux box > > James, thank for the reply. The task causing the problem is > vncviewer.exe, hogging between 50 and 70% of CPU constantly, > causing overheating of my windows notebook. When I connect to > a windows box, there is no problem. > > I thought it could be related to the polling etc on the linux > box, and was wondering if these setting can be altered for a > standard fedora 3 install as a test. > > Has knowone else had these sorts of problems? I have seen it > in other threads here, but it was blammed on a buggy earlier version. > > Thanks. _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
