install-windows-3.11

Install and run Windows 3.11 in QEMU with VNC and noVNC access.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/bianhaifeng789-hue/openclaw-config --skill install-windows-3-11-bianhaifeng789-hue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: install-windows-3.11
Source: https://github.com/bianhaifeng789-hue/openclaw-config/tree/main/skills/tb2/install-windows-3.11
Command: npx skills add https://github.com/bianhaifeng789-hue/openclaw-config --skill install-windows-3-11-bianhaifeng789-hue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides step-by-step guidance to install and run legacy Windows 3.11 in a QEMU virtual machine and expose its display over VNC and a web-based noVNC interface for remote visual verification.

Core Features & Use Cases

  • QEMU configuration guidance: Recommended flags and explanations (cirrus VGA, IDE disk interface, memory sizing, snapshot mode, monitor socket).
  • Remote access setup: Instructions to expose the VM over VNC and bridge VNC to a browser via websockify and noVNC, with notes on nginx proxying.
  • Verification & troubleshooting: Practical checks for QEMU processes, QMP socket connectivity, VNC port testing, and visual confirmation strategies; useful for retro-computing labs, CI testbeds for legacy images, and preservation projects.

Quick Start

Start QEMU with a cirrus VGA, 32MB RAM, IDE disk image in snapshot mode, a monitor socket at /tmp/qemu-monitor.sock, VNC on display :1 and run websockify to bridge port 6080 to localhost:5901 so you can access the VM via noVNC.

Frequently Asked Questions about install-windows-3.11

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Windows 3.11 in QEMU and access it through a web browser?▼

To run Windows 3.11 in QEMU with web access, configure a VM with cirrus VGA and IDE disk, enable VNC, and use websockify to bridge the VNC port to a noVNC browser client.

What QEMU flags are needed for legacy Windows 3.11 virtualization?▼

For Windows 3.11 virtualization in QEMU, use flags for cirrus VGA display compatibility, IDE disk interface, 32MB RAM, snapshot mode, and a monitor socket at /tmp/qemu-monitor.sock.

How do I bridge VNC to noVNC for remote visual verification of a VM?▼

Bridge VNC to noVNC by running websockify to map port 6080 to localhost:5901, with optional nginx proxying, enabling browser-based remote visual verification of the VM.

Can I use websockify and nginx to expose a QEMU VNC display online?▼

Yes, you can expose a QEMU VNC display online by using websockify to bridge the VNC port to a web-accessible noVNC client, with optional nginx proxying for routing.

How to troubleshoot QEMU VNC port and QMP socket connectivity issues?▼

Troubleshoot QEMU VNC and QMP socket connectivity by performing practical checks on QEMU processes, verifying QMP socket connectivity at /tmp/qemu-monitor.sock, and testing VNC ports.

Does QEMU support retro-computing setups for 16-bit Windows systems?▼

Yes, QEMU supports retro-computing setups for 16-bit Windows systems by providing specific display compatibility like cirrus VGA and IDE disk interfaces required for legacy environments.