Those dropped connections are dropped by the Kindle's firmware. I'm sorry that I didn't had much time lately to look into these issues. But the dropped connections are not really specific to the piece of software, that's due to a daemon that will drop longer lasting TCP connections (except for some special dedicated ports, first and foremost SSH).

I've got to experiment more with SSH tunneling of the VNC connection, which should get rid of the disconnection problem. Well, anyone might give that a try. Forwarding TCP connections via SSH is documented on the Web quite often.

Oh! Yes, that should be it. I just didn't know I could just stop the daemon - I thought it would get restarted by the framework again :-) Yes, it's that one that is killing the connections. So wrapping this in the call to the application should work, I think.

Running this solved for me (tip from the KindleTerm forum)
/etc/init.d/netwatchd stop
....

Doesn't seem to help in this case

Sometimes the errors pause (I'm testing this from terminal mode on K3)
& then resume when I move a window on the mac (running vine server because of the Crypto problem using the resident mac vnc server). Pic' attached shows a sample. For a split second after moving a window, the mac screen does appear on K3, followed by the "partially updating..."

Oh! You're running it via the terminal application. Well, unfortunately that wouldn't work - the terminal and the VNC viewer have no way of synchronization. I think running the viewer via launchpad or via SSH/Telnet login is the way to go... The terminal *might* keep quiet if you redirect those debug messages of the VNC viewer to /dev/null, i.e. append ">/dev/null 2>&1" to the command.

Oh! You're running it via the terminal application. ..
I think running the viewer via launchpad or via SSH/Telnet login is the way to go... The terminal *might* keep quiet if you redirect those debug messages of the VNC viewer to /dev/null, i.e. append ">/dev/null 2>&1" to the command.

Initially I tried it via LaunchPad, but nothing, so tried from terminal so I could see some error output - which I did of course

I don't know why it didn't occur to me that the display would be overwritten anyway! I didn't know about the sync' aspect though.

Hi, i tried to follow the instruction in the zip file, and I have some questions.
1) I can't find the launchpad on my kindle 3, am i missing anything?
2) is the entire process be done on Linux platform? because there is no exe file in the zip file.
3) I successfully installed the "tsinghoo's approach" and it's on wifi connection, but the refresh rate is too slow to use it. Does anyone have the same result?

Please could you do a tutorial (a video or written) step by step for no experts in linux of how to use a Kindle (i dont know mine's version, i guess is the simple one) as a second monitor. It will meant a lot to me, i have sight problems and my eyes get tired very quickly and i cant use my computer properly.

Sad to hear of those problems. I start with a warning: I would not yet consider this software to be a good solution for production use, at least not yet, in its current state. It's working to some extent and it has a published code base that allows anyone with the skills to work on it. And for the technically advanced, it might provide enough to be useful.

That said, I think doing a video tutorial is not a good approach to this. First, I do not think that messing with your Kindle to run native apps like this one is a good idea if you do not know what you're actually doing. Even copy & paste isn't always without risks. One small unforeseen glitch and your device ends up bricked in the worst case. I consider this risk to be immense when it comes to video tutorials.

Then there's another problem: there isn't a single right way to do this, there are many ways. Each of them might make sense depending on what you focus on.

However, there's a basic outline:
- jailbreak
- install launchpad
- install (i.e. copy) kindlevncviewer
all of these are documented within this forum.

Then:
- set up vnc server on your OS of choice. There are plenty of vnc servers out there. Probably easiest is to forward your current PC display with "x11vnc" (but mind that the display resolutions will probably differ). You could also use a dedicated VNC-X11-Server like realvnc, tightvnc & co, but you will probably not want that until - someday - kindlevncviewer supports input, too...

I'm sorry that I cannot offer the capacity to do a full hands-on guide. Maybe someone else will jump in, but it's always hard to write proper documentation. And this especially goes for documentation that shall not expect related knowledge.