All right sir, I am reading the .docx.
We enter the realms of personal opinions, so at this stage just brain storming, saying whatever comes to mind, it doesn't have to be accepted or not.
Stage one, big picture article topics.
Stage two would be nitpicking grammar.
So stage 1:
• Forums and article are two different things. I would avoid speculation about Microsoft's "motives" in the article - that's forum posts stuff, more for comments on the article topic.
Good point.
• Love the 'What the fix fixes' section - like I said grammar nitpicking comes later. Really like your concept of the approach to this.
• Love how the less computer inclined readers get an overview - this is *crucial* to them implementing the actual process. You had to go through this the hard way and then by writing this, you made sure others do not. Thank you for that.
• The more I read, the more I see the value in explaining things that need no explanation for experienced users. So I support your style of "hand-holding" approach to this.
It's easy to bridge the divide between the computer experts - just give them the option to skip the intro, through a link. Average home users then still get to do this.
• Possibly once again remind them at the beginning of docx Step 7. that other internet browsers cannot be used.
I agree. I was even considering suggesting that at least for this build process the user should make IE the default browser.
• This is how older .net framework can be installed from Windows 8/10 installation media, quickly without the need to download and install anything.
(If their Win 8/10 computer is a mass produced machine such as HP or Dell it won't come with any installation media. I'm inclined to leave this one alone.) I am not saying that it's not easier to download, just FYI:
Right click on Command Prompt > Run as administrator >
Code:
Dism /online /enable-feature /featurename:NetFX3 /All /Source:D:\sources\sxs /LimitAccess
[Replace D: with your drive letter for Windows 8/10 installation media.]
Wait at least five minutes for the process to reach 100% and finish.
• .docx Step 13 where it says "Note: The June update rollup is not needed." Tell them why. It is already included in the July file.
Good point.
• Love the Now here this! Now here this! section. That is exactly how things should be conveyed to the masses.
• The words "Rufus will only make a USB installer" imply that a DVD installer is needed. The finished .iso is bootable, no DVD installer is needed. I may have misunderstood this part, but .iso file is the dvd installer. Rufus just gets that .iso onto a USB and makes it bootable, which is the only extra thing that is needed. .iso goes straight to DVD by burning an image from the .iso file.
Microsoft's tool
https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool
or Rufus gets the .iso transferred to USB.
My intention was to convey that Rufus won't make a DVD installer by itself. From the Rufus user interface the only choice is USB. But I can add some comments about how to take the ISO and make a bootable DVD with the built-in Windows tool.
• The end advice is very useful. I may have a thing or two to add there when we get to the grammar nitpicking stage.
But you have included a couple of questions I've seen come up every time a novice uses the slipstreamed DVD/USB.
It's just really nice to see you break down the process, computer experts would say "dumbing down" the process... but what this does is makes it actually usable by regular people.
We have a fine start here trents.
.
