#Ptedit32 manual
#Ptedit32 windows 7

#Ptedit32 manual

I'd suggest imaging that drive so you don't have to go through the manual partition process again. Don't worry about what PTEDIT reports, because as the others have said, it's getting it's numbers from the bios and is only meant for compatibility. If you've manually partitioned the drive and it's got an aligned offset, you should simply enjoy the drive. I've heard of others with a similiar problem that you're having with getting the disk aligned and not getting the OS NOT FOUND error or whatever it is. However, if you do the math, 7783 * 255 * 63 * 512B/sector, the totaly size of the disk is not a multiple of 128K! How is this possible? Did PTEDIT missed something? However, I have a question: PTEDIT reports the disk has 7783 cylendars, and the geometry is 255 heads/cylendar, and 63 sectors/head.

The first partition is now only 128K from the beginning of the disk, and my motherboard seem to like it. So I manually created two partitiones, all aligned to 128K boundary. From the RAID guide, it seems like the flash block is 128K bytes large. So, I manually aligned my partition with a PTEDIT32 and calculator. But the first partition being 1MB away from the beginning of the disk is way too large for my motherboard, making it hang at post (think of it like a caveman can't count to 10.

#Ptedit32 windows 7

Windows 7 did recognize that i am installing on an SSD, so it uses 1MB alignment for the partition. I am installing Windows 7 onto my newly purchased X64, on a pretty aged laptop (centrino generation).