Open index.html in Edge, Chrome, or Firefox. No install, build, server, or internet connection is needed. Keep all files together. For recording, use the title bar's maximize button or your browser's fullscreen shortcut (usually F11).
Type these commands, pressing Enter after each:
ping google.com
ipconfig /all
ipconfig /flushdns
ipconfig /release
ipconfig /renew
ping google.comThe first ping fails to resolve the host. Wi-Fi starts with 169.254.45.12 and mask 255.255.0.0, without a default gateway. Renewal obtains 192.168.18.105, mask 255.255.255.0, and gateway 192.168.18.1. The final ping returns four replies and 0% loss.
For Scene 3's release/renew demonstration, first run ipconfig /renew, then cls before recording to start with a working DHCP configuration. During the take, run ipconfig /release followed by ipconfig /renew. New tabs and F8 still start with Scene 4's APIPA problem. The simulator does not include Windows' static/DHCP settings screen. On a real PC, enable automatic/DHCP addressing before this sequence; renewal may return the same address as before.
- F1 / dropdown arrow: open command guide, font size, optional IP highlighting, and instant output.
- Plus button: open another terminal tab with a fresh APIPA problem. Each tab has its own network state, output, command history, and unfinished input. Commands keep running in their own tab when you switch.
- Tab title: switch sessions. Tab ×: close that session and cancel its running command. Closing the final tab creates a fresh session.
- F8: restart only the selected tab with the original APIPA problem and an empty screen.
- cls / clear / Clear-Host: clear the screen while keeping the network state.
- Up / Down: previous commands. Tab: complete a partly typed command.
- Ctrl+C: interrupt the current command. Text selection still supports copying.
- Maximize: fullscreen. Minimize and close hide the simulated terminal; Return restores it.
Tabs are temporary: refreshing or reopening the page returns to one fresh session. Appearance and rehearsal-speed controls apply to all tabs. When a tab title has keyboard focus, Left/Right, Home/End select tabs and Delete closes one.
The initial 26 px bold Cascadia Mono font and colors match the supplied screenshot. Cascadia Mono/Code is used when installed; Consolas and monospace are fallbacks. Font rendering can differ by OS and browser zoom. Keep browser zoom at 100% for the reference size.
Also supports ipconfig, ipconfig /?, ipconfig /renew "Wi-Fi", ipconfig /release "Wi-Fi", ping -4 google.com, ping -n 2 google.com, ping -t google.com (stop with Ctrl+C), and pings to 127.0.0.1, localhost, 8.8.8.8, 1.1.1.1, or 192.168.18.1.
This is a bounded terminal simulator, not PowerShell. Nothing executes on the operating system. Commands, addresses, adapter hardware, lease dates, DNS resolution, packet replies, and timings are fictional fixtures. Unsupported commands/options are not executed. There is no Teams scene, countdown, quiz, or automatic command typing.
Windows output differs with language, Windows version, installed adapters, IPv6 settings, DNS answers, permissions, and the actual fault. These fixtures reproduce representative English Windows formatting for this specific scene; they are not guaranteed transcripts of another computer. In particular, /release behavior and errors on an APIPA interface can vary. This fixture models successful removal of its IPv4 configuration while retaining link-local IPv6.
The scene assumes the router/DHCP service becomes reachable when /renew is attempted. Renew also works without first flushing DNS or releasing: those commands are not an artificial unlock sequence. Flushing DNS does not repair APIPA; an APIPA address can still communicate with compatible peers on the local link, but does not provide normal routed internet access. A loopback ping tests the local TCP/IP stack, not physical network hardware.
References: Microsoft ipconfig documentation, Microsoft ping documentation, and IPv4 link-local addressing, RFC 3927.
Run node --test tests/*.test.cjs for the deterministic command checks and tab-controller checks. Tab tests use a DOM test double; they do not verify browser rendering. The website itself has no runtime dependencies.