Topic: If Nlite and DriverPacks are giving you problems
I started out using nlite, and then RVM Integrator. Ryan's post SP2 update pack turned a long tedious job into a one click process. Still, I stayed true to nlite, using it to intigrate the RVM update pack and many addons.
The third step in this evolution was DriverPacks by Bâshrat the Sneaky. At this point, I discovered several conflicts between the driverpack finisher and nlite.... So I began wondering if nlite was really needed.
Nlite is a great app for easy and fast tweaks, removing components, creating a winnt.sif. etc. But, I have recently discovered all these things can be done by hand, and (of course) by using the RVM intigrator.... thus nlite (although faster) is expendable. The rvm intigrator works great, when used with REGTWEAKS
and the addons for REMOVING WINDOWS COMPONENTS. (Thanks, keytotime)
I then discovered that there was no need to write the winnt.sif by hand. By extracting XPCD\SUPPORT\TOOLS\DEPLOY.CAB, and deleting all files except deploy.chm and setupmgr.exe, you can run setupmgr.exe to create your winnt.sif.
Since I have stopped using Nlite, and use only RVM Integrator (and my reg tweaks added at cmdlines.txt,) no more issues with DriverPacks driverpacks, or other Nlite (commonly experienced) bugs.
NOTE: This post is not ment to slander Nlite..... it is a great app and usefull tool. This post is meant as a solution for those who experience problems when using nlite in conjunction with DriverPacks.
Last edited by ebin25 (2006-10-08 12:38:38)