Karuzip 2.0
Being built now
Rebuilding what happens when an extraction goes wrong.
Extracting an archive is the easy part, and it already works. What 2.0 rebuilds is everything after that: making sure a failure never takes your existing files down with it, and making sure you can tell why it failed without guessing. Unglamorous, and the part we were least comfortable with.
- Extracting into a folder that already has files will not damage what is there Today, an overwrite that stops halfway can leave a half-written file behind. In 2.0 the extraction is assembled somewhere else first and applied in one step at the end. Cancel it midway and your existing files are untouched. The trade-off: it temporarily needs roughly as much free space as the extracted result.
- Archives on network shares and NAS devices will open On some NAS setups, extracting an archive stored there simply did not work, and nothing was written to the log either, so the cause stayed invisible for a long time. We found it, and it is being fixed.
- A failure will say what actually went wrong Instead of ending at an internal error, Karuzip will distinguish between running out of disk space, being denied access, and a damaged archive - and where there is something you can do about it, say what.
- A command you can call from your own scripts A small command-line companion ships alongside the app, so a batch file or a script of your own can drive Karuzip. Irrelevant to everyday extraction, and a real difference if you do the same job every day.