Get-FileHash .\busywin-14-rel2.0-x64.zip -Algorithm SHA256 Compare the output with the hash shown on the release page. BusyWin is portable – you can run it from any folder. Choose one of the three common patterns that best fits your workflow.
BusyWin is the Windows‑ported collection of GNU‑style command‑line utilities (the “BusyBox” of the Windows world). Version 14 REL 2.0 is a stable, feature‑complete release that packs more than 200 tools into a single, tiny executable. This guide walks you through getting BusyWin up and running on any modern Windows PC (Windows 7 – 11, 64‑bit recommended). 1. What You’ll Get with BusyWin 14 REL 2.0 | Category | Example Tools | Typical Use | |----------|----------------|-------------| | File‑system | ls , cp , mv , rm , mkdir , find | Basic file manipulation | | Text processing | sed , awk , grep , cut , tr | Filtering & transformation | | System info | top , ps , free , df , uptime | Monitoring resources | | Networking | ifconfig , ping , wget , nc , telnet | Quick network diagnostics | | Archiving | tar , gzip , bzip2 , xz | Compress & extract archives | | Shell helpers | sh , bash , env , export | Minimal scripting environment | | Misc | chmod , chown , date , sleep , yes | Everyday Unix‑like utilities |
busywin --version busywin ls -l C:\Windows busywin echo "Hello, BusyWin!" You should see: busywin 14 rel 2.0 setup
#!/bin/sh echo "Current date: $(date)" echo "Uptime:" uptime Save the script as test.sh and execute:
For CMD users, create a small batch wrapper: Get-FileHash
busywin 14 REL 2.0 (built on 2024-09-12) total 124 ... Hello, BusyWin! If the commands run, the installation succeeded. BusyWin includes a tiny POSIX‑compatible shell ( sh ). You can launch it directly:
| Option | Steps | When to use | |--------|-------|-------------| | | 1. Extract the ZIP to a folder of your choice, e.g. C:\Tools\busywin . 2. Run utilities by invoking the full path: C:\Tools\busywin\busywin.exe ls -l | Quick test, no permanent changes. | | B. User‑wide “add to PATH” | 1. Extract to a folder inside your profile, e.g. %USERPROFILE%\bin\busywin . 2. Open System Properties → Advanced → Environment Variables . 3. Edit PATH (user‑level) → New → %USERPROFILE%\bin\busywin . 4. Open a new PowerShell / CMD window and type busywin ls . | You want the tools available in every terminal without admin rights. | | C. System‑wide install (requires admin) | 1. Extract to a location like C:\Program Files\BusyWin . 2. Open an elevated PowerShell and run: [Environment]::SetEnvironmentVariable('PATH', $env:PATH + ';C:\Program Files\BusyWin', [EnvironmentVariableTarget]::Machine) 3. Restart any open terminal windows. | Shared workstation, multiple users need access. | Tip: BusyWin respects the Windows PATHEXT variable, so you can rename busywin.exe to simply busywin (without the .exe ) if you want a cleaner command line. Just make sure the folder is in PATH . 5. Basic First‑Run Test Open PowerShell (or Command Prompt ) and type: | Shared workstation
busywin sh Inside the shell you can write simple scripts:
Set-Alias -Name ll -Value "busywin ls -l" Set-Alias -Name grep -Value "busywin grep" Add those lines to your ( $PROFILE ) to make them permanent.
busywin sh test.sh If you use PowerShell, you can map common BusyWin commands to aliases: