#Smallest windows 7 install driver
#Smallest windows 7 install full

My confusion is in what do I need to continue the build. Now, if I understand correctly, I need to startup the '_RUN_ME.cmd' which I did and it gives me a number of menu options.

#Smallest windows 7 install full

I did not see a whole lot of documentation but setup a full Windows 7 Pro environment and installed Winlib since it seems that it uses that as part of the build process. I have been reading up on building PE's and am have downloaded and want to try out the QuickPE for experimentation. Random off topic hint: the (larger) key that you have on your keyboard with a sort of arrow pointing to the left or the letters 'ENTER' or 'INVIO' is something that by convention is used after a period (or dot or full stop) to get a new line (i.e.

(Corollary: All the rest of people is wrong, or see things that don't exist, or both, and I need to make them aware of this, posting these news on the first thread I can find on reboot.pro)Д¬ompliments BTW, you made a good candidate for the 'most OT post of the year' award.

Then you tried B ( for 1 and 1/2 day) and - for whatever reasons - you (partially) failed at it.Д¬onclusion: A is soooo much better than B. So, you tried A (for several months) and - for whatever reasons - you (partially) succeeded at it. always ready for anyone who begs to differ, though. the flattened cosmetics has made it lighter and quicker than win10, at least from a mere user's point of view like mine. To those that say that microsoft has not improved its OSs from win7 onwards, I feel like replying that in fact it has with win10 in many respects, some of which I already mentioned in other posts. As far as I can understand, whatever makes ppl believe win7 is lighter and faster lies in sheer Impressionistic Enlightenment. Like hell, it booted into bsod, and the wim was no smaller than the win10 wims I have. at the end of the experiment, I also wanted wimboot it to see if less space would factor in timewise. there is very very much less to debloat, true, but it is paradoxically not as easy to take out whatever features one does not need as with win10.

#Smallest windows 7 install driver

the transition from post-install first boot to the most analogous configuration possible to win10 was one hell of an adventure with win7 (initial driver injections, incompatibilities, mismatches, system refractoriness to modification, etc.). This was tested after 1 and a half days of getting win7 to the same config as my win10s, not without issues though. win 7 takes more space than and twice as much time as I expected. I was surprised too, despite I have always been a purporter of win10 both in terms of space and in terms of time. 1 and a half day lost - well, nothing is lost in experimenting - at least now we know that, on the same machine, there is an 8-second bootup delay between win10 (14secs) and win7 (22secs). so many ppl say win7 is lighter than win10 so I wanted to scrape a few gbs and secs off the win10 wimboot deployments I mentioned above.

Sorry to butt in unexpectedly, but I am just after trying out a win7 vhd to compare it with my win10 versions.