nuhi

Thx gonna check that. Also to anyone see if this helps: http://www.msfn.org/board/index.php?s=&amp...st&p=733096

Innocent Devil, ok, as I said only clg file was left so please let me know if it's not true in your case, if you find any forth file in your Sources folder after rebuilding let me know, thx. Gonna remove that one as well for the next beta test.

The news kinda gets warped out as it gets passed page by page. First of all it's not 15GB but 13GB (Vista Ultimate) Then I saw on Inquirer that the vLite was downloaded 50 000 times and that is just the Suggestion Box visit count. It was downloaded way more. Anyway at least they spread the word, we'll have to endure the bad comments, there will always be those no matter the tool or the news.

Arneh, yeah it would work, had that one in todo for quite some time but the fear of messing it up and then person can't boot that OS kinda keeps me away from the idea. It's easy for us to test virtually but when it comes to annoyance-ultra when one can't boot the system... Or I should go by the comfort of thinking that they usually have Restore CD or they can backup before tampering with it,hmm?

Innocent Devil, which files are you referring to and in which scenario? What I want to say is that if you select Manual Install for removal it will remove all except install.wim, boot.wim and because I'm not sure for what it is exactly 'install_Windows Vista ULTIMATE.clg' (it leaves only the selected version).

phkninja, I tried integrating IE7 on Sp3 and it works fine. But be sure to do it after the SP3 slipstream of course. legolash2o, is that confirmed that the Sp3 slipstream will detect IE7 or we are here talking about live install only?

Can't confirm that, it works fine here. Maybe you removed Security Center then the SP install fails (fixed for next version) and the SFC Disable reg key wasn't applied?

RPG, sometimes people get confused with that select thing and more and more I think about changing that, here is some explanation why is it like that: "Since not all components are supported to avoid confusions like 'will the component X be installed if it's not listed' and because removed components can not be returned." It is selected size, meaning how much will be removed.

You can do that in unattended (autounattend.xml), but I don't have the specifics here, do you want me to move this topic to the more appropriate forum?

I integrate .net 2 and 3 sp1 fixes because they are MSU type but whole 3.5, doubtful. No, SP1 needs full Vista. Update, capture, configure, reinstall.

Gonna just say explore imagex capture and WAIK WinPE, maybe it's possible.

vLite will warn you if you are to remove something that breaks kept components so go crazy, remove whatever you want, read descriptions carefully, especially red ones.

Not true. Maybe you confuse autorun with boot.

Good, thx back at ya'

Thx. Probable fix: paste Windows\SysWOW64\naturallanguage6.dll into the Protect Files (found on the components page toolbar) Or extract it from the full image with 7zip or something into the live install. Let me know if it helps.

Don't forget nLite was 4 years ago when our machines were a lot slower. It was same feeling to me like vLite is today. But yeah you are right to some extent, 13GB for 64bit Vista is not even funny.

My my...this is starting to get weird. I mean nLite has even more options but only thing for which it was recognized was slipstreaming and driver integration. While vLite is for removals? I guess Vista IS that big...

I presume it's the Natural Language again, because when I was fixing it I was testing the Windows Search which is 64bit, and in 32bit it's the same fix. Only 32bit inside 64bit (wow64) wasn't tested. If some of you wants to confirm keep the Natural Language and let me know.

Ok, that should be easy to fix, thx.

djt, I was just referring to the note on that MS KB page as one of the causes: "The computer uses a storage system that is running the Storport miniport driver." Meaning it might be even connected to the HDD controller. So if you remove the driver and use just the default IDE driver (if properly set in Bios SATA IDE), also possibly use the new driver when prompted if no drives detected, it might help. Since yours is RAID then it definitely won't work as IDE but you might try to remove all Storage Controllers, copy your newest Nvidia raid driver into some folder inside the ISO and try it when prompted because no drives will be detected. advocate_hf, can you please elaborate, what helped you and on which Vista?

Yeah just saw it, great. vLite and SP1 will increase Vista sales. MS should donate to Dino, I think

Also see that you have enough free space on the partition where the Temp folder is and on the one where Vista image is located just in case.

Problem is that even when hotfixes are normally integrated they are only active after install. Setup is just a tiny temporary Windows. More info on the hotfix: http://support.microsoft.com/kb/929777 Talking about the fix for the fix in vLite; unfortunately it was confirmed few times that the fix does not help in the x64 versions, just x86. If the cause is storage driver, maybe removing Drivers - Storage Controllers - nVidia and setting SATA in BIOS to IDE mode would help. And copy new nForce SATA drivers in some folder before making ISO so that you can browse to it if needed to detect partitions on boot. This is just a wild guess but it's worth trying, it would be interesting to rule that one out.

babrali, you can search for *.CAB files inside the: C:\Windows\SoftwareDistribution And the ones which look like hotfixes copy them aside into one folder from which you can insert them.

Just .net 2. IE Core when removed only issue related to nLite is that selfextracting installer has a startup lag.