Closed yoshiki-k closed 8 years ago
Hi,
Not sure I understand what is the issue.
What do you mean by sequence number? UsbDk patches VID/PID only, device serial number left as is. Does this introduce any problem?
What application are you using to view the device tree. Could you please provide some screenshots?
Thanks, Dmitry
Thank you for looking at the post. Is a screen shot. screenshot.zip
Current registry is as follows: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_2B23&Pid_CAFE&Rev_0001 \5&28677613&0&UsbDk6 -> DeviceDesc = C-Media USB Headphone Set \5&28677613&0&UsbDk8 -> DeviceDesc = USB 2.0 Camera \5&28677613&0&UsbDk10 -> DeviceDesc = USB 2.0 Camera \5&28677613&0&UsbDk12 -> DeviceDesc = C-Media USB Headphone Set
[Operating procedure]
Regards, yoshiki-k
Fixed in v1.00-14 by commit e68f982ff7370f9c75bcabce1b76f3df6d9299be.
usbdk is using a sequence number which is counted from the time of OS start-up in the device information. When I redirect the device in UsbDkController.exe, connection information of the device to the local PC registry will be logged.
Connect the device A to the root hub, after the redirect 10 times, and then restart the OS. When I was redirected to connect the device B to the same port, the name of the device A has been displayed in the tree of other devices. After it redirects 10 times, 11 times and later will show the correct name of the device B.
For the device that defines the iSerial in the device descriptor, it will be displayed in the previous device information regardless of the hub to connect.
Regards, yoshiki-k