You just need to make sure that your imaging program will restore the partition with an appropriate starting offset, i.e. a multiple of 4k bytes, rather than the 63 sector (32256 byte) offset that was typically used on Windows partitions pre-Vista.

The program that writes the image back to the disk determines the offset. This press release for Paragon Hard Disk Manager 11 indicates they've added automatic partition alignment, and Drive Copy 11 does advertise HDD>SSD migration capabilty, so at least the latest versions of their software seem to be optimized for SSDs.

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.

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.

It should. I have a Windows Home Server, so I'm familiar with the backup (which is pretty much the same as Windows 7's). Make sure you back up and restore the Windows 7 recovery partition as well.

I have not gone from a bigger drive to a smaller one though, so I can't say what will happen there.

I am fairly sure that the restore will fail before it really even starts. Since you will not have the same size partition, the recovery SW will balk. HOWEVER, since you are using Windows 7, you have the option to shrink the volume. That may not solve the issue entirely, either. There seems to be a limitation in the shrink based on the location of the last file(s). If you can do all of that first, then get a backup, then do the restore I expect that you will have success.

First tried going into the Win 7 advanced setup and formatted the SSD and then restoring an image I made in Paragon Backup & Recovery 2011 (free). It looked like it was working, but then once I hooked it up as a boot drive and nothing. Looked at the partition and nothing. Tried a couple other ways to do it – no go.

So now that I wanted to shrink the partition, thought it would be safer to make a test drive. So I restored to a 500 GB but left the size alone. That booted nicely. Looked to shrink the partition and Win 7 would only shrink it to about 160 GB, still too big for the 128 MB SSD. So tried the Paragon partition manager. It would not allow me to directly shrink the partition. It wanted to shrink one and make bigger any that were next to it. Since I still had room on the 500 GB, I created another partition next to it. It then allowed me to increase it’s size while shrinking the C> to 116 MB. Had to do a restart and it made the changes “outside” of Windows. When done, it booted fine. I made a new image of the smaller partition and then restored it to the SSD. Booted up and was like greased lightning.

•The destination partition must be equal or larger than the source one

and thought that would not work. Then as I got through the process I did, I realized that what I used had the same problem. I did like that Paragon allowed me to do this within Windows, so I could work on other stuff while this image and shrinkage went on in the background.

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?

I have the retail version of Acronis True Image Home. I've also got plenty of disk space on other drives to try the backup and restore method. The only part of this three-week old installation that I dread re-doing is the configuration of all of my cable channels & listings in Windows Media Center.

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.

--The benchmarks listed above are part of the Windows Experience Index. If it's just a matter of WinSAT running a disk test to enable the functionality it would be a very simple command line task.

Frankly, other than double checking that defrag isn't running on the SSD, there's really should not be any need to muck with the OS. It's incredibly unlikely that the system will be faster without SuperFetch and Readyboost. It's also unlikely that leaving the services active will make the system slower.

"Welcome back my friends to the show that never ends. We're so glad you could attend. Come inside! Come inside!"

Sorry for resurrecting this, but I do have a follow-on question. I am thinking of buying a new SSD myself and pass my G2 down to my brother's machine, which is still using a mechanical 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.

I think I get the ImageX part in terms of migrating the data+settings from C: (the whole drive), but has anyone found out whether defrag/superfetch/readyboost is disabled automatically after the SSD is in play? Or is there some documented steps that I need to perform?

The Model M is not for the faint of heart. You either like them or hate them.

The Windows Experience Index (WEI) is supposed to trigger most of the changes (Readyboost & SuperFetch). The defrag change happens as soon as the system sees the drive report itself as an SSD.

There is no point in having Windows change behaviors. If you want to disable ReadyBoost, fine. That saves you a few megabytes of memory. Windows 8 actually reversed the Windows 7 SuperFetch adjustment. Windows 8 now leaves SuperFetch on even with an SSD as the system disk. As I noted in this thread, cached RAM contents are vastly faster than an SSD.

"Welcome back my friends to the show that never ends. We're so glad you could attend. Come inside! Come inside!"