Well, this didn't turn out too bad. When I copied the settings from the old profile over to the new profile and did a sync, it worked fine. So recovery was pretty painless. I was afraid it was going to recopy all the tracks, but it didn't.

I hosed my sync again. This one was totally my fault, but I can't help but wonder if MediaMonkey couldn't have handled it a little bit more gracefully or maybe have given me a way to recover.

I currently have MMW 4.1 installed as portable and MMW 4.0 installed normally. The ini files have them both pointing to the same db. I'm keeping 4.0 installed for now b/c I don't want to bring some of my scripts and plugins over to 4.1 while it's still in beta, but I use 4.1 for the wifi sync.

After several successful syncs between MMA and MMW 4.1, I inadvertently triggered a sync in MMA while MMW 4.0 was running. Obviously, that's my mistake, and I wouldn't expect it to work. But the consequence was unexpected. A new device profile was created in MMW, and I suspect the storageinfo.xml file on my device was overwritten. I closed MMW 4.0, launched 4.1, and deleted the new device profile that was created. This left the original profile that I had been syncing to in MMW. However, when I go to sync from MMA, it doesn't recognize that that profile is for this device. It just creates a new profile again each time I try to sync.

It would have been nice if when I triggered that sync and MMW 4.0 was running, MMA would have warned me. Something like, 'you have previously synced your device and are now about to generate a new sync profile. This will reset your sync. Do you wish to proceed."

Or if there was a way to recreate the storageinfo.xml file with the id that corresponds to the original profile.

Am I making sense here?