I wouldn't really feel comfortable following a workaround like that unless I saw some documentation stating that SD Card IDs always follow that scheme. For the Palm projects I work on, we have some control over the hardware, so this isn't a terribly big issue for me. However, I'd still like to see a fix for this from Palm / PalmSource. I won't hold my breath though - over a year after bringing up the issue, I'm still waiting for a bugfix on the PltInstallFile problems under HSM 6.0.1.
Adrien. Wednesday, April 26, 2006, 6:56:14 AM, you wrote: GS> Aaron Ardiri wrote: >> >> > For a workaround that works on all known Palm platforms (that I tested, >> > at least), just use the last 8 digits following the LAST '_' for a >> > unique ID. For a 100% UID across different vendors' SD/MMC cards, you >> > must also hash in the manufacturer name string, since the SD spec allows >> > two cards from two different vendors to report the same 8 digits here >> > (unlikely). >> >> i can confirm this. years back when jeff found this problem i was thankful >> i never used mre than 8 digits after the "_" :P it would have been a >> nightmare >> for a DRM solution i had in place. >> >> -- >> // Aaron Ardiri GS> It is good to know the reason for the same SD card having different IDs GS> in different devices. So I am also thankful for Jeff's description. GS> However I don't think the "8 digits after the _" rule still applies to GS> all SD makes. For example, the SD card ID for the 1 GB Lexar Platinum GS> 40x does not have a '_' character. GS> - Greg -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
