Outlaws original Windows demo — verified acquisition

Task: NEW-GAME-OUTLAWS-DEMO-20261015.

Initial source audit 2026-10-15 by /root/new_game_refill_after_kkrieger against origin/main d001064bf3cfab6808f7dc3646718667da3b8679. Source-only refill for the standing two-new-game pipeline. No package downloaded, executable inspected, installer run, licence answered, or gameplay qualified in this task. That initial audit did not acquire bytes; the completed acquisition below supersedes its unknown package identity. Runtime still requires a separate grant. Main integration of these notes is a coordinator action.

November 12 covered turn/release calibration; store entry still blocked

Run 20261112-outlaws-covered-turn-east-stairs-health-0904 freshly restored all nine preferred0802 door files into an empty VFS, checked raw bytes, and loaded through native Enter after thumbnail hover. Living rendering stabilized for300ms; subsequent genuine movement kept health0.599999845. No healing, new mission consequence or new save was earned. All14 sets/126 files passed raw/gzip hash checks again.

Original EXE trig routine0x4af8e0 masks its angle with0x3fff; actor-angle code0x432c50 also masks the high-word yaw at actor+0x32. Thus a full turn is16384 units, not65536. The old supposed-east target64500 reduces to15348 (337.24 degrees, near +Z), not east4096. Run-local native-nav.py now records yaw14=(rawYaw & 0x3fff) and degrees; raw actor yaw is retained. Coordinate directions are +Z=0, +X=4096, -Z=8192, -X=12288. This is a helper interpretation correction, not an emulator patch.

Covered Right180 moved raw yaw48673→49207 and Left600 moved49207→45668. Each release remained stable through1.8s idle with keys empty and HP/position unchanged. Separate native Escape resume/idle, unlocked mouse +100X, click-to-Resume and live left-click controls did not change yaw/position. Later Space100 and ordinary Up100 also preserved yaw49461 after release through1.8s idle. Full before/released/idle PNGs were individually reviewed; read-only sampled state is retained. Pointer lock stayed absent: relative mouse behavior and the0833 persistent-turn cause remain unisolated. No emulator regression is established by these controls.

The changed eastern south-window attempt reached(126.992744,0,166.498993), yaw49461 (masked309,6.78955deg), then one native Shift+X+Up300 ended outside at(127.759369,0,165.881165), same HP. The frame remained a solid wall; this does not prove the window permanently impassable or jump height. Up100 later ended(127.936981,0,166.438568), same yaw/HP and released keys. The actual blocker is safe store entry: the eastern iron door near(133,202) connects inside the store to the stair landing, and neither this exterior window nor the previously attempted western entry has been demonstrated traversed. No further low-health crawl or repeated western exposure was attempted. Next work must establish a changed, native traversable store entry before claiming the eastern descent/canteen; the distant jail remains unattempted.

All204 remote evidence paths/172 unique raw hashes were recovered and checked before normal stop. Runtime/Chrome closed normally; remote parent wait/EOF and process absence passed. Box bx_3tfqraze is archived, expiry cleared, stop_ab0b498fb1f8af22 completed unforced; watchdog exited0 without firing. The local long-running launcher tool returned143, separately recorded rather than substituted for the independently verified remote runtime-parent result.

November 12 covered-health approach remains open

Run 20261112-outlaws-door-open-covered-health-onward-0833 earned no new health, mission consequence or save. The western store approach died after turn/movement interpretation drift; native mouse effects and helper behavior were not isolated, so no emulator defect is established. The unchanged whole9 door checkpoint then passed authentic restore/readback, native Enter Load, stable living rendering300ms and fresh Shift+Up180 to (120.999916,0,162.384171), unchanged health0.6. This position was not saved. All14 sets/126 files, including the1.4-health key alternative, remain intact.

Read-only original data identifies a remaining basement canteen at (128.73,-10.75,193.27), reached through the store's eastern iron door near (133,202), then northbound stairs x134–143 descending to-10.75. Landing and basement BGY records do not establish whether those actors remain alive. This is a candidate route, not a safe-route result. JAILDOOR01–05 share OBJECT102 with the opened telegraph door and are another onward candidate. The fresh worker calibrates native turn/release from cover before exposure; it must not repeat consumed street-supply searches or assume western entry.

The coordinator checked202 references /185 unique raw hashes, full attempt and reloaded movement images. Exact25ac/75ec remains pinned; no code/build/ commit or healing claim. The box stopped normally with actual runtime/Chrome wait0/EOF; outer transport143 remains separate. See the run's recovery notes.

November 12 authored shove, Steel Key and opened door102

Run 20261112-outlaws-authored-vertical-use-key-route-0802 found original sector253 named SHOVE_ME. TOWN.INF event32/MORPH_MOVE2 scripts it west4. Native crouched Space performed that shove, cleared the previously diagnosed collision, and allowed genuine entry. Steel Key pickup text and the acquired ISTEEKEY/GSTEEKEY inventory record were retained. Ordinary Space then opened TELEGRAPHDOOR02/door102, with its leaf moving west5 as authored.

