It has been replaced with a similar TightVNC-specific protocol extension, the new DesktopConfiguration pseudo-encoding, which allows users to choose a specific monitor in the viewer when a remote host has multiple monitors connected.
Server for Windows: Support for the third-party ExtendedDesktopSize pseudo-encoding has been removed due to incompatibility issues, complexity, and error-proneness. This version includes both the VNC viewer and server. Well maintained and being actively developed. Cross-platform, available for Windows and Unix, compatible with other VNC software. Useful in remote administration, remote customer support, education, and for many other purposes. Free, GPL-licensed, with full source code available. You can open files, launch applications, and perform other actions on the remote desktop almost as if you were physically there. With its intuitive interface, you can interact with the remote screen as if you were sitting in front of it. RealVNC client version used is "5.0.5 Windows 64bit" on Windows 7 Professional.Ībout the "no keyboard connected" error, I've not tried nothing but connecting a keyboard to the MacMini (when I'm remotely connected I need to have a real keyboard connected to the Mac Mini !).TightVNC is a free and Open Source remote desktop software that lets you access and control a computer over the network. 
For example there is no distinction between left and right buttons when you are connected with VNC (for every client I've tested). In my tests the real events that are received by the server are always different from the local events of an attached keyboard.
Use RealVNC or TightVNC (2.7.10 or above see ) clients to have "Option" key enabled: TightVNC prior to 2.7.10 and UltraVNC viewers do not send the "Windows" key (which will be mapped to "Option" mac key). For strange reasons, with TightVNC both the native OSX server and the RealVNC server treats both the Win/Alt keys as Command. Use VineVNC server, because I found this is the only VNC server that generates complete Mac keyboard events. 
Leave native language keyboard on the remote Mac, but set "US Keyboard" on the local PC. 
I've tried with the native VNC server installed in OS X 10.8.4 Mountain Lion, the one installed in OS X 10.6.8, with VineVNC server (v4.01) and RealVNC server (v5.0.6). I suggest to use it to find what is happening for keyboard related problems. I've performed some tests with Event Viewer tool found into KeyRemap4MacBook software, by comparing events with the local keyboard and the VNC connected keyboard. I found nearly the same problems with Mac-Mini (late 2012), with Italian keyboard.
0 kommentar(er)
