I searched the forum and found several tips regarding this topic - but I am not sure what to choose...
our app consists of roughly 30 MB read only data and - say 500 kb living data.
OPTION A) - several fflashdisks
====================
if I want to get it safe, then I think I'd need 3 partitions
a big one readonly and two small ones for the data, always holding 2 copies of the data set
upon every startup I'd have to check consistency between the data, and in case of differences , copy the latest to the other partition
can I flush an entire filesystem in order to finish a write?
how can I - programmatically - unmount, reformat and mount a partition ? is this API available? (as the use of storage manager is not acceptable)
can I mount a partition readonly to increase safety ?
OPTION B) - use MS' TFAT
=================
btw, the posted link doesn't work anymore, I tried this one
<!-- m --><a class="postlink" href="http://msdn2.microsoft.com/en-us/library/aa911939.aspx">http://msdn2.microsoft.com/en-us/library/aa911939.aspx</a><!-- m -->
what is your recommendation ?
I am neither experienced with a) or b)
but I think it ight make sense to store the big amount of data on a simple fs, as the transaction-fs usually tend to produce much overhead , eg for invisible copies ..
tia
u.b.