OK, that sounds to be a good deal. Many thanks in advance, DRC! Am Samstag, 5. Mai 2018 19:24:12 UTC+2 schrieb DRC: > > 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/5f9b9e98-2007-423e-baa6-765fb2d1d280%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
