nuhi

dAbReAkA, Well, great, thanks, updated. I hope that it's not hotfix dependant and that's it's just some runtime/or something needed of keeping, gonna check the logs and such but I need rest for a few days. If this Component Cache setback can't be fixed I'll remove it, no point in having it like that and the cache is going with component removal in parallel anyway.

lect, you haven't got the exact point of the problem, it's not space it's just changing the temp folder. Set it to default.

Only depends if you manage to make Filter Manager work under it, point it when prompted to the full sp2 integrated installation files and try, but I'm not sure how benign that is.

thidiniz, is there some problem with it or you're just saying the language pack? FnF, the image access denied error or something else? Randy_Rivers, yeah and even though I planned to go this time without any hacking it seems that setup files will have to get some. It's not copied into final Windows anyway, just on the DVD. psf-[busta], welcome, come on in dAbReAkA, sorry can you explain it a little, is that a new component removal request? TheTripleX, today I just agree with you all the time, this is no different, I too saw that only Malicious Tool installed and all other hotfixes had some error, I suspect one of the new components of course, namely first Component Cache. Also thank you all for the compliments and the reports.

Continue here, possible solution.

TheTripleX, THANK YOU, just setting it to C:\ and the error is there. Not the space issue since I had 25GB free, just changing the temp folder. So for anyone having this issue please click Default in the Temp folder and see if it helps until the fix is ready.

Did you remove both Inbox and Premium (if found) games ? Also which OS version is it and did you select for remove and pressed Apply?

It is reported constantly but no clue why it happens. If I manage to get that error it's solved but how to provoke such a thing...

Unsigned popup will be the number of unsigned inf files in a folder. Yes they are integrated as you insert them, insert it last. But why is your monitor off, can't handle the refresh it set? Maybe integrating monitor drivers before the display driver would help but I doubt that they have Vista drivers yet.

Try to remove the read-only attribute on the whole installation folder with files and subfolders.

OK since few people confirmed it I'll make sure to check it for the next update, thx for reporting.

Vista has it's own list of available components in the Control Panel - Programs - Windows Features, but it's only few. One note, to have even those keep the Components Cache component in vLite. And for the custom installation of components via Control Panel is impossible for us because the so called packages are signed. I'll repeat with the risk of being boring but I don't see what's the problem of writing down what you don't need over some time. Install full Vista first if you are not sure and when you see something like Tablet PC and that you never use it why not remove it on next reinstall without any risk. But then don't be greedy and start removing stuff only because you saw how much space they take.

Components are very complicated in terms of file locations and registry entries, but most of all security permissions. So I would have to say only reinstall would guarantee properly installed component, unless you want to spend couple of hours doing it manually. If you have any doubt about some component just leave it then, it's easier to remove more on next reinstall than it is to be forced to reinstall to return some. I'll try to help by making more and more compatibility options. From the times of nLite only thing I needed and removed but wished I didn't was VBScript once for some program autoupdate feature, got the DLL from the full XP. I don't think there is too much risk other than runtime of being needed unexpectedly.

1. oembios.bin? That means that you used the custom remove box for extra files, and maybe even later overwritten txtsetup.sif with older one...can't tell for sure but suffice to say it's not something you can click yourself into. 2. only time when i heard about failed cd key and confirmed it was during Windows XP Media Center edition editing and it got it's own compatibility option. For Windows 2003 it never failed, could be the byproduct of the first errors. You should remodify it by using that same preset but on the clean installation files and be sure not to use the Remove box unless tested (components page - advanced) Also never overwrite txtsetup.sif and dosnet.inf after nlite.

Didn't ask me anything during testing. You mean when file deleted, like File Protection? If full one restores on delete then it would be nice to know. It's not like I had this version much longer than you do, just look at the release dates

Jeronimo, ahhh true! The function left commented out while I was testing something before release, gonna update silently. Updated.

I don't know, never tried. Next time use Virtual machines to do testing before real install. If I find the dependency I'll report to you, otherwise it will be just a dependency.

Checked it, it needs Task Scheduler. If you remember the Defrag when it worked it has a tiny GUI with total focus on Task Scheduler so this outcome would be expected. I'll check if maybe some tweak would allow it to run without Task Scheduler but until then keep it while making the ISO.

It doesn't differ from the normal Windows version in that regard so your question would be better fit on the other sub-forum. Also a little searching would help you a lot more because it was hot topic on these forums quite often.

The enthusiasm is appreciated, thank you all. Fru T Bunn, if you think on it missing from the components then yes. TheTOM_SK, if they work when you manually update them in Vista from the Device Manager then yes.

This is kinda weird report as I have ADSL as I'm sure also does the majority of nLite users and no one complains. To be on the safe side next time use Ethernet DHCP compatibility option and don't apply any network tweaks, nlite's or your own, until you find what causes that for you.

No problem. I was watching your avatar anyway

And you didn't say the most important fact, that you're probably using the Framework Lite made for nLite. It doesn't support vLite.

Should work, I'll test it later, if you find out first let me know, you could start with the new components, thx.

Hochi, well then in a few more versions with new components you'll be able to reach 700.