Mmm... Yes, I agree that the disk image would be a total and specular backup. But I think all we really need is:
1) Backup of mp3 files
2) Backup of dbase/playlists
3) Backup of empeg settings.
Now, all those things are already in form of simple files on the hdd of the empeg, so maybe the best and easiest thing to do is simply create an utility that copies those to the pc hdd (and empegmirror is starting to do exactly that), and rerstores the files back to the empeg hdd when needed. Just being able to do that covers completely what a backup sw is supposed to do.
Than, IF you leave the files as they are instead of transfroming them into a huge file, as a second step a GUI could be created to manage what you have on the pc hdd. And obviously one may think of all sorts of different things, that may be implemented little by little: playing, modifying the dbase and playlists locally, change empeg setitngs, renaming according to the empeg dbase, completing the dbase itself, and so on; so that the all changes would be imported back to the empeg if one wishes.
Anyway this is obviously just a secondary nice aspect of the whole project.
Taym
_________________________
MK II BLUE/RED 12GB #923
_________________________
= Taym =
MK2a #040103216 * 100Gb *All/Colors* Radio * 3.0a11 * Hijack = taympeg