Preserve both new whole-nine sets and their pins:

Both sets passed fresh whole-nine VFS restoration/raw readback, ordinary Load, stable living rendering300ms and fresh movement. From the door save, native Shift+Up180 crossed the genuine doorway to (120.148949,0,166.426819), health0.6 unchanged. This final outside position was not saved. Original108 ancestral files remain unchanged. No healing or mission completion is claimed.

Two initial key-load checks incorrectly demanded exact yaw despite native menu mouse movement; those exposed attempts died. Saved living bytes remained unchanged. Corrected native Enter Load records yaw and verifies position, health and rendered stability, rather than enforcing the false yaw predicate. Both successful reload/movement results and failed attempts remain retained.

The coordinator checked393 references /328 unique raw hashes, both complete raw/gzip save sets, full key/door/fresh-movement frames and original script/live geometry. Source remains exact25ac/75ec, with no emulator fix/build/commit. The box stopped normally; actual runtime owner/Chrome and watchdog waits passed, with outer transport143 separate. The next task seeks covered native health and onward progress from the door-open checkpoint, retaining the1.4 alternative.

November 12 native aperture collision cause

Run 20261112-outlaws-aperture-collision-key-route-0738 tested a changed southern approach with bounded passive native tracing. Blocking branches 0x4e6825/0x4e6833 after recursive query0x4e6990 selected two walls: raised sector253 corner0x10d9414, floor4.25, and aperture73 southern lip0x1193374. Crouching reduces height5.99→2, fitting the opening's3-unit clearance, but keeps radius1.5. Original wall test0x4e80a0 expands the wall interval at each end by radius, rather than using the previously hypothesized circle-corner metric. The raised obstacle extends south149.5+1.5=151; aperture73 requires center z≤150.5 at its south boundary. These forbidden extents overlap0.5. This explains the horizontal stall for this approach; no emulator defect or global impossibility of earning the key follows.

The unsaved diagnostic ended (134.760681,.25,150.270660), health2.2, without x134 crossing, SteelKey or door102. All nine restored VFS files remain byte-identical, and all12 ancestral sets/108 files remain preserved. Continue from the0710 east-threat whole9 save. The next investigation targets authored vertical/use behavior or a different access route; repeated horizontal crawls and unsupported counter jumps add no evidence. Actor+0x38 is a sector pointer; earlier helper fields calling it a descriptor do not prove actor metadata.

The coordinator checked172 references /149 unique raw hashes, the full final native frame and causal trace summary. Runtime remains exact25ac/75ec, with no source change/build/commit. Tracing affects timing and is not a benchmark. Some initial intermediate captures were reviewed only at final audit; completed live/paused frames were reviewed before dependent actions, and later diagnostic frames were each reviewed before further action. Actual runtime owner wait0/EOF, Chrome0 and normal box stop passed. Outer client143/missing client wait remains separate. Exact findings/recovery are in the run's RESULT.md/RECOVERY.md.

November 12 east gunman defeat and aperture limit

Run 20261112-outlaws-east-corner-threat-supplies-0710 identified the armed east-corner gunman directly in view and defeated him with one aimed native shot: loaded ammunition4→3, health stayed2.2. Full upright/collapse images and authentic saved actor data establish the new corpse at (148.73146,0,157.70334). Attribution of the earlier unseen bullet remains an inference.

Prefer all nine east-threat-saves/ with east-threat-save-pins.json. Saved position (127.880249023,0,161.501007080), yaw37279, health2.2; ninth raw 229741 bytes, SHA256 9e1b6f21a928ed066d7fd5919892d9c4bbf5aa93e0f4d3e484cbe852b801193f. Normal Load of the explicitly highlighted ninth slot restored that exact rendered state stable300ms, with the corpse present. Fresh crouched movement reached (134.591629028,0,161.501007080), unchanged health; it was not resaved. Hover and review the ninth row before clicking: an initial bare click selected an older living slot, which failed exact-state validation and was paused. All99 ancestral save files remain unchanged.

The cleared corner allowed a north approach without damage. Calibrated west movement entered floor.25 near (135.14352,149.57620); one settled crouch attempt stalled near x134.980 and ended x134.782, still health2.2. No x134 crossing, SteelKey pickup, door102 opening or healing follows. Native collision cause remains unknown; the fresh successor must isolate it or find a different authored approach before another attempt. Nearby street supplies were absent from the authentic saved state; global medical-item defaults are not possession.

The coordinator verified464 references /372 unique raw hashes, complete new raw/gzip saves and full armed/collapse/reloaded-movement images. Exact source remains25ac5466d/WASM75ecda5701, with no code/build/commit. Runtime actual wait0/EOF and independent PID/profile/port closure passed; the box normally stopped before expiry. Outer transport143 is separate. See the run's RESULT.md and RECOVERY.md for exact pins and native input controls.

