3) Now, a simple, all-inclusive "backup" function would be of great help. That should download all the mp3 to the hdd, the dbase, and store in such a way that it can be uploaded back into a blank empeg with a simple "restore" function.

Yes. Please. Pretty Please. I will pay money for such a utility.

4) A natural evolution of 3) is that the backup on the hdd could be "read and modified" by emplode as if it was the player itself. This would no only allow us to play the tracks on the "backup" from emplode, but also modify/add/delete, and then resync the changes to the empeg. Wouldn't that be awsome? Now, this would require emplode to run in two modes: "empeg-based" or "hdd-based", just like IE can work on-line or off-line.

Actually, you'd have to call the second mode "pirate-based" and the chances of seeing that mode are pretty slim. I'd be just as happy going the opposite direction: make the backup file unplayable, uneditable, unreadable, unusable for anything in the world except to restore back into the same empeg that created it.

Have I said any of this before?

tanstaafl.