|
From: Xiaofan C. <xia...@gm...> - 2011-08-11 07:08:49
|
2011/8/11 Alex <Ale...@ya...>: > Service... I also know nothing of Windows services and > definitely would'n want to use it. > Using device driver is absolutely unacceptable in my case, I > really need filter driver. Yes, you need the filter driver. > On a clean machine I can't get libusb to detect devices without > device driver. But when I install device driver, and then remove it, > replace by the original one and install filter driver everything's OK. > Why is that so? Even more so - I got the impression that after the > installation of a device driver for one device I can use filter upon > ANY device and detect it successfully. Have to doublecheck it, though. Ah, now I understand you better. In order to install the filter driver, you have to have the kernel driver and dll installed first. We provide the installer for you with the name libusb-win32-devel-filter-1.2.5.0.exe http://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.5.0/ > Is it possible to get the source code of inf-wizard utility? I have the > impression it's capable of doing what I need, I just need to make it > automatic. The source codes are there. It used libwdi. http://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.5.0/ libusb-win32-src-1.2.5.0.zip libwdi wiki is here: http://sourceforge.net/apps/mediawiki/libwdi/index.php?title=Main_Page Your application need to autorun in order to be able to catch the insertion of the device when the user plugs in the MTP device, that is why I suggest a Windows service. But please remember, we would not recommend this use cases. So you are kind of on your own if some MTP device does not like the filter and causes BSOD... -- Xiaofan |