CLI automation, integrity checks, and secure operations

Use this page when you are integrating Pure Zip Core into scripts, scheduled tasks, CI jobs, or security-sensitive desktop workflows.

Frequently asked advanced questions

• How do I view CLI help from inside the app?

  Open Help → Command-line reference in the GUI. This shows the currently supported nz.exe command surface.

• How do I run scripts without interactive prompts?

  Use non-interactive CLI flags and request JSON output where supported. This keeps automation deterministic and parser-friendly.

• What should automation parse: text or structured output?

  Prefer structured JSON and numeric exit codes. Localized human-readable text is useful for operators but fragile in machine pipelines.

• How should I pass archive passwords securely?

  Use environment variables such as NEATZIP_PASSWORD when supported by your workflow. Avoid exposing secrets directly in command history.

• What does "busy" mean when multiple tasks hit one archive?

  Concurrent writes to the same archive can fail with a busy status. Serialize writes or implement retry logic in your automation layer.

• How can I validate file integrity besides archive testing?

  Use the hashing tool (available through More tools / command flow) to generate checksums for verification before and after transfer.

• When should I use file split tool outside archive splitting?

  Use file split when you need to segment a single large file independently of archive format, for transport or upload constraints.

• What is the role of Password Manager in Pure Zip Core?

  Password Manager helps reduce repetitive entry in GUI workflows. For unattended scripts, use environment-secured input methods.

• What is secure delete and when should I use it?

  Secure delete is for sensitive files where normal recycle-bin delete is insufficient. Always verify target paths before execution because recovery may not be possible.

• How do I debug unexpected CLI behavior?

  Start by confirming help syntax, checking output JSON envelope, validating file paths, and isolating with small repro inputs. Keep logs without sensitive data.