On Fri, Aug 24, 2012 at 4:06 AM, David Grant wrote:
> On Fri, Aug 17, 2012 at 5:56 PM, Pete Batard 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
On Thu, Aug 23, 2012 at 1:31 PM, Pete Batard wrote:
> Be mindful that what's currently missing in libwdi is not due
> to the developers thinking that it may be too complex to implement.
> Instead, it's just the usual matter of priorities.
> Uninstallation/restore has just been (and still is) low
On 2012.08.23 21:09, David Grant wrote:
> ...and I assume this part can all be automated through some API. I know
> someone else at our company that has done the "scan for new devices"
> part programmatically. I assume that uninstall part can be done through
> setupapi.
Yes, as a driver related AP
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 featu
On Thu, Aug 23, 2012 at 1:06 PM, David Grant wrote:
> 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.s
On Fri, Aug 17, 2012 at 5:56 PM, Pete Batard 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 lib
On Wed, Aug 22, 2012 at 5:00 PM, Xiaofan Chen wrote:
> Please take note VirutalBox's USB support is not Open Source.
> You need the extension pack which is under non-open-source
> license.
> https://www.virtualbox.org/wiki/Downloads
> https://www.virtualbox.org/manual/ch01.html#intro-installing
>
On Wed, Aug 22, 2012 at 3:06 PM, Pete Batard wrote:
> On 2012.08.22 18:55, David Grant wrote:
> > It just seems like the driver swapping is the main
> > issue we need to resolve.
>
> Well, if you want to contribute a driver swapping/removal patch to
> libwdi, I'll be happy to review it.
>
>
Thank
On Thu, Aug 23, 2012 at 1:55 AM, David Grant wrote:
> I don't understand why that would be the case. libusb + libusbK seems like
> the perfect solution for us especially when we consider the fact that we are
> already using libusb in the Linux (x86 + ARM) environments with great
> success. It just
On 2012.08.22 18:55, David Grant wrote:
> It just seems like the driver swapping is the main
> issue we need to resolve.
Well, if you want to contribute a driver swapping/removal patch to
libwdi, I'll be happy to review it.
Regards,
/Pete
---
On Tue, Aug 21, 2012 at 10:14 PM, Xiaofan Chen wrote:
> On Wed, Aug 22, 2012 at 8:04 AM, David Grant wrote:
> > Thanks for the detailed response Pete.
> >
> > So the big missing feature seems to be how to remove libusbK.sys and
> replace
> > it with the original driver without having to embed th
On Wed, Aug 22, 2012 at 8:04 AM, David Grant wrote:
> Thanks for the detailed response Pete.
>
> So the big missing feature seems to be how to remove libusbK.sys and replace
> it with the original driver without having to embed the original driver.
> Currently the original driver _can_ be restored
On Fri, Aug 17, 2012 at 5:56 PM, Pete Batard wrote:
>
>
> Well, libwdi can already perform the first part of silently switching an
> existing USB driver to libusbK: you could create a service based on
> libwdi (with libusbK embedded in the library), and use the libwdi silent
> installation facilit
On Sat, Aug 18, 2012 at 6:49 AM, David Grant wrote:
> On Wed, Aug 15, 2012 at 7:28 PM, Xiaofan Chen wrote:
>> You can use install-filter to install and uninstall libusb-win32 filter
>> on the fly without a reboot. But take note you need to use 32bit
>> install-filter.exe for 32bit system and 64bi
On 2012.08.18 00:03, David Grant wrote:
> After looking at what VMWare View Client does, they seem to replace the
> existing driver with their own generic USB driver called vmusb.sys after
> the user decides to remote a particular USB device. Then after the user
> decides to un-remote the device, o
On Fri, Aug 17, 2012 at 3:49 PM, David Grant wrote:
> On Wed, Aug 15, 2012 at 7:28 PM, Xiaofan Chen wrote:
>
>> On Thu, Aug 16, 2012 at 5:32 AM, David Grant
>> wrote:
>> > Ok, so that sounds promising. I guess the next question is: is it
>> possible
>> > to use libwdi to install a filter driver
On Wed, Aug 15, 2012 at 7:28 PM, Xiaofan Chen wrote:
> On Thu, Aug 16, 2012 at 5:32 AM, David Grant wrote:
> > Ok, so that sounds promising. I guess the next question is: is it
> possible
> > to use libwdi to install a filter driver for a device, or to replace that
> > device's driver, take over
On Thu, Aug 16, 2012 at 5:32 AM, David Grant wrote:
> Ok, so that sounds promising. I guess the next question is: is it possible
> to use libwdi to install a filter driver for a device, or to replace that
> device's driver, take over the device, and then put everything back to where
> it was, all
On Thu, Aug 16, 2012 at 5:07 AM, David Grant wrote:
> I've looked at using libusb-win32 as a filter driver but it
> seems I can only install it as a filter driver for all classes of the
> devices that are already plugged in.
That is not true. We provide the capability to install the filter driver
On 2012.08.15 23:09, Peter Stuge wrote:
> Pete Batard wrote:
>> WCID could help [1]
>
> Just a small note that the term Microsoft uses is "WinUSB Device".
Which is explained in the 3rd paragraph of the of the link provided at
[1]... Obviously, we can't use "WinUSB device" for something that
appl
Pete Batard wrote:
> Now, if part of your concern has to do with avoiding user intervention
> with regards to manually installing a driver, WCID could help [1] since
> WinUSB/WCID devices
Just a small note that the term Microsoft uses is "WinUSB Device".
That can help for finding their info abou
On 2012.08.15 22:32, David Grant wrote:
> Partially answering my own question here... I was just going through old
> posts to the mailing list and found this:
>
> >> 1. Can I use Zadig to install a WinUSB driver for the VID/PID?
>
> > Yes, that's one of the things it is meant for. You can also us
On 2012.08.15 22:07, David Grant wrote:
> Is it possible to do this (or something similar) on Windows at all
Not without Microsoft's help in making the underlying usbport.sys driver
(the one that accesses the device outside of a standard driver being
installed) generic enough to support all of t
On Wed, Aug 15, 2012 at 2:07 PM, David Grant wrote:
> On Linux we use libusb to access any that the user plugs in (except
> keyboard/mouse/hub). We just detach the kernal driver from the device and
> then claim the device and then send transfers to the device with
> libusb_submit_transfer. Is it
24 matches
Mail list logo
