You have to be careful with 'DISKPART' it rounds off the value to the nearest 0.5.
E.G
32Kb could actually be 31.5Kb, which would be misaligned.
------------------------------------------------------------------------------------------------------------
'DISKPAR' <--- no 'T' at the end, will display the exact value correctly.
Download: https://kb.wisc.edu/images/group14/4556/diskpar.exe
Command: diskpar -i 1 (where 1 is the drive number).
E.G
StatringOffset = 32256
(32256 (31.5Kb) / 4096 (4kb) = 7.875 ,is not an integer of 4, hence is in misalignment).
------------------------------------------------------------------------------------------------------------
Windows system information (components > storage > disks) will also display the exact value in bytes.
E.G
Partition Starting Offset 524,288 bytes
(524,288 (512kb) / 4096 (4kb) = 128 which is an integer of 4, hence is in alignment)
------------------------------------------------------------------------------------------------------------
As grb said Vista SP2 and Windows 7 will automatically align a solid state drive to a 1024Kb offset by default.
E.G
(1048576 (1024kb) / 4096 (4kb) = 256 a integer of 4, hence is in alignment)
@kallogan
Yup benchmarks across the board were much improved especially on the 4Kb read and writes.
In real terms you may not notice much of a difference, but being in alignment definitely helps for I/O throughput.
Maybe more important for the first gen SSDs that have smaller cache and suffer from the infamous I/O stutters and pauses.