November 12 two further defeats and frontage save

Run 20261112-outlaws-frontage-threat-key-route-0630 defeated the bank redshirt and a separate western lightshirt through native firing, hit reaction and continuous collapse. Preserve all nine frontage-saves/ files and frontage-save-pins.json. The ninth file is230345 bytes, SHA256 68f93d1bedf3643736e60bbba58c6f919bfbb1929297fb4d18c6afe02926ec32. The saved position is (83.264503479,0,185.097595215), yaw41029, health2.2. Normal Load restored that rendered state stable300ms with the fallen attacker; fresh crouched forward movement reached (83.068260193,0,177.684265137) at unchanged health. That movement was not resaved. All11 ancestral whole sets (99 files) remain unchanged, including the earlier4.6-health alternative.

An unsaved eastward branch reached (137.371292,0,160.434662), where an out-of-view attacker reduced health2.2 to1.0. This shooter remains unidentified; the western lightshirt defeat does not establish that it was the earlier aperture attacker. No aperture crossing, SteelKey pickup, door102 opening or healing was proved. The fresh successor investigates that threat or supplies before another exposed approach.

The coordinator checked737 recovered references /610 unique raw hashes, complete new raw/gzip saves, full aftermath and reloaded movement images. Runtime remains exact25ac5466d/WASM75ecda5701; no code/build/commit was needed. The box stopped normally before expiry, with runtime parent/watchdog wait0/EOF; outer transport143 is reported separately. Exact recovery is in the run's RECOVERY.md.

November 12 healthier combat successor

Prefer the whole nine combat-saves/ and combat-save-pins.json from 20261112-outlaws-earlier-gunman-health-successor-0558. Earlier close-range interception defeated the tracked doorway gunman while preserving health4.6, instead of0.2. The hit and continuous collapse were reviewed. Native Save recorded (105.79972,.25,183.37161), yaw45471, health4.5999999046; ninth raw 229536 bytes, SHA256 3b4dcbb2caab03ea677d9bbb73124de7a37bf1709a2c0fdcae96dc069a05bbfc. Normal Load restored the rendered exact state stable300ms and fallen attacker. Fresh crouched backward movement reached (108.70386,.25,182.90546) at unchanged health; it was not resaved. Parents and the older low-health combat set remain unchanged fallbacks. This is damage avoided, not healing.

An unsaved outside branch still encountered the bank shooter and a further close attacker. It ended alive near (136.331,0,150.447), health2.2, without crossing x134 into aperture73. No SteelKey pickup or door102 opening follows. Original IDOCBAG COUNT3/MAX15 are item defaults, not current possession proof. The next worker addresses surviving threats from the healthier save.

The coordinator verified631 recovered references /541 unique raw hashes, all nine raw/gzip saves and full hit/collapse/reload/movement images. Source remains25ac5466d/WASM75ecda5701, with no production change or build. Runtime parent wait0/EOF and normal box stop passed; outer transport143 is separate. The run's RESULT.md and RECOVERY.md retain exact continuation and the helper C-timer cleanup correction, which was not rerun against the original.

November 12 gunman defeat and living combat save

Run 20261112-outlaws-store-native-heal-shooter-0525 tracked the actual black-hatted, light-shirted attacker firing and moving through the store doorway. Native centered revolver shots produced blood/hit reaction and a continuous collapse sequence. The fallen body persisted through normal Load and fresh movement. This establishes an enemy consequence beyond a single prone image. Other enemies and permanent safety are not ruled out.

Preserve all nine combat-saves/ with combat-save-pins.json from that run. The ninth raw file is230314 bytes, SHA256 386585cd8141512575b061c4f662b8de334825a82f0d994127dc477207605a4c. Native Save recorded (105.79972,.25,183.37161), yaw42300, health0.199999869. Normal Load restored the exact rendered state stable300ms, with the attacker fallen; fresh crouched backward movement reached (107.00921,.25,185.51430) at unchanged health. That movement was not resaved. First eight files and all parents remain unchanged.

This is a living low-health combat checkpoint, distinct from earlier dead .2 branches. Do not take it along the old exposed aperture approach. Healing remains unproved: inventory attempts showed Crowbar, with no reviewed MedicalBag label or use. A new attempt starts from whole store5.4 to reproduce the defeat earlier or obtain native health before further route exposure. No aperture traversal, SteelKey pickup/use or door102 opening is claimed.

The coordinator checked570 recovered references /472 unique raw hashes, all nine save gzip/raw hashes, and the full upright/hit/collapse/reloaded-movement images. Tested source remains25ac5466d/WASM75ecda5701; no production code, build or task commit changed it. Runtime parent wait0/EOF and normal box stop passed; outer transport143 is separate. Exact whole-set recovery is in the run's RECOVERY.md.

November 12 SteelKey route and living fallback

