nuhi

docthemac, this error doesn't mean that your image is corrupted, it's just ISO/Boot problem. It is solved for the majority, weird that you got the error if you used v0.95.

Biggest is probably Search service, Defender, DWM, Remote Desktop and Assistance, Sidebar.

Is your Windows English or some other language? And name at least 2-3 files which are reported corrupted.

That's error in Vista setup because you don't have 256 and more ram free. You can't use it. Why would you even want to with so little ram, it would be hell. That other error don't know.

Did you used All In One Winbeta Vista and extracted just one version from it?

Ok, thanks.

Is that partition FAT32, does it have enough free space? Also maybe it's done, have you waited more to see if it progresses, it stop there for me too for 10-20 seconds? Disable resident antivirus or set it to scan on execute only.

Can't confirm that, seems fine to me. edit: one other confirms it, I'll try it on Vista, I presume it's only issue there.

I appreciate the enthusiasm but unless we know which service or setting that exactly is there is no hope for the resolution How did you even saw that polling to be sure in it?

RYU81, try to reset in the options Temp folder to default and restart vlite. If that doesn't help try restarting your pc too.

Ok, thanks.

lorcan , you know what else...kinda stretched but it may help: (This is only for this purpose of older hotfix detection, not how I normally do things) Integrate IE7 first, then all other hotfixes with reporting enabled, then nlite prompts during those hotfixes if some file is obsolete, then if you see that you get multiple prompts for the same hotfix during progress then it's more likely that it is obsolete and you may check it. For example if it says mshtml.dll, detected newer version on CD then imidiatelly you can ditch that hotfix because it is for IE6.

Do you have less than 256ram ? Count if your onboard vga is sharing it.

Thank you for the compliment. Are you sure that this is something you want to disable, I would like it to check if "everything is ok"? But if you're actually implying on that DRM pooling for protected content then I agree. Now if it's legal to disable that (highly unlikely) and even possible to find and disable I'll gladly do it. Try to remove WMP with the codecs, that might help since it's directly connected to DRM. But wait for the next version few days, it has even more components which removal may secondary lower latency.

Without going into much detail suffice is to say that eventually vLite will get there and you will be able to remove all that you don't need with a click of a button, but as you no doubt already know it takes time to debug that. So until then all I can say again it's easier to disable than it is to remove post install. If you mess something up it can't boot and you end up frustrated. Of course you're welcomed to try, my advice for the start is don't delete winsxs subfolders, it contains needed runtimes and component backup files, which are needed for the hotfix installs, unless found otherwise. That component is hidden in vLite as of lately, too much fuss and by removing more components winsxs is shrinking anyway. I'll see about that driver store temp folder, seems to me it's post install thing, I would catch it on the radar if it was that big in the image prior the install.

Don't mix size with speed. Removing, or at least disabling services for now would yield much more in terms of speed and RAM memory. http://www.speedyvista.com/services.html Removing some random folders just because they are big will gain you nothing except more free hdd space.

How can you use RVM pack on Dutch XP, it is for English only. You can insert RVM pack with nLite all in one pass with the other modifications (use the hotfix page). But that pack is for English only.

nLite tcpip patch works perfectly for xp and 2k3 all versions except newest with 2k3 sp2 64bit I think, I tried 32bit and it's fine, but I think someone reported that 64bit didn't work ok, gotta check though.

Final like 1.0 final, not just 1.0 ?...who knows, 2-3 months. 1.0 beta is out soon, next week.

That means that your sysoc.inf file is missing [components] section, which is critical and should not happen through nlite alone. Did you use some other tool, modified your installation in some way, that file especially? Maybe some addon you're using...try without them...recopy clean installation files when you retry it.

When you click Apply did you select the second option to Rebuild?

Well how do you expect it to modify the installation without actually modifying it. Making ISO is just copying files into certain format suitable for the CD/DVD drives, modifying installation isn't just copying files. In Vista's case it's editing one big file, the image. You should have selected to install drivers obviously. That means you are using beta or non-vista drivers. Use WHQL certified and it won't popup.

WCF component removal is responsible for failing .NET 3 updates, component removed in next version, gonna be replaced with .NET 3 later on. You can install all updates. Aero theme is there but you are mixing it with the Glass effect. vLite won't show a component if it's not detected, it is not static list. And for the last suggestion I agree, it should ask to recopy the source where to set the modified version. But that takes time, it should recopy the whole folder and modify it, somehow I think that it's you who should have done the backup, I always keep the full version on some other partition for fast retrieval. Btw if you spin up the drive it will copy much faster, it's some detail which I got to deal with eventually.

Extract i386\svcpack.in_ edit the svcpack.inf file and remove all double entries, they just copy it to the i386 folder, delete the old svcpack.in_ If you confirm double entries in the svcpack let me know, and if this is something common I'll release a fix.

Well I said select the root, but hopefully it will copy all. If it doesn't then you copy the whole dvd to some folder and then just point it to that folder.