Changes between Version 190 and Version 191 of windows_backend

Timestamp:

06/20/11 15:39:38 (2 years ago)

Author:

stuge

Comment:

--

windows_backend

@@ -57 +57 @@
 == Driver Installation ==
 
-To access your USB devices with the Windows backend, if the device is not HID compliant, you will need to install the relevant driver. Two options are available:
+To access your USB devices with the Windows backend you will need to install the relevant driver. Two options are available:
   * The easiest option is to use the most recent version of our Automated Driver Installer GUI: "zadig.exe", which is part of the Windows Driver Installer library, '''[http://libwdi.akeo.ie libwdi]'''.[[BR]]
   The current version, which is compatible with both 32 and 64 bit Windows platforms, starting with Windows 2000, should be able to install a WinUSB driver for any USB device.[[BR]]
@@ -82 +82 @@
 == Development Considerations ==
 
-  * If you want to access devices outside of WinUSB [http://msdn.microsoft.com/en-us/library/aa476426.aspx WinUSB] or libusbK, such as HID ones, you can use the [http://git.libusb.org/?p=libusb-pbatard.git;a=shortlog;h=refs/heads/HID;js=1 HID branch], which is maintained separately due to an executive decision not to include HID support in Windows, from the current libusb maintainer, or use another library such as [http://www.signal11.us/oss/hidapi/ HIDAPI]. For more info about the HID removal, see the libusb-devel mailing list.
+  * If you want to access devices outside of WinUSB [http://msdn.microsoft.com/en-us/library/aa476426.aspx WinUSB] or libusbK, such as HID ones, you can use the [http://git.libusb.org/?p=libusb-pbatard.git;a=shortlog;h=refs/heads/HID;js=1 HID branch], which is maintained separately due to an executive decision by the current libusb maintainer not to include special case HID support for Windows, or you can use another library such as [http://www.signal11.us/oss/hidapi/ HIDAPI]. For more info about the HID removal, see the libusb-devel mailing list.
   * Windows' handling of composite devices is done with multiple drivers (VID_####&PID_####&MI_##), descendants of the usbccgp.sys driver (Composite Generic Parent), as this is Windows' default. For more info, see "2. How Windows handles a composite device" at [http://www.cygnal.org/ubb/Forum9/HTML/001050.html]. It is however possible to replace the composite parent driver with WinUSB to access the device.
   * Because Windows does not provide a native poll() function, and cygwin is the only development environment that provides such a call, the use of libusb file descriptors with poll() on cygwin is '''NOT''' supported. We should provide native Windows events, to use with WaitForSingleObject/WaitForMultipleObjects, in a future version of libusb.