Mouse location mismatch using Remote Desktop and VRDP.
Posted: 15. Sep 2010, 00:18
Dear Ma'am or Sir:
Is there a fix for the mouse location mismatch when using Remote Desktop to access a VB guest via VRDP? This is a more fundamental problem than a lagging mouse due to performance. The expected behavior is for the mouse pointer to be fully captured in Remote Desktop with an escape character (back to the Windows instance running Remote Desktop, used to access the VB guest). Instead, the Windows mouse and the VB guest mouse (inside the Remote Desktop window) appear at different locations on the screen and scroll at different speeds. This makes working in the VB guest OS from a Remote Desktop window very difficult. VB version 3.2.8 r64453 is in use on an OEL5 host, running an OEL5 guest. The default port 3389 (set in the VB Display Settings) is used to enable remote access using Remote Desktop (via VRDP). Remote Desktop is running on Windows XP 2002 SP3. The FAQs, forum posts, and user manuals have been searched to no avail. This is in support of a very important project!
Thank you very much and best regards,
Andrew Paullin
(414) 212-5372
Is there a fix for the mouse location mismatch when using Remote Desktop to access a VB guest via VRDP? This is a more fundamental problem than a lagging mouse due to performance. The expected behavior is for the mouse pointer to be fully captured in Remote Desktop with an escape character (back to the Windows instance running Remote Desktop, used to access the VB guest). Instead, the Windows mouse and the VB guest mouse (inside the Remote Desktop window) appear at different locations on the screen and scroll at different speeds. This makes working in the VB guest OS from a Remote Desktop window very difficult. VB version 3.2.8 r64453 is in use on an OEL5 host, running an OEL5 guest. The default port 3389 (set in the VB Display Settings) is used to enable remote access using Remote Desktop (via VRDP). Remote Desktop is running on Windows XP 2002 SP3. The FAQs, forum posts, and user manuals have been searched to no avail. This is in support of a very important project!
Thank you very much and best regards,
Andrew Paullin
(414) 212-5372