Can't Disable Mouse Integration

[OstermanA]

I'm using Windows 7 to host Windows XP SP3 using VirtualBox version 4.0.6. Both the host and the guest are brand-new installs and Guest Additions were installed in safe-mode to allow for 3D support.

Now, whenever I try to disable mouse integration the host cursor flies to the top left corner of the left monitor (I have two) and the cursor in the host behaves unpredictably. It seems to try to follow the host cursor when I move it over the virtual machine, but the host cursor is not limited to the bounds of the guest window even when the status icon in the bottom corner claims mouse integration is off and the cursor is "captured".

I'm... not sure where to proceed. I hate just reinstalling randomly, as that teaches nothing. Does anyone have any ideas for working on this?

Edit: Oh yeah. I turn off integration because a couple apps I have do not tolerate it well and never have. However, as things stand they're unusable. The cursor movement is completely random.

Edit 2: Curiouser and curiouser, it only happens when I put the VBox window on the secondary screen. If left on the primary screen it functions correctly.I haven't seen a program with different behaviour between the two screens since KotOR.

[Sasquatch]

Do you also have Absolute Pointing Device disabled in the VM settings? That could explain the strange behaviour.

[OstermanA]

Enabling Absolute Pointing Device had no effect on the symptoms.

I don't know if it's related, but when I first started Dungeon Keeper 2 (The game I'm trying to play in the VM) the screen popped up with eight instances of the "the virtual machine is designed to operate in 32 bit color mode but is currently set to 16" message and DK2 crashes. If I click "Don't show me again" the VM window resizes a number of times very quickly, the DK2 crashes to desktop. If I set the VM to Scale Mode it operates correctly.

Before I reinstalled the host system, I believe I was running version 4.0.1 and in that DK2 ran almost perfectly (occasional CTDs if I did certain things in game, figured it was an issue with the beta nature of 3D acceleration).

Note that the capture issues exist even when I'm not trying to run this game, the VM itself is doing it when at rest state.

[Sasquatch]

I meant that you have to disable the setting. I now see that it can be read the wrong way. It's that when it's enabled it would explain the behaviour. Now what you need to do is disable the setting and disable mouse integration through the Machine menu. Should give you what you need. If Scale Mode is causing strange mouse behaviour, resize the window to match the resolution (probably 800x600).

[OstermanA]

I may have been unclear. APD was already disabled when symptoms began and activating scale mode solved a potentially unrelated problem. However, it is looking like a host-side rather than guest-side problem as I determined that on my dual head setup the unfortunate behavior only occurs when the VM window is partially or completely on the secondary monitor. I know from experience with Knights of the Old Republic that Windows can have issues with OpenGL on a secondary monitor. Pretty much everything in game failed to render at a low enough level OS screenshots would reflect this. I'll see if I still have them or try to recreate them, it was.... Odd.

I am going to try a Linux guest with and without the 3D extensions as well as Windows with and without and report the results.

Bottom line is I'm starting to think this is a graphical bug host-side but I don't know if it's from VBox or ATI's drivers. The KotOR issues were on an nVidia card and was unique at the time with the behavior so it could go either way.

[The Headacher]

I am going to try a Linux guest with and without the 3D extensions as well as Windows with and without and report the results.

No need. I installed a Linux in Virtual Box 4.0.6 (on win XP), and I am getting a very similar result. No guest additions or 3D extensions used. I can't reliably use the mouse in any way on the second screen, but it works fine on the first screen. I'd say we got a bug on our hands.

[OstermanA]

I'm showing the same behavior here. You can get the behavior on a VM with no OS at all just by hitting F12 to enter boot device selection. Definitely a bug.

I have never submitted a bug report to VB before, is there anything I should know before I do it?

[Sasquatch]

Bug reports go into the Bugtracker (separate account needed). When reporting bugs, be as specific as you can. Always include a log of a run that has errors, they're very picky at that. And of course, something that could be more important than anything: check if the bug you want to report doesn't exist yet.