Paquet Builder 2.6
Packaging installation programs can be a difficult and
expensive business. Leading solutions like InstallSHIELD have
a long history in the market and can meet just about any
functional requirement. But at a price. And if you simply want
to distribute file archives, you can always plump for WinZip.
Well now there is something between the two, Paquet Builder,
which – if you think about it – makes it perfectly
positioned in the market.
Paquet Builder allows you to quickly and easily package up
data, documents or program files and to distribute your
software, demos and updates.
Similar to WinZip, you can create file archives. You can
specify that files be compressed either in standard zip format
(devised by PKWare, and the most common compression method in
use) or Cabinet (.cab) compression (the LZX technology
designed by Microsoft). All the functions you would see in
WinZip (such as full path support, password protection, etc.)
are there, and you can turn your archives into self-extracting
executables. The real strength of Paquet, though, is its
ability to create professional setups for software
installations.
Paquet Builder provides you with a rich variety of options
for controlling your installation files, accessible through a
highly intuitive interface. Outlook-style groups of buttons
are arranged down the left-hand side of the window, which walk
you through the whole process, start to finish. Adding files
to your package couldn't be easier. An Explorer-style facility
allows you to add multiple files and entire folders (using
wildcards, if you wish) or subfolders. You can also drag and
drop files from Windows Explorer. If you prefer, you can load
existing Cabinet and Zip archives to your package.
Using Resource Strings allows you to build international
packages. You can customize all end user messages (error and
warning messages, dialog boxes buttons, texts and captions,
etc.) with the resource strings (you can also import strings
from external language files).
Critical to the professional user, Paquet Builder gives you
the ability to work with variables to store data, return
standard information, read and write to the Windows Registry,
etc. Your finished setups can create Windows shortcuts,
execute multiple programs, display message boxes and read-me
texts, prompt the end user for information, such as the
destination folder. Or you could read the destination path
from the Windows Registry. Even more advanced functions are
supported, such as registering ActiveX controls, executing
multiple setup programs and removing all temporary files.
There is also support for Windows INF Setups: Paquet Builder
provides you with an expert which will automatically configure
your setup project for executing a Windows INF Setup instead
of a traditional setup program.
GDG has thought to include nice touches in Paquet Builder
which you would expect from full-blown installation packagers.
You can specify your own custom icon (.ico file) for your
package, or select from a set of icons shipped with the
package. You can also specify that end users are prompted to
enter a single password for continued extraction, a trial
expiration date and even a final size check, to verify
downloads (archive truncated) or test for unwanted external
modifications.
At any point, you can specify that a document be opened or
a program executed, and you can display the destination folder
in a shell window after extracting files or load a web page
after a successful extraction for, say, online registration.
You can also work with the predefined system folders like
Windows and Fonts folders.
You have full control over you installation package's
appearance, with window controls and a progress meter
including a standard (but customizable) animation. You can
also display unlimited "Read Me" or License Agreements at any
time in Rich Text Format. As a nice touch, Paquet Builder even
includes a built-in RTF editor for creating your texts
directly.
Should anything go wrong during installation, you can
specify that your company name and an email address is
displayed in the eventuality of a fatal error
Finally, and importantly, you can add an uninstall engine
to your installation packages. End users can remove the
entries from the Registry and the files your packages
extracted, although it will not interfere with any new folders
or files added post-installation. | 
