I'm not sure why it works like this but I found out what I was doing wrong
shortly after posting my question.
I was actually wasn't using the libusb driver (although I thought I tried
this). I got it working by using the libusbK-inf-wizard.exe from libusbk.
I replaced the driver with WinUSB.sys driver. It's been difficult for a usb
novice to figure out the different hang ups in terms of drivers for windows
(signed vs unsigned etc..). Are there any pitfalls with replacing the
default driver with WinUSB?
Thank you for you response Tim.
On Wed, Sep 12, 2012 at 12:20 PM, Tim Roberts <t...@probo.com> wrote:
>
>
> Interfaces 0 and 1 are CDC (communication class). It's possible those
> interfaces are already being claimed by a virtual COM port driver.
>
> How did you install the libbusb driver?
>
> --
> Tim Roberts, t...@probo.com
> Providenza & Boekelheide, Inc.
>
>
>
>
------------------------------------------------------------------------------
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
