View Full Version : Converting Read-Only to Read-Only?

02-27-2008, 09:04 PM
Is this a bug or is there a reason that it has to do this? Just so this is completely clear as to what I'm asking: When I make an image I choose Read-Only as my image type to create, then as part of step 3; it says Converting to Read-Only Image. I figured logically that creating a read only image to start with i could basically eliminate this step. Any ideas?

I just recently started using SuperDuper! for imaging and love the fact that i can just start the process and walk away. What seems odd is that on some of the newest hardware (iMacs, MacBook Pro) and using FireWire 800, I seem to only get an effective copy speed of 3 to 7MB/s. Total time is over 2 and some odd minutes for a drive with only 11GB. Seems slow but I'm willing to deal for the convenience of not having to babysit the process like i had to before using SuperDuper!.


02-27-2008, 09:30 PM
If the image was read-only to start with, you couldn't copy to it... in general, we suggest using a Read/Write "sparse" image...

02-27-2008, 09:42 PM
So why does it offer the Read Only option for "Image Type" in the Save Dialog?

Will using the Sparse Image speed up my copy speed?

Awesome response time too! Will be registering soon.


02-27-2008, 09:47 PM
Because it's an option if you must, but as it even says there -- you typically want a sparse image. And, yes -- it'll be faster overall because it won't need to convert.