Launch

tools/dnstt/README.md

@@ -0,0 +1,13 @@
+# DNSTT folder
+
+DNSTT is embedded in SocksRevive PC now. You normally do **not** need to put `dnstt-client.exe` or `dnstt-client` here.
+
+This folder is kept only as a legacy fallback if you disable the embedded DNSTT engine in the DNSTT tab and intentionally run an external DNSTT executable.
+
+For normal use, leave this enabled in the app:
+
+```text
+Use embedded DNSTT engine / no external EXE
+```
+
+Then fill resolver type/address, tunnel domain, server public key, and local SSH host/port directly in the UI.

tools/wintun/README.md

@@ -0,0 +1,44 @@
+# Wintun for Windows TUN mode
+
+The Go TUN/tun2socks logic is compiled into SocksRevive PC. Windows still needs the official signed `wintun.dll` driver loader because Windows does not provide a pure userspace TUN interface.
+
+You have two options.
+
+## Option A: self-contained EXE / internal Wintun
+
+1. Put the official amd64 `wintun.dll` here:
+
+```text
+tools/wintun/amd64/wintun.dll
+```
+
+2. Run:
+
+```powershell
+powershell -ExecutionPolicy Bypass -File .\scripts\embed_wintun_from_tools.ps1
+powershell -ExecutionPolicy Bypass -File .\scripts\build_windows.ps1
+```
+
+The script copies the DLL into:
+
+```text
+internal/wintunloader/assets/wintun/windows/amd64/wintun.dll
+```
+
+Then Go embeds it into `SocksRevivePC.exe`. At runtime the app extracts it automatically before creating the TUN adapter.
+
+## Option B: external DLL fallback
+
+Put `wintun.dll` beside `SocksRevivePC.exe` or in:
+
+```text
+tools/wintun/amd64/wintun.dll
+```
+
+The app will copy/detect it at runtime.
+
+## Notes
+
+- Run the app as Administrator for TUN mode.
+- Use only the signed DLL from the official Wintun package.
+- The default adapter/device is `wintun`.

tools/wintun/amd64/PUT_WINTUN_DLL_HERE.txt

@@ -0,0 +1,4 @@
+Put official signed amd64 wintun.dll in this folder if you want either:
+
+1. Runtime fallback: build script copies it beside dist/SocksRevivePC.exe.
+2. Internal/self-contained EXE: run scripts/embed_wintun_from_tools.ps1 before build.

tools/wintun/arm64/PUT_WINTUN_DLL_HERE.txt

@@ -0,0 +1 @@
+Put official signed arm64 wintun.dll in this folder if building Windows arm64.

tools/xray/README.md

@@ -0,0 +1,14 @@
+# Xray executable folder
+
+Put your Xray executable here:
+
+- Windows: `tools/xray/xray.exe`
+- Linux/macOS: `tools/xray/xray`
+
+The default Xray profile starts:
+
+```text
+xray run -config configs/xray.json
+```
+
+Edit `configs/xray.json` with your real VLESS/VMess/Trojan/Shadowsocks settings. The app expects Xray to expose a SOCKS inbound at `127.0.0.1:10808`, unless you change that in the Xray tab.