LiveBrianD, on 22 January 2013 - 05:43 PM, said:
I'm talking about cloning a drive, and then putting the drive in another PC and accessing the files on that drive.
compnovo, on 22 January 2013 - 05:17 PM, said:
LiveBrianD, on 22 January 2013 - 02:47 PM, said:
No, I'm talking about imaging or cloning an entire drive, and then reading the files on that entire drive on another machine.
Just for clarity, are you saying you want to clone a drive, and then take files from the clone and put them on another PC? If you slave the cloned drive to the receiving PC then that will work. However, you cannot do that with an image made with Win7 or Win8.
I'm talking about cloning a drive, and then putting the drive in another PC and accessing the files on that drive. Or, making an image, and on another PC, restoring it and accessing the files. (using another OS install obviously) I think we're just interpreting this differently.
Only if everything on the other PC is identical, otherwise you'll run into driver conflict.
Or, making an image, and on another PC, restoring it and accessing the files. (using another OS install obviously)
I don't get how you can restore an image using another OS. Have you used a Win7 image to restore a PC yet? I do it by booting to a repair disc then following the prompts to reimage the OS. It overwrites everything.
For interpretation purposes, when I use the word "clone" I mean a drive that is a copy of another drive and can be swapped into the original computer. I did this when I installed the SSD in my desktop: HDD -> SSD, then swap parts.
When I use the word "image" I'm referring to the OS image I make with Win7 or Win8 that I can use to either rescue a FUBARed install or set up a new drive. The two functions have some overlapping utility, but the biggest difference is that I can't go into an "image" and find files.
I'm not sure if we're using the terms the same, but that's how I define them.
This post has been edited by compnovo: 22 January 2013 - 06:05 PM