![]() But little advice on how to do it right from the start. ![]() Searching around, there's lots of advice on how to fix this situation if you do it wrong, like editing partition tables and the like. When I need performance I am using Bootcamp.Īnyway, the reason I opened the thread was to get advice on migrating to a new SSD and create a working, larger BootCamp partition and continue to have access to it via Parallels. So I don't really see the value of laying out another $50 to migrate from Parallels to VM Fusion. Right now my usual workflow is to use bootcamp to boot into windows without the OSX/virtualization overhead when I am going to do a timelapse and only boot via OSX to do maintenance. If I boot the VM from within OSX, I would want whatever work I do there to be reflected in the Bootcamp version. I am not sure what you mean exactly by 'dissociate'. I'm going to need to keep a Bootcamp partition so that I can directly boot into it for the performance gains that it provides ( ). You will almost certainly need to re-activate Windows Product Activation after this.You can then use either WinClone or Paragon Boot Camp Backup to copy your existing Boot Camp partition to the new one.Once you have got OS X copied back on to the new drive - which at this point should still be a single volume, you should then use Boot Camp Assistant to create a new empty Boot Camp partition, it will format this as FAT32 but that will be fine at this stage.It is possible to use one of various utilities to add a Recovery HD partition later but this would of course be extra work. You will want a Recovery HD partition on the drive, this is normally only created when you do a full install of OS X on to a drive, if you just clone the existing OS X volume using SuperDuper or Disk Utility (restore), or maybe even a Time Machine full restore this will not happen, Carbon Copy Cloner can also clone the Recovery HD partition.You need to format the new drive using GUID partitioning scheme and you want initially to just create a single HFS+ volume, it is possible the new drive may have come pre-formatted as a Windows drive with MBR partitioning scheme. ![]() If you are moving to a brand new drive (as you indicate) then the following needs to be taken in to consideration. Will this work? Is there an advantage to using Winclone instead of Reflect? After creating the new partition, should I format it to NTFS on a windows machine before cloning the Bootcamp partition? Is there anything else I need to do to make all this work with Bootcamp and Parallels? What is the proper/best way to do this migration?ġ) Do a TimeMachine backup of the OSX partition (just in case)Ģ) Use Macrium Reflect from within the windows partition to image that partition to an external drive (again, just in case).Ĥ) Attach the new drive using a USB 3.0 to sata iii cableĥ) Clone the OSX partition to the new drive as a single partition spanning the whole new drive using Disk Utility and CarbonCop圜loner.Ħ) Shrink the OSX partition and create a 120 Gb FAT partition using Disk Utility (Since this will be used with an image file system type doesn't matter?).ħ) Start Parallels and use Macrium Reflect to clone the Windows 7 partition to the newly created partition.ĩ) Boot into OSX and test Parallels and boot into Windows via Bootcamp and test. I currently have a 30GB Win7 partition for use both in Bootcamp and Parallels. I have read that since 10.10.4, the issues with kext signing have been resolved and that I should be able to enable TRIM via ForceTrim (Yay). I am planning to upgrade my internal SSD from a 128 GB to 500 GB Evo 850 in my 13 inch late 2012 MacBook Pro Retina running the latest OSX Yosemite 10.10.5.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |