|
From: Alex <Ale...@ya...> - 2011-08-11 07:52:05
|
Thank you very much for the support! I don't know how could I miss that libusb-win32-devel-filter-1.2.5.0 tool. I hope it will solve my problems. Can't wait to get to the office and check it on a clean machine. Arguments on using filter driver not being preferable are noted, but still it's the only way, so I'll take the risk. Only one last question (I hope) - may I have a setup script with which libusb-win32-devel-filter-1.2.5.0 installer was created? I would like to recreate it but tune here and there for unattended installation, or even embed it into my program's setup, but I don't know which registry records it creates. Thank's again for your help. Best regards, Alex 11.08.2011, 11:21, "Xiaofan Chen" <xia...@gm...>: > On Thu, Aug 11, 2011 at 3:08 PM, Xiaofan Chen <xia...@gm...> wrote: > >> 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 case. >> So you are kind of on your own if some MTP device does not >> like the filter and causes BSOD... > > That being said, we have not received any BSOD report recently. > And if you indeed find a problem, we will try to fix it if possible. > > Still take note the filter driver will not work for some device > like those using UMDF (user mode driver framework) since > libusb0.sys is a kernel mode filter and a upper filter and it is not > possible to have a kernel mode filter on top of a user mode filter > like those based on UMDF. > Eg: http://sourceforge.net/tracker/?func=detail&aid=2993645&group_id=78138&atid=552262 > > -- > Xiaofan > |