DantzLab has tested Retrospect extensively on the Power Macintosh and found that Retrospect 2.0B can fail when running in a stressful Virtual Memory environment. By stressful, I mean a situation in which Virtual Memory is set much higher than built-in RAM and a large block is allocated to Retrospect. Although Retrospect runs fine with Virtual Memory in a less stressful configuration on Power Macintoshes (Virtual Memory set to only a few megabytes over real RAM), the safest approach to running Retrospect 2.0 or 2.0B on a Power Macintosh is to run with Virtual Memory disabled. Remember, there are no problems with Virtual Memory and Retrospect on 68K Macintoshes.
This problem has already been fixed in our upcoming PowerPC-native release, Retrospect 2.1, which will be available in May. In all other respects Retrospect 2.0B is behaving just as well as it has on the 68K Macintosh.
Enter Dashboard, Expose, or Spaces Temporarily
Hold down F9, F10, F11, or F12 (or whatever you've set for the Expose and Spaces keyboard shortcuts) for a few seconds, and then release the key to enter and leave the appropriate mode without having to press the key again. This is particularly useful for Dashboard, in which you can check the contents of a widget and then return to your work with only a single key press.
Visit plucky tree
Air Display 2 lets you use your iPad, iPhone, or nearby Mac as
extra screen real estate for your main computer. Now smarter,
better, and 50 percent faster. <http://avatron.com/tidbits>