RDP is always going to be fundamentally slower than TurboVNC. That's one of the reasons why TurboVNC exists. The ultimate solution is going to be to fix the keyboard mapping problem, but I need to sit down and try to reproduce it first. Hopefully I will have time to do so this week.
On 5/5/18 12:15 PM, torsten wrote: > Hi all, > > I just found a solution for the keyboard layout issue: VirtualBox has > its own RDP Server, so a VM can be accessed via RDP. Now I can see the > VM twice, once in the TurboVNC Client showing the VM through the > VirtualBox Viewer, and once in the RDP window. In the latter one all > keys provide the correct character in the VM. But there is a new > problem: The RDP window needs about 8-9 seconds to show the result, > while in the TurboVNC Client it is visible without any delay. So now I > could use the RDP window only for keyboard typing and the TurboVNC > Client only for seeing the response. But that's not practical, since any > mouse action must happen in the RDP window too for not loosing the > keyboard focus. So now I must try to accelerate the RDP connection > considerably. But I think, this I must ask otherwhere. Or has anyone an > idea? > > Kind Regards > Torsten -- You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/f6343875-b4d6-84cf-eb99-c6254d758cec%40virtualgl.org. For more options, visit https://groups.google.com/d/optout.
