Command xx

Spinning drive, fragmented output, damaged archive? Read in stored order, write sequentially.

Quick summary

xx extracts with sequential write: a shortcut for x -recover. Same switches as x, a different strategy: the archive is read in stored order (random read, SSD advised), output files are buffered in RAM and written sequentially. Faster on spinning drives, less fragmentation, and it gets out as much data as possible from a damaged archive.

Power user usage

• -ramsize X size of the write cache (default 1GB)
• everything else (-to -only -not -until -force...) as in x

Lo spiegone

xx is command x with flagrecover set: extract() hands the work to extractstdout(). That engine is not in the ANCIENT builds (#ifndef ANCIENT): there xx does a plain x.

Real-world examples

Everything into folder muz7

zpaqfranz xx z:\1.zpaq -to z:\muz7\

Bigger cache

zpaqfranz xx z:\1.zpaq -to z:\muz7\ -ramsize 4GB

Salvage a damaged archive

zpaqfranz xx z:\1.zpaq -to z:\muz7\ -force