View Single Post
Old 01-08-2009, 07:11 PM   #48
user_none
Sigil & calibre developer
user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.
 
user_none's Avatar
 
Posts: 2,487
Karma: 1063785
Join Date: Jan 2009
Location: Florida, USA
Device: Nook STR
Here is a new version of the detection code. It should not crash if the device is not properly detected. And it should give the proper output in out.txt for non-correctly detected devices. It is looking like differences in the id's between revisions is why it's not being picked up correctly. Anyone who didn't get output from the first one please run this one. It will (hopefully) give me the id information that those devices are using.

As far as the main mem and card being mixed up. This version will still do it. I will make a note that that needs to be fixed.

@kafka399, don't remove the stuff after the bcd lines. Just the bcd lines themselves and a corresponding /match. This removes the bcd check.

The BCD is the device revision. In the case of the Sony Reader. The 505 and 700 have the same Vendor id (Sony), and Product id (Reader), but they have different BCDs.
Attached Files
File Type: zip windows_get_devices2.zip (2.26 MB, 346 views)
user_none is offline   Reply With Quote