nuhi

Just posting to let you all know that I'll be checking this.

If the ones which you are integrating are WHQL you don't have to remove anything. If it repeats in the new version when it's out in the future let me know.

Hm, do you have another partition for testing or it cab be detected by the virtual installs? If yes then attach your preset and I could recommend what to try to keep.

Well done. BitLocker hopefully fixed in next one, Firewall and ICS are known issue for certain hotfixes which I'm trying to take care of (if anyone knows how to disable Firewall Rule applying let me know). System restore is solved, probably gonna keep that file by default. VSS leaves as the only mistery so far.

I doubt that vLite is the cause. Check if you are remembering from the 64bit and now using 32bit, or it's some of the hotfixes.

Deleting versions from the image won't save size, it just removes the allocation for the specific image preset which is represented as a Windows version, they all basically use the same files.

MrTijo, what did you expect, for it to run setup.exe or something? It will just integrate the basic driver. I integrate Intel and Nvidia drivers, they work as expected. Check the versions in the device manager, also if you are unsure how to properly integrate then tell us how you do it.

No it will not be smaller if you don't use Rebuild. It just adds new info to exclude files from the image on top of the old one. Does not influence the install, just the way how the files are read from the image.

Both Apply methods (Just save and Rebuild) contain the same files, it's just the first one contains the old image plus the extra bits while the rebuild overwrites the replaced or removes the removed ones. This doesn't influence the outcome, only the way how the image is written, transparent to the user.

Latest vLite version doesn't have this WMP issue, it may be something else. What did you remove?

mhyll, that's how MS does it, they keep old versions in the winsxs cache after you install/integrate a hotfix. It's beyond any logic except for the uninstalls, but who would want that after the OS install. Anyway I will be exploring an option to clean out the old files, they are annoying me as well. It is probably using only the newest, check the properties of the one in the system32.

This is why: http://www.msfn.org/board/index.php?showto...st&p=654386 You can do whatever you want after it split the first one to the desired size.

KnightCrawler1, what was the folder's total size of that dvd during splitting so that I can check? In the meantime since vlite does some optimizations to the ISO (double files written once) you ISO might be smaller than the specified, and all after the first one are smaller by design feel free to raise the targeted size until the first ISO hits the wanted mark.

KnightCrawler1, aa right, AIO, I forgot about that. UKSimon, fixed in next version, can't be manually fixed so please have patience.

Please attach your preset with which you made that disc (last session.ini on that CD). And you don't have to work that hard again, just load the preset. Other tools should have the presets as well, if not then next time backup the folder before every bigger step.

You can delete the pack since it's not so legal anymore to distribute hotfixes. Problem with lang packs and hotfixes is that it can fail from time to time on it's own and simple restart of the host machine helps and then it works. However if I find the time before the next release I'll try your full setup. Unless you try it before that and report that it works. In that case I will anyway make that integration reporting. Next version has even better hotfix cleanup on removals so it could prove better. For now you can simply use that only_integrated folder as your starting ground, no need to integrate every time from zero.

re*s.t.a.r.s.*2, you don't have to repeat it every time, I was talking to Leviathany2k (note to self: should have stated that).

KnightCrawler1, is that before or after the Apply window popup, do you click OK then that happens or even before, on the very Apply button click? Does the processing starts?

It is worth disabling it IMO. - no adware or virus will be stopped by it kept enabled, the authors already made their programs with SFC enabled in mind and they rarely replace the system files, they add similarly named files so that you think it's the genuine file, SFC can't help there. - DLL version conflicts are solved by every installer out there, it will keep the newest or popup the question while installing the program. Better yet nothing changes the system files except your hotfixes so why even mention this. - big annoyance if you want to change some file, like patched Uxtheme or TcpIp

I have tried your preset on the 1.4RC2 and it went fine. But I didn't insert your addons so the cause may be in them. So you could try the RC2 and if it doesn't help then try to see which addon it is, if you find which one was it I'll be glad to check and fix it. You can test it fast using virtual machines, no need to burn media or real installs for this.

Ok, those with the SFC error, try to get the Syssetup.inf from the full slipstreamed source but unedited, overwrite the one in the Windows\Inf that should help with the popups. Let me know if it does but be sure that you got the clean file suitable for your Windows version. Then I will automate it if some of you confirm. So far comecme confirmed. edit: PM me if you want the test version.

AgiHammerklau, I'll think about returning NetDDE, I have experienced freezing with other removals as well but every situation was because of something removed vs something kept that shouldn't. Meaning removed DTC and kept Com+, that would hang as well. korri, manually removed oembios files? comecme, yes. Gonna just put a popup that SFC disable is a must if you integrate IE7 unless we find a solution.

I did get this report few times, that nLite under vista errors out when you insert items in the hotfix page. Do you have any protection program installed, something Mcaffee, Symantec, Zonealarm...? Try uninstalling it, reboot then try. If you confirm then I go install the trial and test. But I was there before, didn't break for me, worth the try anyway.

Nothing can change your computer name without your consent, unless you put * for random name. It could be that your Windows have it integrated, OEM setting of some sort. Branding maybe.

Well it's now Lang pack, hotfixes and extras...that brings into question could it be MS mistake, because if you didn't remove anything vLite cannot be the guilty one. If you are using virtual machines please try just the lang pack, it should work because it did on my tests. One thing which may be worth mentioning, I see from your lang pack size that you use 64bit, mine was 32bit, so if your test of full windows with just lang pack integrated fails I will download and try the 64bit pack.