Runs 20261112-outlaws-steel-key-telegraph-door-0418 and 20261112-outlaws-telegraph-counter-alternate-route-0458 identify original GSTEEKEY → ISTEEKEY, USE102, matching TELEGRAPHDOOR02/object102. The locked door visibly requires the steel key; pickup and opening remain unproved. Native Space opened the separate TELEGRAPHDOOR01.

Original geometry offers a raised barred counter, the locked south door, or the low east aperture into the rear room. Counter jumping failed. A changed fresh crouch/settle approach reached (134.762,.25,149.806), consistent with the earlier blocked endpoint. The next resume produced explicit “You got shot to death!” before further movement. This proves neither aperture entry nor a new collision limit. A future attempt must address the shooter or verify native MedicalBag healing before another continuous crouched approach. Charges remain unknown; no kill or safe cover is inferred.

Retain the whole nine onward-saves/ from run0418 with onward-save-pins.json: saved store health5.4 at (105.800,.25,183.372), yaw43470, ninth raw SHA256 8f187147e1a189cdccef748f33a21875ae446f157651e4497144dc8150ea2c5d. Run0458 actually restored all nine into a fresh empty matching VFS, verified all raw bytes, normal-loaded the rendered exact state stable300ms, then proved fresh movement alive at health4.6. Movement was not resaved. The whole frontroom-saves/ at health3.8 also passed fresh restoration and living movement. Keep all parent sets; exclude both .2-health/dead branches. Run0458 RECOVERY.md contains the exact continuation recipe.

Tested runtime remains Git 25ac5466d… / WASM 75ecda5701…; later shared renderer changes were excluded. No production change or build was made. The coordinator verified 430 recovered references / 344 unique raw hashes and the full death/living-store images. Actual runtime wait0/EOF and normal box stop passed; outer transport143 remains separate. A Stop All → relaunch null-memory find_window error occurred on this legacy host. A fresh host page worked; no current-main reproduction or generic cause is established.

Selection and provenance

Selected Outlaws (LucasArts, 1997), updated original single-player demo. git grep -n -i outlaws origin/main returned no matches, including public DESKTOP_APPS, candidate corpus, TODOs, and investigation notes. Shared copies of those files and handoffs also had no match. git log --all searches for Outlaws commit subjects and the two plausible re-note paths found no history. This is a new title relative to that observed repository coverage; these negative checks do not assert knowledge of unrecorded external experiments.

The primary publisher document is the LucasArts Archives III Quick Start Guide, printed pages 8–9 (PDF pages 8–9, zero-based 7–8). Its Super Sampler 2 section describes Windows 95, DirectX, an Outlaws demo installation screen, single-player versus single-plus-multiplayer choices, and the installed demo launcher. The launcher provides play, readme, troubleshooting, sound/video configuration, and video mode selection. This establishes an original publisher demo and normal route; it does not establish that the separately archived updated download has identical installer packaging.

Paleface's historical demo page links its 13.5 MB single-player demo directly to ftp://ftp.lucasarts.com/demos/pc/outdemo_v2.exe. That exact link was read from the HTML on 2026-10-15 (the browser text rendering omits FTP links). The page describes one Sanctuary level and lists multiplayer and retail patches separately. This is a historical third-party pointer into the publisher's domain, not a freshly validated publisher download or byte-authenticity proof.

The Internet Archive item and metadata endpoint identify the item as Outlaws Demo, creator/publisher LucasArts, 1997, and describe the updated single-player version with optional 3Dfx graphics, Aureal sound and an alternate multimedia sound driver. These are archive metadata claims, not measured API requirements. Read-only metadata and HEAD observations at 13:48 UTC:

Field Observed value
Package outdemo_v2.exe
URL https://archive.org/download/outdemo_v2/outdemo_v2.exe
Size 14,186,356 bytes
Metadata SHA-1 5568d44da014b6be21d105b1149ec022c10c0655
Metadata MD5 ccd7678d2276fe1b39cef399598d4a6d
Metadata source/format original / Windows Executable
HEAD HTTP 200; Content-Length 14186356
HEAD final URL https://dn711100.ca.archive.org/0/items/outdemo_v2/outdemo_v2.exe
HEAD Last-Modified Sun, 19 Jan 2014 22:45:26 GMT
SHA-256 / downloaded-byte verification Unknown; no package GET performed

The archive's original field describes upload lineage, not a publisher signature. Do not use archive screenshots as Wine-Assembly evidence. Other search results named oldemo.exe, a modern Windows batch wrapper, retail updates and full-game uploads; none is the selected artifact. No alternate engine, remaster, retail disc, patch or replacement DLL is part of this lane.

Initial bounded acquisition plan (completed below)

