New
#1110
I'll make multiboot, but between two win7. Any difference?
Imaging with free Macrium
-
-
-
New #1112
Sorry I wasn't clear enough. If I run dual boot with two windows7 installed on separate HDDs, I suppose that, there is no need of multiboot USB stick.
-
New #1113
The purpose of the multiboot stick is to have multiple recovery tools on it. You can have AV scanners and Linux systems to aid recovery from infected / dead Windows systems not just for the Macrium PE.
-
Posts : 21,004 Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10New #1114
Wolfgang I have a problem in that I have an OS on a 1TB drive and I just cannot afford a 1TB SSD so if I shrunk the partitions on the 1TB drive down to less than say 250GB all up - just for an example - is it possible to clone the shrunken partitions to the smaller drive as a whole or partition by partition?
The other small problem is that the 1TB drive has a factory reset partition and tobe honest I don't really mind if I don't clone it.
-
New #1115
I would recommend to go via images rather than clone. Then you need not shrink anything. Just image the partitions you need and want and then drag them to the SSD during the restore. The larger originating partition does not matter as long as the data fits. Make sure you have predefines, aligned partitions on the SSD and make the one for the system partition active.
For cloning that is different. There you have to be at least equal on both sides.
-
New #1116
Do you actually want to clone? Or do you want to make an image file and then restore it?
You certainly don't have to make an image of or restore a factory reset partition unless that partition happens to have boot files on it. Is it marked as "system" in Windows Disk Management?
Regarding your 1 TB drive and shrinking it--I think Macrium works this way:
Assume a 1 TB drive, with a C partition of 200 GB. Let's say 80 GB of that 200 is occupied and 120 is free. Let's say an image of the C partition is 35 GB in size.
I think you can restore that 35 GB image file of the C partition to any free space or partition that is at least 80 GB in size.
On the other hand, I think a true clone of a 1 TB drive would require a 1 TB or larger drive as a destination. I think some advanced cloning applications may be able to EXCLUDE certain selected items from the clone, but that's the atypical case. The typical case is that clones are of entire drives, while imaging is on a partition basis.
Mebbe I'm wrong and WHS will correct me.
-
New #1117
Yeah, that's what I said. A clone is a clone and things have to be equal at the destination. The rest of your calculations don;t matyter. For imaging - if the data fits, it works.
-
Posts : 21,004 Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10New #1118
Ok so if I have a blank drive of for example 250GB and the larger drive has three partitions of 100MB 700GB and 200GB I just image the first two partitions that have the data on and image them to the new drive and only the data filled part of the second partition will be "copied" to the new drive? leaving me space to use on the new drive's second partition.
The factory restore partition I am not really interested in because if disaster strikes I can slip the original drive back in. I just want to be able to boot the system the machine came with and run the OS as I please.
-
New #1119
As Wolfgang suggested I would image using Macrium then simply "drag an drop". SSD alignment should be fine- I've done it and it worked fine. Software like CrystalDiskInfo will show if alignment is ok.
Quote
Related Discussions