nuhi

Yeah standard ACPI issue, not related to vLite but I'm glad you found the solution.

Kaneda, does that happens when you run IE on that OS installed or during integration? I presume it's the first case, then it could be that you integrate some hotfixes which are for IE6, it's probably the case since there are so many of them. Try it virtual in Virtual PC for example with just IE7 added, if it fails please attach that preset. If it works then start adding hotfixes ABOVE IE7 unless they are IE7 hotfixes then BELOW IE7 installer. Ok? There are plenty of sites explaining which hotfix is for what. Usually it's enough to move them above IE7 but lets play safe. I know you tried with IE7 on the bottom and usually that should have worked but I would never recommend integrating obsolete (IE6) hotfix if you integrate IE7 anyway. Btw nLite doesn't support Directx installer integration as far as I know, you must have got a few warnings during integration?

It's ok. This bug is located and fixed thanks to your SP tip, just waiting for confirmations. But you know that already edit: Version with the fix released, v1.4.1.

There is a difference. Just try to delete some of the dlls of the disabled service, most of them are still used. Maybe not actively running which is good, but still parts can be loaded and locked. I don't feel good knowing that Remote Registry service disabled or not is in my OS.

Gorki and mitsukai, I only saw that in Vista with Firefox and it went away virtually on it's own, probably not nLite's fault in your case either, could be some of the hotfixes? Anyway keep me updated and if you confirm how to reproduce the issue with just nLite used let me know and I'll gladly try it. You can make sure in virtual machine very easily. acex, attach your preset please.

No it won't. Today managed to provoke this in Win2k with SP5.1, reason is SFCFILES.DL_ file. You can overwrite it with the one from 1.3.5 if you can't wait. I'm fixing it of course. edit: Fixed for 1.4.1 version.

There are plenty of guides on MSFN to be able to simply add few lines into that XML with Notepad and be done with it.

I'll try that SP and report. So "Last Session" without the date is the latest used, those with the date are backups from previous sessions. edit: Yeah that SP did it. Cause is in the sfcfiles.dl_, fixing.

I remove all (except IE and Aero) and Photoshop CS3 install works fine. Be sure to use CS3 in Vista. Oh and try to keep Application Experience component if you removed it.

Didn't I already answer that, read #1 in my last post. Btw I think that the fact of you using SP 5.1 is crucial for this, can you explain in short how can I do the same?

hubutz, also read descriptions and be very careful with the "Hardware Support" branch. If you are not sure then keep it, you can again reinstall in a few months with more removed once you see what you do not need and use the newer version. Or take a backup image of your full install, put it aside and play with lite configs all you want, once you see what you need write it down and reinstall or simply return your full one until you are in the mood for reinstall.

If you used Direct Burn it's the same as making ISO and burning it, just more convenient. If you burned just files with Nero or something then it will not be bootable. Anyway if it's the first one then try that oscdimg. heh da to se cesto desi, ja sam ti jedini na ovom projektu, ako ne kontas ogromnu pomoc koju dobijem od svukud prilikom testiranja ili trazenja bugova.

Hm. Try to run vLite with /unwim switch. When it prompts that it uninstalled or asks for reboot then reboot it. After it run vLite again and install Wim. Maybe that helps but it's a far fetch. Is that retail Vista or some Recovery version?

It's the ISO creation issue when it rarely doesn't work for someone or the media was burned too fast. Use RW media so that you can test few times without any loss. Try MS tool, oscdimg to create ISO, then you can burn it with vLite. http://www.google.com/search?hl=en&as_...img&spell=1

That means that the data is invalid. Please recopy those installation files again from a DVD or ISO into a new folder and try there.

Sorry for the delay, just found this in my bookmarks. Try by not using Network Tweaks and don't remove Hotfix Catalog files.

1. "Last session" is what it says it is, the one with the date is previous one so that you have a backup of it, better than overwriting. 2. Presets - Load that page should work, but edit with notepad that file (in nlite\presets folder) and see if it actually has anything in it regarding to that page. If it's hotfixes or drivers and they are not in the place where the preset first saved them then they won't be readded. Presets - Load is for that page only, if you want to load all pages then double-click on the Presets page. 3. Make sure that the Load last session on Startup option on Presets page is selected and that you actually have last session on the list. If you don't then import it. Last 11 posts are not related to the bug, can we get back on the track.

Just to tell to others that we're still not sure if it actually helped because you removed the WMP hotfixes which were not necessary with that addon (or are they?) or the version itself. Btw mixing those Mediahotfixes with that German addon is a disaster in it self, this is a good info for others as well.

Yeah then I'll keep that one by default in the future. If you're remaking ISO before new version then add Windows\SysWOW64\winscard.dll into components - protect files If you're copying manually from full then copy from syswow64 to syswow64, not system32, it's already in that one.

Shell Services.

Oh ok, in that case next time copy the CD manually using the explorer to your HDD and then browse with nLite to that folder.

Try 1.3.5 with that installation, and if it works better than 1.4 I sent you then report. With whatever you want but write it down how to mimic the situation if 1.4 breaks.

Try to extract them with 7zip (after installing it you can right-click exe and choose where to extract). If it doesn't give any reasonable folders which to integrate once extracted then try running it, do not press next and explore your temp folders for driver files which may be it. If that also doesn't help then try to catch the drivers with one of the driver extracting tools by running it from the OS in which that driver is installed.

That nLite installer is smaller because it doesn't include translated language files. Don't know how to explain that more clear, download public 1.4 selfextracting, extract them both and compare. If by that DX9 integration you mean you used HFSlip then please delay that during bug testing. Also you gotta be careful to integrate before or after nLite. DX is integrated after nLite to be safe that some line isn't deleted while cleaning components, or if you use addon version then simply insert it into nLite.

Lets backup a little, what is 1MB smaller? I thought you're saying about the nLite package. That DX9, was it an addon or installer from MS site, if it's installer then nLite doesn't support that. Try HFSlip, search msfn for it.