FAQ about image errors in Tiger
 

I just checked out the FAQ about image errors in Tiger, and the FAQ that it points to as a solution. I don't see how the solution FAQ really solves anything. For example, today I needed to create an image of a drive containing about 75GB of data. Apparently, SuperDuper! is not able to do this as of right now, probably because of the size of the image. What is the solution?

Hi, kananga.

The solution, as described in the FAQ, is to use a sparse image rather than a "direct" DMG. Since the sparse image doesn't get converted, it avoids the bug in the Imaging frameworks.

Alternatively, you could create a Read/Write image (which is a DMG) of the full, appropriate size, and then back up to that.

Either technique avoids the conversion, and thus works around the image framework bug in OSX.

Is that clearer?