nuhi

Ask Microsoft that, I didn't lock it. People will have preintegrated ISO anyway when it comes out so this will be a mute point. Tell me one thing, can you imagine someone making XP Lite SP1 then install SP2 over it? I can't, seems so funny.

Try new vLite when it comes out on Monday, if you are open to a reinstall. And make sure to keep Firewall, it was needed for one hotfix in my tests. Other than that 2 other hotfix installs were fixed so that might solve your chain reaction.

mimanig, that removal wasn't changed so I presume it has something to do with update packs or your INTL.INF file is somehow different. Attach your preset and explain to me how to see that error. Also make sure you have clean installation files while confirming this, not tampered with.

If you get Invalid URI then it was probably networked drive or something like that out of the local drive. But that Filter Manager error is one of those rare bugs. I don't have any explanation for it so far. People say that it's solved by reinstalling the host machine but that cannot be the recommended solution. Try to run it in VMWare from some freshly installed OS, that way you can configure your ISO and just get it out of there after it's done.

Not any more. I saw that Firefox starts faster with it so I leave it. In my latest install I kept: Aero, IE, Media Scheduler, Superfetch, App Experience, Game Explorer (but this one won't survive next reinstall).

Since the new SP1 RC Pre fails almost on any removal I recommend that you don't install SP1 on vLited installation. Procedure should be: install full on another partition, run sp1 on it, boot to another Windows or WinPE and capture that SP1 install with imagex. Now you have new WIM file which can be used with vLite. And you don't have to install SP1 on every reinstall. But of course all this trouble is worth it only after SP1 final is released.

It's not you, it's me It is taken care of in the next version.

There are some components removable in the new one that are always loaded and once removed it will lower it but nothing drastic. Out on Monday, no comments until then. If you have less than 1GB of RAM upgrade it now, it is so cheap these days. I just bought another 2GB and now have 4GB, Vista takes it all to cache and it flies. To not get you confused the reason why I remove components is that they get in the way and take resources which are not there to be spent on the OS itself (Crysis anyone?)

Oh, do you maybe remember how much you had when it failed so that I can up the warning?

pizzag, wait for a new version, it has a lot of stuff fixed, this might be one of it. Since I never had this issue I can't guarantee it but it's best to wait. Out on Monday.

brotherik, then simply backup iernonce.dl_ and when nLite is done integrating that hotfix return the original iernonce.dl_ by overwriting the new one. I'll add this later.

This error is only possible in older nLite versions, use latest 1.4 final instead. Starting from the clean source of course.

No. I never announce because that would put the tension on me, the "must" factor.

Please try just IE7, without the hotfixes. Could be that they updated runonce dll again and when they do that it doesn't. After you confirm that it works with just IE lets find which hotfix it is, or if it fails I'll try your preset without the hotfixes.

Hvala, samo sta ovo nije moj forum, samo sam gost u ovom podforumu. Vlasnik je xper, takodjer nas razumije. Malen je svijet u zicama /sorry to all for non-english, it's nothing related to the subject.

If I understood it correctly you used nLite just for the SP slipstream and Unattended settings? In that case nLite can't make those mistakes with files since it didn't touch them. Try by just using nLite, to integrate RVM pack as well all in one go. Start from the clean installation files again. Next time if you get some file missing error that is a reason enough to quit, that shouldn't happen and it usually goes bad. Btw redownload 1.4, it was updated, not related to this but anyway. And test your ISO in virtual pc before actually burning.

64bit removal is too slow because there are double the files, gonna try multithreading but the HDDs are the bottleneck so maybe I can't help it.

3 seconds? It is 8 seconds on my pc, that's borderline. Maybe you got offended judging from that lame reply about deleting this topic but for my standards vLite is too slow. Not completely my fault since there is tens of thousands of files but I believe it can go faster. 10 seconds is not nothing if that feature isn't really needed. You pressed Apply, what good is it if you find out 30 seconds before how big it will be, why spend 10 seconds for the calculation. And yeah you need to get info on every file, there is no folder size option in the code.

Yes, keep Manual Install and Easy Transfer.

Don't remove Manual Install component. Pozdrav

Yes I am aware of this Winrar issue, noticed it when the selfextracting exe is ran there is a big delay until it's started. Haven't tried to fix it yet since I considered it as a dependency...and weird one, I mean if it didn't start ok, but it goes slowly...what's up with that.

Please try the latest 1.4 (redownload it) and let me know does it solve your issue.

This has been fixed in the latest 1.4, check the main topic and let me know if it works with the Lite now. This applies just to those with the cablib error.

Kurt_Aust, interesting. beats, ok, wrote it for later. mttbac, uh it's so nice to read that. Updated it again silently because not many people reported this: fix: cablib runtime error on source browse

That section doesn't support wildcards and probably won't work for the root files, only for those inside amd64 or i386 folder.