NSIS Self-Extractor kit

v0.21e

Added ${SE-ExtractDirRO}
Makes the extract directory path box read-only; stopping the user from changing the extraction directory path.

Make-List utility added
Generates a list of files in a directory.

-Stu

Thanks

Afrow UK Thanks a lot it is really good.

Deepesh AGarwal,

password security

Hi!

I am concerned about the securcity of the password protection. Is the exe being encrypted with a standard system( Aes, ...)?

The exe is not encrypted. I don't know how I'd encrypt it even without modifying and recompling NSIS's source?

I will be adding a ${SE-AddDir} macro which will add a whole directory (with overwrite check-box support.)

-Stu

New version is available with ${SE-AddDir} and ${SE-ShortcutCheckBox}

-Stu

Bug in SE_FILE macro.
Labels don't work if OUTFILE contains spaces.

This bug wasn't there in v0.21e

Ah thanks. I will fix it tonight.

Edit: Fixed

-Stu

Theres a very minor bug (if it even is a bug) in the ui, when you use custon windows color schemes. Check the attachment. The area around the "branding text", is different in colour.

And also some /solid switch drama. 😉

Hello there, thanks for the bug report.
Try the updated version that I have uploaded.


-Stu

Nope! No luck, still the same. I think you have to remove the SS_WHITERECT flag from that static.

Try now.

-Stu

Sorry, don't work. I din't see any change I see except there are dlg_original.exe (Resource Hacker leftovers I guess) in the package, but the SS_WHITERECT was still there in dlg.exe.

Woops my mistake I had the dlg.exe set to read only.
Try now.

-Stu

👍 Ok now the UI is OK, but you still need to add...

GetDlgItem $R1 $R0 10
SetCtlColors $R1 0 FFFFFF

...To the ReadSettings function. 🙂

Are you sure?
ReadSettings only gets the states of the check boxes.

GetDlgItem $R0 $HWNDPARENT 10
SetCtlColors $R0 0 FFFFFF
...is already in .onGUIInit where it needs to be because the control in question is on the outer (parent) dialog.

-Stu

Well see your self. Happens also in XP.

The installfiles dialog also haves a 10 control and apparently installfiles dialog overlays the 10 control in the main dialog, because it's bigger that the other dialogs. I tryed first just to remove that control from the installfiles dialog, but that didn't work.

Edit: Is it just me or is this starting to get a little bit boring?

Yes very tedious! The problem is that I haven't opened the source file for over a year!
I'll have another look.

Edit: Fixed now.

-Stu

Now It works

👍 Yeah the source is a bit overwhelming, but now It works.

two questions :

1. i use ${SE-ForceExec} "setup.exe". the compiler tells me :
"SE_FORCEEXEC" requires 2 parameter(s), passed 1!"
in your readme file there is only one parameter.
what do i enter for the second one ?

2. it is posible to begin extraction on extractor initialisation ? without pressing on "extract".

thanks.

1. I'll have a look when I get home.
2. In other words you don't want a directory page (and no check-boxes)?

-Stu

i want the window, but i want the extraction to begin automaticaly (in some cases).

OJi.

In ${SE-ForceExec} first parameter is the file and the second is open mode action ("open", "print"...) it also can be an empty string to use the default action.

So ${SE-ForceExec} "setup.exe" "" should work just fine.

Look also the ExecShell function in NSIS manual.

Thanks {_trueparuex^}, even I had forgotton what the last parameter was for! I've updated the readme (and changed that ugly colour scheme!)
So you would like to skip the page sometimes or show the page for X seconds before performing the extraction?

-Stu

i do not know how to explain this in english. i want the page to appear. not skip it. but i want the extraction to begin automaticaly. not to press on extract !
so, the user double-clicks on the .exe, the window shows up and it extracts already.
something like the downloaded nero burning does.

OJi.

The thing I don't understand is how can the user change the extraction location or other options when the extraction has already started?

-Stu

I think that o_owd don't know that the extractor actually haves two pages. So there might be misunderstanding about skiping the page.

o_owd the first page is where you set the directory, options and press the extract button and the second page is the one where the progressbar moves and the options and directory field is disabled. Do you want to skip the first page?

Originally posted by {_trueparuex^}
I think that o_owd don't know that the extractor actually haves two pages. So there might be misunderstanding about skiping the page.

o_owd the first page is where you set the directory, options and press the extract button and the second page is the one where the progressbar moves and the options and directory field is disabled. Do you want to skip the first page?

i feel so stupid....🧟
i did not knew that it has two pages.
... and yes, i want to skip the first page. sorry for all the trouble.

OJi.

Try:

${SE_DIRECTORY_PRE_FUNC} SkipDirectoryPage



Function SkipDirectoryPage

 Abort

FunctionEnd

This may lead to some undesired results as it hasn't been tested but see how it goes. If it doesn't work then I'll probably add a define to the header to disable the page.

-Stu

hi, I'm very new to the whole NSIS thing (only 2 days 😳 ), I just wanna ask one thing, can I use this along with the ultra modern ui? that's really cool UI, and if I can use this with this self-extractor, it'll be awesome😁

thanks in advance (sorry if my question is ridiculous, I'm just a newbie😉 )