The line 122 error seems to be the general fail code for if not everything at least many things. I got it to work with the zip from post#1. So if anyone now what/where too change and in what file(s) that would be appreciated. Have not tried that yet and probably do not have time for 1-3 days. So i assume i have too change something (or a bunch) in the kvnc lua files. I do want too run windows on my nuc that is the machine i would use the kobo as a screen for.īut i guess i could do linux if there is no fix for the crap looking graphics on win.īut it would probably take days or even weeks to get linux setup the way i need it, and that does not include xvnc if that decide to not wanna play ball. I do get the same 32bit/true color on on ultravnc/thightvnc/realvnc (on windows).Īnd from what i have learned there is no arguments that can set the resulotion/bit/color/etc on windows like there is on x11vnc/xvnc. 09:14:54 TRUE colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0And then specifically the 32bit and true color crap. 09:14:54 Least significant byte first in each pixel. 09:14:54 Connected to VNC server, using protocol version 3.8 09:14:54 Selecting security type 2 (1/2 in the list) 09:14:54 We have 2 security types to read 09:14:54 VNC server supports protocol version 3.8 (viewer 3.8) luajit a -password bulldozer 192.168.2.1 I assume this has something too do with it.Ĭode: ~]# cd kvncviewer]#. Have tried with medium and fast mode too (and combined with dithering) but it only gets ALOT worse. If i try running kvnc with the no dithering mode it gets a bit better the text is then readable (as long as the text is black or white on a black or white background) but anything that have any greyscale or color is really still really bad. If you for example scroll one line the text becomes almost impossible too read scroll one more line and you can´t even see that it is supposed to be text.Īnd i have setup the kobo resulution on windows (so the kobo screen is used all the way). Now the problem is it looks really really bad and is hard too read. I guess i assumed that a vncviewer that you can´t choose port with command line arguments would use the standard vnc port 5900. The problem was that i did not change the port from 5900 to 5901 on the vnc server/s. Ok got it working now even on the 4,5,9587 FW and usbnetwork works in both pbchess and KSM menu. I have opened ip/ports in firewall, also tried to disable windows firewall (after disable wifi card) but no go.Īlso tried with -password added in the startup string and with -debug added (with or without -password) but gets the same error again.īut if so where and what name, i looked around but could not find any. I have tried ultravnc/tightvnc/realvnc (not at the same time and with or without password) but get the same error. : at 0x0000bd31I assume that "ConnectToTcpAddr: connect" means that i get a connection to the 192.168.2.101 ip (my win8,1 that i connect kobo with usbnetwork to).īut then the vnc server rejects to connection.Īnd the input device error i assume is for input devices/touchscreen on the kobo (so you can controll the vnc server os). luajit: a:152: cannot initialize client 05:54:47 Unable to connect to VNC server luajit a 192.168.2.101:1Ĭould not open input device /dev/input/event2 (possibly harmless)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |