WPI, nLite and RVM Addons [AddOn] nLite AddOn Maker v1.2.4 Sign in to follow this. Followers 1 [AddOn] nLite AddOn Maker v1.2.4. With Add-On Maker for nLite. Create your Add-Ons for nLite and customize the installation of your Windows. NLite Add-On Maker helps you to add programs to windows installation in order to install them in the moment of installing windows. Instructions: 1. Aug 27, 2012 [AddOn] nLite AddOn Maker v1.2.4 Sign in to follow this. Followers 1 [AddOn] nLite AddOn Maker v1.2.4. By ricktendo, July 8, 2007 in WPI, nLite and RVM Addons.
Ultraware 1.63 more. Here is the quick explanation of the supported entries.ini values which you can use to make your own addons for nLite. I will just list them all with brief explanations so that those who have previous experience can use the new functions.
Going to update this page later on with more detailed info. NLite v1.4.9 and newer: • (uncheck or warn about the needed component) • (protect needed files from removal) nLite v1.4 and newer: • (update a cab file) • strings (same as [filenames], for%var%) • (add a new directive in the specified file e.g. Supported variables: builddate description language title version website Supported switches: forcelang flags=IgnoreFileVersions Example: [General] builddate= description=RyanVM's Post-SP2 Update Pack for Windows XP language=English title=RyanVM Update Pack version=2.1.5a website=forcelang=English First variables are more or less selfexplanatory and are used only for displaying purposes.
Variables, first flags, it is the new line which for now has only the IgnoreFileVersions variable which is needed for packs which overwrites some existing file and has lower version. So by using IgnoreFileVersions you are telling nLite to not skip virtually older files. Forcelang will instruct nLite to allow only specific Windows language version for this addon to be used on.
[SetupData] CatalogSubDir=' i386 SERVICE' and rename your svcpack dir to service, then your svcpack dir is now service and all hotfixes, stuff created with addon maker etc go in services not svcpack. Svcpack.inf still has to be called svcpack.inf so that's ok, but it would be good to have an option in which you can set the svcpack dir in the cab if you've changed it so you don't have to change the folder in the cab. Still not clear, but that's as simple as I can explain it.
Edited June 22, 2006 by T D. [SetupData] CatalogSubDir=' i386 SERVICE' and rename your svcpack dir to service, then your svcpack dir is now service and all hotfixes, stuff created with addon maker etc go in services not svcpack.