John,
When I initially submitted the wizard to Pelle I naturally packaged the project and wizard executable in a poinst created deployment.
Pelle's firewall blocked the submission so I repackaged everything in a zip.
If one were to simply extract the setup and run it, then the wizard install would present the GPL (with special exception for the scripts generated, that I copied from BCX - thanks mrBCX), an information file, and would present the user with the choice of installing the wizard, the source code, or both.
As a bonus, if the wizard and source code are installed in the default location one could extract the POINST Wizard Project file "POINST Wizard.pwp" load this file into the wizard and use it as a demo to create another deployment of the POINST Wizard!
Using SetupPOINSTWizard.exe will not create an uninstaller, modify the registry, or hide files on your system outside of the installation directory.
Here is an excerpt from my original email of this submission to Pelle:
Here is something I wish POIDE had when I put together my first deployment using poinst.exe.
The POINST Wizard is a tool for quickly creating poinst scripts based on menu selections and a drag-n-drop tree structure for organizing files into installation sections.
Wizard configurations can be saved into project files and recalled later.
poinst scripts can be saved as is, modified, or compiled on the fly into an installer.
The zip contains:
Folder: Images - images for Readme.html
Folder: Projects - the project used to build POINSTWizard installer
Folder: ScriptFiles - the poinst script used to build POINSTWizard installer
Folder: Source - the POINST Wizard open source
File: POINST Wizard readme.html - an html help file
File: poinstWizard.exe - the wizard
File: SetupPOINSTWizard.exe - a setup that could be posted in the source code section
