So I tried doing this prodecure, but the windows 7 installed saying "cannot install required files". Also during vlite while applying changes had a similar error "cannot find file" or something which I think is related to why the install didn't work either.
I did make some mistakes though (used an older session file, possible other files older as well. It was rather confusing since dead0 didn't post his latest file package in his original post), so I'm retrying the procedure again, with just the new files, and hopefully with no mistakes.
Anyway, the main reason that I'm posting, is I'd like an explanation of what is being removed by the dism bat and removal bat (and/or the vlite preset)for win7x64 of dead0's latest file package, and what impact it has on the functionality of windows.
I can see the components obviously from vlite, so that's less of an issue, but with the dism, there's no description of the components that it removes, so it's harder for me to understand it's impact.
Is there a basic explanation of the functionality that is still there or the functionality that isn't? For instance I saw some diagnostic and/or network things were removed with both vlite and the dism bat - does that mean I wouldn't be able to view the network (or even system) performance section of (task manager's?) resource manager?
Also, Windows Remote Management is on vlite's removal list, but it says it's required for event log. Is this false, or should I uncheck remote management if I want to use the event log?
Same thing goes on with "quality of service" (network section) and "IPSec Policy agent" (service), to have enabled windows update (service).
Or is it possible that the remove/dism already removed components that allow the event log or windows update to work already?
One big thing I was wondering about is that the removal batch file says something like ".net framework will not be installable in the future" I assume this is still true, or is there some sort of fix or what? I was just wondering because what if a more recent net framework (or small, but critical for some, update for it) pops up in 1-5 years down the road? Will I just be screwed? I don't want an OS that won't last for a long time.
Oh another thing: I am using an ISO which already has updates slipstreamed onto it, I presume I can skip the add an remove stages of the guide fine, right?
Edit: so I tried doing the guide procedure again and It didn't work perfectly. When vlite was just finishing up the modification it said "The system could not find the file specified" (although it didn't SEEM to abort the whole process, but the ISO file size was hardly shrunk at all, so maybe it did abort).
The only things different is when I ran vlite I kept zip/cab viewing, Quality of Service, Digital Rights Management, and IPSec Policy agent. Also the Windows ISO has updates on it already, and I skipped the updating steps.
Also errored on install, something like "windows cannot find install files". This occurs before even doing step 12 or 13.
This post has been edited by joesi: 31 January 2011 - 06:38 PM