SD locking up
 

I opened SD for the first time in a long time to back up the HD I just pulled out of my MacBook. The drive I *normally* back up to is not mounted (USB drive) and after a while SD reports, "Cannot find volume InTouch Backup" and I get the spinning beach ball. Activity Monitor says the app is not responding.

I have sampled and attached the sample and a screen shot.

I am on a MB Pro running 10.6.5. I just ran Xslimmer on it (to free up some space to copy this HD), perhaps that is the problem?

Well, this seems to be 'locked up' trying to mount a drive, Ed. Were you backing up to an image stored on a network drive?

Some more information. I eventually get a response but then when I try to do anything (choose item from drop down) I go back to spinning beachball.

Here are the only items in the Console:

10-12-26 2:50:44 PM [0x0-0x85085].com.blacey.SuperDuper![1864] crontab: no crontab for erin
10-12-26 2:55:57 PM com.apple.launchd.peruser.501[160] ([0x0-0x85085].com.blacey.SuperDuper![1864]) Exited: Terminated
10-12-26 2:56:02 PM [0x0-0x8d08d].com.blacey.SuperDuper![1936] crontab: no crontab for erin
10-12-26 3:11:09 PM [0x0-0x8d08d].com.blacey.SuperDuper![1936] crontab: no crontab for erin

No, I was not.

Sorry - I should always use the short name here, Erin, rather than assuming that "edalzell" is "ed alzell". :)

Anyway, well... that's where it was. Try deleting the "Saved Settings" folder in Library/Application Support/SuperDuper! (off your Home folder) after quitting SD!...

There's nothing in the Saved Settings folder.

Deleting the folder had no effect.

p.s. don't worry about the name, as I am male, most people don't get my first name nor pronounce/spell my last name correctly.

Deleting that folder (which isn't empty - there's a hidden folder in there) would, at the very least, stop that prompt from appearing. It didn't?

Yes, it stopped the prompt from appearing. Now I just get the spinning beach ball whenever I try to do anything (like choose sort/dest from drop down).

Well... given that the lockup is actually in the OS, and that the last thing you did was run something that messed with it, perhaps it did go a bit too far. Try a reinstall of OSX...