$status = if ($proc.ExitCode -eq 0) "OK" else "FAIL ($($proc.ExitCode))"
$report += [pscustomobject]@ Timestamp = (Get-Date).ToString('s') Archive = $archive Destination = $dest Pattern = $pattern ExitCode = $proc.ExitCode Status = $status
Write-Host "Processing: $archive" -ForegroundColor Cyan phoenix sid unpacker v1.5 beta 2.rar
| Switch | Syntax | Example | Description | |--------|--------|---------|-------------| | -i / --input | <path> | -i myapp.sid | Path to the SID archive to unpack. | | -o / --output | <dir> | -o C:\tmp\myapp | Destination directory. If omitted, a folder named after the archive is created beside it. | | -p / --pattern | <wildcard> | -p "*.exe" | Extract only files matching the pattern. Multiple patterns can be comma‑separated. | | -v / --verify | – | -v | Force signature verification and abort on failure. | | -j / --json-meta | – | -j | Write a metadata JSON file next to the output folder. | | -l / --log-level | info|debug|error | -l debug | Set verbosity. | | -b / --batch | <list.txt> | -b archives.txt | Process a newline‑separated list of SID files. | | --no-update | – | --no-update | Skip the automatic update check on start. | | -h / --help | – | -h | Show help. |
$psu = "C:\Tools\PhoenixSIDUnpacker\bin\PhoenixSIDUnpacker.exe" $report = @() $status = if ($proc
The beta channel (v1.5 Beta 2) will be superseded by in Q4 2026, which introduces a native .NET 7 front‑end and a plug‑in architecture for custom signature providers. 11. TL;DR – Quick Reference Cheat Sheet | Action | CLI Example | |--------|-------------| | Extract everything | PhoenixSIDUnpacker.exe -i app.sid -o C:\out | | Extract only .exe & .dll | PhoenixSIDUnpacker.exe -i app.sid -p "*.exe,*.dll" | | Verify signature & abort if bad | PhoenixSIDUnpacker.exe -i app.sid -v | | Produce JSON manifest | PhoenixSIDUnpacker.exe -i app.sid -j | | Batch process a list | PhoenixSIDUnpacker.exe -b list.txt | | Disable auto‑update | `PhoenixSIDUnpacker.exe --
$args = @("-i", "`"$archive`"", "-o", "`"$dest`"") if ($pattern) $args += "-p", "`"$pattern`"" $args += "-v", "-j", "--log-level", "error" | | -p / --pattern | <wildcard> | -p "*
PhoenixSIDUnpacker/ │ ├─ bin/ │ ├─ PhoenixSIDUnpacker.exe (main GUI/CLI binary) │ └─ libsid.dll (core extraction engine) │ ├─ scripts/ │ ├─ unpack_batch.ps1 (PowerShell helper for batch mode) │ └─ verify_signature.ps1 (sample script to validate signatures) │ ├─ docs/ │ ├─ README.md │ └─ changelog.txt │ └─ resources/ └─ icons/ └─ app.ico The bin folder contains the only files that need to be placed on the target system; the scripts folder is optional but useful for automation. | Step | Action | |------|--------| | 1. Extract the RAR | Use WinRAR, 7‑Zip, or any compatible utility. Extract to a folder where you have write permission (e.g., C:\Tools\PhoenixSIDUnpacker ). | | 2. Verify Integrity | Open a command prompt and run certutil -hashfile PhoenixSIDUnpacker.exe SHA256 . Compare the hash with the one listed in docs\checksums.txt . | | 3. Install Prerequisites | The unpacker needs the Microsoft Visual C++ Redistributable 2015‑2022 (x86 & x64). If not already present, the installer will prompt you. | | 4. Run a Test Extraction | Double‑click PhoenixSIDUnpacker.exe → File → Open → select a small test SID archive ( sample.sid ). Click Extract to a temporary folder. Verify the output appears in the file tree. | | 5. Enable Command‑Line Mode (optional) | Add the bin folder to your PATH environment variable if you plan to call the tool from scripts. | 5. Command‑Line Interface (CLI) The binary ships with a fully‑featured CLI that mirrors the GUI functionality. Below is a cheat‑sheet of the most useful switches (run PhoenixSIDUnpacker.exe -h for the full list).