Xiaofan Chen wrote: > There is a warning, not so sure if it is really of importance or not. > ... > C:\work\libusbx\libusbx-1.0.11-win\examples\bin32>xusb.exe -d 0483:3748 > Using libusbx v1.0.11.10499 > > Opening device... > [timestamp] [threadID] facility level [function call] <message> > -------------------------------------------------------------------------------- > > [ 0.000000] [000004a0] libusbx: warning [init_device] could not get node > connect > ion information for device '\\.\USB#VID_0000&PID_0000#5&2D0620DE&0&1': [87] > The > parameter is incorrect.
You understand this is not the same device, right? 0000/0000 is what you get when a device fails to enumerate at the hardware level. -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
