Sorry, i'm french and my english is very poor
I try here to explain my goal and my method. First some reply to your "questions" even if these questions are not explicit.
if it was a time when bootvhd.dll was not required to boot a VHD
Yes it was a time where bootvhd.dll was not required to boot into a vhd. My disk 500 GB shows that. But yes, you can't see that. And i understand that you can't believe it. I'm not a guru whose words you can believe. And you are rigth to do so.
he uses Go for GB and To for TB
In french, Go is for Giga Bytes because Byte = Octet in french. Sorry, now I'll be watching this point
WinPE on VHD
Because i don't say how to describe the use of a winpe into a vhd; all files of boot.wim are pushed into a vhd with (for sample), "dism /apply.."
Then also boot.sdi is required to boot the boot.wim file located on sources folder of the WinPE.
I don't boot into/on a boot.Wim. I use winpe in Flat Mode
...or boot.wim file on Ram
Because of my poor english, i never understand what is this mode. If you can take time to explain, it will be good for me
I can't understand what is the point to put a WinPE on a VHD, if it is easier just to boot a WinPE.wim or boot.wim file directly.
Yes, i understand you and it's very specific for me. My goal is not to create a winpe with classic tools like winbuilder (good tool) or WiMBuilder ( by Slore and my prefered tool, faster and "open" ). I built winpe since a very long time, since XP. And i always construct my tools to adapte winpe for the goal needed for my job when i was active in a compagny. And actually i was retired. So i continue to play with winpe and windbg and procmon and other tools. On an other web site ( ...oven), you can see ( if it was on line but this week it was not on line, i hope no relation with corona virus) the result of my work. Actually i can use bluetooth in winpe. Last year, i find how to use WDP - MTP ( in two words KMDF and UMDF drivers in winpe), printers ( with some restricts ). And YES, it's not helpfull. But i like to play with winpe and windbg. So, i prefere a "copy file" and know how to find what i need to copy rather than to use a good tool that stayed finaly a black box for me.
One precision: adding a feature to winpe is not (for me) adding an application like a partition tool or "opera" or "vlc". It's add feature present in w10 that MS doesn't add in winpe .
About winpe in a Flat mode : for research ( sorry, i don't know an
d other word for my investigation into winpe for adding new features), this mode is better because modify files and registry is easy and fast. Don't need to rebuild a boot.wim file. Adding symbols for windbg is also easy and possible all the time. This mode is not helpfull for an IT people, i understand and i know.
And why putting this winpe "flat mode" in a VHD? because i can use different winpe during investigations. Because i test one hypothesis or an other.
I understand that many peoples want to use some effective products. And don't have time to product their tools. And don't need to kown how tools are build.
And yes, it's only because i don't need winpe for my job that i can do this way to play with winpe ( add new features, use windgb/procmon ...)
I know how to remain humble in computer science because I'm not at the top of this science.
I absolutely do not want to convince you that my questions and my opinion are relevant.
I should add that I feel honored when wonko or other speakers like you take the time to answer me and also ask questions about what motivates my actions. It allows me to question myself.
I hope you better understand my goal and my way.
To go faster, I don't always use a translator.
I hope I didn't offend you.
My point is respectful, but because of the language barrier, it may seem uncourteous to you. Rest assured that this is not my will.