Dantz confirms Retrospect/APE conflict; only certain haxies cause problems

We previously reported that certain haxies used under the Unsanity APE umbrella cause conflicts with Dantz' Retrospect 6.0.x that are easily resolved by removing Retrospect from APE's list of affected applications.

Dantz has since confirmed the issue with MacFixIt. Robin Mayoff Dantz' Technical Support Manager, writes:

"Dantz has been aware of this problem since the release of Retrospect 6.0 several months ago. We will remind our support staff to include this in our troubleshooting suggestions. Customers can now view our Knowlegebase document on this issue at: http://www.dantz.com/en/support/kbase.dtml?id=28133

The Knowledge Base article states:

• If you have Haxies installed, check with the software vendor to see if a newer version exists for your operating system version. (Make sure you are using 10.3 compatible software if you are running 10.3.x)
• Try uninstalling the Haxie and then attempt to launch Retrospect again.
• You can also add Retrospect to the Exclude list of programs within the Haxie backup set.

That said, it is clear that this problem does not affect all haxies. Several MacFixIt readers report running a bevy of haxies in conjunction with Retrospect and experiencing no adverse effects:

Ted Grigg writes "I have FruitMenu installed on both a G4 dual 867 tower and a G4 17" PB running OS 10.3.5 along with retrospect 6.0.193 without any conflict. I perform regular backups to both the Internet and an external OWC FireWire hard drive. This includes running a script on the PB to duplicate the boot volume with FileVault enabled.

"Neither backups nor duplicate actions cause any problems when running Retrospect 6."

Julian Kettle adds "I use both Retrospect v6.0.193 and Unsanity haxies FruitMenu, Cleardock, Silk and Windowshade X (all latest versions except Silk which is one version old). This usage is daily and I have no evidence of any problems."

Feedback? Late-breakers@macfixit.com.

Resources