nuhi

Ok I'll reenable * for Computer name...anywhere else?

Ok fixed for next one.

Well if already 2 programs aren't working then it's safe to assume that it's bad installation of Framework, just uninstall 2.0, then delete: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 reboot, and then reinstall 2.0. It must work, unless it's services but lets first see this.

Yeah, I disabled the IDE controllers and was able to reproduce the problem, thanks, fixed for next update which won't take long.

Post a link to that driver, tell us which textmode entry you choose, which Windows and what is the actual problem. You say once it loaded the drivers, that means you're not sure how to operate it, just ask step by step what is not clear.

Don't worry I'm not attacking but also trying to help. I'll assume that you tried without tampering with services from your post. If someone else can confirm it's merging that would be good.

I don't think that Merging can have anything to do with it, instead reset your Services page, you disable Workstation amongst others, that can be the reason.

Delete Workgroup. It's because of the rule that there can be only one

Haven't tested it but as long as you don't enter same name in both nlite and oobe you'll be fine. Just choose to autologon with some user created in nlite and oobe will be skipped. If not let me know.

Little searching wouldn't kill you. Discussed here

Limitations are identical, even the allowed characters. If you find a mistake I'm listening (just a statement). Documents are from whom created them, meaning if you're looking some documents from your previous install and they are not named My Documents but for example John's Documents then go in, show hidden files, and delete Desktop.ini file.

dhedges, if this wow32 thing solved your problem then let me know which nLite did you use as 1.2 has that fix in it, if you kept Printer Support.

Username is with what you logon, full name is like a descriptive full name of that username. Username can't be blank, fullname can in all except administrator if you want fully unattended installation. You ask basic things like you never installed Windows before? Those things weren't invented by nLite, it's only a tool to do it before install, search on microsoft.com for better info.

Ok thanks, that helps.

You were right, it was in Cluster service, nlite parsed the obsolete NT4 entry with security.dll Temporary solution is to put: security.dll into Components page - Advanced - Keep files list.

diorser, I tried to insert the wmp10 addon and it didn't display anything. Weird I thought. Then corrected the message, for me it says it's French addon and cannot be used on English Windows. Do you have French Windows version to begin with? And what was the 1.0.0.16 error, you say not compatible...what that means?

There is agreement for update packs because Ryan do listen, but those addons are like little pacts around their forum. As I said it's up to you, me and Siginet are not on the best terms lately...and don't expect me to try every addon out there, I do my best with the features this program is primarily intended for. It's simple...report a link, say what's wrong, I try and fix...then in a week they will generically all work.

Just came to me why, have you ever tried putting Administrator for a full name during windows installation? I'm 99% sure it won't allow it, but for that 1% you can in virtual to see for yourself.

And he strikes below the belt...10,9,8,7...

I'll see about those addons and what feature is needed, shouldn't be a problem. Don't be reluctant to report if you need some addon support in nLite. Basically all I care personally was update pack compatibility, those addons use Siginet introduced functions which he introduces how he likes. Fine, I don't ask him what to remove either. Anyway it's up to you users to require what you need then I'll review and update if the feature "feels good".

Or mine Or something removed then it thinks that it needs hotfix, happened before. Anyway I'll check this, thx for reporting.

Yeah that is the problem with this phantom...but it's so rare that we can simply recommend retry or reinstall, thx.

It's not that, problem was with indexing when you insert windows classic theme and remove it. Then any added theme if selected on the right will popup this error.

What, it's over? No blood? ...ripoff...

Excellent, got the same error, gonna fix, thx.