Hi Xiaofan, > libusb-win32 still uses libusb-0.1 API (with extensions on its own > async APIC and isoc support for Windows).
Ok, thanks for the update > How do you install the driver? Take note you need to install > a suitable driver for your device to use libusb-win32. I think this is the part I've omitted :-( It might explain why it works on my old XP installation, where the FTDI official VCP drivers are installed. > 1) To use inf-wizard GUI, this will replace the original vendor > driver with libusb0.sys. The vendor application will not run > any more. Ok, I'm fine with this solution. > Zadig driver installer for winusb, libusb-win32 and libusbk > http://sourceforge.net/apps/mediawiki/libwdi/index.php?title=Zadig Ok, thanks. I think I'll stick with lisbusb 0.x to start up, till I find a workable combination. I have another question related to the way libusb-win32 manages devices. I'm using an FTDI 4232H device for the test, along with PyFtdi. This USB device is a composite one, which contains 4 interfaces, each of them is reporting two endpoints. Under Linux and OS X, the device appears as a single device, with 4 interfaces Under Windows, it seems the device appears as 4 distincts devices, with 1 interface each. Is it the expected behavior? Thanks for your help, Emmanuel. ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ pyusb-users mailing list pyusb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pyusb-users
