On 31.3.2013 1.56, "Xiaofan Chen" <xiaof...@gmail.com> wrote:
>> Ref: http://www.osronline.com/showthread.cfm?link=239028 >> Tim Roberts wrote the following in the above thread, >> "A right-click install simply runs the [DefaultInstall] section >> and is only useful for non-PnP devices. It doesn't associate the >> driver with any PnP identifiers." Thanks, once I got the tip that it was usable in this situation I found the info from MS documentation too. > >The solution here is to write a simple driver installer. >1) Microchip provides a driver installer example for the >CDC-ACM driver package in the Microchip Application Library, >using DIFx API. > >microchip_solutions_v2013-02-15/USB/PC - Driver Management >Tool/Example CDC Installer > >2) You can also use libwdi's wdi-simple example, using >either Inno Setup or NSIS. >https://github.com/pbatard/libwdi/tree/master/examples Yes, you are right, I need to something like that I and will have a look at that. Thanks again for everyone who responded. Just came to think of it, what I really should do! If I turned my device into real vendor specific device and not masquerade it as CDC ACM I could use libusbx to access it. That would not be hard, but so far I have got away without ANY native libraries on the host side but been able to do everything from Java. My app is a single jar, which is double clickable and I also automatically produce .exe file and an .app bundle from it and a it looks like bash script on Linux, so it is really very nice both for end users and me. If I add a native library I would have to compile that on all the platforms or cross compile it, unless binaries are available. I guess for libusbx binaries are easy to obtain. And then I would need find/hack a mechanism that extracts the natives from the single jar to the file system on launch of my app (and deletes them on exit). Doable as I'm using JNA which does exactly that though it does not expose that mechanism. BUT under the hood libusbx uses the native API on each platform to access USB right? And I can call any native API from Java with JNA without ANY native code and the C tool chain issues...so what I really should do is to re-write libusbx in Java! Just like my PureJavaComm project does. Now that would be no-end useful for Java community. Too bad I don't have the time for *that* at the moment. Ok, cheers and thanks for letting me bounce off this issue here. br Kusti This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general. ------------------------------------------------------------------------------ Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
