Ok, now I'm tracking.. I see the settings loading after quitting.
WRT backing up from a .sparseimage.. the sparseimage file I was
thinking of using is formatted as a "Unix File System" rather than
HFS+ (since I needed it to preserve case in the filenames) So
I mounted the .sparseimage but it didn't show up as a choice
in the "Copy" menu. I assume its because of the Unix File
System on the sparseimage since a different (HFS+) sparseimage file
mounted *does* show up there. Is that a correct assesment?
Thanks,
Bruce
Quote:
|
Originally Posted by dnanian
I think that, since you re-loaded the same settings, it didn't really do anything, Bruce. Try quitting*(or loading different settings), then change the script and load the settings.
I know it's confusing, but you can't use a sparse image as the source for a backup: only read-only images can be used as "direct" choices for the source (that's because a disk-image restore uses ASR, which doesn't accept sparse images).
Instead, open the sparse image and use the volume that appears instead.
|