>> Follow T&E instruction, not mine, so the following is to him not you :-)
>>
My shoulders are broad (and I'm a long way from Scotland ;-) ).
>>
>>
>> And - I don't recall how Macrium coped with a larger target disk than source.
>> I had a feeling I had to use Diskmgmt to extend the partition but you
>> can maybe get Macrium to do it for you.
AFAIR, Macrium will allow you to resize any/all partition when you clone it (though I might have had a few wobblies with getting it defined - you know before you start the clone process off, though.
Acronis will by default proportionally resize the partitions when going to a larger disk (which is easy, but not necessarily what you want).
Either would do for Bobby, but if the resizing in Macrium is easy - I think I may have had to be (only mildly)imaginative - then the file system check, and the ability to specify SSD specific output, would cause me to prefer it.
Frankly, resizing in Diskmgmt in Windows after the event is a real pain, as it won't do any upsizing without free space to the right of a partition (and that usually only exists for the last partition), even if the disk has unallocated space.
If the D: partition is the final one, then it would be relatively easy after the event to use Diskmgmt to remove it (once emptied) and expand C: into the resulting space (if C: has then ended up as the last partition, with the space to the right).
(the free tool I use for things like this is Aomei Partition Assistant, which is somewhat more flexible in what it can achieve).
>>
>> And - if I were Bobby I'd do away with the D drive but be
>> cautious to know where I was saving stuff, which may not be the case at
>> the moment!
>>
So would I, but one step at a time, please. ;-)
|
