nuhi

Madhits45, how is it possible that that the line (movex syssbck ...) is missing from your nlite.inf? Maybe you think that I should know that but it simply seems not possible, even though I hope that's the case and we find out why. Do you (all with this issue of not having the restored file) run Windows by setup.exe (winnt32.exe) or use your own winnt.sif file or anything that would skip this portion? Because by just using nLite with it's Unattended options should be fine.

legolash2o, ok but why get pushy with those files, it's obvious not the reason for this problem. It's something removed I presume.

Ok then I'll download the Spanish lang file and try.

KB932596 is already fixed for the next version. Yeah I saw that USB thing, tried it and it semi-worked for me. Unattended didn't work. But it's probably my fault, there were some USB emulation options I tampered in the bios and I have USB drive, not a flash. It is a possibility as an option in the future.

They always edit some stuff in their OEM version. Sometimes people couldn't slipstream service pack until it was cleaned out of the integrated stuff they put in. It doesn't matter which driver inf you select, the whole folder will be integrated.

wondras, thanks. nLite should have done that on it's own, you can find the command in the nlite.inf. But this helps a lot because I didn't know that the function failed for some reason, at least it will be easier to debug now. Things which trigger syssetup patching are: - patches - component removal - ie7 integration - addons which edit syssetup.inf Btw nLite backups clean syssetup.dll to the syssbck.dll in the i386 folder, just extract that, it should be the clean version. If it's not then that is the problem, maybe you ran nlite more than once and it didn't detect the clean version properly on the second run. edit: tried it now with all removed and the backup was restored just fine. If someone finds out how to break this yell. Also check windows\setuperr.log for errors, maybe your nlite.inf never got executed if something else broke before it.

No, the problem wasn't with the driver or nLite, it was the Dell Windows. But I managed to bypass the issue. Out in a 7-10 days.

spick204, yeah I know it's not the retail version, otherwise you wouldn't have this issue. As I said it is already fixed in the next version, and when it will be out no one knows. I can predict in 10 days but could be sooner or later. Madhits45, then don't comment in a negative way on what you don't try.

There was some thread about the error when you run sp1 exe on the already installed Windows. The cause is still unknown to me but haven't got to it yet so don't dispare Ok so it's not the Firewall for that, k. Dr. Phil...man Google it

Fixed this weird error in the next version. It happened only on some special Windows version, I mean that single file was different than on mine or the majority of Windows out there. That's why this wasn't known before. Got this report 3 times so far. And it is fixed so don't worry you won't be sick of it any more. Madhits45, you're making no sense. nLite is most famous for it's textmode driver integration.

Current vLite can't integrate SP1, next one will (it's not just drop it in the hotfix page). It will work fine with the already integrated SP1. Version will not be correctly detected, fixed that too. If you integrate SP1 on your own then keep Windows Firewall or the setup will fail. Don't know yet about this post-install manual install, maybe it's the Firewall again, maybe more...anyway I'll be checking that. Let me know if you find more issues with the SP1 beta, Phil is listening.

People always reported SFC popup on hardware insert after integrating IE7. Rvm wasn't an issue. If you delete some component then especially. I hate that SFC issue...it's so weird and when nLite first started we all disabled SFC anyway, it's now the Integrate_only_users who want that fixed. And I would gladly fix if I knew where is the problem, what file is the one that confuses it. Gonna try a few things...but I don't believe that 1.3.5 don't have this issue if that is what you're telling me.

Integrating IE 7 will do that. Either disable SFC on the Options - Patches page or don't integrate IE.

Right on the Apply, not after the Apply during processing? Was the Log page shown with the progress or it fails before even seeing the 2 Apply options? I tried your preset and there was no error in my case.

Where is the preset? Also if you integrate KB932596 then don't until the next version, it breaks.

Only thing that's fixed regarding that is in the modem drivers it was removing bluetooth modem drivers too. So reinstall and keep that, see if that helps. There is that topic how to insert drivers back without reinstall, maaybe it will help, the needed index is "mdmbtmdm.inf"

Just run that EXE and it will create LP.CAB in the same folder, copy that aside and you can abort the EXE install. But then reboot your Windows before trying to integrate that cab.

I don't understand why do you even try it if you don't know what is it for? Just curious, no reason to get offended. Btw vLite is for Vista, nLite is for XP, I hope that answers your question.

Ok but when does it happen?

Is that EXE2Cab thing safe? Can you try just running that exe and the lp.cab should appear in the same folder after preparation, that is more safe IMO. Then after you copy it you can abort the exe and integrate the cab. If that fails too then attach your preset.

Try to delete all and try again from the original DVD/ISO.

Fixed in next version.

No point. Vista checks dynamically, and it is right with what it requires. Don't forget to count temporary files during install and the pagefile.

Yes I have noticed this too once, gonna follow your instructions and fix, thx.

How can I know. It depends if there is something to fix. What are those severe issues?