From mboxrd@z Thu Jan 1 00:00:00 1970 Mime-Version: 1.0 (Apple Message framework v753.1) In-Reply-To: <1f6f8dbaddf506e174b22cc079a13d09@quintile.net> References: <1f6f8dbaddf506e174b22cc079a13d09@quintile.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Ethan Grammatikidis Date: Tue, 1 Dec 2009 22:28:20 +0000 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] remote access to audio devices Topicbox-Message-UUID: a67fc82e-ead5-11e9-9d60-3106f5b1d025 On 1 Dec 2009, at 8:44 pm, Steve Simon wrote: >> VNC can (has been) be a butt-saver' - but pales in comparison to >> remote desktop >> / remote X for relative responsiveness and seamlessness. > > My experience of serving a Windows desktop to a plan9 terminal > is that TightVNC with the DFMirage "Mirror driver" works really well. I've had responsiveness issues when the viewing machine hasn't enough CPU power to decode the screen data in real-time. A lot of power seems to be needed, my PDA, a 416MHz ARM can't cope with any compression at all, I have to limit vncviewer to copyrect and raw encodings only. Encoding doesn't seem to need half as much CPU power. I ran Xvnc on a headless server with a 400MHz AMD K6 with no issues that I recall. All that gear was using either TightVNC or the plain vnc-x.y.z.tar.gz from RealVNC. When using Vine Server on a 466MHz Apple screen updates are not really adequate, while the mouse pointer lags if I use the VNC server supplied with OS X Tiger on the same machine. x0vncserver is a known problem server which I haven't used, IIRC it basically works by taking screenshots continuously and sending those.