Dominik D
Regular
Please. Don't patronize me. I know it's Internet and stuff but just because we're anonymous doesn't mean you can make any assumption about other people you want.Obviously you don't know much about Windows PE then.
No, it's 'load-me-into-memory' image. It's closer to hibernate file than file system let alone virtual drive.Windows PE in XP/2003 boots from an SDI file, which is a hard-drive-in-an-image file.
It's handled by a minifilter driver that exposes file level APIs only. That means there's no block level functionality and no interaction with another file system (there's no NTFS partition on WIM file). Not only that but you load this into memory and don't have to deal with the volume this file was on initially. In case of VHD you have to deal with file system on a volume on a virtual drive which is file on a file system on a volume on a real hard drive (or another virtual drive if that's also supported). Add to that the fact that you can't load entire image into memory and there are dynamic VHDs which grow as you add data. And that's not all the complexity.Better yet, Windows PE in the Vista platform boots from a WIM file, which provides pretty much the same data storage platform as VHD minus sector-level emulation.
I don't think there's any argument that would be convincing to you. So I'll pass on this one. You're right, VHDs are like SDIs.Nevertheless, both the SDI and the WIM boot image process required bootloader support, so again, why is VHD so "radically different" this time around? You've still yet to make a convincing argument of this.