-
The Win64 build include a SFX module (zsfx.exe)
Here the stand-alone for Win32 and Win64
The sfx command
can be executed with, and without, the -sfx switch
In the first form will write the SFX module (.exe) with the same name of the provided ZPAQ, of about 300KB
zpaqfranz sfx z:\1.zpaq
=> make z:\1.exe that, if executed in the same folder of 1.zpaq, autoextract the data.
This is for archives 2GB+, that cannot be "translated" into Windows executables.
Can run with parameters, for example z:\1.exe -force to overwrite, just like zpaq 7.15
Support encrypted .zpaq archive
The second mode (with the -sfx switch) will create a "real" SFX (a single .exe with the .zpaq embedded)
zpaqfranz sfx z:\1.zpaq -sfx z:\2.exe
in this example => z:\2.exe
The sfx switch (for add)
When creating an archive, it is now possible to make a SFX
zpaqfranz a z:\ugo\mycpp.zpaq *.cpp -sfx z:\ugo\autoexe.exe -sfxto .\sourcebackup -sfxforce
will
- create z:\ugo\mycpp.zpaq adding all the *.cpp in the current directory
- create z:\ugo\autoexe.exe
- z:\ugo\autoexe.exe will extract in .\sourcebackup folder (-sfxto), in overwrite mode (-sfxforce)
The SFX module is not very small (~300KB) but is rather... smart.
Can work alone, embedded, and as a builder (if named zsfx.exe)
Support just always the functionality of zpaq 7.15, and just as fast
Does NOT support (yet) encrypted .zpaq data
-
Some fixes. Removed the gcc-bug workarounds: sometime makes nasty side effects
-
The sum() function, with the -output switch, sort hash checksums to quickly test a restored server
Something like hashdeep (in this example -all using SSD/NVMe. Do NOT use with spinning drives!), runs and very high speed (typically the max bandwidth of the media multigigabyte/s
server1:
zpaqfranz a copia.zpaq /tank/condivisioni
zpaqfranz sum /tank/condivisioni -sha3 -all -output /tmp/server1.txt
(...send the copia.zpaq and server1.txt to server 2...)
server2:
zpaqfranz x copia.zpaq
zpaqfranz sum /tank/condivisioni -sha3 -all -output /tmp/server2.txt
diff /tmp/server1.txt /tmp/server2.txt
Note: on SSD/NVMe multi-core server using "heavy" hasher (like sha3) does NOT slow down the process