Page 1 of 1

Mouse probs in Win XP guest after installing guest additions

Posted: 5. May 2008, 04:43
by timprice
A request for suggestions - installation of VirtualBox 1.6 Guest Additions stops the mouse working on a previously functioning Windows XP Pro SP2 guest running on an Ubuntu 8.04 host (the problem was the same on earlier versions of VirtualBox and Ubuntu).

Once Guest Additions are installed and the guest is rebooted, mouse integration captures the mouse (basic PS/2 wheel mouse), but it does not work (it seems to right-click randomly a few times on the desktop, but left-clicks don't work at all; the keyboard also works only intermittently).

If I disable mouse integration then the mouse seems randomly to right-click very quickly and repeatedly all over the place, so the guest is either way completely dysfunctional. I've tried various screen resolutions for the guest (since sometimes when I reboot after installing Guest Additions the resolution has changed and is set very low, as Windows XP informs me), but this makes no difference.

Any advice would be greatly appreciated - having looked through these forums a bit it seems unusual that installing Guest Additions makes things worse instead of better.

Posted: 14. Jul 2008, 02:46
by jptechnical
***Update***

I found some references to logitech devices in my forum searches... I changed the mouse to generic microsoft ps2 mouse, instead of the logitech one that was there. All is gold! If you have this problem, set the mouse on your guest to a generic MS mouse and see if that does it.




Same problem for me. This was a p-to-v of a working XP machine. In my case, I can use the mouse just fine when connecting to the guest via vnc, just not from the actual host. Any ideas?

Thanks - it worked!

Posted: 18. Jul 2008, 12:23
by timprice
jptechnical, Many thanks for your suggestion, which worked perfectly for me. I'd noticed that virtualbox had mysteriously chosen to use a Logitech mouse driver, and must admit had thought I'd long ago tried changing to the correct generic Microsoft PS/2 version, but obviously I hadn't, because when your post prompted me to try doing so again the problem was immediately fixed. Much appreciated!