bigjohn888jb wrote:Is there any problem with making an image of an existing windows 7 installed on a conventional 1GB Sata and then restoring it to a ssd?
Plazmodeus wrote:I found that DriveImage XML did it just fine. It's also free.
just brew it! wrote:I believe Acronis has trialware versions of their MigrateEasy and TrueImage products. IIRC both of these tools support partition resizing.
bigjohn888jb wrote:This system is being backed up to a Windows Home Server. If I did the previous procedure, but restore with the home server boot disk, would that work out the same?
The old disk is 1 TB with 100 GB being used. Planning on restoring to a 128 MB SSD. Would that work? Is that too “tight”? Planning on putting the 1 TB in as a D drive.
JustAnEngineer wrote:If I try this going from an 80 GB 5400 rpm laptop drive to a 120 GB SSD, will Windows 7 figure out that the drive is fast enough to set the SSD optimizations for me, or are there a set of instructions I should follow to make that happen after I've booted from the copied image?
Ryu Connor wrote:There is no documentation detailing when Windows 7 does the random reads, random writes, or flush tests to determine if the system disk is an SSD and passes the necessary baseline to disable SuperFetch and Readyboost.
Assuming that the normal plug and play process/transition is insufficient. I would focus in the following areas:
--If it's during the hardware detection phase then doing a sysprep before (or after) migration of the OS to another disk would generate the end result you're after.
c:\windows\system32\sysprep\> sysprep /generalize /oobe
This would regenerate the entire disk subsystem. Just don't get in a habit of doing something this. I resets activation and the OS can only handle that so many times without having to start mucking in the plumbing.
Users browsing this forum: Google [Bot], MSN NewsBlogs and 3 guests