A packer plug-in (wcx) for Total Commander for the ZPAQ format.
Based on zpaq 7.07.
Zpaq is a journaling (append-only) archiver for incremental backups.
Files are added only when they differ from the version(s) already stored.
Both the old and new versions are saved.
It also features:
See http://mattmahoney.net/dc/zpaq.html for more details.
In short: you can't delete files, only add new ones,
but it's very efficient for detecting duplicate file fragments,
when you'd add several versions of a file to an archive.
Additionally it has very efficient compression modes (level 4/5),
which in most cases creates even smaller files than 7-Zip in it's best mode,
but can be quite slow.
The lower compression methods (up to method 2) compress fast, and decompress very fast.
In default mode, when you open a zpaq archive in TC, you can only see either the
latest update's files, or all "collected" files from all updates you made,
with each file showing it's newest version, just like you would expect from other
archivers (zip, rar, ...).
This view depends on how files were added to an archive.
To use the unique journaling feature, i.e. when you want to get your
old file versions, enable the Show all archive versions option
(through Pack files -> select zpaq -> Configure),
so that you will be able to view all of the archive's updates.
For that you will now see unique dir names in the root of the archive,
(either ascending eight-digit strings, or a date string representing the
date when that version was added to the archive) which will portray
every update you made to it.
This means you can decompress your old file versions out of the archive,
like you would with every other file.
This will also mean that you won't see all your files "collected" in one of
those single dirs. Use e.g. TC's branch view (Ctrl + B) for that,
or *NEW* the Show the default archive view in extra dir option.
It's probably best to leave the default view enabled most of the time, when you
just add files to the archive, but enable it if you need an old version out of it.
For using more than just one compression/decompression thread, the x64 version is highly recommended. While two parallel threads might initially work on 32-bit, they could fail to work until the end, crashing the plug-in.
Compression level 4 is very slow, and level 5 is extremely slow, so take care before starting them with huge file collections.
Total Commander 7.50 or newer is required.
Works on Windows 2000, XP or newer (no support for Windows 9x).
Requires either a SSE2 capable CPU (for 32-bit version, all x64 CPUs support SSE2 anyway),
or use the non-SSE version from the plug-in archive (see installation section below).
I recommend at least 384 MB of RAM for the base use, but when you try to decompress a new/unknown zpaq archive, you should be aware that the creator of such archive might have used the maximum compression level/method (5) for it, meaning that up to 850(!) MB are needed when using one decompression thread. In such case, 1024 MB system mem should be the minimum (and will use most of your RAM for decompression), but if you want to use more than one thread, the memory requirements need to be multiplied by the number of threads!
Also note that there is additional "management" data needed for the compression/decompression procedure, which can be as high as 50 MB, and even increases with the number of files you try to process at once, and the number of threads you use. Additionally, the deduplication mechanism requires 1 MB of memory per GB of deduplicated but uncompressed archive data to update, and 0.5 MB per GB to list or extract. This means, for example, that doing a backup of 100 GB of data, where deduplication reduces this amount to 90 GB, would require an additional 90 MB of RAM on top of the basic memory requirements. Doing a backup of 1 TB of data might therefore need up to 1024 MB of additional RAM, which could be impossible for the 32-bit plug-in.
You should take special care in the 32-bit TC, because a 32-bit program can only
use up to 2 GB of RAM (TC isn't flagged as large address aware).
Therefore it might crash, even with a mem usage WAY below 2 GB, due to address space
fragmentation and several other factors.
A typical scenario I tested to crash under 32-bit is:
- compress a large file with level/method 3 and two threads -
which might crash, although it doesn't use more than ~1100 MB.
For such reasons I recommend to only use one thread at all time in 32-bit.
Note that the 32-bit plug-in is LIMITED to two threads anyway.
The plug-in supports background packing/unpacking. For using more than one operation in parallel, the memory requirements will of course accumulate!
The plug-in will likely catch memory exceptions.
So when you get a message like: bad allocation
you will know that you've run out of memory.
There are a plug-in options to warn you about memory requirements and/or parallel operations.
tl;dr
The rough memory requirements per thread in summary:
| Method | Compress | Decompress |
|---|---|---|
| 0 | 64 MB(?) | <=32 MB(?) |
| 1 | 128 MB | 32 MB |
| 2 | 450 MB | 128 MB |
| 3 | 450 MB | 400 MB |
| 4 | 550 MB | 550 MB |
| 5 | 850 MB | 850 MB |
Just open the plug-in archive in TC and it can install the plug-in (as packer plug-in) automatically. Otherwise copy the archive's content to the location you want (preferably a sub-dir of TC's installation directory) and select the plug-in manually in the configuration.
There is a non-SSE version of the 32-bit plug-in provided, which will work on older CPUs that either lack any SSE instructions whatsoever, or don't support SSE2 (Athlon XP, Pentium III etc.), but is slower, due to the lack of a JIT compiler. Just overwrite the original plug-in file with it, when the plug-in isn't loaded (like directly after a TC restart).
The plug-in ships with both the 32- and 64-bit version. If you don't use Total Commander x64, you may delete the zpaq.wcx64 file to free some space, likewise delete the zpaq.wcx if you never plan to use 32-bit.
Opening and creating multi-part archives is supported by the plug-in.
The basic format is part001.zpaq, part002.zpaq, ..., with an optional index part000.zpaq.
This means a group of digits anywhere in the file name, starting with one and increasing with
each part, and the optional index being all zero digits.
Basically that feature allows you to make fast incremental updates as separate files
(part001.zpaq, part002.zpaq ...), that you can move offsite (or not), keeping only a
small index locally (part000.zpaq). Each part represents a single "update" of the archive.
With the index file you can list or compare the archive contents from just the index,
without retrieving the rest of the archive at all!
This might come in handy if you moved your backup files to an offline/remote location,
but still want to know what's in it.
That single index file will still allow you to update the archive (creating a new part),
i.e. no other part needs to be present in order to create the next update,
because the index contains all subscripted deduplication data needed for an update.
If you keep all files local, then zpaq will make sure they are consistent with the index
(if available) when you update such archive.
To restore any files out of the archive, you would retrieve parts 1 and higher and extract as usual.
When updating a multi-part archive, zpaq will create a new part using the next available
part number, starting with 1. If an index (part 0) is present, then it is also checked for
consistency (number of versions and archive size) and updated. An index is created only if
part 1 is also created. Thus, if you do not intend to move the archive parts to a remote location
then you may safely delete the index and it will not be re-created.
See the standalone zpaq executable or the zpaq homepage for further details.
To create a new multi-part archive you'd use the same syntax as in the standalone zpaq executable:
When packing, TC shows you the Pack files box with the target file name, and the zpaq
extension already added, e.g.:
zpaq:c:\myfile.zpaq
Now just append a question mark wildcard group anywhere in the file name (in the name only,
not the other path parts), which will represent that digit group used for the parts, e.g.:
zpaq:c:\myfile???.zpaq
This would create c:\myfile001.zpaq and the index c:\myfile000.zpaq.
It is recommended to use a decent digit group length, if you expect a lot of updates,
like at least three digits or so. The position of the digit group in the name doesn't matter,
but it is recommended to put it to the "very right", i.e. closest to the file extension.
Note that unlike the standalone zpaq program, an asterisk wildcard is not supported.
To list or extract, or appending to existing multi-part archives, things are way easier, since there is an optional multi-part detection. See the Multi-part detection option explanation below for details. Just make sure you hold all relevant parts in the same dir, if trying to extract files from such archive. You'd see an error message otherwise.
You can set all options by a dialog accessible through
Pack files -> select zpaq -> Configure.
As TC doesn't provide another access to that dialog, the decompression/misc
settings need to be configured in there also.
All options are saved in the config file pkplugin.ini, which is normally located
in the same location as the TC main config file (wincmd.ini), and where
all packer plug-ins can store their settings (but only a few actually do).
You could manipulate that file directly (most key values are represented by numbers),
but I don't recommend it.
Sets zpaq's compression mode.
It's the same level you'd set with -method L in the standalone zpaq program.
Just be aware that method 4 and especially 5 can be VERY slow, even on fastest machines.
Default is level 1.
Sets the block size for compression.
It's the same amount you'd set with -method LB in the standalone zpaq program
(L is compression level, B is block size with a number from 0 to 11, meaning 2^blocksize MiB).
This size determines how "granular" zpaq will pack data into blocks.
Using larger blocks can improve compression but requires more memory and may be slower,
because each block is compressed or decompressed by a separate thread (lower parallelization
due to worse data granularity).
A smaller block size on the other hand will provide more updates to the progress dialog,
so that your are able to pause or cancel a pack/unpack process quicker, and will ease up
the memory requirements.
Note that unlike the standalone zpaq program, this number is currently limited to 64 MiB (2^6 MiB)
for any compression level. This is for safety reasons and for keeping the rough memory requirements
in reasonable limits. Decompressing archives created with larger block sizes (standalone zpaq)
will work, but for a huge size the memory requirements might be impossible (especially for the
32-bit plug-in), because there is currently no way to detect actual requirements before starting
decompression.
The check box Use default size (checked by default) will use the program's default block size
every time, which is 16 MiB for compression levels 0 and 1, and 64 MiB for levels 2 through 5.
Attempt to add files, even if the last-modified date has not changed.
Files are added only if they really are different.
It's the same option you'd set with -force in the standalone zpaq program.
Detailed explanation:
Normally files are added only if the date (last modification timestamp) has changed
since the last update. With this option you will override that behavior, but in any
case the file will be deduplicated and not saved unless the contents have really changed.
This means that when the option is disabled, a file is not read at all, if the
timestamp AND file size AND attributes (hidden, write-only, etc.) are identical to
a file of the same name (and path) already found in the archive. It might be
dangerous in situations where a file content change doesn't affect those parameters.
With that option enabled, the file's content is always checked for differences against
the already stored file version, no matter the pretended equal parameters, so that
you're definitely on the safe side if such situation occurs. Therefore the option
is basically a shortcut for speed when packing files, so that some e.g. multi-gigabyte
file read operation doesn't even need to start to check for differences.
Default is disabled.
Prevents marking files in the archive as deleted when files existing in the
archive's last update are not amongst the files intended for the current archive update.
This makes zpaq consistent with the behavior of most non-journaling archivers.
In other words: when disabled, all files from the last update which are not included
in the current update will be marked as deleted, so that you would see in such archive
in the normal view mode (w/o the Show all archive versions option) only files from
that very update you just made. When enabled and opening such archive, you would see all
"collected" files from all updates you made, with each file showing it's newest version,
just like you would expect from other archivers (zip, rar, ...).
You should be consistent with this option, i.e. either enable or disable it
for ALL updates you'd make to an archive, because otherwise you might "lose"
some files in between the updates for the normal archive listing, and could only
access them through the Show all archive versions option.
It's the same option you'd set with -nodelete in the standalone zpaq program.
Default is disabled.
Will force to use full/absolute file paths in the archive for all files you feed to it,
ignoring the path structure that TC is requesting.
Without this option, TC will request
relative paths in most cases, with search results fed to list box probably being the only
exception. The main advantage of this option is that you don't need to worry about using
the same base dir for all updates you'd apply to an archive, because when not doing so,
zpaq would probably see some or all files from the previous update as deleted, or rather
all files for the current archive update as being "new", although they may have the same
content as in the previous archive update. Full paths will make sure that it doesn't matter
if or which parent dir you'd select in TC to feed files to an archive, as long as you use TC's
Also pack path names (recursed only) option in the Pack files box.
Default is disabled.
Stores the drive letter or the UNC ComputerName (as in \\ComputerName\SharedFolder\Resource).
That is, only if you pack files with absolute paths, i.e. from TC search results
fed to list box or when using the Always store full paths option. Thus directly packing
a file from a normal view and default options will not trigger it.
Disabling this option will remove drive letters from the stored archive entry name in any case,
like with most other archivers.
Default is disabled.
Stores all available Alternate Data Streams from files and directories from NTFS drives.
This means that every file is searched for available streams, and, if found,
they are stored in the archive like every normal file.
This will of course not find anything for non-NTFS file systems, like FAT on
USB drives and SD cards, but won't trigger any errors by doing so, so that you
may leave it enabled all the time.
Currently this function will only work on Windows Server 2003 / Vista or higher
(i.e. not on Windows 2000 and XP), as it relies on API functions only available
for these OSes. Note that enabling this option will slow down the pack operation a bit
(depending on the amount of files you want to add).
Default is disabled.
Sets the parallel threads for both compression and decompression.
The maximum number you can set is the number of CPUs reported by your system.
So for s single CPU you can only choose 1.
In 32-bit TC, this is always limited to 2, no matter if you have more CPUs than that.
Note the memory requirements section above for details on this.
In 64-bit TC, the string below the box will inform you about the CPUs reported by your
system, plus the detected real/physical CPUs (i.e. fully functional cores), to identify
a SMT/HTT processor configuration (where you might not want to use all available threads,
due to lower speedup compared to using fully functional CPU cores).
It's the same amount you'd set with -threads N in the standalone zpaq program.
Default is 1.
Enables the unique journaling feature, which you can e.g. see when you
open an archive by pressing return or Ctrl + PgDown in TC.
See the top section explanation for more details.
Just keep in mind that you might not see a different listing of an archive
immediately, when you already listed it shortly before, due to TC's content cache
(see the Notes and Limitations section above).
Default is disabled.
When you enabled Show all archive versions, it will show the dir names in
the archive's root as a date string, representing the date when that version
was added to the archive, instead of the default ascending eight-digit string,
in a format that you can customize in the text box below.
The default format string is
$Y-$M-$D-$h-$m-$s
which will result in the dir names following the scheme:
YYYY-MM-DD-hh-mm-ss
You can customize the format string to your very liking, using any order of these
individual date fields and any "aligning" characters, including spaces and Unicode
characters, you prefer.
Just note that all date fields ($Y, $M, $D, $h, $m, $s) are mandatory, meaning
they are enforced to append to the dir names if you omitted some or all of them,
so that all dir names are guaranteed to have individual names, no matter your
customization.
Additionally you can refer to different special fields in the format string.
All special references are in the format
[percent sign][letter][minimum field width]
The minimum field width is a lower-case hex number (0-9 and a-f), which represents
the fields guaranteed minimum width, filled with leading zeros.
For the archive name field, this width determines the number of characters used,
with a length of 0 using the whole name.
The fields for referencing are:
%v - the ascending version/update number (the same you'd see w/o this option)
%a - the number of added files for this update
%d - the number of deleted files for this update
%b - the compressed size for this update in Bytes
%k - the compressed size for this update in Kilobyte (kibibyte - KiB)
%m - the compressed size for this update in Megabyte (mebibyte - MiB)
%g - the compressed size for this update in Gigabyte (gibibyte - GiB)
%s - the number of added NTFS Alternate Data Streams for this update
(%a already includes this number)
%n - the archive name (i.e. the file name w/o extension)
Hence the format string can get as complex as e.g. :
%v4 $D-$M-$Y_$h$m$s +%a4 -%d4 (%s2 ADS) (%ba %m6)
which could result in things like:
0007 04-11-2015_181534 +0260 -0017 (02 ADS) (0014842769 000014)
Note that the dir names might not sort in an ascending order, if you
changed the order of the date fields. In that case you can still sort the dirs
by date in TC (Ctrl + F5).
Also note that when changing the format string, you might not see a different
listing of an archive immediately, when you already listed it shortly before,
due to TC's content cache (see the Notes and Limitations section above).
Default is disabled.
Will show an additional dir in the archive's root when listing an archive via
the Show all archive versions option.
This files and paths shown in this dir will be identical to the the default view
(showing the latest archive state) i.e. when not having Show all archive versions
enabled.
You can customize the name of that dir in the text box below.
For this name, the SAME format string as for the Show archive version names as
detailed timestamp option can be used. However, the date fields will not be mandatory,
and all fields for the update size, added/deleted files and ADS will show as zero,
as the exact number can not be determined.
Note that in order to work, all relevant files (incl. path) will "move" out of the
version sub-dirs into that extra dir, meaning that you won't see any individual file
twice in that view. This will also mean that the the latest "version dir" will be removed,
as all files found in there represent the latest archive state. If all files from
a version sub-dir are moved to that extra dir, such dir will be left empty. The
Mask empty archive versions option (see below) would remove such dirs.
This also means that a customized dir name (via Show archive version names as detailed
timestamp option) might not fit the version dirs that you now see (e.g. the number of
added or removed files doesn't fir the amount of files you see).
Also note that when changing this option or the dir name, you might not see a different
listing of an archive immediately, when you already listed it shortly before,
due to TC's content cache (see the Notes and Limitations section above).
Default is disabled.
Used together with the Show the default archive view in extra dir option, and, when
enabled, will also include all "deleted" files from the archive, each in it's latest version,
meaning it would show in that special dir a combination of all files (and paths) that the
archive ever came across, which might help in cases where you didn't add files to an archive
via the -nodelete option (standalone zpaq program) or the Don't mark files found only in the
last update as deleted option.
Default is disabled.
When you enabled Show all archive versions, this option will mask all "empty"
archive versions, so that you won't see them in the archive's root. Empty means
that a version dir either contains no files at all or empty dirs only.
When adding something to an archive, zpaq always creates another entry, even if
you didn't add anything new to an archive. For constant backups of the same files,
where you don't want to check for a change in file timestamp and/or content, this
option will therefore help you showing only the relevant versions of your files
(but TC's branch view (Ctrl + B) would of course also help in such case).
Default is disabled.
When enabled, it will mask (delete) drive letters or the UNC ComputerName
(as in \\ComputerName\SharedFolder\Resource) possibly stored within the archive,
which can be there due to the Store drive letter / UNC name when possible option,
or archives created by the standalone zpaq program.
Note: this will not work with Show archive version names as timestamp, since
there's no reliable way to detect drive letter dirs in that mode.
Default is enabled.
When enabled, will provide "dummy" files with all version dir names, located in a
custom named sub-dir in the archive's root. You can customize the name of that dir
in the text box below.
Extracting one of such dummy files will not create or write anything in the output dir
(you may safely ignore the possible File not found! error message), but will remember the
underlying version choice in the plug-in memory and apply the "-until" option (same as
in the standalone zpaq program) the next time TC opens the archive.
Opening another archive before that might be necessary, due to TC's archive content cache
(see the Notes and Limitations section above).
This option greatly helps viewing and extracting an older archive state with the full dir
structure (instead of only the selected file versions belonging to the archive update in
question and missing files and dir structures taken along from previous update), either by
using the Show the default archive view in extra dir option, or by disabling the
Show all archive versions option before opening the archive again (since the dummy file
dir only appears when showing all archive versions, but a choice will still be remembered
without it). The choice is held in RAM only temporary, and only a single archive/version
number combination will be saved, meaning that using the option for a different archive will
clear your choice for the former archive, just like when manipulating the archive in question
(updating it) or when restarting TC.
Note that this option will not help you to "rollback" the archive state when used in
conjunction with adding files to an existing archive, as the "-until" option isn't applied
in such case, to prevent unwanted data loss.
Default is disabled.
When enabled and when trying to extract or copy nothing but a complete version dir out of a
Show all archive versions listing, the plug-in will ask if it should extract the complete
archive state in the selected version to the output dir, instead of only the selected file
versions belonging to the archive update in question and missing files and dir structures
taken along from previous updates.
In other words, selecting just a version sub-dir like 00000005 in the archive root any trying
to copy/extract it to the output dir would trigger a question dialog.
The option works similar to the Show dir for customizable "-until" archive view option, except
that you can only fully extract an archive state, and not list/view it first.
The option may work in conjunction with the Show the default archive view in extra dir
option, but only when none of the individual files from the targeted version move to the
extra dir (like when the version in question holds old file versions only).
Note that extracting the full archive state directly to a different archive will not work, unless
you switch off the Support content search in archives option. When that option is enabled, you
would always extract the version sub-dir as selected, not triggering the question dialog. So
either disable that option or use
a manual extraction to disk and subsequent packing to the other archive for such task.
Also note that the complete archive state may hold much more files than selected, extracting
may therefore take a long time.
Default is disabled.
When enabled, it will try to set the last modified date of folders you just extracted.
This is done after all files have been extracted, so you won't see it happen if you
canceled an unpack process.
To be able to do this there must be single directory entries stored within the
archive, which is the case with all archives you created with the plug-in, but
might not be the case with archives created with the standalone zpaq program.
You might not want to enable this if there are already files existing within a dir
structure, where unpacking to and setting a dir date might not represent a file-set
state as it was intended, but for e.g. unpacking files to a new (empty dir) location
it makes sense.
Note that if you did enable the Show all archive versions option, the correct timestamps for
directories will only be shown for the first (oldest) version with an individual (a new)
timestamp, but extraction will set the correct timestamps (see Notes and Limitations
section above).
Default is enabled.
Extracts all stored Alternate Data Streams, if this is possible for the target
locations's file system.
This means it will only work for NTFS targets, and not for things like FAT USB sticks,
but won't trigger any errors by doing so, so that you may leave it enabled all the time.
Of course this also means that ADS not belonging to a file/dir you selected for unpacking
will not be extracted, but only the streams belonging to your selection.
Unlike the Store NTFS Alternate Data Streams option, extracting ADS should work
on all systems.
Default is disabled.
Will allow TC to search archive content for text in the main search function (Find files)
and to compare archive's file content in the Synchronize dirs function.
Just remember that this can be VERY slow (see the Notes and Limitations section above).
You might want to disable this option when dealing mainly with archives created with
higher compression modes and/or larger files, because the reaction speed until you can stop the
content search could be quite high, and switching this option off wouldn't even start
a content search in the first place.
A 2nd reason to turn it off is the Support full archive state extraction option
and wanting to extract the full archive state directly to a different archive (see the
notes for that option).
However, as it is not clear how often and when TC will ask the plug-in for it's features,
the feature isn't turned off fully until the plug-in caps in the wincmd.ini section
[PackerPlugins] are modified from 663 to 535.
If this is not yet the case, the plug-in will at least skip the slow individual file extraction,
but would still start to extract the LAST file listed in the archive, which might take some time
after all. Likewise, re-enabling the option probably needs another manual modification of the
plug-in caps.
Default is enabled.
Shows a warning dialog when your memory requirements might exceed the safe limits, every time when you:
When you confirm the dialog, you'd continue the operation despite the warning,
otherwise you'd cancel it (or return to the config dialog).
You might want to keep this enabled for the 32-bit version (see the memory
requirements section above).
Default is enabled.
Shows a warning dialog when you start a pack/unpack operation, which will inform you
about any background operation still pending, that would use additional CPU/RAM resources.
This might be especially important for the 32-bit version, where even two parallel
operations might exceed the available memory or address space.
Note that there won't be any checks of which operations might be safe to run concurrently
(like when you have enough memory or CPU cores), it will just inform you that there is
at least one operation not finished yet.
Default is enabled.
When dealing with encrypted archives, the plug-in will need to ask for a password every time you:
By using this option, the last used archive name, path and attributes are stored
together with it's password, so that these dialogs will appear less frequent.
Since it's not that hard to read the password from e.g. viewing the raw process memory
with known offsets, you should probably disable this option when safety is a concern.
Default is disabled.
Enables or disables support for archive "rollback".
This means you can "cut" a custom number of coherent archive updates, starting
from the "archive's back". So if you e.g. backed up some files you didn't mean to,
then you can truncate the last update and repeat the procedure, or, if you need
to, truncate even more updates.
In other words: discard all archive updates AFTER the version you specify, and delete
that compressed data from disk (i.e. whole part files in case of multi-part archives).
In order to do this you need to pack new files to an archive into one of the
"version sub-dirs". Normally this would update the archive in the usual way,
adding a new version/update to that archive. But with this option enabled you
will be asked for a rollback instead (so you will still have the chance to deny
a rollback).
It means that you should at least temporary enable the Show all archive versions
option, to display all version names in the archives root, navigate into one of
these dirs, and now either copy your files into it (press F5), or drag and drop them.
When you now confirm the question, you would discard all archive updates AFTER the
version you just navigated to (represented by the dir name) and immediately after
that pack all files you just copied/dropped to the archive, like any usual archive
update. So for just discarding the LAST update, you would copy new files to the
last but one (next to last) version dir, for discarding the last two updates you
would copy files to the last but two (second from last) version dir, and so on.
Copying files to the last/latest version dir therefore doesn't trigger a rollback,
as there are no versions following it.
Another method to rollback is to enter the sub-dir directly when packing.
So when TC shows you the Pack files box with the target file name, like
zpaq:c:\myfile.zpaq
you just append the desired version number in an eight-digit scheme, to which
you want to rollback, i.e. the last version that should stay in the archive:
zpaq:c:\myfile.zpaq/00000005
(this would discard all updates after the 5th update)
This would only work for an existing archive of course, and for a newly created
archive you would pack all input files to the sub-dir 00000005 instead.
Default is disabled.
Enables a "discard" of the archive update at hand when you cancel a pack process.
In other words, it will cancel the pack process as soon as possible, so that already
partially appended data will be left unfinished and not being "indexed". This will
be no problem, as such data will be ignored when reading the archive, so that no trace of
this update will be seen. (it might waste disk space though.) The data would be overwritten
on the next archive update.
Without this option, any files already processed or currently being processed at the time
when you cancel the pack process will be taken into account, so that a valid archive update
will be created in any case, only missing the files from the "queue" after where you canceled
the pack process.
Therefore it might help in cases where you don't want partial updates and otherwise have to use
the archive rollback capability (see above) to discard them.
Default is disabled.
When packing, this option will allow the progress dialog to show the same block stats as the
standalone zpaq program would show.
This will be the three-part format (XX,XXX,X), which means compression level and block size, the
estimated compressibility (0..255, where 0 means random data), the detected data type (1 for text,
2 for x86, 3 for both, or 0 for neither).
When using more than one thread, it might overlap a past block quite fast due to parallel operation
(unlike the standalone program, where you have a console output history), but it can still be
interesting for estimating the data at hand.
Note that this option might trigger wrong "file count " stats in the progress dialog, because TC
will see the string as an unknown file name, depending on the block size.
Default is disabled.
Enables or disables the automatic detection of (remote) multi-part archives
(part001.zpaq, part002.zpaq, ..., and optional part000.zpaq).
Automatic detection means that when you open an archive for listing/decompression
or packing, all archive files in the same directory are checked if they resemble
a possible digit group scheme of the input file. If they do, and they have at least
the minimum amount of digits that you set by this option, the archive will be opened
as multi-part, by replacing the digit group characters with wildcards (question mark).
If no index file (part000.zpaq) is found, at least two archive parts need to
exist, in order to treat the archive as multi-part. If this is the case and you
are about to pack new files to such archive, you will be asked if you really want
to treat it as multi-part, for not accidentally missing the sync of an index file
currently placed elsewhere.
A single index file w/o another part file will always be treated as multi-part for
extracting, with this option enabled. If you have a file incidentally resembling
the index part scheme (a group of all zero digits somewhere in the name), this may
give an error message when trying to extract from it (but not when opening it for listing).
Just turn the option off to treat it as a normal file instead.
Note that when having multiple digit groups in the file name, the "last" group will be
be used, i.e. the group being closest to the file extension.
Default is disabled.
This plug-in was created by Michael Loster "milo1012".
It is released as freeware and can be distributed freely.
This software is provided 'as-is', without any express or implied warranty.
In no event will the authors be held liable for any damages arising from the
use of this software.
The source code (besides the third-party code mentioned below) may be used freely,
provided that the original author is mentioned for any use of modified or unmodified code.
This plug-in uses the ZPAQ source, which was released to public domain.
See the source provided, or http://mattmahoney.net/dc/zpaq.html for details.
This plug-in uses the SimpleIni library from Brodie Thiesfield, see the "SimpleIni.h" file in the source for legal stuff.