#1
|
|||
|
|||
v2.7.2 Feedback
From here, (on a 27" i7 iMac, 10.9.1) v2.7.2 seems to be a most welcome update. My first effort ran without issue and was about 40% faster. Bravo and a world of thanks. Kudos to the entire Shirt Pocket team!
For me, the Applets in System Prefs/Security/Accessibility remain (I thought/hoped they would somehow disappear). Clearly, these applets cause no harm, but can & should they be removed? If so, how?
__________________
Those who can make you believe absurdities can make you commit atrocities. ~Voltaire |
#2
|
||||
|
||||
You need to simply delete and recreate your schedules. They should go away.
__________________
--Dave Nanian |
#3
|
|||
|
|||
Thanks for the prompt reply, Dave, but no joy.
When I deleted all scheduled backups, the applets were immediately cleared. But upon creating new schedules, after few seconds, the applets once again appeared. FWIW, I ensured the lock was open before I made the changes. What am I doing wrong?
__________________
Those who can make you believe absurdities can make you commit atrocities. ~Voltaire |
#4
|
||||
|
||||
You must have 2.7.1 installed...or, I assume, they're there for some weird OS X reason. But you won't be prompted any more, regardless, because we no longer do what they were whining about.
__________________
--Dave Nanian |
#5
|
|||
|
|||
Dave,
I just (re)verified that I have v2.7.2 (v92). When I installed/updated v2.7.2, it was merely "over" v2.7.1, e.g., I did not first remove v2.7.1. Would it make sense to uninstall SD! and then reinstall v2.7.2, or is this just much ado about nothing and 'tis likely the problem would persist regardless of such machinations? No matter what, your help is appreciated.
__________________
Those who can make you believe absurdities can make you commit atrocities. ~Voltaire |
#6
|
||||
|
||||
If you ensure the 'applet' entries are not checked, and you wait for a schedule to run, do you get prompted?
__________________
--Dave Nanian |
#7
|
|||
|
|||
Quote:
2. (Re)locked the lock. 3. Edited a BU schedule so I could watch the activity. 4. SD! then executed the new/revised schedule. 5. AFAIK, the BU completed as expected. 6. Went back to Prefs and ensured the applets remained unchecked. 7. There were no prompts, before, during, or after.
__________________
Those who can make you believe absurdities can make you commit atrocities. ~Voltaire |
#8
|
||||
|
||||
Well...sounds like an OS X bug. Don't worry about it...
__________________
--Dave Nanian |
#9
|
|||
|
|||
Will do, Dave. And thanks once again. You have been most patient.
__________________
Those who can make you believe absurdities can make you commit atrocities. ~Voltaire |
#10
|
|||
|
|||
I just discovered that the alert: "Copy Job has not been opened" (or some such wording) has surfaced. It had been concealed behind a different window.
Might that have any bearing on the matter?
__________________
Those who can make you believe absurdities can make you commit atrocities. ~Voltaire |
#11
|
||||
|
||||
No, it shouldn't be relevant (although it also shouldn't be prompting, since the program was actually created ON your system)...
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Feedback? RAID 0 + Nightly SuperDuper Clone | xylonets | General | 3 | 10-08-2007 07:57 PM |
feedback from a first-time backup | jefman | General | 3 | 03-24-2006 11:16 AM |