nuhi

phaolo and jaclaz, you both are mentioning iterative approach. nLite does support multiple sessions, it is not made to be used only once, just that it is recommended approach because of what I will explain next. There is confusion with presets, as you start piling up last sessions, they would need to be merged. If something was removed then adding hotfix for it popups up missing files messages and people wonder why it is not integrating. Update packs can literally change everything, and nLite can't track that, or should I say it would be a nightmare to map all changes into entities and undo packages. nLite gives you the ability to save whatever it does in a single file (plus unattended preset for safety reasons), so you can easily start fresh by copying your prefer source. That source can be whatever you want and made from whatever steps you want. Configure that source before nLite, back it up, and there is your nLite undo. I see no real problem there, maybe you can give me a scenario where you must use nLite many times and prefer to use multiple presets each time. Of course it would be ideal if nLite detected that you already enabled a certain tweak which can be done with a group policy, reg entry, a batch script, an addon, but that is just dreaming as the combinations are too great. And lastly, returning missing components is simply too much work for a non-issue, simply start fresh and use same preset with that component not removed, simple as that and requires no tricky - easy to messup - multiple combinations of post-hotfixing returning of old component and who knows what other combination. In short, if you find a bug that is caused by running nLite multiple times, please report. To undo what nLite did, use your source on which you used nLite and configure the preset differently. And in case you get mad at me not understanding, I am not dissagreeing with you that it would be ideal, I am just saying it is not practical to have undo from nLite itself, it would be much more complicated and prone to bugs.

hehe, yeah refreshing my memory, and rewriting whatever I see... dayum must... resist. I am always using latest Windows as I like to see those dll numbers increase, so yeah, new tool is in the works. Not fixing nLite would be a shame, regardless how many people will continue using XP. If it starts taking too much of my time then I will drop the idea, but for now I am willing to try both. edit: and I am going over all of these posts, if I do not reply directly that doesn't mean I ignored it, but I don't say anything until it is checked and can't be reproduced, or it is unexpected and needs more info

Thanks guys. Kelsenellenelvian, oh that. The section merging I was doing with nLite already from way back. I think it is automatic if file is edited in any way. If it is not merged, or some files are skipped - I'll check. That some files are not compressed, if I understand that file diff correctly, will check that too. "Launch folder windows in a separate process", that option is in Explorer - Folder Options. Unless you mean that the special way nLite is doing it, is not safe, in that case I would remove that tweak. Or you mean MS stopped XP support and it was said by them to never fix?

Thanks guys for the warm welcome. -X-, nicely compiled list, saving that for detailed review, appreciated. Kelsenellenelvian, I'll check the optimize function - whatever that is. Can you please elaborate with at least one file as an example of leftover SP3 files and/or uncompressed ones, and when does it occur if it is only after nLite?

Well, hi So I am back, in other words free to work on nLite again. I am willing to consider updating it if you guys have some serious requests, be it fixes or missing functionality over the years. For now there is no plan to update vLite, I am working on something else which will cover that area. The release date is not yet known, it is safe to say it can be counted in months, not years. Fire away, if there is anyone left