I think you could even use its .dll version which is only 100 kb. http://sunsite.cnlab-switch.ch/ftp/.../unz551dN.zip. If you want to be easier choose the .exe version.

Uploaded new build v0.11

Includes new Zip-To-SE program (works a beauty!)
Complete SE file-system has been changed (new Bin folder).

The Self-Extractor will ask you to remove the old extraction before allowing you to continue, so remember to backup any non-SE files that may exist.

-Stu

Added VersionInfo to build 0.11, plus a few code additions to Zip-To-SE.

-Stu

I have uploaded a new build. The dialogue has had some major changes:
http://myweb.tiscali.co.uk/imker/dow...-extractor.png

Now includes a heading text which has customisable color, bold/unbold. Also custom function defines added.
Script-Generator has also been updated.

-Stu

I think the appearance could be better:

- I don't think the "Please enter a directory ..." setence should be with the "Extract to:" label. You should remove one of them.

- Before "Extract to:" was above the textbox text height, now it's below! You should make it to be in the same height of the textbox text height.

- Putting the "Please enter a directory..." in bold doesn't make your program looking better in my opinion. I think that's because the first setence is near title of the program which is bold too.

- This is a very old thing: the ProgressBar and the text on the side positions. ProgressBar should be below the text (you could make the ProgressBar smaller too if you want). This would make the text to have much more space and would make it not to break lines so often.

The "Please enter a directory ..." text is customisable. Like I said, you can use ${SE-ExtractDirTextUnbold}, and set the actual text to whatever you like.

I will make it unbold default, so instead of ${SE-ExtractDirTextUnbold}, one would have to use ${SE-ExtractDirTextBold} (to make it bold again)

Good idea on the progress bar :) Currently the progress text is really jumbled up, and when two lines get in it looks messy.

I'll make the directory box 100% width (without the extract to text) and see what it looks like (with LR padding too of course!) The new text makes the Extract to text redundant now.

I will make the progressbar thinner, stretch out the white area at the bottom and move the progress text label to 100% width over the top.

I may also make the spacing under the two checkboxes bigger too (which will make it more spaced out).

-Stu

Ok, updated to 0.13 (download from same URL)

Included some more changes to the dialogue... looks much nicer - thanks diguix!

-Stu

Write deguix next time. Who says that is my mother when she tries to understand what I'm doing on the computer the whole day (tries but she doesn't understand anything). ;)

Talking about the Self-Extractor:

WOW, what a great dialog design now. About the bottom part text and ProgressBar positions, they are like they were measured with ruler...

Another new build
 

Uploaded 0.14 (same link!)

Fixed some major bugs in the Make-Script utility.
Changed ${SE-Readme} syntax. Readme's must now be compressed manually with ${SE-File}

-Stu

can please tell me how to delete specific files from specific dir and how to move files from one dir to another

Delete "C:\Dir\File.ext"

Rename "C:\DirSrc\File.ext" "C:\DirDest\File.ext"

Password
 

hi!

Is there any possibility to ask for a decompression password?

Re: Password
 

This would require a InstallOptions dialogue to be created. You'd be better off incorporating it into the default NSIS system (classic/MUI). See Contrib\InstallOptions.

-Stu

But come to think of it, that would be a cool little feature to have for a Self-Extractor. I use my Self-Exractor to distribute programs and game content for testing. A password would be ideal just in case it got into the wrong hands! I may work on this tomorrow :)

-Stu

Ok, password support added (v0.15).
http://nsis.sourceforge.net/archive/...b.php?page=589

-Stu

Password test fails
 

Hi!

Thank for your update.

1. I am sorry but I have troubles to use it.
Following error occurs, when I start my simple test script testself.nsi starting makensis:

..\..\makensis testself


File: "dlg_rm+ow.ini"->"$PLUGINSDIR\dlg" 375 bytes
File: "C:\Programme\NSIS\Contrib\Self-Extractor\Bin\dlg_pass.ini" -> no files fo
und.
Usage: File [/nonfatal] [/a] ([/r] filespec [...]|/oname=outfile one_file_only)
Error in macro SE_FILES_START on macroline 274
Error in script "testself.nsi" on line 23 -- aborting creation process

If I am diabling the line :

${SE-Password} "rocky"

it's working properly.

2. Question: Is it possible to start an exe file after decompressing(e.g. setup.exe )?

Ah that was my fault sorry. I accidentally left out the dlg_pass.ini file from the download!

Added now:
http://nsis.sourceforge.net/archive/...b.php?page=589

-Stu

Starting setup.exe afterwards
 

Hi!

Thank you for the password extension.
Excellent work!

It would be helpful to another function implemented, like it works in Winzip self extractor.

It's like the readme function, but

1. There should be a info text with an enabled button.
e.g. When done decompression starting: setup.exe

2. This action should start a program (e.g. setup.exe) as last thread after decompressing. Before it is started the main dialogue must be finsihed.

I can do it with the readme function, but the decompression main dialogue is not diappearing before starting the readme.

Your feature request has been added. I ended up re-coding the whole check-box system, so now you can have two check-boxes in any order you like and by any combination.

Re-did the readme file too. Check out Section 4 of the readme for the below which you need to use:

${SE-Exec} "$INSTDIR\app.exe" "Run app.exe when complete"
${SE-ExecOnClose}

-Stu

Exec Run
 

HI!

I have checked out, but I had some problems.

1. If I am using the password feature the text is wrong:

