Optimize Windows Installation: PeaZip nLite Addon Step-by-Step
Creating a streamlined, unattended Windows installation allows you to strip away bloatware and pre-integrate your favorite essential tools. nLite is a classic deployment tool that lets you customize legacy Windows installation media by slipstreaming drivers, updates, and software directly into the setup process. By integrating PeaZip—a powerful, open-source file archiver—as an nLite addon, you ensure that high-performance compression utilities are ready to use the very first time your desktop boots.
This guide provides a comprehensive, step-by-step walkthrough to creating and integrating a custom PeaZip nLite addon into your optimized Windows installation source. Prerequisites and Tools Required
Before beginning the creation process, ensure you have the following components downloaded and organized in a dedicated workspace folder:
nLite Deployment Tool: Download and install the latest stable version of nLite.
Windows Source Files: A copy of your Windows installation disc (e.g., Windows XP or Windows Server 2003) copied to a folder on your hard drive.
PeaZip Installer: Download the official PeaZip Windows installer (the standard administrative .msi or silent executable .exe installer is preferred).
7-Zip or PeaZip: Installed on your current machine to compress the addon package.
An Addon Maker or Text Editor: Notepad or Notepad++ to write the configuration files. Step 1: Understand the nLite Addon Structure
An nLite addon is essentially a compressed archive (typically using .cab or .7z formats) that contains the application binaries or installer, along with an information configuration file. When nLite processes the addon, it reads this configuration file to understand how to silently install the software during the Windows text-mode or GUI-mode setup. The standard layout of an addon archive features:
A configuration file (usually named entries.ini or website.ini).
A subfolder (often named SVCPACK) containing the application installer executable. Step 2: Prepare the Silent Installer
For an application to install automatically without user intervention during Windows setup, it must support silent switches. Download the latest PeaZip installer.
Verify its silent installation parameters. For the standard PeaZip Inno Setup installer, the universal silent switches are /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-.
Rename the downloaded installer to something short and predictable, such as peazip_setup.exe. Step 3: Create the Configuration File (Entries.ini)
The entries.ini file instructs nLite where to place the installer and what command to execute during the installation phase. Open Notepad or your preferred text editor. Create a section called [Entries] to register the addon.
Create a section called [Svcpack] to list the executable and its silent switches.
Copy and paste the following template into your text editor:
[Sections] PeaZip.Registration [PeaZip.Registration] AddReg=PeaZip.Reg [PeaZip.Reg] HKLM,“SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce”,“PeaZip”,,“%%SystemRoot%%\System32\svcpack\peazip_setup.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-” [FileCabCopy] peazip_setup.exe Use code with caution.
Note: Alternatively, if you are utilizing the standard advanced inf structure, your entries.ini can simply point to a custom .inf file inside the archive that hooks directly into the Windows Svcpack architecture. Save the file strictly as entries.ini. Step 4: Package the Addon Archive
Now you need to bundle the configuration file and the installer into a single archive format that nLite can parse. Create a temporary folder named PeaZip_Addon. Inside PeaZip_Addon, create a subfolder named SVCPACK. Move your peazip_setup.exe into the SVCPACK folder.
Place your entries.ini file in the root of the PeaZip_Addon folder (alongside the SVCPACK folder, not inside it).
Highlight both the entries.ini file and the SVCPACK folder, right-click, and choose your archiving tool (PeaZip or 7-Zip).
Compress the selection into a 7z or CAB archive. Name the file clearly, for example: PeaZip_nLite_Addon_vX.X.7z. Step 5: Integrate the Addon via nLite
With your custom addon successfully compiled, it is time to inject it into your optimized Windows installation source. Launch nLite and click Next on the welcome screen.
Browse to the folder containing your copied Windows installation source files. nLite will detect the operating system version. Click Next.
Skip or load a previous session configuration on the Presets screen and click Next.
On the Task Selection screen, click to select Hotfixes, Addons and Update Packs and Bootable ISO. The buttons will turn green. Click Next.
On the “Hotfixes, Addons and Update Packs” insertion screen, click the Insert button at the bottom right.
Select Add from the context menu, browse to your local directory, and select your newly created PeaZip_nLite_Addon_vX.X.7z file.
The addon will populate in the list. Click Next to begin processing.
A prompt will ask if you want to start the integration process. Click Yes and allow nLite to compile the files into the Windows installation source. Step 6: Build and Test Your ISO
Once nLite completes the integration process, you will be advanced to the Bootable ISO creation screen.
Give your compilation a distinct Volume Label (e.g., WIN_XP_PEAZIP).
Click Make ISO and save the resulting .iso file to your computer.
Crucial Step: Before deploying this image to live hardware, test the ISO inside a virtual machine environment such as VirtualBox or VMware. Ensure the Windows installation runs completely unattended and verify that PeaZip is fully installed, configured, and present in the Program Files directory upon your first login.
By automating the addition of PeaZip through nLite, you cut out manual software deployment, leaving you with a clean, fast, and optimized environment ready for production right from the initial boot.
To ensure this guide fits your deployment pipeline perfectly, could you let me know which version of Windows you are targeting? If you run into any errors during setup, sharing the exact error message or behavior will help me troubleshoot the configuration for you.
Leave a Reply