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
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the
'subdir-objects'
automake: automake option hasn't been enabled. For now, the corresponding
output
automake: object file(s) will be placed in the top-level directory.
However,
automak
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
New feature of the Windows 8.1 (native) upgraded drivers:
http://msdn.microsoft.com/en-us/library/windows/hardware/dn303354%28v=vs.85%29.aspx#usb_wdk
Maybe this was mentioned elsewhere, but I don't remember seeing it.
Also confirmed from my 8.0 and 8.1 platforms: the 8.1 version of
winusb.dll (
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).
