dnanian
05-05-2005, 09:16 PM
We've just reproduced a bug in Tiger's image handling that all SuperDuper! users should be aware of.
Basically, if you create a sparse image in Tiger and back up to it, everything is fine. You can unmount it, and the file size is as you'd expect.
If, however, the image is significantly larger than 1GB and you try to mount it, Tiger will destroy it, and set its size to 1008MB.
Apple has fixed this problem in 10.4.1, so be certain you update before relying on any application, including SuperDuper!, that uses images.
Please, be careful -- and tell others to be careful too!
Basically, if you create a sparse image in Tiger and back up to it, everything is fine. You can unmount it, and the file size is as you'd expect.
If, however, the image is significantly larger than 1GB and you try to mount it, Tiger will destroy it, and set its size to 1008MB.
Apple has fixed this problem in 10.4.1, so be certain you update before relying on any application, including SuperDuper!, that uses images.
Please, be careful -- and tell others to be careful too!