Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C2D With this information we should at least understand a lot better what the situation is, and if it should work or not. Then open the properties of a USB device, go to the "Details" tab, and get the value of the "Physical Device Object name". Then open the properties of the controller (not the device), get the driver details. The easiest way to find the USB controller in question, use the device manager, and in the "View" menu select "Devices by connection", and then start unfolding "ACPI based PC", "Microsoft ACPI-Compliant System", "PCI bus", and from there each USB controller until you find where your devices live. Not saying you must be wrong, we just need to get the necessary information. This change has been tested with the controllers and drivers (yes, the silly Windows USB controller driver design requires that the VirtualBox USB support uses different locations for different controller drivers), and many users confirmed that this works.
Complete failures are generally not related to specific devices, and in VirtualBox 4.2.18 we did make changes to the USB code on Windows, as anyone can see who looks at the ChangeLog. Klaus wrote:Sorry, you apparently missed that I was asking for the USB controller details.
0 kommentar(er)
