I want to make custom nsis installer with no install data at the end.
I mean that generated nsis exe header must work correctly with random zip archive queue at the end.
I hope you understand me 🙂
Self extracting zip?
7 posts
Yes, I think I understand you. What is the question?
The question is how to make that, I would imagine 😉
The method he's hinting at would be to just stick the ZIP data onto the end of a compiled installer.
So the solution would then be to split that data off to a new ZIP file on installation, and then handle the ZIP file from there. Splitting the data off would be the annoying part, I think... reading bits (starting at the end of the installer, the size of which should be known) and writing them back out.. pretty slow for larger files.
The method he's hinting at would be to just stick the ZIP data onto the end of a compiled installer.
So the solution would then be to split that data off to a new ZIP file on installation, and then handle the ZIP file from there. Splitting the data off would be the annoying part, I think... reading bits (starting at the end of the installer, the size of which should be known) and writing them back out.. pretty slow for larger files.
I thing I found a sollution for this problem
nsUnzip::Extract "/d=$INSTDIR" "$EXEPATH" /END
but now I've got another big problem, make custom dialogs 🙁
nsUnzip::Extract "/d=$INSTDIR" "$EXEPATH" /END
but now I've got another big problem, make custom dialogs 🙁
nsDialogs is very easy to learn. The nsDialogs readme has an excellent tutorial.
Thank you guy! I had started with ini based interface 😁 I think this is more intuitive 🙂
But can you tell me how to customize buttons next, cancel, install?
I didn't see such a control.
But can you tell me how to customize buttons next, cancel, install?
I didn't see such a control.
Search the forums. That question has been asked a thousand times.