nuhi

Seems so. Probably just server maintenance. "Our hosting operations team is working with our hardware vendor to bring the server back online as soon as possible. ETA for resolution is not later than 8am PDT"

Ok I wrote down that issue, seems like error is self-explanatory, I just wonder if it's because of something removed or it's normal. Btw tested xp sp2 32bit with all removed, including Netlogon, and Framework install worked. Meaning that maybe there is a mistake or a special dependancy when removing netlogon in 64bit (like IIS was)...so I'll try to fix before killing it.

Great. If you reread your previous message you'll see that you said vice-versa. The other day I found that Netlogon breaks Logical Disk Manager, I think this component screamed it's death cry, it will be removed in the next version. Thank you, you saved me hours of testing.

Yes I know you found the Netlogon issue but you're confusing me again, maybe unintentionally Can you confirm that NetDDE can be removed?

I tried it the first time you reported just NetDDE and it didn't help. Then I kept JUST Netlogon and it works. So please try to keep just Netlogon, it is the new component, while NetDDE is the old one and this issue would popup earlier if that was the cause. Maybe you have some installer or an error for me to check uppon for NetDDE, .NET framework 2.0 64bit works without it.

Description does imply that to some extent: Gonna change it a little to reflect this.

Thank you, I will check that now. About IIS, as I said I just removed Accessories and it fails, meaning it's the IIS entries (in the winnt.sif file), not the components.

Ok thanks. I can confirm that the .NET x64 hanged while preparing so it's another for the trial and error squad tomorrow. Let me know if you will be hunting it so that we both don't do the same. I presume some of the new components is breaking it and it's simply a dependency. I will fix this IIS thing, it's just a matter of removing some server entries.

I think I saw such a guide somewhere, try googling for it. I have no plans for such support, it's too trivial while there is more than kernel in Windows

Are you saying you tried all of what I asked you to and MSI still fails?

Ah it has it in, it's SP2...pardon my noobness

Ok confirmed, it is the IIS install issue. Now since I got the error even if only Accessories removed that means the problem is that IIS setting alone. It is quite complicated multi entry so it's no wonder, and it's maybe set for Server version only. So now I finally have a task for you, if it's late you can do it tomorrow. Try your preset with IIS set to Don't Install. And if setuperr.log is empty then try to install the IIS from the Control Panel. Let me know how it goes. In the meantime if the Installer fails after all that let me know. But first upgrade the installer to 3.1 or integrate that. p.s. ok saved your note about the burn speed.

No since I didn't got your _u part of the preset where the users are. It's probably the IIS...testing now with it set to Don't Install. Meaning it was the combination of some component which was needed and this setting No wonder it was hard.

Ok it's not the Tweaks. Suddenly it seems logical that it's the Unattended, that was the only thing on all my tests enabled to speed up the testing :\ I never considered it this dangerous. Checking now. Btw this thread looks like an IM chat, this isn't how I do things usually but what the hell it's too late now anyway, lets finish this edit: Ahhh it's probably IIS failing.

Ok then it's fine. That sfcfiles.dll in the log is normal if SFC kept enabled. Btw it's not the Options page. Only Unattended and Tweaks left. Or god forbid a combination.

I presume it didn't work when IE, WMI, nlite.inf...all failed...because setup failed before all of them then they weren't applied. It's a wonder that it works at all. I don't understand fresh source with IE7...how's that fresh No need to confirm anything, since I got the same errors you do with your preset. Just wait since I have a template for fast testing now.

Ok confirmed this: Start a new preset (meaning delete last session.ini before starting nlite) Then select component and unattended page, and in the components page you can go preset - load - preset2 - components that will remove the components from it same as would preset2. BUT this works, not a single error. And then I reload same directory, load whole preset2 (from the preset page) and it breaks the hell out of it...meaning it's not the components it's something else. edit: btw it's not the integrations, I skipped that when it failed the same.

When I use your Preset_2.INI it kills all, IE is just an Internet Option icon and so on. And then if I even just use Tweaks page on the clean install it kills it. Like that preset has some secret code in it Can't wait to find it.

I have even more weird report. If I do anything with your preset loaded it breaks the installation. I spent many hours trying different combinations and everything breaks it! But if I start a preset from the scratch and remove all the components you do it's fine. Now trying to load other pages to see what actually breaks it. Btw I don't know why did you check your source, I never blamed you. Use normal installation until I fix it or at least tell you what not to do. All of this is a big coincidence, otherwise it would be reported all the time. Even though I did get that framedyn error while testing your preset, and that was reported few times lately.

anonim1979, thank you for such a nice report. Btw it is properly cleaned it's just maybe it cleans too much or it's just signature issues. I'll be contacting you if anything pops up.

Just copy the file in the folder structured in the root of the Windows ISO you're making: $OEM$\$$\system32\ http://unattended.msfn.org/unattended.xp/view/web/18/ Then click make iso and it's inside and will be copied automatically, this is Windows feature if OEM Preinstall is enabled in the unattended page.

Just check your windows\setuperr.log file. It's a disaster. And worst thing is it breaks always...I'm now trying elimination process but it seems that it will break always if WMI is kept...not sure about this just guessing.

mushu13, in that case anoymous_person might be right that for JPG it needs Picture Viewer to be kept, it started to ring some bells.

Did you checked the setting which Maxfutur said, not some tweak, in your installed Windows on which you have the problem? Only other thing that could be is that you have to update your display drivers and set your display to 32bit color. Also disable active desktop background if it's enabled.

The error log is so full that there is no reason to list all the bugs, it's simply a failed installation. Checking.