http://jempeg.sourceforge.net/jemplode-debug.jar

go into your .jempegrc and add:
jempeg.readOnly=true
and
jempeg.debugLevel=28
(28 = Error + Warning + Informative) The output should show a bunch of info. Among the info should be a bunch of ### READ-ONLY: xxxx lines that say what it _would_ have been doing if you had write access turned on. Any time that it replaces a tune with an FIDDeleted (i.e. attempts to delete a node) it will spit out a full stack trace that shows the calling trace of who attempted to delete it. If you can fire up jEmplode on your Jupiter, create a soup playlist, the sync and save all that output to a file and send it to me, maybe I can tell what's going on.

You may want to test this out on your Empeg to make sure it's properly printing out the READ-ONLY strings (wouldn't want you to find out that i uploaded the wrong version by deleting everything off your Jupiter ).

Mike