Skip to content
⌘ NSIS Forum Archive

NSIS v3.06.1

5 posts

Anders#

NSIS v3.06.1

20th anniversary.

If you find any issues, report them in this thread and/or on the SF bug tracker and please include compiler error messages and sample code if possible.
  • Release notes
  • AV false positives
    • Setup
      • SecureAge APEX (Malicious)
      • MaxSecure (Trojan.Malware.*.susgen)
      • Qihoo-360 (HEUR/*.Malware.Gen)
      • Rising (Malware.Heuristic!*)
    • Example1.exe
      • SecureAge APEX (Malicious)
      • SentinelOne (Static ML) (DFI - Suspicious PE)
      • eGambit (Unsafe.AI_Score_67%)
      • Trapmine (Malicious.moderate.ml.score)
    • ZIP
      • Cylance (Unsafe)
      • MaxSecure (Trojan.Malware.*.susgen)
      • Rising (Malware.Heuristic!*)
T.Slappy#
Hello Anders.

Thanks for this release and for your work, we have updated our tools.

I cannot believe it is already 20 years. Happy birthday NSIS!
T.Slappy#
Maybe a question / feature request for next version:

Can be NSISBI integrated/merged into official NSIS? https://sourceforge.net/projects/nsisbi/

Are there 2 versions completely different? The support for large files is totally a must-have thing!
JasonFriday13#
The two versions are basically the same with regards to the script, but there are a few extra commands related to external files of course. Nsisbi is basically a patch against official nsis.

Anders has mentioned in the past that they are open to taking it at some point, but it would need a reconfigure so that it doesn't break existing scripts (eg solid compression, nsisbi currently ignores that by default). There also needs to be a discussion about code design and organization to better suit integration into nsis.

I can see why it's appealing though, 4GB all-in-one installers, and a theoretical 8EB for both the external file and single source files (a 3GB file now adds properly without a size error in nsisbi 🙂 ).
JasonFriday13#
Oh, I forgot to mention that the core file offsets of the installers is slightly different (to accommodate 64bit lengths), so probably a major version bump would be needed as well. But right now there just isn't enough demand to justify merging it.

On a side note, I just recently found out that Unity (game engine) is using nsisbi to distribute it's editor software on windows, which surprised me 😱 . (I sometimes do google searches on nsisbi to see if there are any issues or discussions happening about it).