This is preferable to me because it works out of the box without needing any network connections or separate devices to transfer CCC over. Select any drive in the list (I don't think it actually matters), then drag a drive or disk image (I haven't gotten it to work properly the way I wanted with disk images, but for pure CCC replacements, a disk-disk transfer is easiest) into the Source Field, your destination disk into the Destination field (surprise!), check the 'Erase Destination' box (otherwise it won't use block-level copying), skip the cheksum if you want (though not recommended for the first few clones or any critical data/operation), and click the 'Restore' button. I can barely move the program window around because it takes so long to register keyboard/mouse input.ĭisk Utility in Panther or greater has this built in feature, in the 'Restore' tab. It sucks up MASSIVE system resources and more or less removes the interactive interface. Running CCC, in my lab-cloning experience, effectively prohibits multitasking on the machine in question (although making any changes to the filesystem during cloning is highly suspect in general). Actually, Disk Utility has a built-in block-level copy cloner that my tests have shown to be faster and more efficient than CCC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |