#62 Filter driver should not be power policy owner

v0.1.12.2
closed
Main (14)
9
2012-07-06
2009-03-03
Tim Roberts
No

The libusb-win32 driver always acts as a power policy owner (see http://msdn.microsoft.com/en-us/library/ms798249.aspx). When it is an FDO, that's perfectly fine. But when the driver is a filter, that's wrong. It actually causes blue screens if the filter is applied over a KMDF or UMDF driver.

Discussion

  • Xiaofan Chen
    Xiaofan Chen
    2009-04-20

    Nice finding. Do you think this is the main problem with libusb-win32 filter (which is said to have no future) causing it not to work under Vista 32bit? Or are there other problems? The device driver seems to work for me under Vista 32bit.

     
  • Xiaofan Chen
    Xiaofan Chen
    2009-04-21

    This is in line with the following discovery.


    http://wikee.iphwn.org/news:libusb-win32-filter_under_vista
    Libusb-win32-filter was not designed to run on Windows Vista, but it can be made to work. You must right click the “libusb-win32-filter-bin-0.1.12.1.exe” executable, click the Compatiblity tab, and check “Run this program in compatibility mode for”, and select Windows XP (Service Pack 2) in the list.

    If you fail to do these steps, the driver will install without any complaints, but all USB devices on the computer will be rendered inoperable until you figure out how to uninstall it.

    Please also be aware that the driver is unstable on Windows Vista and occasionally causes the operating system to kernel panic (blue screen of death). This happens particularly when the computer attempts to enter a low-power mode.

    If you do not wish to install libusb-win32-filter on Vista (and we do not recommend you do), you may still use the ipsw tool without it.


     
  • Xiaofan Chen
    Xiaofan Chen
    2010-04-20

    I think this can be fixed and it will then solve many issues with the filter driver.

     
  • This should be fixed in revision 163 of the repository.

     
  • This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).