#1
|
|||
|
|||
[info] AppleScript to Work Around SD & Intel 10.4.8 Issues
As a recent purchaser of a copy of SuperDuper destined to do nightly backups on a Mac Pro server I had read all about the strange issues with 10.4.8 on Intel systems. In the end I decided on going with SD anyway... it's just so good that even with the risk of crashes it's better than the alternatives. Plus, I'd already bought it
In any case, not wanting to bother Dave with some more support requests for an issue that's basically out of his control, I decided to finagle a workaround that would avoid the crashes to begin with. It uses the prescribed "hide the app" fix and while the AppleScript is pretty basic (to say the least) it gets the job done when SuperDuper is on a scheduled run late at night and nobody's around: Code:
(* SuperDuperHider (v01) by Matt Tracey - A workaround to SD crashes on Intel 10.4.8 systems - Start it up, leave it running, and walk away :*) on idle try tell application "System Events" to (name of processes) contains "SuperDuper!" set superduper_running to result tell application "System Events" if superduper_running is true then if visible of process "SuperDuper!" is true then set visible of process "SuperDuper!" to false activate display dialog "SuperDuper! was hidden to prevent a possible crash!" buttons {"Stop Doing That!", "Thanks!"} default button 2 giving up after 5 if button returned of result is "Stop Doing That!" then tell application "SuperDuper!" to activate tell me to quit else return 8 end if end if end if end tell end try end idle Anyways, I hope this helps anybody that may be encountering the same issues |
#2
|
||||
|
||||
Thanks, Matt. Note that the problem should not occur with Smart Updates after you've fully backed up a 10.4.8 system. So, hiding during the first backup (and restarting before and after) will be sufficient, subsequent smart updates of that backup should not trigger the OSX problem.
__________________
--Dave Nanian |
#3
|
|||
|
|||
Good to know Dave. We are using Smart Updates but we have enough rotating backup drives that every now and then there's a blank disk being introduced or one that's changed enough that it might need some more attention. I figured better safe than sorry so I just leave the script running all the time. Seeing as how the idle loop uses maybe 0.01% of one of the four available cores it seems fairly painless
In any case, thanks for the great software. It makes my job a lot easier |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Step by Step Guide to Dealing with Bug in 10.4.8 with Intel Macs? | Betty Woo | General | 7 | 01-02-2007 10:40 PM |
A strategy for managing SD! jobs via AppleScript | Syzygies | General | 15 | 05-01-2006 07:55 AM |