From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from b-painless.mh.aa.net.uk ([81.187.30.52]) by ewsd; Fri Feb 1 13:37:03 EST 2019 Received: from 132.198.187.81.in-addr.arpa ([81.187.198.132] helo=quintile.net) by b-painless.mh.aa.net.uk with esmtp (Exim 4.89) (envelope-from ) id 1gpdg7-0001yQ-BR for 9front@9front.org; Fri, 01 Feb 2019 18:36:39 +0000 Received: from [10.14.98.253] ([85.255.236.125]) by quintile.net; Fri Feb 1 18:36:37 GMT 2019 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii From: Steve Simon Mime-Version: 1.0 (1.0) Date: Fri, 1 Feb 2019 18:36:36 +0000 Message-Id: <0168FCC2-569E-40C1-9397-A4B13B4F4927@quintile.net> Subject: Re: [9front] vncs: some clients report 'bad hextile data' References: <992C40EA1D1C5B2F36A1FD80DADC3B90@felloff.net> In-Reply-To: <992C40EA1D1C5B2F36A1FD80DADC3B90@felloff.net> To: 9front@9front.org X-Mailer: iPhone Mail (16C104) List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: encrypted ACPI over SOAP cloud factory-scale controller i know its functionally a bit different but you could try remote desktop to w= indows. i use rd(1) to talk to windows from plan9. it occasionally dies due to messa= ge decode failures, but a reconnect only takes 2 or 3 secs so i live with it= . -Steve > On 1 Feb 2019, at 5:03 pm, cinap_lenrek@felloff.net wrote: >=20 > yeah... i tried a bunch of vnc client and server implementations on window= s > when testing and each one seems to have something lacking. i had to try li= ke > 4 experimental builds of ultravnc until it started listening on ipv6 addre= ss > using obscure undocumented .ini settings. >=20 > the best working linux implementation seems to be tigervnc. >=20 > good luck. >=20 > -- > cinap