Owner: coordinator-assigned acquisition worker after an explicit grant. Use an isolated remote directory, preserve this host's free-space floor of 2 GiB, and initially reserve 256 MiB remotely. Do not acquire a full sampler ISO.

  1. Save fresh metadata and response headers with retrieval UTC and final URL. Download only the exact 14,186,356-byte package above, bounded to 120 seconds and 20 MiB. Reject HTTP/error pages, unexpected size, or either metadata digest mismatch. Record computed SHA-256 as the recovery pin and retain the original immutable package. An example acquisition command for the granted remote directory is:

    curl --fail --location --max-time 120 --max-filesize 20971520 \
      --dump-header outdemo_v2.headers \
      --output outdemo_v2.exe \
      https://archive.org/download/outdemo_v2/outdemo_v2.exe
    sha256sum outdemo_v2.exe
    sha1sum outdemo_v2.exe
    md5sum outdemo_v2.exe
    stat -c %s outdemo_v2.exe
    
  2. Inspect PE/container identity and list members without executing. Discover the actual package format before choosing an extractor. Bound listing and extraction to 60 seconds each; reject traversal/absolute member paths and halt if declared expanded content exceeds 256 MiB. Do not guess an InstallShield format or reuse Jedi's extractor on filename similarity.

  3. Read the original readme/help/licence and setup metadata. Record version, actual executable names, arguments, working directories, asset paths, required registry values and default controls. Inventory every original payload file with SHA-256. OLWIN.EXE is only a search lead until confirmed by this package; there is currently no registered app ID or launch command.

  4. Determine whether original installation is required. Static extraction alone does not prove installed registry/configuration. Preserve the normal launcher path. If setup generates a child, capture its actual bytes, arguments, cwd, VFS and registry rather than inventing installed state. Stop at any licence choice; do not supply an automatic acceptance.

  5. Commit the verified recovery recipe, inventory and original readme-derived launch instructions. Only then prepare nonpublic candidate registration under a distinct proposed ID outlaws-demo. Keep binary assets ignored.

Acquisition done criteria: exact package digests verified, original readme reviewed, reproducible bounded extraction/installation plan, full payload inventory, and explicit unresolved launcher dependencies. A failure to obtain these is an acquisition blocker, not an emulator regression.

Later runtime proof criteria (not granted)

After acquisition review, obtain the serialized temporary-box runtime slot; IW and Jedi currently own the runtime queue. Begin with a bounded 120-second ordinary original setup/launcher observation with no licence input. Record source tree, compiled module and fixture digests, process result and cleanup. Choose the original default software/video path if the package offers one; do not add retail graphics updates or wrappers to make a launch succeed.

Gameplay qualification requires the actual demo level, ordinary menu/input navigation, an idle baseline followed by held/released movement and turning, and a visibly changed player view attributable to those inputs. Confirm key release and retain a reviewed full-frame gameplay screenshot with run/source identity. Read controls from the acquired original documentation before programming input. A menu, attract sequence or archive screenshot is not player-control proof. Retain failures, hashes and cleanup receipts under a unique scratch/runs/ directory; write result.json last under the ops capture convention. Report frame rate, audio, combat, save/reload and session stability separately, and leave each unmeasured property unknown. No public deployment or redistribution follows from source readiness or runtime success.

Validation of this document: source URLs/HTML and archive metadata inspected, HEAD length matched metadata, current-main coverage and history searches completed, and git diff --check passed. There was no local fixture creation, build, browser, VM or runtime test.

Verified acquisition, 2026-10-15 13:56–13:58 UTC

Owner /root/outlaws_original_acquisition, branch task/outlaws-original-acquisition, source base b5a7e11db. Jedi owner explicitly released process 141587 after exit 0 and postflight 13:55:49.897Z. Independent receipt read and fresh process inventory at 13:56:21.859Z found no active game/build/browser before acquisition.

The exact package downloaded in about 3.5 seconds on bx_9ef2wdsw:

Field Verified value
Bytes 14,186,356
SHA-1 / MD5 Both match the table above and fresh metadata
SHA-256 501f37aa475b6c27c87ce04e30b5207f91b81603cb376aaa9ffde1647a40e7b3
Container ZIP self-extractor, 22,255-byte PE32/i386 stub
Payload 31 members, 23,300,090 expanded bytes, every CRC verified
Preserved remote directory /home/user/outlaws-original-acquisition-20261015
Payload directory payload/ within that directory

7z l -slt identified ZIP and listed members before extraction. The hash-pinned extractor validates all paths, encryption/symlink flags and expanded size before writing a new directory, and never executes the SFX. All 31 original records, including CRC, SHA-256 and PE identity where applicable, are in outlaws-demo-inventory.json. WDIRNOP.COM and wdirnop.com are identical five-byte files with identical SHA-256. Both remain preserved on the case-sensitive host; a later Windows VFS manifest must map that equivalent case-insensitive name once, with the duplicate explicitly recorded. No original member was changed or removed.

Original documentation and normal launch

