Page 1 of 1

USB support in Beta2

Posted: 24. Jul 2007, 03:33
by ozydingo
Sorry, this must be the last thing you guys want to deal with right after you got it all working for the beta2; but:

Failed to create a proxy device for the USB device. (Error: VERR_SHARING_VIOLATION).

Result Code: 0x80004005
Component: Console
Interface: IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}

I was trying to read my USB thumbdrive, a SanDisk Cruzer, 512MB. With or without the drive mounted in OS X I get the same error.

Posted: 24. Jul 2007, 08:25
by achimha
Unfortunately, Apple changed the USB stack in 10.4.10 which no longer allows us to grab USB mass storage devices. You can use Shared Folders to access the stick from your VM. The next release will contain a rewritten USB implementation that also works on 10.4.10.

Posted: 25. Jul 2007, 15:46
by ozydingo
Gotcha; thanks!

Posted: 26. Jul 2007, 16:38
by kwharrigan
I received a similar error for a USB to serial adapter I have. Is that considered a USB mass storage device as well?
achimha wrote:Unfortunately, Apple changed the USB stack in 10.4.10 which no longer allows us to grab USB mass storage devices. You can use Shared Folders to access the stick from your VM. The next release will contain a rewritten USB implementation that also works on 10.4.10.

Posted: 1. Aug 2007, 00:46
by ozydingo
achimha wrote:You can use Shared Folders to access the stick from your VM.
So I did that; I set up my XP machine to access my thumb drive as a shared folder. Today I wanted to run the machine, but I didn't have the thumb drive plugged in, and on the machines list my XP machine comes up as "inaccessible" because the shared folder could not be found (since the thumb drive isn't there!). Yes, I could just stick it in right now to get around this, but what if I didn't have my thumb drive with me? I cannot change the machine settings; the button is greyed out because the machine is inaccessible. So missing shared folder completely locks me out of the machine and its settings, where I would go to remove the drive from the shared folder list in order to run the machine. It seems you should still allow access to a machine's settings even if the machine is marked as inaccessible for this kind of reason. Better yet, also allow the machine to run in this case but display a warning that the shared folder could not be found.

Andrew