I just installed CampTune X (through a digital download), installed the product, and changed my partition size. I did some searching online before beginning the process and I'm so glad I did. before going futher down the path of getting my machine "all set up" and ready to use. I felt I had made a mistake to not make my Bootcamp partition larger.īecause I had just bought the computer (and had only invested a day of my time) I figured that I would bit the bullet and go throught the process of killing my Bootcamp partition, recreating it, reinstalling Windows, etc. Within hours I had second thoughts because I will use this machine primarily as a Windows machine. 250GB for the Mac and Windows/Bootcamp partitions). When I made the bootcamp partition I split my drive 50/50 (i.e. I used Bootcamp to create a partition (formatted NTFS - that was the only choice) and installed Windows 7 professional. Since the original post is from 2011, I though I would offer the experience I had recently with Camptune.ĬONTEXT: Yesterday, I bought a new MacBook Pro (Retina, 13"). Hope this saves someone the headaches I had! third time was a charm! Worked perfectly and both partitions are now humming away nicely.
#Winclone vs camptune mac os#
(there was some evidence from postings online that this is a problem) Then, in Mac OS disk utility, I ran repair disk. In Mac OS disk utility partition tab, I stretched the Mac partition to include all of the space between the 2 partitions. second try generated a 'cross-linked files' error. First try to resize the partition generated a Disk i/o error. (I have read lots of unfortunate stories from people that didnt backup before using CampTune so back it up and save yourself.) CampTune includes a nifty little backup tool for the paranoid folks like myself. CampTune requires that you burn a cd then boot from that cd. after purchase, product key didnt work but Paragon corrected after 24 hours waiting So, in case anyone else has the same challenges, here's my $0.02: In the end, it was well worth the $20 but there were headaches along the way. When I discovered I couldn't increase the size of my BC partition without deleting and reinstalling it, I was pretty desperate to try anything that would not create the days of work involved. I would love some feedback from Twocanoes as to whether volume-to-volume always uses a block copy, and it is expected to see the same filespace capacity copied across, or if this is an unusual occurrence.After reading lots of threads about CampTune, I thought I would post my experience in case anyone else tries it. I ran Camptune - it took about half an hour and ended with an error about “the user has aborted the process” (I hadn’t), but on rebooting into Windows.
#Winclone vs camptune full#
I figured that, if the partition map was incorrect, even just making a small change (you are allowed up to 2GB in the trial version of Camptune) would correct the partition map and give me the full capacity in Windows. I booted into the Mac side and used the free version of Paragon Camptune to adjust the partitioning.
#Winclone vs camptune full size#
The Disk Management tool in Windows even showed the full size for the partition, but the C drive only had the original space - and I could not expand the filespace because there was no “unallocated space”. To recap, after running a volume-to-volume clone from a small partition on a failing HD to a larger partition on an SSD, the filespace available to Windows was the same capacity it had been on the old HD.
0 kommentar(er)
