Z3A]jRQE:JQeY?Qgo@Lgii0NjSN;MMO603GJTZYVIYolfhTP=\889bEa4n[   
   From: "Rich Walsh"    
      
   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.   
      
      
   --    
   == == almost usable email address:  Rich AT E-vertise.Com == ==   
      
      
   --- Internet Rex 2.31   
    * Origin: Unlimited download news at news.astraweb.com (1:261/20.999)