Please enter a directory to extract my Mytest files to.

2. If I am using the ${SE-Exec} feature it does only accept one parameter :

!insertmacro: end of SE_README
!insertmacro: SE_EXEC
!insertmacro: macro "SE_EXEC" requires 1 parameter(s), passed 2!
Error in script "examplepw.nsi" on line 16 -- aborting creation process

3. If I am using the exec feature with one parameter, then it's not working and as text "$TEXT" is shown.

Oops. I will check them out!

Edit: Fixed
http://myweb.tiscali.co.uk/imker/dow...-Extractor.exe

-Stu

SE-ExecOnClose
 

Hi!

Thank you.

Sorry, but I found another problem.

If I am using ${SE-ExecOnClose} the Exec Program is not started. If I am disabling ${SE-ExecOnClose} it works properply.

Another comment. If I am setting also The readme option, the check box for the exec program is not available.

I was unable to reproduce your second problem. I can have both the readme and the Exec check-boxes in any order without a problem.

I have fixed the problem with ${SE-ExecOnClose}
I've also added ${SE-AutoClose} which makes the Self-Extractor automatically close itself when finished.

Download from same URL above.

-Stu

SE-ExecOnClose is ok
 

hi!

Thank you. Now it's ok.

Regarding second problem. It seems that only 2 check boxes can be active. So I can't add ${SE-OverwritePrompt}, when ${SE-Readme} and ${SE-OverwritePrompt} are inserted.
But that's really a problem.

I will add a feature to allow for this.

-Stu

I've added the new feature and I've changed a few of the setting names.

Use ${SE-ForceOverwritePrompt} (see Section 5 for more info).
See Section 4 for the new Check-Box setting names.
e.g. ${SE-Readme} is now ${SE-ReadmeCheckBox) and so on...]

(Same download link as before)

-Stu

New build available from same link (v0.18).

Fixed a bug if files contained spaces (macro label problem).

Added Dir-To-SE program which converts one or more directories into a NSIS Self-Extractor.

-Stu

Maybe you could put the automatic detection of the NSIS folder on your example. I have NSIS in a totally different location than $PROGRAMFILES\NSIS.

I'll do that tonight :)

-Stu

New build available. I fixed some bugs with Dir-To-SE.

-Stu

This is a very cool util - my first experience with an installer of any kind. I did have a few problems when installing a shortcut using a script created by the script generator (which is also very cool)...

This is what was generated and didn't work:
;- Shortcuts to create
${SE-ShortcutsStart}
${SE-Shortcut} "$DESKTOP\Glow Fish 2.lnk" "$INSTDIR\glowfish2.exe"
${SE-ShortcutsEnd}


I found that changing the middle line to include the middle (2nd) field *did* work:
;- Shortcuts to create
${SE-ShortcutsStart}
${SE-Shortcut} "$DESKTOP" "Glow Fish 2" "$INSTDIR\glowfish.exe"
${SE-ShortcutsEnd}

I also had to change "$DESKTOP\Glow Fish 2.lnk" to "$DESKTOP" since the first created an error when the script tried to install the icon at "$DESKTOP\Glow Fish 2.lnk\Glow Fish 2.lnk"

The icon on the desktop also was not the one that I specified using ${SE-Icon}, but was instead the icon that appears with the original .exe file (the one specified with "$INSTDIR\glowfish.exe"

any ideas on the whys, and what can be done?
Thanks!

I'll have a look tonight. It has been a while since I did anything to the ${SE-Shortcut} code. I'll add another field to the ${SE-Shortcut} command perhaps which specifies the icon path to use (or "" to specify default).

I may have used ${SE-Shortcut} simply to keep in with the ${SE-[Command]} syntax style, so you could try using CreateShortcut as a complete replacement. See http://nsis.sourceforge.net/Docs/Chapter4.html#4.9.3.4

-Stu

Uploaded SE v0.20
${SE-Shortcut} now takes the exact same syntax as NSIS's default CreateShortcut command.
Example.nsi now has some ${SE-Shortcut}'s in it.

-Stu

Thanks, Stu :-)
The script compiles and executes properly now with the fields as they are generated using v0.20

My desktop is still not getting the icon that is specified with ${SE-Icon}, and is still getting the icon that appears with the original .exe file

Maybe this is how it's supposed to work? If so, maybe there's a workaround? I'm still new at this ;-)
Thanks for your time.

You'll have to store your .ico file in the Self-Extractor and extract it to $INSTDIR.

code:
 ${SE-OutPath} "$INSTDIR"

  ${SE-File} "icon.ico"

Your shortcut would now be like this:

code:
  ${SE-Shortcut} "$DESKTOP\shortcut.lnk" "$INSTDIR\file.exe" "" "$INSTDIR\icon.ico"

-Stu

Would it also be possible to REMOVE the temporary extraction folder after running the (forced) exe after extracting?

Perhaps there should be a routine, which checks, if the process is still running.

Would be a very nice feature.
Do you understand, what I mean?

To do something like that, you could put some custom code at the bottom of ${SE-FilesStart} (just before ${SE-FilesEnd})...

${SE-OutPath} "$INSTDIR\TempFolder"
${SE-File} "app.exe"
ExecWait "$INSTDIR\TempFolder\app.exe"
RMDir /r "$INSTDIR\TempFolder"

-Stu

oh okay - ExecWait seems logical! thanks

does this also work for "Zip-To-SE"?

I shall add some functionality to allow you to do this.

-Stu