NSIS 2.0 Final Released

nandhp writes "The NSIS (Nullsoft Scriptable Install System) project has finally released version 2.0 final. NSIS is a powerful open-source install system for Windows that is based on scripts. It was invented by Nullsoft for the distribution of WinAmp. You can get it here"

Yeah, SuperPIMPin!

[TheSHAD0W]

Just FYI, NSIS stands for the product's original name, the "Nullsoft Super-PIMP Install System", before AOL made them change it.

Re:"install scripts"

[Anonymous Coward]

Ever used a Mac?

You click the thing you want to download.

A few moments later a window appears with a single icon and maybe a readme. Drag the icon somewhere, double click it and it runs.

All libraries (DLLs), all run-time files, etc, are hidden inside that icon (because it's really a directory with a special flag set that conceals the contents).

Install scripts are left for system files, kernel drivers, non-app stuff.

Or at least, that's how it is supposed to work, a lot of software ported from Windows doesn't quite work that smoothly! :-)

Another free/open source installer

[aled]

I also used Inno setup [jrsoftware.org] with good results. It had some features that NSIS didn't and we switched to it. Very good so far. It is actively being developed.

Re:Details please

[aled]

It was more scriptable, it has a scripting language based on Pascal. Sorry I don't remember the details.

Second Life uses NSIS

[Critter92]

Second Life [secondlife.com] has been hapily using NSIS -- featuring Super-PIMP(tm) technology -- for 3 years. We played with just about all of the different installers and settled on NSIS because it generated by far the fastest installs and also created the smallest files. Throw in the fact that it was incredibly easy to use and you had a winner. We haven't switched over to 2.0, though.

Re:"install scripts"

[Chacham]

Seriously, why don't apps just look at their environment, fix whatever is missing, and not require any install script at all?

There are so many things involved in installation that makes your question one of sheer ignorance. Having worked at a Windows Installation software company, i'll mention a few.

1) DLLs. In order for a DLL to be properly used in a system it must be registered. If it uses OLE, it must be "self-registered". That is, the DLL itself has a subroutine called OLESelf-Register, and it must be called in order to work so the OLE system knows where it is. For a quick example, find ComDlg32.ocx on a system (System or System32 directory) and choose proeprties. On the Version tab, in the list, you will see OLESelfRegister. To selfregister it (it doesn't hurt) go to start run and type regsvr32 ComDlg32.ocx. A dialog box then reports success.

Common DLLs must be marked on the system as to how many program claim to use it. This is so it is deleted only after the very last program stops using it.

Since the DLLs must be placed in the system directory, and the Windows directory is not always known, a system call to get the Windows directory is required.

2) BDE. For those programs using the BDE, the installation process is under an NDA.

3) Uninstall. Creating an uninstall can be painful. An automated system is nice.

4) Installing ODBC. This takes various system calls to be done properly.

5) INI writes. If an INI file is used, the official way to write to it is with as system call. (So NT can divert it to the registry).

6) Temporary files. Creating a temporary files for the installation requires a unique name, and automatic deletion.

There's so much more it's amazing, A very simple project does not need much other than a folder copy (assuming the user can make his own shortcuts). Most programs need some knowledge of Windows, and there is no reason for the programmers to waste their time there.

Also, note, that a great deal of programmers are absolute morons. They having the slightest idea what to do. They can do VB, but when it comes to windows they haven't a clue. For them, an instllation system is a must.

Also, now, with Windows Installer, the installation file must be a specific format. An installation system can make that for you easily.

Re:"install scripts"

[Anonymous Coward]

Than why did iTunes have a version whose install script deleted your hard drive in some cases?

You wrote that backwards. What you should have said was, "Buggy install scripts are why we don't use them any more."

Somewhere? Oh, so you mean that you open your hard drive, find the applications folder, drag the icon in, and make an alias in the Dock.

Wow. You really haven't used a Mac. The "applications folder" is an icon in the window sidebar. You already have a window open, obviously, because you're looking at the program you want to install. All you do is drag the program icon to the Applications icon.

If you want to put the program in your dock, do. Point is, it's up to you. There's no annoying installer to put it there for you.

Thanks, but I'll take the Windows style.

Sure, 'cause ignorance is bliss.

Python scripting for NSIS...

[pschmied]

And now for something completely different.

It's...

Python scripting for NSIS. [hispeed.ch]

Seriously, there are times when these scripting systems can't do the heavy lifting of a "real" scripting language. I've often thought that Python might be an ideal embedded scripting language for an installer, especially with Mark Hammond's excellent Windows Extensions [python.net].

Has anyone used this NSIS/Python package? I suppose the only thing stopping me from trying at this point is my own laziness. Alas, this plugin requires that you track your own Python module dependencies.

-Peter