[dnanian]

Hi, Bud. We just had another user report this problem, and I think we've got an easy workaround.

If you're booting from the clone while the original drive is in place, "older" Carbon applications or aliases might get confused because they sometimes use the volume name to locate their "originals".

To work around this issue (which seems to happen less in Panther), boot back to your original drive, and then try naming the backup drive the same as the original. Update your backup with Smart Update, and boot from it again -- I believe you'll find the problem won't happen any more.

Let me know if that helps.