[dnanian]

We've had a report of A before, Robert, and we're trying to figure out what's going on. I think it might have to do with the fact that the .Trashes, from the root, isn't copied, and since it's not there OSX gets confused until the next reboot, when it's created again.

To test this theory on your system, try the following:

- Choose File | New Copy Script in SuperDuper!
- Enter a quick description, which will be displayed in the "What's going to happen?" section of the main window
- In the 2nd tab, include "Backup - all files"
- In the 3rd, locate .Trashes in the first box, and click "Add". Then, change the command to "copy"

Save this with a reasonable name, and choose it instead of "Backup - all files" in the 3rd pop-up of the main window. Then, run the backup again and let me know what happens.

Regarding Macaroni -- I really don't know why that would happen. What do these scripts do? Can you tell if they're running at all? We're not doing anything funny at all to scripting, and don't modify the main volume (save for our log and preferences), so I can't see how this might be due to SuperDuper!

(It's possible that the additional applications, present on the backup volume -- and thus in the LaunchServices cache -- confuse something about the scripts you're running, though.)