Asghan: The Dragon Slayer (demo)

Silmarils, 1998. Fixture: test/binaries/win98-games-a-d/Asghan-demo-SW-D3D-Glide.exe (13 MB), a WinRAR self-extractor (RAR 2.x payload: readme.txt, _setup.exe, _start.exe, *.IO data, sst1init.dll, DirectX setup DLLs).

Next: why the Extract press does not hit the child button (hit-testing of WAT-native dialog children created from this template), and what exe+0x40329c checks for IDOK (it starts with call 0x40d246 and returns 0 when that fails). Alternatively unpack the RAR host-side once a RAR-capable extractor is available.

Status 2026-10-06: parked (claude:d10ba697); TODOS NEW-GAME-ASGHAN-DEMO-20261006.

Un-parked: install, setup and gameplay (claude:202b4b39, 2026-10-06)

Correction: the SFX Extract click works (claude:202b4b39, 2026-10-06)

The in-emulator WinRAR SFX extracts the whole archive; the earlier "Extract never produces WM_COMMAND" reading was a budget artifact. A held click on Extract (241,270) does reach the button (it takes focus, and readme.txt, _setup.exe and _start.exe are written within 6,000 batches). The [input-route] down ... candidates: 0x10002 dlg line only names the top-level window the press routes to; the child is resolved after it. RAR decompression is CPU-heavy: all 117 files are out after ~310,000 batches (7.5 s here) and the SFX then exits. 116 are byte-identical to the host-side node-unrar-js extract (_start.cdp differs only because the registered tree holds the post-setup copy). A 40,000-batch run stops after ~13 files with no .IO data, which is what looked like a failed click.

node test/run.js --exe=test/binaries/win98-games-a-d/Asghan-demo-SW-D3D-Glide.exe \
  --exe-guest-path='c:\asghan.exe' --quiet-api --stuck-after=0 \
  --max-batches=400000 --input=700:mousedown:241:270,720:mouseup:241:270 \
  --save-vfs=OUT --save-vfs-prefix='c:\'

Private browser movement verified (2026-11-02)

Run 20261102-asghan-native-browser closes the browser-input gap for the registered asghan_demo installed software build. One original invocation used the private loopback route index.html?candidates&app=asghan_demo&no-log, native headful Chrome 151.0.7922.108, 1024×768 viewport, cross-origin isolation and guest workers. The host renderer stayed at its default webgl; the guest ran the registered _start.exe software renderer. No renderer override, guest patch, injected game state or CLI replay was used.

The shipped readme says Up runs forward. After reviewing the title, a balanced Enter press opened the visible NEW GAME menu; a second balanced Enter started the level. The opening castle camera view was not counted as gameplay. A neutral capture then showed Asghan standing on the wooden pier.

Reviewed full-page captures (paired canvas captures are also preserved):

Phase File in the run directory Observation
Before 05-movement-before.png Standing on the wooden pier; no keys held.
Held 06-movement-up-held.png Running on the adjacent ground near the rock wall; pier and camera view displaced.
Released 06-movement-up-released.png New location retained as the run animation ends.
Settled 06-movement-up-settled.png Standing at the new location after release.
Later neutral 07-movement-neutral-confirm.png Same ground/wall location retained without further input.

All six native key events were trusted and balanced: two Enter pairs and one Up pair. Up was requested for 1,500 ms and actually held for 1,965 ms including capture overhead. A forwarding observer recorded the real renderer input consumption: VK38 WM_KEYDOWN then WM_KEYUP; the held sample had physical and async state true, and the settled sample had both false with an empty queue. The immediate released sample still had the key-up queued; consumption was recorded 9 ms after native release. This is actual browser player movement, not a title/menu capture or a claim inferred from input dispatch alone. Combat, audio, level completion and sustained play were not evaluated.

Identity: _start.exe SHA-256 29069cc0d8e81ebb601fe70fac62a29c637eec4371946fc3bd4c64c60f275ca5; browser manifest af9b9c136595e3b8496cd6c07b368b1912f8699238814873f32d989627540957; wasm 6d9563ff4a1c089c9d0ac4153748411990dc3c92f3a50e2509bbe9ffaaca30a7 (2,069,384 bytes), from the coherent locked build after GL commit 93793279e. All 120 installed files (30,448,512 bytes) matched the earlier local observed readiness hashes; this is not an upstream comparison. The historical SFX path mentioned above is absent locally. The immutable transfer verified all 2,985 members before and after extraction and explicitly included the runtime lookup asset src/api_table.json. Source/compiler, served-byte, original-file and module hashes are retained in the run. The optional system-data lookup test/binaries/tlbs/stdole2.tlb returned 404 in this transfer; level loading and movement still worked. No claim is made for applications needing that omitted system-data asset.

The controller and Chrome exited 0, the static server closed, the temporary browser profile was removed, and no keys remained held. Guest natural exit is unknown: the controller closed the browser after the neutral confirmation. Evidence retrieval, delegated own-boat shutdown and publication records are in the run's result.json, final.txt, and RECOVERY.md.