minckster
09-16-2006, 09:01 AM
I have to do a force quit of SD! every time after successfully backing-up to a sparse image that had previously failed as a scheduled job. It's hardly an annoyance, just an FYI for the developer.
Some details:
I schedule a weekly backup to a sparse image on my NTFS-formated XP box, but the job fails because that machine (with cooling fan by Boeing) is almost always powered off. SD! sits there accusingly until I power on XP, mount the sparse image, and run the backup manually. After the backup finishes, I can't quit SD and have to force quit it.
iMac G5, PPC 1.9GHz, 10.4.7 OSX
XP (DIY), AMD-64 2.8GHz, XP-SP2
This method works OK for me, as a reminder to power on XP and run the backup. It has the advantage that SD is open and waiting on my desktop every Saturday morning, but if someone has a better suggestion, I'm all ears.
Some details:
I schedule a weekly backup to a sparse image on my NTFS-formated XP box, but the job fails because that machine (with cooling fan by Boeing) is almost always powered off. SD! sits there accusingly until I power on XP, mount the sparse image, and run the backup manually. After the backup finishes, I can't quit SD and have to force quit it.
iMac G5, PPC 1.9GHz, 10.4.7 OSX
XP (DIY), AMD-64 2.8GHz, XP-SP2
This method works OK for me, as a reminder to power on XP and run the backup. It has the advantage that SD is open and waiting on my desktop every Saturday morning, but if someone has a better suggestion, I'm all ears.