Custom Query (16363 matches)
Results (1615 - 1617 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4111 | fixed | Mac OSX Host: Numlock Misbehaves When Focus Changes from Host-to-Guest | ||
| Description |
I use an Apple extended keyboard (includes numeric keypad). I've noticed odd behavior with numlock for the numeric keypad when focus is switched from the Host-to-Guest. In summary one of two things happens:
This behavior is reproducible with VBox 2.2.2 using Mac OSX (Leopard) Host and WinXP Guest as outlined below. First: Set-up Guest in Fullscreen Mode in its own Space I prefer to run in Fullscreen Mode with a WinXP guest in its own Space. I like to easily switch Spaces back and forth with ctrl-arrow. You can do this if you do the following:
Now on to unusual behavior with a numeric keypad. . . I have an iMac with an Apple wireless extended Mac keyboard (i.e. numeric keypad included) and I do a lot of number entry in my work. With this keyboard the "numlock" is the key combination "shift-clear". When switching Spaces from Mac use (I'll call it a "Mac Space" from here on) back to my VBox guest WinXP ("Guest Space" from now on) the numlock is off. To turn the numlock back on I have to do the "shift-clear" twice to resume use of the numeric keypad in the Guest Space. Now here is another strange thing I noticed, if you switch Spaces 2x using the configuration outlined above the numlock comes back on without activating it. Since this numlock behavior might be a bit hard to follow from the above, you can see it in action for yourself with the following experiment:
Pretty weird! This just demonstrates this problem of the numlock reactivating on every-other Space switch from Mac Space to Guest Space. Otherwise you have to activate the numlock twice to use the numeric keypad after a change in focus. This seems to be a Virtualbox 2.2.2 bug. If you have a work-around to keep a numeric keypad enabled during Host-to-Guest focus changes (as with my Space switching) please let me know. |
|||
| #4168 | obsolete | Grayed-Out USB Devices Require Cable Dance to Connect to Guest | ||
| Description |
I've been working with VirtualBox 2.2.2 and 2.2.4 with a Mac OSX (v. 10.5.7) Host and WinXP SP3 Guest. I have noticed a problem with a grayed-out USB device (a signature tablet HID in my case). To get the grayed-out device to show up in the USB Devices list for activation I can add a filter (either device specific or empty). The problem I've got now is that each time I start the VM the device is grayed-out in the USB Devices list. With a filter applied, the only way I can activate the device is by going through the unplug/replug the USB cable dance.
I'd like to see these sort of grayed-out USB devices just shows up in the device list each time the guest is started without going through the cable dance of unplugging & replugging cables.
Observations About Installing Grayed-Out USB Device (My Experiences) I thought some of my experiences might help you address this problem with grayed-out USB devices.
Failed to attach the USB device "X" to the virtual machine
|
|||
| #5723 | fixed | USB Devices Menu Grayed Out - VirtualBox 3.1.0 | ||
| Description |
I've run into a strange problem after upgrading a Mac OSX Host from VirtualBox 3.0.12 to the new 3.1.0 build. The "USB Devices" menu for the Guest is completely grayed out. This problem has been listed in the forum for about a week. Please see images and further details at forum post: http://forums.virtualbox.org/viewtopic.php?f=8&t=25474 Here's what I'm running on this machine:
Host = Mac OSX Leopard ( v. 10.5.8 ) Interestingly, I can still attach to USB devices through the icon in the lower right-hand-side of the Guest window. I thought perhaps reinstalling VBox 3.1.0 might fix this problem with the grayed out USB Devices menu. I've tried two reinstalls so far without success. I can revert my WinXP VM back to VBox 3.0.12 and then use the USB Devices menu just as before -- everything works fine. The problem is reproducible. I couldn't locate any info on resolving this problem. This appears to be a bug. Please let me know if you have questions or need further details to resolve this problem. VBox log attached. |
|||

