[CharlyBrown]

Actually I burned the whole HFSLIP-folder to a DVD and use it from the very first try. But I started my builds @home with 1.5.0. I just have an "older" build with v70506 that I finished in our company.

Don't lough but right now I did a strange "trick" to force the installation to pass the ASMS-Error:
I used the latest build you can see in the newest log file and waited for the ASMS-error. Then I replaced the installation CD with the older (v70506) build and rebooted. The setup continued at that position. Right after the CD-access I replaced the CD again with the fresh build.

Result: IE7 is integrated (REALLY integrated!) not installed at T-13 with SVCPACK, that did not work doing it this way, WMP11 is integrated, patches seem to be integrated (have to check it), ... My "branding.cab" did not work. In our company I just gave up to use the branding.cab-file and added all needed information to a REG-file that does the trick perfect. I'll try the same here later (low priority because I use Firefox all the time).
So far so good - but at the first boot I get an error message that says something weired about "msoobe.exe". Low Priority because it may be ASMS-error-related as well. The ASMS has to be fixed first.

The one working build (when I thought that it was the hyphen in the folder) was made from the same source and the same patches. I already tested that anyone of the patches is enough to cause the ASMS-error to appear. I am a little bit helpless right now.

Next to try: I'll use the 1.4.5 and/or the test release and report back... Tomorrow... Have to get some sleep now.