On 2013.09.30 08:26, Ramon Zambelli wrote:
> I modified my device as you specified on the wiki and it now works as
> expected. Thanks a lot!!!
I'm very happy to hear that. Thanks for your patience while we looked
into it.
Regards,
/Pete
Hi,
I modified my device as you specified on the wiki and it now works as
expected. Thanks a lot!!!
Regards,
Ramon
On 9/29/2013 9:52 PM, Pete Batard wrote:
Hi,
Sorry for the late reply. I finally managed to test and reproduce the
issue, as well as figure out what you can do to avoid it (a
Hi,
Sorry for the late reply. I finally managed to test and reproduce the
issue, as well as figure out what you can do to avoid it (and no, using
Zadig is not an acceptable workaround - it completely defeats the
purpose of using WCID in the first place).
What you really want to do to keep us
On Tue, Sep 17, 2013 at 2:45 PM, Ramon Zambelli
wrote:
>> Also note that there exists limitations with regards to using WinUSB when
>> accessing interfaces using LIBUSB_RECIPIENT_INTERFACE
>> See
>> https://github.com/libusbx/libusbx/wiki/Windows-Backend#wiki-Known_Restrictions
>
> From the linkj
Please see my comments below:
On 9/17/2013 12:55 AM, Pete Batard wrote:
Hi,
I just tested on Windows 8 x64 and, while I was at it, Windows 8.1 x86
(MSDN RTM version) against the WCID enabled benchmark device and found
no issue when using an USB 2.0 device, be it through an USB 2.0 or and
USB
On Tue, Sep 17, 2013 at 6:08 AM, Ramon Zambelli
wrote:
> On 9/16/2013 3:36 AM, Xiaofan Chen wrote:
>> I think WinUSB version should not be the problem. Please post the
>> debug log (eg: xusb -d yourvid:yourpid).
>
> The problem seems to come from my device having two interfaces. If I
> change the
On 9/16/2013 3:36 AM, Xiaofan Chen wrote:
> I think WinUSB version should not be the problem. Please post the
> debug log (eg: xusb -d yourvid:yourpid).
The problem seems to come from my device having two interfaces. If I
change the device to only expose one interface libusb can open the
devic
On 9/16/2013 3:36 AM, Xiaofan Chen wrote:
On Sun, Sep 15, 2013 at 8:08 PM, Ramon Zambelli
wrote:
I have a device which used WCID to install WinUSB drivers. The driver
installs automatically as expected, but when I try to open the device
using libusbx 1.17 I get error -12 (ERROR_NOT_SUPPORTED).
On Sun, Sep 15, 2013 at 8:08 PM, Ramon Zambelli
wrote:
> I have a device which used WCID to install WinUSB drivers. The driver
> installs automatically as expected, but when I try to open the device
> using libusbx 1.17 I get error -12 (ERROR_NOT_SUPPORTED). I'm using
> windows 8.
> Using zadig I
I have a device which used WCID to install WinUSB drivers. The driver
installs automatically as expected, but when I try to open the device
using libusbx 1.17 I get error -12 (ERROR_NOT_SUPPORTED). I'm using
windows 8.
Using zadig I see that the driver installed is WINUSB (v6.2.9200.16384)
whic
10 matches
Mail list logo