Skip to content

Wilenty/InnoSetup-with-latest-LZMA

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

40 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

InnoSetup v6.3.0-dev with FastLZMA2 compression

Latest Version Total Downloads Latest Release Downloads v6.3.0-dev Release Downloads v6.2.1-FIXED Release Downloads

InnoSetup v6.2.2 with LZMA v22.01 and 4GB per part

Latest Version Total Downloads Latest Release Downloads v6.2.3 Release Downloads v6.2.2 Release Downloads v6.2.1 Release Downloads

Get it from there: https://github.com/Wilenty/Plug-ins-for-InnoSetup Filename: InnoSetup-6.2.2-LZMA2201-4GbPerPart.7z

At the outset, according to the license: https://github.com/Wilenty/InnoSetup-with-latest-LZMA/blob/main/license.txt#L26

4. Modified versions in source or binary form must be plainly marked as such, and must not be
misrepresented as being the original software.

I admit that it is not the original software (since the LZMA was not updated from 7-zip source for 12 years in the original one).

At the beginning I updated the compressor only, and later I updated the de-compressor also, so I share version v6.2.1 that works with Windows 7 and newer. These files "islzma.dll", "islzma32.exe" or "islzma64.exe" was detected as a virus after compiled by using VS2015CE: https://www.virustotal.com/gui/file/9a704b833bda243bf2181ce234b1fa5add16157a2530024bef2934abc39cfcf0

And mixed results when compiled in VS2010: https://www.virustotal.com/gui/file/6758892ec6275e54962d5a531e455574aee34030ef2edd7f3a35788a807d515a https://www.virustotal.com/gui/file/c3ab31ec28fdbebb76830833c33c853f0f25bf77bd4485cc1c757943c3ed3e8e https://www.virustotal.com/gui/file/f6d326b551bc54c4f238abffd9621d625120d894a055592c948df00a042402ef

But, when compiled in VS2005 it's not detected (strange):

islzma

https://www.virustotal.com/gui/file/366db9cb6d7d67ff8257407d6b8471b8b882a9bac027c37eac898c0bf17ddbb2

islzma32

https://www.virustotal.com/gui/file/472624f34a4107d00ab43e901bc2ba9f3c86bed8e03374ce75c65b30bbbc9ec4

islzma64

https://www.virustotal.com/gui/file/652ca4b5e85963a6adb4b8230065fa4a637f9dab999376478b19f180a61f52d4

Only the executable files was detected by "SecureAge APEX", because they are *.EXE and not digitally signed in contrary to the original ones: https://www.virustotal.com/gui/file/0b2e19e473a47e10578b05a2f3b43ad96603f3ee1e397c06a280c3b7458a76e2

I don't collect Viruses on my own computer, nor on the VM (virtual machine), where I test programs on different OS's and it's architectures!!! So, if you don't trust me - please don't download it at all!

Of course it can happens that I can get one (or more) when surfing the internet, but I checked my computer with many online scanners and I don't found any. So, open question to the creators of the AV scanners: where the virus was, in the Visual Studio 2015 Community Edition and (some part of) the Visual Studio 2010? But not in the Visual Studio 2005? It was compiled from exactly the same files, on exactly the same computer and the OS, but with different compilers...

Differences in the modified InnoSetup with LZMA v22.01 to the original one with LZMA from 2010:

  1. changed maximum LZMA block size from 256MB to 4GB for separate threads. With 4GB block size and separate threads it will use about 12GB of RAM for LZMA2 and about 10GB of RAM for LZMA. Single thread not changed and limited to the 32-bit app as described in the help file.
  2. about one minute faster compression time in the highest compression levels
  3. a bit smaller result (installer) file in the highest compression levels
  4. a bit faster extraction time

It was compiled by using:

Delphi

If you need, or you will need professional help in the InnoSetup script/code, please donate me, and I will try to help you as much as I can. Sorry, but I don't help on GitHub, or other forums...

Publicity

By the way, I am preparing to sell my works done in pure InnoSetup code without any external DLL's via donations. I will show you some of them on the screenshots, what I currently did. I hope that I will finish the examples to end of vacations, but I not promises it... These examples are protected from unpacking, so, sometimes they are detected as dangerous/malicious. Anyway you can test them in the VM (virtual machine).

ListWindows


Cpu-Info-XP

CPU-Info-W10x86


ListSrvices-1

ListSrvices-2

ListSrvices-3

ListSrvices-4


IPconfig-XP

IPconfig-XP-1

IPconfig-XP-2

IPconfig-W10x86

IPconfig-W10x86-1

IPconfig-W10x86-2


GetBusType-CD-Atapi

GetBusType-CD-Sata

GetBusType-FIXED

GetBusType-REMOTE

GetBusType-REMOVABLE-Usb

GetBusType-Unknown