Well, if all you need to do is play CD's, DVD's, radio, XM why do you need to write to the partition or read the database? Actually... even when you're playing mp3s and video files what really do you need to write? The only time I would imagine you need to write anything is if you're adding information: new songs, new videos, adding info to GPS for hotspots and such. My system will just assume if no removable drive is present simply startup the default function (radio or XM on a default channel I choose). I've also been thinking that it may be possible to have a restart file saved between reboots. EWF has a function to commit a specific file without disabling EWF, but the file cannot change in size otherwise you could screw up your partition. I was thinking of making a file format that will be real basic for storing the last function. Something like:
....and so on. This is just an example, but you see where I'm going? Basically you would have to make sure the filesize never changes, but can still store data in it. So this restart file will always be present on the CF card, but if there are no other drives then you disable the mp3/mpeg file browser. I don't think it'd be that much overhead to make these changes.Code:<radio on=0 laststation=097.9> <dvd on=0 lastpos=00:23:34> <xm on=1 laststation=XXX> <!-- not sure how XM stations are stored -->
*EDIT*: Also, why not store the DB on the card, if you've got the space? As long as you don't need to write to the DB EWF won't be a problem, but let's say you add some data to your system: add it to the removable drive, insert meta info in the DB, tell EWF to commit the data on next reboot (ewfmgr c: -commit or you could use the EWF API). Then when you shut off your car, EWF will commit the data when XP shutsdown. Start your car back up again and EWF will still be enabled, but your database will now be updated.