mail-complaints-to="news_AT_tioat_DOT_net"   
   From: "Doug Bissett"    
      
   On Sat, 24 Dec 2011 00:04:55 UTC, Mike Luther    
   wrote:   
      
   > Hi Lars!   
   >    
   > Lars Erdmann wrote:   
   > > Forgot to mention:   
   > >    
   > > make sure that USBEHCD.SYS comes FIRST in config.sys.   
   > >    
   > >    
   > > Lars   
   > >    
   > >    
   > > "Lars Erdmann"  schrieb im Newsbeitrag    
   > > news:4ef4a90d$0$7613$9b4e6d93@newsspool1.arcor-online.net...   
   > >> I have updated the USB host controller drivers   
   > >> USBUHCD.SYS,USBOHCD.SYS,USBEHCD.SYS   
   > >> I have now placed these on hobbes.   
   > >> They will eventually make it into directory:   
   > >> /pub/os2/system/drivers/misc   
   > >>   
   > >>   
   > >> I have now READDED USBD.SYS. It's experimental. Don't expect too much    
   > >> but you may want to give feedback.   
   > >> If it doesn't work, back out to USBD.SYS 10.162 and retry with the new    
   > >> HC drivers before you report any bug against the HC drivers    
   > >> (USBUHCD.SYS,USBOHCD.SYS,USBEHCD.SYS) themselves !   
   > >>   
   > >> The biggest fix: http://svn.netlabs.org/usb/ticket/9   
   > >>   
   > >> I still have problems with OHCI driver. You need to have a device    
   > >> attached on a OHCI port in order for getting the HC to work.   
   > >> The data transfer as such works ok. I am working on the issue.   
   > >> Unfortunately there is no real good information on how to properly    
   > >> initialize the HC and the ports. I am looking into the Linux and Apple    
   > >> code.   
   > >>   
   > >>   
   > >>   
   > >> Lars   
   > >>   
   > >    
   >    
   > Doesn't SET KILLFEATUREENABLED=1 have to come first, followed by the .JFS   
   and    
   > then HPFS device drivers with the AUTOCHECK specifications absolutely   
   required    
   > defined in each of them.  Which if those device drivers are not in that   
   place    
   > and in that order, there are certain system failures which will actually   
   then    
   > totally corrupt a dirty shutdown accident, that can on reboot cause the    
   > horrible OS/2 is not able to operate your hard drive unfixable error that    
   > follows.  Upon which your only hope to recover a drive is from a backup tape    
   > or whatever?   
   >    
      
   I am sure that he means that USBEHCD.SYS should be the first of the    
   USB drivers, not first in CONFIG.SYS, which is incorrectly claimed by    
   half a dozen other things (not sure why, and it used to be that it was   
   best to be last). My systems seems to be just as happy with it last.   
      
   --    
   From the eComStation of Doug Bissett   
   dougb007 at telus dot net   
   (Please make the obvious changes, to e-mail me)   
      
      
   --- Internet Rex 2.31   
    * Origin: The gateway at Omicron Theta (1:261/20.999)