i cant find the hardwarer when i try to use usb support on virtualbox with windows xp
anyone know how to fix this? thanks
virtualbox usb help
This is a bit old topic already and I was just waiting until the time I got free enough to provide the solution I discovered.
At least with me, the launcher doesn't really make the driver work to VirtualBox and you fall down forced to install the driver. However, I discovered a solution, read this .reg file that tells all that the VirtualBox USB driver does to the system:
Edit: FIXED VirtualBox full portable USB support is possible with the code below
Instructions:
1. Where I cut off the data numbers, ImagePath, place the driver filename as following: \??\C:\Documents and Settings\User\My Documents\Folder\VBoxUSB.sys, if it is not assigned like that ! ('Documents and Settings' is the default folder for who use Portable Software inside My Documents foder)
2. Edit the German AutoIt3 VirtualBox wrapper launcher source code to meet the following structure: "cmd /c sc create VBoxUSB binpath= "&chr(34)&"%CD%\"& $arch &"\drivers\usbdrv\device\VBoxUSB.sys"&chr(34)&" type= kernel start= auto error= normal displayname= "&chr(34)&"VirtualBox USB"&chr(34)&" group= Base". That's the right structure to the creation of the drivers services.
3. Edit the remaining service drivers and start, stop, delete commands to meet their original .inf files (except for the 'start' argument). I don't see any reason to modify such things. Done!
Note: I don't know from where the value DriverDateData came from... GOOD NEWS! The driver works without this value!
These values below are just for system curiosity, you don't need them for this!
I cut off some data numbers to avoid people getting personal and useless information. After some meditation I have found the only importants and necessary keys: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0001 and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VBoxUSB
As you can see, you can point a custom path to the inf file as long as the name of the file has the "oemxxxx.inf" format, where xxxx represents the installation number.
Now It works
!!
JRE portable and Visual C++ '05 Runtime portable, wait for me
At least with me, the launcher doesn't really make the driver work to VirtualBox and you fall down forced to install the driver. However, I discovered a solution, read this .reg file that tells all that the VirtualBox USB driver does to the system:
Edit: FIXED VirtualBox full portable USB support is possible with the code below
Code: Select all
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0019]
"InfPath"="C:\\Documents and Settings\\User\\My Documents\\VB\\app32\\drivers\\usbdrv\\device\\oem12.inf"
"InfSection"="VBoxUSB.Dev"
"InfSectionExt"=".NT"
"ProviderName"="Sun Microsystems, Inc."
"DriverVersion"="3.0.0.0"
"MatchingDeviceId"="usb\\vid_80ee&pid_cafe"
"DriverDesc"="VirtualBox USB"
"DriverDate"="6-30-2009"
"DriverDateData"=hex:00,40,02,b6,15,f9,c9,01
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VBoxUSB]
"Type"=dword:00000001
"Start"=dword:00000003
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):00,
"DisplayName"="VirtualBox USB"
"Group"="Base"
"DevLoader"="*ntkern"
"NTMPDriver"="VBoxUSB.sys"
"Tag"=dword:000000161. Where I cut off the data numbers, ImagePath, place the driver filename as following: \??\C:\Documents and Settings\User\My Documents\Folder\VBoxUSB.sys, if it is not assigned like that ! ('Documents and Settings' is the default folder for who use Portable Software inside My Documents foder)
2. Edit the German AutoIt3 VirtualBox wrapper launcher source code to meet the following structure: "cmd /c sc create VBoxUSB binpath= "&chr(34)&"%CD%\"& $arch &"\drivers\usbdrv\device\VBoxUSB.sys"&chr(34)&" type= kernel start= auto error= normal displayname= "&chr(34)&"VirtualBox USB"&chr(34)&" group= Base". That's the right structure to the creation of the drivers services.
3. Edit the remaining service drivers and start, stop, delete commands to meet their original .inf files (except for the 'start' argument). I don't see any reason to modify such things. Done!
Note: I don't know from where the value DriverDateData came from... GOOD NEWS! The driver works without this value!
These values below are just for system curiosity, you don't need them for this!
Code: Select all
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup]
"Installation Sources"=hex(7):00,
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Device Installer]
"SearchOptions"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\LastKnownGoodRecovery\LastGood]
"INF/oem1.inf"=dword:00000001
"INF/oem1.PNF"=dword:00000001
"INF/oem2.inf"=dword:00000001
"INF/oem2.PNF"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\GroupOrderList]
"Base"=hex(3):00,
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_PORTABLEVBOXUSBMON]
"NextInstance"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB\Vid_80EE&Pid_CAFE]
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB\Vid_80EE&Pid_CAFE\5&fffffffe&0&2]
"DeviceDesc"="VirtualBox USB"
"LocationInformation"="W270"
"Capabilities"=dword:00000000
"UINumber"=dword:00000000
"HardwareID"=hex(7):00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00
"CompatibleIDs"=hex(7):00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00
"ConfigFlags"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB\Vid_80EE&Pid_CAFE\5&fffffffe&0&2\Device Parameters]
"ExtPropDescSemaphore"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB\Vid_80EE&Pid_CAFE\5&fffffffe&0&2\LogConf]
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB\Vid_80EE&Pid_CAFE\5&ffffffff&0&2]
"DeviceDesc"="VirtualBox USB"
"LocationInformation"="USB camera"
"Capabilities"=dword:00000000
"UINumber"=dword:00000000
"HardwareID"=hex(7):00
"CompatibleIDs"=hex(7):00
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"
"Class"="USB"
"Driver"="{36FC9E60-C465-11CF-8056-444553540000}\\0001"
"Mfg"="Sun Microsystems, Inc."
"Service"="VBoxUSB"
"ConfigFlags"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB\Vid_80EE&Pid_CAFE\5&ffffffff&0&2\Device Parameters]
"ExtPropDescSemaphore"=dword:00000001
"SymbolicName"="\\??\\USB#Vid_80EE&Pid_CAFE#5&ffffffff&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}"
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB\Vid_80EE&Pid_CAFE\5&ffffffff&0&2\LogConf]As you can see, you can point a custom path to the inf file as long as the name of the file has the "oemxxxx.inf" format, where xxxx represents the installation number.
Now It works
!!JRE portable and Visual C++ '05 Runtime portable, wait for me
Last edited by castman on Sat Jul 18, 2009 1:31 pm, edited 5 times in total.
Re: virtualbox usb help
I'm puzzled by something in catman's post.
The Regedit shows a "Driver" key which finishes "..}\\0001" (please note: I am interested only in the fact that there are *two* backslashes there), while in the accompanying text there is only "..}\0001".
Does this matter or not?
I have discovered a similar anomaly between two PCs running WinXP SP3: the one with the *two* backslashes refuses to show any USB memory sticks in My Computer if they are plugged in after system boot, while the one with *one* backslash happily shows them immediately they are plugged in and they disappear when they are unplugged. So I did a Google Groups advanced search and this post showed up, and I'm wondering if I should do something about it.
All comments would be greatly appreciated.
The Regedit shows a "Driver" key which finishes "..}\\0001" (please note: I am interested only in the fact that there are *two* backslashes there), while in the accompanying text there is only "..}\0001".
Does this matter or not?
I have discovered a similar anomaly between two PCs running WinXP SP3: the one with the *two* backslashes refuses to show any USB memory sticks in My Computer if they are plugged in after system boot, while the one with *one* backslash happily shows them immediately they are plugged in and they disappear when they are unplugged. So I did a Google Groups advanced search and this post showed up, and I'm wondering if I should do something about it.
All comments would be greatly appreciated.
Re: virtualbox usb help
OMG! Don't assign my registry log to existing devices! That was not my intention.
As I previously said that numbers oemxxxx.inf AND ALSO (correcting me) \xxxx were modified to avoid providing personal and useless information
.
No big secrets at all. That's why people should avoid copy and pasting without thinking what the info. are actually does.
And don't always use this code, the system changes it whenver a driver is installed/modified/uninstalled. These are crescent numbers.
AH! I understood what were you trying to say! As the information I read on the internet, the regedit.exe program was buit in C language. Then in order to get a backslash in registry values, you must do a double backslash.
That was not my intention.As I previously said that numbers oemxxxx.inf AND ALSO (correcting me) \xxxx were modified to avoid providing personal and useless information
.No big secrets at all. That's why people should avoid copy and pasting without thinking what the info. are actually does.
And don't always use this code, the system changes it whenver a driver is installed/modified/uninstalled. These are crescent numbers.
AH! I understood what were you trying to say! As the information I read on the internet, the regedit.exe program was buit in C language. Then in order to get a backslash in registry values, you must do a double backslash.
FIXED
People who are interested take a look at my first post.
Re: virtualbox usb help
Why don't you try another virtual machine application? For Linux there are better options than Windows, I suppose. Example: KVM. Take a look at http://wikipedia.org !!