readme.txt is README V7.0; ol.ver says DEMO 1.1W, Build 1. The original README explicitly instructs creating a directory (example C:\OUTDEMO), extracting the downloaded self-extractor there, then opening OLDEMO.EXE. This download does not require the CD sampler's installer or launcher. No command-line arguments are documented. The next ordinary launch is therefore C:\OUTDEMO\oldemo.exe, empty arguments, cwd C:\OUTDEMO, with the complete original payload available beside it. OLWIN.EXE is absent.

The actual game is oldemo.exe, 1,298,944 bytes, SHA-256 46b72a094e891494cfa8f411d1942ea9dd7f06151d28f2af4bc1c1dca1e4ec79, PE32/i386, six sections, image base 0x400000, entry RVA 0xf10d0. Original configuration executable olcfg.exe is 64,512 bytes, SHA-256 52cab1f49d16e3c9b58455a9101e1c788c62088c2826d432e4631f23a1c22d79. Assets include outlaws.lab, start.san, end.san, and the supplied DLLs.

README requirements include Windows 95, Pentium 60, 16 MB RAM and DirectX 3.0a. regpatch.lst declares Demo Default display driver LECDDRAW.DLL and sound driver LECDSND.DLL. It is package data, not permission to fabricate registry state. There is no separate registry installation instruction in the README; actual initialization and configuration writes remain unobserved. Start with the original default path and clean guest state. Resolve failures from actual loader/API evidence rather than installing replacement DLLs.

Outlaws.doc is a Word 95 troubleshooting guide, decoded using catdoc without running Office. It describes OLCFG.EXE display and sound selection, including 320×200 DirectDraw, original Window display mode and MGL alternatives. Window mode recommends an 800×600 16-bit desktop and documents no mouse control in that mode. Alternatives require later ordinary UI observation, not patched configuration. DirectDraw is the first/default path; no Glide dependency is assumed merely because optional original Glide DLLs are present.

Default controls from the README: Up moves forward, Left/Right turn, Shift runs, Space nudges/opens doors, X jumps, C crouches, Ctrl fires, R reloads and Escape opens options. The README labels Down as "Move Down"; its actual behavior is untested. Do not substitute WASD without observing the in-game configuration. Later movement proof should use held/released Up and Left/Right with an idle baseline and retained screenshots.

The README includes the original licence: original-form noncommercial copying, restrictions on modification and reverse engineering subject to applicable law, and warranty/liability terms. This is a record of the included text, not a legal conclusion or an acceptance action. No licence UI was encountered or answered, and no guest executable was run.

Recovery and next prerequisites

On a granted remote host with Node, 7z, curl and file, choose a new absolute directory and run the committed recipes:

node tools/acquire-outlaws-demo.js /home/user/outlaws-recovery-UNIQUE
node tools/extract-outlaws-demo.js /home/user/outlaws-recovery-UNIQUE/outdemo_v2.exe /home/user/outlaws-recovery-UNIQUE/payload

The acquisition recipe enforces 120 seconds/20 MiB for the package and fresh metadata identity; extraction uses JavaScript validation and inventory around 7z listing, CRC testing and extraction, with a shared 60-second deadline and 256 MiB expanded bound. JavaScript independently checks each extracted CRC, size, SHA-256 and PE identity. Recovery must compare the generated inventory against the committed inventory before launch. Do not overwrite this run or retain fixtures locally where they would break the 2 GiB free-space floor.

Compact receipts live in shared scratch/runs/20261015-outlaws-original-acquisition/receipts/: fresh metadata, headers, acquisition/list/extract receipts, full original README and decoded troubleshooting text, inventory, and postflight. Original package and all bytes remain remote. Postflight at 13:58:35.923Z verifies all 31 payload hashes and package SHA-256 unchanged, active process inventory empty; acquisition slot was released to the coordinator. These are acquisition receipts, not runtime or dashboard gameplay evidence.

Next prerequisite: review this identity/route and prepare a nonpublic complete VFS candidate manifest (no app registration was added here), pin a matching source/module, then obtain the serialized runtime grant for a bounded ordinary oldemo.exe first launch with no initial input. Stop on any licence choice. Runtime compatibility, registry/config initialization, menus, gameplay, audio, frame rate and control release all remain untested. Syntax and diff checks passed; the actual hash-pinned extraction and CRC/size/hash inventory succeeded.

Recipe correction: the initial 13:57 extraction used an embedded Python ZIP reader, contrary to the JavaScript-only script requirement. That historical script and receipt remain preserved remotely and in Git history. The current recipe is JavaScript plus the existing 7z CLI. Do not treat the historical run as execution of the corrected recipe.

Corrected recipe baa9fcdd1b383171fde0f152e36b433506c81bfe was independently verified after the IW owner's release: IW's 14:09:24.467Z postflight retained unchanged source/donor and no active processes, fresh inventory at 14:09:57.373Z was empty, and PID 148227 was absent from current Boat ps. The extractor ran 14:10:36.660–14:10:37.508Z into the new payload-js-verified/ directory beside the preserved original payload. All 31 complete inventory records matched the committed inventory exactly, including CRC32, SHA-256 and PE identity. Postflight at 14:10:55.195Z independently rehashed both payload copies and the immutable package, verified no active processes, and released the acquisition slot. No guest, browser or build was run.

