Firefox/4.0b8pre SeaMonkey/2.1b2pre   
   hCO[lOLo>dRRnA[^CT1A^BL@[^Y@lV4ARVjg[7;GLGboB   
      
   >> What I did was to make sure that all the host controller drivers   
   (USBUHCD.SYS, USBOHCD.SYS, USBEHCD.SYS) use the standard   
   >> method of PCI power management to power up the USB host controllers on boot   
   (when the drivers receive the INIT call from the OS).   
   >> While PCI power management was always the way to go for EHCI (it's mandated   
   by the EHCI standard)   
   >> this was not true for earlier implementations of UHCI and OHCI (they had   
   and have their private way of powering up host controllers).   
   >> However, for newer UHCI and OHCI implementations they now also make use of   
   PCI power management (possibly on top of   
   >> their native methods).   
   >>   
   >> It seems that on shutdown of Windows (WinXP, Windows 7 etc.) Windows will   
   power down all USB host controllers via   
   >> PCI power management if they support it. Therefore they need to be powered   
   up via PCI power management.   
   >> Not doing lead to an endless loop at least in the USBUHCD.SYS driver.   
   >> (When you power up from power off, this is seemingly not a problem as the   
   BIOS will obviously do that by itself but YMMV).   
   >>   
   >> This is what my patches add to the existing USB drivers.   
   >>   
   >> Lars   
   >   
   > Okay, that makes sense (well, sort of). Next question: Where does the   
   > average user get the patches from, or do we all have to figure it out   
   > for ourselves?   
      
   Currently, it's only my private patch. I would be interested to know if it   
   also fixes the problem for other users that have this setup   
   and the same occasion of hang. Once I know it's reliable (and does not   
   introduce other problems) I would try and get in into   
   the eComStation.   
      
   Lars   
      
      
   --- Internet Rex 2.31   
    * Origin: Arcor (1:261/20.999)