b9810959, I won't be supporting Windows Embedded in any of my tools, I don't see the point as they are already split.
R4D3, I'm sorry that you are sad, but it seems to me your emotions are misplaced.
nLite is free, that is my gift to you (and Kels). If I am to give the next tool, which is completely written from scratch and basically has nothing to do with nLite except me, if I am to give it to all the fans for free, I would be left with 0 coins of compensation, and bye nuhi again.
Now you will have a free version of the new tool, and those of you that really do help I will gladly give free license, updates and what-not. And people that are good with the community I will include in as well.
But it is my subjective opinion as to what that valuable help will be.
So you think that I should not charge to poor people? Hm, that is a difficult subject and I won't be commenting on it.
Kickstarter could be a good idea, but not to sell code. People mainly use Kickstarter to kick-start a startup, not to do a one-time job and sell their livelihood (code in this case), thus killing that startup. And I would not be able to collect 0.5mil anyway, so it would again be sponsored by my savings.
Ultimist, I agree with your expectations, there will be more and more warnings to scare away those who do not understand what this tool is doing. One can't expect 100% Windows functionality with parts of it removed.
But up to some point of basic functionality on which we can agree, and make compatibility options, by all means, if you find a bug let me know and I fix it.
Pro feature... soon
Basic/Advanced mode... yes it might become necessary to hide tempting components. For now, there are compatibility options which are checked by default and they make protected components unclickable.
I also can't wait your feedback so that we can get to that dream tool one day.
sixcentgeorge, "instead of visiting the forum", lol, indeed. But without the connection I find this job boring.
MagicAndre1981, everything in Windows is files and registry entries, so in a sense I am not sure how to answer this. Let me just say I aim to not have any leftovers.
I saw people are using vLite with Windows 7, I cannot refer to what it is breaking or not.
I can add to that, if a package has, lets say 40 components in it, and I allow to remove them individually, you can't expect the tool to edit that package file and resign it to not know about the missing component(s).
That only Microsoft can/should do, I won't be bypassing any protections.
This brings issues with big hotfixes which essentially expect full Windows.
I have some ideas how to tackle that in the future, which I cannot discuss now, and until then I recommend to reinstall in that case.
Lets say you edited Windows 8.1 and Update 1 was out, of course Update 1 will error out and you would need to make a new ISO with it integrated and trimmed.
Us tweakers should all know this from using nLite, vLite and similar tools, so if you are in any way surprised, I am surprised at your surprise.
That said I went through a few patch Tuesdays on my lite OS, and hotfix failure rate is very very low, I am satisfied for now.
The tool was built from the beginning to treat WinSxS integrity as a must.
Of course I would like 0% failed hotfixes, but I am aware that is not possible post-install with every configuration, especially with big Update packs.
There will be a warning about this, to scare away anyone that is not really into it.
edit: there will basically be a beta version soon (in a month probably). And if you meant will there be a free open Pro beta test, then no, due to the nature of the tool (you might need it only once), the Pro version will be a beta pre-purchase for those who want to have some fun and show support in advance while basic bugs are being ironed out.
Edited by nuhi, Today, 08:39 AM.