On 2012.08.23 21:06, David Grant wrote: > So why the need, as > you say, to embed the original driver for the restore part?
If you read what I wrote, you'll see that what I pointed out is if you wanted to do it with the *current* version of libwdi, i.e. one that doesn't implement a restore feature. I wasn't talking about limitations for implementing the restore feature itself. Basically, if you want to do a restore with the *current* version of libwdi, and you know the old driver, you can. But you need to have the driver you plan to "restore" embedded in the library. This isn't a proper solution though, just a workaround for a missing feature. > And I hear that you are saying that if the driver was non-WHQL it would > lead to a prompt? Logically, that's what I would expect, since if the user had to go through a prompt during driver installation, they're likely to have to go through the same prompt when the same driver is restored (re-installed). Regards, /Pete ------------------------------------------------------------------------------ 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
