Migrating to an SSD

  • Thread starter Thread starter Yousuf Khan
  • Start date Start date
What tax? A capitol gains tax? I bet I pay more then Romney pays for
what he gains every year.

It that what a ruler pays for having a center of government?
 
Who disabled System Restore? I dunno, maybe the driver or something. Or
maybe Windows 7 does this for all SSD drives by default, I dunno. And it
has been over 2 years ago that I ran Windows 7 under an SSD. So I don't
recall what it did for System Restore.

System restore works on my Win 7 SSD-equipped machine.
 
OK, thanks for that information..

Well, the "original" win 7 installation was to a hard drive. It had
been "cloned" a few times as I tried RAID configuration(s), and
eventually trimmed what I had on the drive down before swapping to the
SSD.

Now I followed the instructions from the site you gave, and my results
are: Partition 1
Type Primary
Size 107 GB (it's a nominal 120 GB OCZ)
Offset 31 GB

Reading the info on the site says the number (in MB) must be divisible
by 4, so I multiply this by 1024 and get a number in MB that "is"
divisable by 4, so I should be OK. Is this your interpretation as
well?

Looks like it probably is. 31MB is the alignment that XP used, so it
looks like even the XP alignment was compatible with SSD's.

Yousuf Khan
 
Charlie said:
OK, thanks for that information..

Well, the "original" win 7 installation was to a hard drive. It had
been "cloned" a few times as I tried RAID configuration(s), and
eventually trimmed what I had on the drive down before swapping to the
SSD.

Now I followed the instructions from the site you gave, and my results
are: Partition 1
Type Primary
Size 107 GB (it's a nominal 120 GB OCZ)
Offset 31 GB

Reading the info on the site says the number (in MB) must be divisible
by 4, so I multiply this by 1024 and get a number in MB that "is"
divisable by 4, so I should be OK. Is this your interpretation as
well?

Get a copy of PTEDIT32 here. This will at least cover primary partitions.
I don't have any logical partitions here, so can't say if it lists those OK
or not.

ftp://ftp.symantec.com/public/english_us_canada/tools/pq/utilities/PTEDIT32.zip

When you run it, look at the "Sectors Before" value for each partition.
That tells you the alignment. If "Sectors Before" is divisible by 63, then
you have an old CHS alignment, which is not optimal for 4KB sector HDDs or
for flash based SSD drives.

For example, my primary partitions are like this:

Sectors Before
Partition #1 63 / 63 = 1.0 (CHS aligned, not for SSD)
Partition #2 40965750 / 63 = 650250.0 (CHS aligned, not for SSD)
Partition #3 81931563 / 63 = 1300501.0 (CHS aligned, not for SSD)
Partition #4 119427210 / 63 = 1895670.0 (CHS aligned, not for SSD)

They're all evenly divisible by 63.

Now, if they were evenly divisible by 256 or 512 or 1024 etc, there
is a better chance that would be a good alignment for an SSD. It
depends on the SSD flash "block size". Depending on density of device,
it could be 128K (256 sectors), 256K (512 sectors) and so on. Microsoft
uses a value for the offset, which tries to cover the most likely
block sizes. Some day, a flash chip may exist which is so large, that
the alignment is again non-optimal, but I expect they'll fix that
with a new OS :-) It wouldn't be like Microsoft, to issue a patch
instead.

Paul
 
In message <[email protected]>, Allen Drake
at once. On an off week or so I might have slipped in a 128GB or the
Crucial Adrenaline but most are the 256GB versions. I even put one in
my Netbook. That one really needed something to bring it up to speed.

And how well did it succeed?
 
Back
Top