nuhi

Ok, thx for the info, updated the description.

To some extent I agree that it may be confusing since it's related to the SFC rather than SFC patch while the upper UXtheme patch is regarded to the patch itself. Gonna see about it. Ponch, is it better in rc1 ?

Search for DirectX 9 and WMP10 addons, it's all separate download on other users sites.

1. Fill out Admin's (first user) Full name in Users page 2. Maybe only wallpapers but no plans yet 3. Nah...reshack your own then overwrite 4. Yeah that one is long overdue but simple runonce entry in Unattended - Runonce page "regedit /s file.reg" would suffice 5. Try those 2-3 addon makers and just integrate with nlite, point is same and I don't have time now, maybe later. Also what I use lately is extracted addons integration...meaning for example notepad.exe and entries.ini in the same folder then integrate entries.ini and it will pull the needed info...easy to update or change some entries

1. That's true about admin name but I think now it is ok, before it was lacking Full name support. If you can prove that full windows are using only username to show the name of the admin, which i doubt then let me know. 2. Huh that's weird...which files was it? 3. That's normal, for it to be invisible I would need to apply some third party tool and I don't want that. 4. Works great for me...also in RC1 it is massively fixed, especially verify feature...so if it behaves same for you in RC1 send me a PM then we'll see about the burn log Thx

For example removal of SCSI drivers will solve majority of them. There is floppy support component too... But only disabling...nice idea...i would use that too for some parts which are used later on after pnp install but i don't have any use of them in textmode. Only problem that's luxury Someone can make that addon

LOL

It should be there after install...also in sys32\drivers if installed. I'll freak out ...you have working CD and I don't see what is the problem to see on it where should the file be after your network preparations.

msdemich, thanks for the compliments. So what is the conclusion on this theme, it's actually ok but you tried different versions or it is really bugged? I'm ready to fix if you confirm the problem.

Continued discussion here

Fixed many things, no need to thank me again this is simply clean continuation of 1.2 topic to be more readable. Changelog and download

This problem is real for some and only reason why it's not yet fixed is because it always logs on ok for me when I try it. But you provided enough information to try once more. Gonna check it after RC.

msdemich, please send me the link to that theme to try. Active...if not active then user can't logon...admin can reenable it.

Noted. Seems like some part of registry reapply which isn't allowed for limited users somehow found it's way into the reapply section once again. Gonna try your setup and isolate it. After RC version.

msdemich, nice find. It's true that OOBE relies also on Autoupdate option which prompts after install but I didn't know it could alone be the cause of skipping OOBE. Going to review that and make an option to ensure OOBE runs with a single click in one of the next versions.

TheTOM_SK, oh man you were right, if merged with more than one cab (for example if you have sp1 and sp2 integrated) it takes files from older (sp2) and then breaks all. Nice catch, fixed in next one. Gonna release it in a day or two, too many things fixed.

1. not true, find out what you did wrong, maybe tampered with boot sector, maybe your cd didn't burn right...and so on 2. not true, there must be some failure in your install, check windows\setuperr.log 3. search if someone else was talking about it, maybe it needs some component, I use Foxit reader 4. What is not compatible 5. Try MCE with that removed and you'll see it works, it keeps 1.0 which is needed for MCE 6. Because if you have MCE edition it does that on it own internally 7. What's that, no 8. Which part Try to be more informative...statements like "doesn't work" without proof will only annoy me and won't help anyone.

No, there is only one sif. Was there Workgroup entry in the sif? If so remove it.

Ok gonna look at that, sp2 over sp1 isn't my favorite combinations but that CAT file will be taken care of. Without merge sp1 is autoremoved because all the files are in sp2.cab...you can check for yourself.

Yeah Windows require that you fill out built-in admin full name. nLite would warn you that if you select Fully Automated

Pistolero, now I understand, thanks for reporting, will be fixed.

Did it ask you will you login with admin first? Anyway login with admin first after install.

Ok putting Smart Card into Printer support protection.

don1959nlite, what is the issue actually?

TheTOM_SK, consider that merge produces bigger image...do you see only driver.cab after merge and driver.cab and sp2.cab without ?