Okay sorry about that, but if what you say is true that means they left Vista RTM with most of the non-critical bugs (they didn't even bother to fix the pending registry issues) that were posted during the Beta 2 stage. I'd say that this way it's very difficult to distinguish between whan vLite did and what Microsoft did, so I will have to use another method of investigation.
My next approach will be the following:
- considering the highly modular level of building Vista (inspired from XP Embedded), I think it is possible to re-extract from a Vista distribution the original primitives and packages that it's made of, each with it's full set of dependencies, registry data, install order...
- doing so for the original and for the vLited edition will allow the comparison of these through diff. In a beta it's quite explainable to find missing files and erroneous registry data, but in a stable RTM that should not happen, and I am quite unsatisfied over this case by the Ultimate edition.
- so, when removing stuff with vLite, one should actually remove just one or more primitives from its repository. This may be the perfect way to check if files from other primitives are also getting removed, thus distinguishing between what vLite did and what was initially bad in there.
Thanks nuhi for clearing the case on this one, as I still have some sets of stuff that I will have to send to Microsoft for them to sort it out. Hope I can find a automated solution for doing what I am planning. The biggest problem is that I do have a life , otherwise C# rules.
P.S. my bug reports are detailed because I am one of those beta tester geeks... Server 2003 SP2, Codename Longhorn Server and the IIS7 Preview Program, since they started it
This post has been edited by dexter.inside: 12 December 2006 - 09:51 PM