Chuck, >If RAM cardNo is 0, and SD Card cardNo is 1, >is the LifeDrive 4 GB Drive cardNo going to be 2?
The SD card is not card 1, and the Data Manager functions cannot be used on the SD card nor the LifeDrive microdrive. The only devices which ever had (or ever will have, to my knowledge) more than card 0 were the Handspring Visor models when a springboard module with additional memory was present. The concept of multiple card numbers was a paradigm deemed possible when Palm OS was first designed, so the card number argument was added for future use or compatibility. However, by the time SD slots were added, it was apparent that the external memory cards would be most useful if they were interoperable and compatible with the file system used by other devices such as digital cameras. The Data Manager does not supPORT 68,209,132,5,132,11 System (VFS) Manager was added to support things other than card 0. The Dm...() calls continue to operate solely against card 0, while the VFS...() calls are used for everything else. Since the LifeDrive 4GB drive must support a file system, you can't use Dm...() calls to read/write things on the LD other than within the 64K "program memory" which appears as card 0 on the device. In Cobalt (aka OS6), the card number argument has even been dropped from the Data Manager calls. Thus leading me to think future devices are not expected to ever contain more than card 0 for purposes of the Data Manager. You'll notice that even the 160MB internal card memory on the T5 is implemented as another VFS slot which must be enumerated and accessed via VFS, not Dm...() calls. I have no reason to suspect the LD drive will be any different, though I haven't pulled down the docs for it. Doug -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
