Be careful on this last. We found that on certain distros, a reboot was
necessary (we tried the reload commands, but to no avail). I don't
remember now which distros were the problem (sorry).
-Original Message-
From: Tormod Volden [mailto:lists.tor...@gmail.com]
Sent: Tuesday, October 30,
We ran into the same problem with XP after migrating to W8 level
co-installers for WinUSB. We had to roll back our support for XP.
This can also occur if an item is built on Vista and you attempt to run
it on W8 (there are some items in the support DLL that are no longer
there).
-Original Mes
Thanks for your comments.
Just a note in regards to WinUSB and Windows 8. It would appear that a
device will not need to provide an INF as long as it provides Windows
specific info in its OS descriptors (refer to Microsoft tech note
http://msdn.microsoft.com/en-us/library/windows/hardware/hh450799
One of the major factors in using HID in unorthodox ways is that there
is no need for the Windows INF/driver install business. This has always
been a potential problem with a customer's machine (permissions and the
like). I agree that many devices using this class might be better served
using bulk,
Can libusbx run on Windows 8?
Thanks.
--
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
When our app first comes up (actually the interface layer for our apps),
it uses libusb to get a list of devices that are currently on the bus.
The information in that list is placed in our own internal list,
filtered by the user's request to our interface layer (in that, all USB
devices, devices w
Pete wrote:
"It is clear that part of libusb(x) during enum aims at
duplicating what we would actually like the OS to provide us with, which
is an up to date device list, with all the USB properties libusb(x)
requires already filled, and preferably cached. If the OS doesn't, I
think we could us
