@nuhi

I'm curious about how nLite handles direct-integration of hotfixes, and so i would really appreciate if you would please answer two questions for me, then

During direct-integration of hotfixes in nLite, then the reg-entries gets imported from nlite.inf at T-12, but how exactly are you capturing them ?

I mean, are you on each new patch-tuesday then installing all the new hotfixes in a VM and then capture the added reg-entries and hardcode support for them into nLite, or do you manually retrieve the keys from the INF's of the hotfixes and then hardcode support fot them in nLite, or are nLite smart enough so that it parses the INF's for the 'addreg' sections of each hotfix automatically and then adds all the entries to nlite.inf ?

HFSLIP for instance, strips the INF's out from all the hotfixes and adds them to I386 and then installs all of them from T-13 to get the correct reg-entries, but i don't see a bunch of INF's in the source of an nLite processed folder, so some other method is obviously being used here instead, then.

Also, if nLite dosen't support direct-integration of a hotfix, then am i right in saying that it first tries to do '/integrate' on them(OK, using the '/integrate' switch is also "direct-integration", but as the *.exe's is still run and the hotfixed binaries is sitting uncabbed in I386, then i wouldn't call it a true direct-integration method), and then if that dosen't work, then it just manually places them in 'I386\SVCPACK\' and references them to be run at T-13 in svcpack.inf, right ?

Thank's in advance.

I would really appreciate if i could please get a reply to this, thank's

or are nLite smart enough so that it parses the INF's for the 'addreg' sections of each hotfix automatically and then adds all the entries to nlite.inf ?

Yup thats the one.

Thank you very much Kelsenellenelvian

Much appreciated mate