On Thu, Jul 12, 2012 at 9:04 AM, Pete Batard <p...@akeo.ie> wrote: > Having recently reinstalled one of my Windows 7 platforms, I just found > that, while plugging the WinUSB WCID enabled Benchmark device, after a > search through Windows Update the WinUSB driver was installed automatically > the same way as it would be on the WCID enabled Windows 8 platform [1]. > > A second test on a different machine appears to confirm that at least for > x86 and x64 Windows 7, Windows Update now provides a full blow > WinUSB WCID driver for any device that can report the > USB\MS_COMP_WINUSB Compatible Hardware ID.
Nice. > > Closer inspection seems to indicate that: > > 1. Once Windows Update has churned through the search, a > winusbcompat.inf, dated 2012.05.11, gets installed in > C:\Windows\System32\DriverStore\FileRepository\winusbcompat.inf_<arch>_neutral_#############\ > > 2. The inf provider for that file is identified as "Windows Phone", and the > resulting driver package installed is set to version 1.0.0.0, though the > winusb.sys is still the 6.1.7601.17514 system one. This version discrepancy > seems to be due to Microsoft setting DriverVer to "05/11/2012,1.0" in the > .inf. > > In other words, Windows 7, and possibly earlier versions up to XP SP1, have > now been brought up to the level of Windows 8 in terms of WCID capabilities, > albeit with the major difference that Windows 8 doesn't have to fetch the > driver from Windows Update, and therefore can offer near-instantaneous & > offline WinUSB installs. > > This is probably good news for Windows libusb/libusbx users, as well as > libusb/libusbx as a whole, since it should invite USB manufacturers to > simply add the WinUSB WCID to their devices and avoid the user installation > headaches with USB drivers on Windows. I think this is a good for Microsoft's part. WinUSB will play an important role in the future and more and more USB device will use WinUSB as the driver down the road and not using the generic HID device. > Not sure how this will impact libusb-win32 & libusbK though... I think there will be not much impact. libusb-win32 has many users and the compatibility with libusb-0.1 API makes it a good choice for people porting libusb-0.1 API based program to Windows. And libusb-0.1 API will be there for a long time. As for libusbK, it is quite new and it is Windows only. I expect it to be a niche player (especially the API) behind libusb-win32 and libusb-1.0 API (libusb and libusbx) for some time. For Windows only users who want nice API to be used, libusbK will still be quite attractive if compared to libusb-win32 API and libusb-1.0 API. libusbK API is also a superset of WinUSB API. So down the road, we expect libusbK API to have quite some users as well, but probably not as popular as libusb-0.1/libusb-win32 API and libusb-1.0 API. -- Xiaofan ------------------------------------------------------------------------------ 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