The exact corrected script is preserved remotely as extract-outlaws-demo-js-verified.js; js-verification.json, payload-js-verified-inventory.json and js-postflight.json retain the result. Compact local receipts include js-verification-api.json, js-postflight.json, js-prior-release.json, js-preflight-inventory.json and js-release-handle.json (the last records absence from live process inventory, not an independently recovered historical exit code). The ordinary launch recipe and all untested runtime prerequisites above remain unchanged.

Current browser enemy interaction and ordinary save, 2026-11-11

Run 20261111-outlaws-current-browser-enemy-response-0740 supersedes the historical runtime-unknown statements above. It follows the successful 20261107-outlaws-worker-ne-lifecycle movement/secondary-fire evidence and uses the canonical registered outlaws_demo: unchanged test/binaries/candidates/outlaws-demo/game/OUTDEMO/oldemo.exe and its browser manifest, empty arguments, normal C:\OUTDEMO working directory. No guest state, executable, media or save bytes were edited.

Chrome 151.0.7922.71 loaded the current production guest Worker and software DirectDraw presentation. The browser's loaded-module identity and HTTP body hash both matched module 75ecda5701c15f6fe2c269455ead4e15457b90653733df15d35674b08e8849d5. Source identity is main 72e3f0c892b2a45f992898b76cdaadc3ae0523a0 plus the run's recorded relevant tracked diff and new-file patches. Matching locked build evidence was reused after checking the source fragments/module hashes; this task made no emulator change. Trusted, balanced native input controls passed locally and on the same leased box before the original launch.

The ordinary MAIN GAME → GOOD route reached the level. Full current browser images were personally inspected before each native action. Arrow movement reached the alley door beside the hotel; Space opened it. The decisive retained full frames under retrieved/original-output/ are:

SAVE GAME while dead returned without writing a save. Documented Space restarted the level normally. While living, Escape → SAVE GAME → first slot → typed e → Enter created the original game's C:\OUTDEMO\SAVE\SAVE000.OSG (186,861 bytes, raw SHA-256 54f1291541668eae68189ece9f8bcf43ead63d53efbe4f2cc89f16c354023bf8). The unchanged bytes were retrieved as save000.osg.gz; compressed and decompressed hashes were verified. It is a living start-of-level save after restart, not a saved combat/death state. Reloading it was not tested.

All 396 original remote artifact paths and the save were recovered and hash-verified before stopping, then verified again after archive. Browser, controller and their parents exited normally with actual waits and both EOFs; an independent process/profile/port inspection confirmed absence. The private 45-minute box bx_2y3bv8qs had a prearmed independent fixed deadline of 08:23:27 UTC. Delegated normal stop stop_c835a15f7de92793 completed at 07:52:41 UTC, forced:false, error null; independent GET confirmed archived, current expiry null. The watchdog exited unfired with wait/EOF evidence.

Validation: local and same-box native input controls, source/media/module hashes, matching locked-build reuse, complete artifact/save recovery checks, and documentation diff checks. Audio, frame rate, full mission completion, enemy kill count and save reload remain unmeasured. No public deployment or additional runtime prerequisite follows from this completed interaction.

Authentic save reload and surviving enemy defeat, 2026-11-11

Run 20261111-outlaws-authentic-save-enemy-defeat-0800 successfully reloaded the preceding run's unchanged SAVE000.OSG, then defeated an armed gunman while the player survived. The canonical registered outlaws_demo, original media, production guest Worker and software DirectDraw route were reused. The browser-loaded module and served response matched 75ecda5701c15f6fe2c269455ead4e15457b90653733df15d35674b08e8849d5. The tested source was main 25ac5466dac0b6a5194d953090ca0096ab400c77 plus the run's recorded tracked diff and new-file patches; concurrent renderer work was captured in those pins. This task changed no emulator code. Matching locked-build proof was reused after checking all WAT fragments and the module. Local and same-box trusted, balanced input checks passed before launch.

The retained save's 186,861 raw bytes and SHA-256 54f1291541668eae68189ece9f8bcf43ead63d53efbe4f2cc89f16c354023bf8 were verified before restoring through the ordinary VFS directory/create/write/ close APIs at C:\OUTDEMO\SAVE\SAVE000.OSG. No save or guest-state bytes were edited. Original LOAD → slot E → Enter restored the living start state. Full browser images were personally reviewed before every native action. The decisive full captures in retrieved/original-output/ are:

