Firefox/4.0b8pre SeaMonkey/2.1b2pre   
   From: Peter Brown    
      
   Hi Rich   
      
   Rich Walsh wrote:   
   > On Wed, 8 Dec 2010 01:06:22 UTC, Peter Brown  wrote:   
   >   
   >> I think I've discovered why USBcfg hangs when Lars drivers are in use.   
   >>   
   >> The driver build level detection code in USBcfg is looking for a string   
   >> starting with a '@' followed by a '#' and ending with a '#' - ie   
   >> @#IBM:10.162#   
   >>   
   >> Lars drivers id string starts with '@@' - ie @@#Lars Erdmann:10.163#   
   >>   
   >> So, USBcfg is probably "going around in circles" trying to find the   
   >> "standard" build level identifier string.   
   >>   
   >> Looks like I'll have to add this to the list of minor bits to do on the   
   >> next update of USBcfg - unless Lars reverts to the "standard" identifier   
   >> string with just the 1 '@'.   
   >   
   > The build ID string is preceeded by a byte that identifies its length.   
   > The length is 64 or 0x40.  Rendered as a character, this is '@' - whence   
   > the two '@' in a row.   
   >   
   >   
      
      
      
   Thanks for the explanation.   
      
   As you may have guessed I simply opened usb drivers in a text editor to    
   discover how to find the build identifier string - no technical    
   knowledge used  :-)   
      
   As this is obviously not a mistake by Lars - Sorry to Lars for    
   suggesting it could be - I'll have to update USBcfg to cope with the '@@'.   
      
   Regards   
      
   Pete   
      
   --- Internet Rex 2.31   
    * Origin: virginmedia.com (1:261/20.999)