Registered: Dec 2003
From:

Please Note:
I do not certify these to be bug free, problem free or even work on your system. These scripts are designed to make it easier to work with NSIS and I and Humgun International OX are 100% unresponsable for any problems that occur from their usage.

Anyway, end that disclaimer mumbo jumbo

I've designed these for in-house use and have released them to the public. They are NSIS Scripts and DOS Batch Files which make installers based on a template. The installer detects the install directory automaticly and sets it to that of NSIS.

THere are three shortcuts created, in the NSIS\Contrib foler in the start menu.

Each of them are self explanitary.


URL submitted by user.
URL submitted by user.

NOTES:
Users of Windows 95/98/ME will need to rename Make.cmd and MkNew.cmd to Make.bat and MkNew.bat respectively.

If there are any bugs please reply here or e-mail me

The code does not currently come with an uninstaller, but one is planned for 1.0.1.1.

Versioning system:

1.2.3.4

1 = Code base (If incremented code was fully re-written)

2 = Major Change (A large ammount of code has changed, addons\modifications will no longer work(

3 = Service Pack (Large upgrades to code)

4 = Build (Ammount of installer or software builds)

Attachment: humgun nsis template-1.0.0.2-setup.zip
This has been downloaded 356 time(s).

Last edited by HG-Owen on 12-24-2003 at 10:52 PM

Quick Link | Report this post to a moderator | IP: Logged

Registered: Dec 2003
From:

Code for the installer

Note: This is not built by the template due to complications with the creation of the uninstaller. All code was copied and modified.

Attachment: nsis_humguntemplate.nsi
This has been downloaded 350 time(s).

Quick Link | Report this post to a moderator | IP: Logged

Registered: Nov 2001
From:

SetOutPath "Contrib\HumgunTemplate"

You forgot to add $INSTDIR, the installation does not work.

Why not add your application to the NSIS Archive?

Quick Link | Report this post to a moderator | IP: Logged

Registered: Dec 2003
From:

Woops :-P

I'll fix that

Here comes 1.0.0.3 ;-)

Quick Link | Report this post to a moderator | IP: Logged

Registered: Dec 2003
From:

Version 1.0.0.3

ChangeLog:

INSTALLER
---------
Bug Fix: SetOutPath not correctly defined.

Attachment: humgun nsis template-1.0.0.3-setup.zip
This has been downloaded 317 time(s).

Quick Link | Report this post to a moderator | IP: Logged

Registered: Dec 2003
From:

1.0.0.3 Script:

Quick Link | Report this post to a moderator | IP: Logged

Registered: Dec 2003
From:

Woops... Forgot to attach

Attachment: nsis_humguntemplate.nsi
This has been downloaded 262 time(s).

Quick Link | Report this post to a moderator | IP: Logged

Registered: Dec 2003
From:

Service Pack 1 Released (1.0.SP1.1)

We have released Service Pack 1. Among other major setup changes, a bugfix was made to MkNew which now means that the installers build from Make. Before, a missing slash made them fail.

Source included in installer.

Attachment: humgun nsis template-1.0.sp1.1-setup.zip
This has been downloaded 322 time(s).

Quick Link | Report this post to a moderator | IP: Logged

Registered: Nov 2001
From:

I don't really see the use of all these different files and batch files.

If you want to provide a few macros and header files that can help other people, why not make one or two header files with good comments and a few examples?

Why did you add all these batch files that only write a few commands to a file? Why not a normal .nsi example?

About the NSIS Archive page: Please don't create new folders etc. that don't belong there. Full installer examples should be posted in the 'Real World Installers' folder, other examples in the 'Examples' folder. Header files and function belong in the 'Useful functions' folder.

Last edited by Joost Verburg on 12-24-2003 at 11:39 PM

Quick Link | Report this post to a moderator | IP: Logged

Registered: Dec 2003
From:

Aah... OK, I was actualy thinking it made a sub-folder at the time, but i'm now thinking of moving it.

As for the batch files, they automaticly output the base from which you work from. The program is designed to save the time it takes to specify the full MUI and other definitions. A one time configure, file addition, specifying name and version and then your ready. I'm using this in house and find it useful.

As for the multiple files, they made things easier for me.

Quick Link | Report this post to a moderator | IP: Logged