You are OK. The first (100MB) partition is properly aligned. That aligns all the other partitions automatically. I guess you were confused by the "101MB" for C. But if you convert 101MB into KBs, it is also divisible by 4.
PS: I updated the tutorial to explain this particular case.
Last edited by whs; 12 Sep 2011 at 08:12.
Thanks whs. You are exactly right in your guessing.
I'm not clear on why win7/64 divvied up the SSD into two primary partitions either. Oh well.
Well, the 100MB active partition has to be a primary. The C partition can be a logical (because it is not the active partition) - but MS always uses primaries. Just to make our life more difficult.
Well, typically on hard drives, I think the general convention is to create 3 primary partitions first, then an extended if necessary and logicals within that. That's always how I have done it, seen it done or read about it being done for decades.
So, I would have fully expected this setup to be 2 primary partitions. Not sure why MS doing this would have made anybodies life more difficult.
I quit creating logical drives a long time ago with the advent of NTFS. I didn't find it to offer any advantages that I could see.
I was mainly curious why the Win7/64 HP install process automagically created the two partitions.
In many OEM installations, you have 4 primaries out of the box (100MB, C, Recovery and tools). If you then want to create more partitions, you have a problem. Many people not familiar with the NTFS restrictions go ahaead and run into the dreaded dynamics.So, I would have fully expected this setup to be 2 primary partitions. Not sure why MS doing this would have made anybodies life more difficult.
We had a lot of examples of this problem and it could be avoided if MS and the OEMs used the primary partitions more sparingly.
What you show above is alignment which is right at 1024.
Trim query is this command.
fsutil.exe behavior query DisableDeleteNotify
If enabled it will give: = 0 as in Snip.
Quote