On Fri, Aug 17, 2012 at 5:56 PM, Pete Batard <p...@akeo.ie> wrote:

>
> Now, due to time constraints as well as other considerations
> (removing/deleting anything needs to be carefully considered), libwdi
> doesn't support restoring the original driver, so unless you also embed
> the driver to restore in the library, you'll be missing the second part
> of a driver toggle. Hopefully, in the long run, this feature can be
> added to the library. It's also likely that VMWare use a trick for the
> driver disabling and restoration, as non WHQL drivers would produce a
> prompt on restore if using the standard Windows API for driver
> replacement, which I don't think their process does.
>
>
I have a simple test program that uses libwdi to install libusbK for a mass
storage device. It works great! (although I haven't actually tried talking
to the device using libusbx yet...)

Then to get back to the mass storage device driver (USBSTOR.sys) all I have
to do is right-click on the file and select "uninstall" and when the dialog
pops-up select a checkbox that says something like "delete driver files as
well". Then I just had to "scan for new devices" and it picked up
USBSTOR.sys again and "mounted" the drive. So why the need, as you say, to
embed the original driver for the restore part?

And I hear that you are saying that if the driver was non-WHQL it would
lead to a prompt? I don't have any known non-WHQL devices to test with but
that's something we need to look into.

David
------------------------------------------------------------------------------
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

Reply via email to