You are cordially invited to read my other posting, explaining in nauseating detail why it's functionally impractical for both these programs to have the same name. It's not a knock, it's not an attack; you simply *cannot do it*, adn expect users to be able to make any use of the information available about either.
What I had was confirmation from Peter that *he got it to build on some machine about which I know nothing*.
No reason to believe it's not his dev machine, which is *of course* running the version he modified, rather than a version he had just retrieved from the same place *I* must retrieve it. None at all; he certainly doesn't say in his posting here.
As for firewalls: those and realtime AV blocking are completely separate things, but *either* will prompt me before blocking something, as that is the default setting, and also my preferred one -- and indeed, my Winbuilder082 attempts with Win7_PESE popped an AV fail on SetMaxResolution, which I had to remove from the build to succeed... so I know that they're working as expected.
Neither subsystem popped up a warning when attempting to do a fresh, clean, AUTO build.
Oh: to further illustrate my point:
> You are unable to build *any* kind of winbuilder project.
I am? No; I've built two: Win7_PESE with the recommended build, and an expanded version, which took three attempts due to various fails in different places.
Oh, you didn't *mean* Winbuilder 082?
Edited by Baylink, 26 December 2013 - 04:51 PM.