Escape → SAVE GAME → second slot → Enter → f → Enter wrote the authentic combat checkpoint C:\OUTDEMO\SAVE\SAVE001.OSG: 194,221 raw bytes, SHA-256 dd041c9bd7f538ae0c5deff741e16c6aa8670bcc9b85c3f91bfd571e0a712750. Both saves were retrieved unedited into authentic-saves/, with compressed and raw hashes verified; the first save still matches its predecessor hash. Reload of the new combat save, numeric kill count, audio, frame rate and full mission completion were not tested. The observed result is visible enemy defeat with player survival, rather than a kill-counter measurement.

All 232 original runtime paths and 23 control paths were recovered and hash-verified before delegated shutdown; both saves were verified separately. compact-recovery-local-map.json maps every original runtime path to either its raw local artifact or a lossless gzip object and records its raw hash. Post-archive checks reverified the complete recovery. Browser, controller and parents returned actual wait code 0 with both EOFs; independent PID/profile/ port checks confirmed absence. All 40 recorded native input events were trusted and key presses balanced. Menu document mouseup was unobserved, but both guest WM_LBUTTONUP messages carried zero buttons and native actions used a finally-release path.

Private box bx_9t365nv9 had an independently prearmed fixed 08:43:31 UTC watchdog and initial service expiry 08:43:32.100 UTC. Normal stop stop_46e831b90a43713a completed at 08:09:45.397 UTC, forced:false, error null. Independent box and stop GETs confirmed archived with current expiry null; the watchdog exited unfired with actual wait 0 and both EOFs. No worker, restart, resume, delete or deployment was performed.

Validation: authentic filesystem restore and original Load UI, full reviewed before/after enemy and health/ammunition captures, native updated Save UI, source/media/module identity, local and same-box input checks, reused matching locked build, complete recovery/raw-hash checks, and documentation diff checks.

Combat-save onward route and retained Drygoods entry, 2026-11-11

Run 20261111-outlaws-saved-combat-onward-1410 restored the preceding 194,221-byte SAVE001.OSG unchanged through ordinary VFS file APIs, then loaded second slot F in the original Load Game UI. frame-14.png confirms the prone gunman, living player, three loaded rounds and 18 reserve. The canonical original-media outlaws_demo, tested source 25ac5466dac0b6a5194d953090ca0096ab400c77 plus the parent recorded patches, and module 75ecda5701c15f6fe2c269455ead4e15457b90653733df15d35674b08e8849d5 were reused. The immutable module was resolved through scratch/usage-watch/retained-module-restorations-20261111.json; matching locked-build proof and all 1,324 provisioned files passed hash checks before and after gameplay. No emulator, media, map, script or save bytes were edited.

Shipped controls establish R reload, Space “Nudge” for doors (also revival after death), and Enter inventory use. Native movement and interaction reached new consequences beyond the parent combat position:

Native Escape → SAVE GAME → first empty slot → Enter → b → Enter wrote C:\OUTDEMO\SAVE\SAVE000.OSG: 199,852 raw bytes, SHA-256 f88b8ec7ad54bb867224a33c67fd9af3d1e5f7529c783ef997b361cf8a2164d8. The unedited export is retained as authentic-saves/save000.osg.gz with compressed and raw hash manifests. The original combat SAVE001.OSG remains byte-identical to its parent hash. Restore the new bytes through ordinary file APIs and select first slot B; second slot F remains the fallback.

This is retained door/room-entry progress and a new combat encounter, not item acquisition or mission completion. Low-health exposure to gunfire caused repeated deaths, including after the save and after both loads. A later Space action led through a loading screen back to the starting courtyard with reset health/ammunition; it is not counted as a mission transition. Native Escape pause assistance was used for menus, saving and inspection. Full current images were reviewed before every bounded action, followed by actual release and passive settling. One move's transport returned blank stdout; its remote accepted acknowledgement was inspected without replaying the input. Legacy live-key readback was null; recorded trusted key events balanced, and every click has a guest mouse-up with zero buttons.

All 860 original runtime paths, 23 same-box control paths and both saves were recovered and hash-verified before shutdown and again after archive. The lossless compact-recovery-local-map.json retains every runtime path/hash; 175 PNGs passed CRC and IDAT checks, 80 inputs have current-image review/hash bindings, and all 167 recorded input events were trusted. Browser/controller and parents exited normally with actual waits and both EOFs; independent PID/profile/port checks confirmed absence. Private box bx_n8ufhbqa had an independently prearmed fixed 14:49:33.916 UTC deadline and initial service expiry 14:49:34.211 UTC. Normal stop stop_d6e1e51335b5abe2 completed at 14:29:15.578 UTC, non-forced with no error; independent GETs confirmed archived with current expiry null. The watchdog exited unfired with actual wait/EOFs.

Validation: authentic restore, native Load/Save and repeat Load, shipped controls, full reviewed captures, local/same-box input qualification, reused matching locked build, provision/served-module/media hashes, complete recovery and documentation diff checks. No shared code changed. Next: use B for a faster protected interior route or resolve the remaining shooter from F, then find the brass key. Audio, frame rate, additional enemy defeat, item pickup and full mission completion remain unverified.