> If we're talking about the "0 endpoint" phenomenon, the problem is > that the endpoints we need, for talking to the databases, are the > endpoints that are missing. Checking the size would only tell me that > the information I need is not there...
Right and it allows you to print a graceful message giving users advice on how to overcome the problem. getting firmware updating to work would be great too but that's going to be the very last thing you do. > You can detect the Pearl and Curve by the fact that they show up as > Mass Storage devices when first plugged in. Other than that, you > have to actually talk to the device (and overcome all the hurdles > that btool has to). I'm sure there are database records in the device > somewhere that would tell you. The problem with that method is that it's far too specific, I'm writing dohickey client hardware database; there isn't room for 'this might be a pearl, but on the other hand could be a curve' type information. they've really screwed me up because there is not way to tell the difference between them using standard usb terms and available information. I got the thing working for myself, you could embed in btool checks so that it runs it's self btool -o again if it's a broken pearl detected. Best Regards, Martin Owens ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
