SVCPACK.INF vs /INTEGRATE

[pucelle]

Also which hotfixes cannot use the /integrate switch, is it all the IE7 ones? Last time I made an unattended installation DVD I used a combination of nLite and some other tools, but this time I want to know what going on so I'm doing it manually and getting somewhat confused as to what should be installed where.

[Martin H]

The difference is that the /integrate switch actually slipstreams the updated binaries from the updates into the install-source, whereas using svcpack.inf, only integrates the update-installers into the install-source, and installs them at T-13. However, the /integrate switch is implemented pretty badly IMHO, since this method still also leaves all the update-installers into the install-source, and runs them at T-13, just to get the needed reg-entries and possible post-install commands. Another bad thing, is that if the outdated binaries in the install-source where cabbed, then the /integrate switch will leave the updated binaries uncabbed in the install-source.

nLite by default slipstreams the updated binaries directly without using the /integrate switch method, but not all updates are supported, and for those, then nLite either uses the /integrate switch, or lastly the svcpack.inf method.

There is also a cmd script named HFSLIP, which will slipstream the updated binaries directly, without integrating the installers and running them at T-13, and without leaving the updated binaries uncabbed in the install-source, and it supports more updates for direct integration than nLite does(atleast for win2k that is)...

Edited January 24, 2009 by Martin H