There was an error while loading. Please reload this page.
Update example download URL to v0.5.29.232
Add Arch Linux installation guide and update wiki navigation - New page: Arch-Linux-Installation.md (4 install methods, post-install, troubleshooting) - Update Linux Environment Setup: mark Arch as supported (native .pkg.tar.zst package) - Update Home.md: proper navigation table linking all wiki pages
Windows setup: ARM64 binaries come from CI, not Releases create-release.yaml does not include windows-arm64-build.yaml, so the ARM64 installer/portable are only published as GitHub Actions artifacts — not on the Releases page. Updated §1 (install options) and §5 (build from source) to point ARM64 users at the Actions tab. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Windows setup: add Camera privacy permissions section The Mini-KVM's video capture shows up as a webcam, so Windows privacy settings can block it. New §3 walks through Settings → Privacy & security → Camera access and the three toggles required (master, let apps access, let desktop apps access). Subsequent sections renumbered; video-capture troubleshooting now cross-references it. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Windows setup: drop Installer Packaging Notes section Internal packaging detail (Inno vs NSIS, admin elevation) — not relevant to a user setting up their environment. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Windows setup: drop CH9329 from driver table CH9329 is not a USB serial device and shouldn't be listed as a serial chip option in the Windows driver setup docs. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Windows setup: clarify per-chip driver requirements Only CH340 needs a driver install. CH9329 and CH32V208 are recognized by Windows out of the box (CH32V208 is standard CDC-ACM). Added a Device Manager appearance table so users can identify which chip they have and whether action is needed. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Windows setup: drop 22H2 row from support table The 22H2 driver quirk is a setup-time detail already covered in the Driver Setup section — doesn't belong in the top-level support matrix. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Windows setup: promote ARM64 to supported Pre-built ARM64 installer and portable .exe are published on the Releases page, so Windows 11 ARM is a supported target — not a build-from-source-only one. Updated the supported-versions table, install options, and reframed the MSYS2 section accordingly. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Updated OpenterfaceQT‐Linux‐Environment‐Setup (markdown)
Add Linux Environment Setup guide Covers: supported distros (Ubuntu/Debian/Fedora/openSUSE/Arch/RPi/NixOS), installation methods (pre-built binary, Flatpak, Nix, manual deb/rpm, build from source), device permissions (udev, groups, BRLTTY), Wayland vs X11, Raspberry Pi notes, and troubleshooting. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Updated OpenterfaceQT‐Windows‐Environment‐Setup (markdown)
Add Windows Environment Setup guide Covers: supported Windows versions, installer/portable install, CH340/CH341 driver setup, build from source (Qt Creator x64 and MSYS2 CLANGARM64 for ARM64), installer packaging, and troubleshooting. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Created Linux permission access (markdown)
Updated Keyboard shortcuts (markdown)
Created Keyboard shortcuts (markdown)
Updated Common software problems (markdown)
Updated _Footer (markdown)
Created _Footer (markdown)
Created Common software problems (markdown)
Add OpenterfaceQT-Linux-Environment-Setup
Add OpenterfaceQT-Windows-Environment-Setup
Destroyed HomeOpenterfaceQT‐Windows‐Environment‐Setup (markdown)
Initial Home page
HomeOpenterfaceQT-Windows-Environment-Setup