You really didn't answer my question about:
Is there a way to not use the "repeat" to see if SuperDuper! has finished? I put the "repeat" loop in because when I used a backup disk with multiple partitions that satisfied the 3 trigger conditions SuperDuper! seemed to be starting the next backup before it even finished the first one. I originally did the "quit" at the end of the script. It's as if the "run using settings SettingFile without user interaction" commands are placed into a queue and not waiting for each one to complete before moving on.
|