Jedi Knight demo — current original launcher blocker

Ordinary licence acceptance and the 28-file original installation remain accepted. On 2026-11-03, exact original acquisition and recovery succeeded: all 361 observed mappings and 28 installed originals matched full SHA-256.

The latest ordinary installed Jedi.exe session uses genuine pinned DSOUND.VXD and DDHELP.EXE through supported explicit VFS mounts. All four original file checks pass; the prerequisite predicate returns zero and reaches 0x402905. This is file-only provisioning, not a complete DirectX installation or native driver execution. All28 originals, 136 observed VFS entries and 76-key registry remain unchanged; existing builtin execution policy is preserved.

The first new blocker is WinExec's unquoted long-path handoff: the runtime looks for absent C:\Program.exe rather than the installed JkDemo.exe and returns 2 on both original attempts. The personally reviewed capture shows the original “Unable to start” dialog. No child engine starts; gameplay, game input, audio and FPS remain unqualified. No direct engine launch was followed.

Next: establish faithful Win98 launch/path and short-name behavior before a focused repair and another bounded ordinary Play. See current trace, identities, recovery and shutdown evidence. Own boat bx_k44k9b4f was stopped after evidence retrieval; snapshots-disabled metadata removal leaves info404/list absence/preview410, with the terminal STOPPED receipt explicitly unavailable. No worker/session is retained. The earlier missing-file trace and genuine prerequisite provenance remain historical evidence.