Neverhood original Install command and dependency boundary (2026-11-13)
The original launcher’s enabled Install control 105 reaches 0x404b60. On the ordinary fresh-install branch, it checks the OS, obtains/writes setup registry state, calls the original DSETUP.DLL!DirectXSetupA, then opens installation-directory dialog 114, and finally executes the ten installation records through progress dialog 113. DirectX comes before the directory chooser. This is bounded static evidence, NO_NATIVE_RESULT. Native installation, first room and gameplay remain OPEN.
This continues the first-dialog trace and installed asset contract. It does not repeat launcher creation as installation evidence. No production edits, original-code execution, state seeding, supplied menu answers or fake DirectX version/result occurred.
Bytes and scope
Evidence is scratch/runs/20261113-neverhood-install-command-2140/. All 50 seals in the 2120 run were checked before reuse. Its resource tree, launcher dispatch, setup-resource parser and code windows remain inputs. One authorized recovery requested only original SETUP95.EXE;1, extent 317836, ISO byte range 650928128–651130367, length 202240, from https://archive.org/download/neverhood_202508/Neverhood.iso. Admission required HTTP 206, exact Content-Range: bytes 650928128-651130367/651438080, exact declared/actual lengths, identity encoding and full SHA-256 ceae7885f49569fdc1100870286634c36d05eabe6010c228efef214c9444a95e. The prior manifest pins the 651438080-byte image to 94de724bb47eb2aa588ac4eff28ddc6fd10edebcf2be4dd131ef76875ef5ffd3.
fetch.py, http.json and member.json preserve the one-request recipe/receipt. The member existed only in RAM and was removed after every retained code window was compared with it; ram-removed.json records that check. An independently launched 600-second watchdog was armed before recovery. No ISO, other member or media under /home was downloaded. No retry/access workaround occurred.
Addresses are preferred x86 VAs at image base 0x400000. windows.json is the authoritative set of 31 current windows, 22759 bytes, with byte strings, file mappings and individual SHA-256s; tables.json pins the selected callback/vtable/jump tables and GUIDs. Earlier exploratory text files outside that manifest are superseded, not additional path proof. pe.json agrees with all 40 prior resource leaves. records-raw.json retains only small RCDATA/dialog records, not the bitmap or an extracted tree.
Dispatch, OS gate and installed-state split
0x405380 handles WM_COMMAND. For ID 105 it calls IsWindowEnabled on the stored Install HWND; only a nonzero result calls 0x404b60 at 0x4053df. This is the original named/default-button route; no coordinates are needed. A forged command to a disabled button does not pass this check.
0x404b60 constructs the progress object, clears uninstall switch/global restart bookkeeping, zeroes an OSVERSIONINFOA in the setup object, sets its length to 0x94, and calls GetVersionExA at 0x404bb2. It does not check that API’s return value. Resource 7000 declares Win9x tuple (4,0,0) and alternative-platform tuple (0xffffffff,0,0). Platform 0 selects string 44 and exits; platform 1 compares major, minor and build independently, using unsigned comparisons, against the first tuple. Other platforms take the second tuple; its major -1 is rejected with string 46. The code is not a general lexicographic version comparison. String 45 on the Win9x rejection literally reads empty; 44/46 require Windows 95. Do not change version state to force passage.
After the gate, calls 0x409530(FALSE) and 0x409de0 must return nonzero before progressing. The first reads Data Drive or derives the setup module directory and writes that default REG_SZ; the second writes the product PID. Thus Install already has real HKLM mutations before copying. Missing/read-only registry behavior cannot be replaced by seeded values.
At 0x404ca7, 0x409700 checks Installed:
- Fresh/uninstalled:
0x404d43checks again, conditionally calls 0x404ad0 unless the recorded platform is 2, then calls 0x4049f0 for directory selection. DX raw return -12 goes to string 36,Installation was canceled.Other negative raw values go to generic failure; nonnegative values continue. The platform-2 skip exists, but the unchanged resource’s earlier OS gate rejects its declared tuple. - Already installed: the branch calls 0x4045b0 (also used by Play; its body is outside retained windows), may force source-directory refresh, verifies source
Data Drive + setup\nhc.exethrough 0x409cb0 → 0x407240, and can open source-location dialog 116 via 0x404910. Accepted source choice is copied to setup field+0xcc. It then writes Data Drive, reparses resource 7000, reads Installed Directory, and conditionally checks DirectX before joining the copy dialog. It does not automatically open dialog 114 on this branch. The result and internal behavior of 0x4045b0 remain unknown here.
Actual modal/object path and choices
Modal helper 0x40a730 calls DialogBoxParamA, passing DLGPROC 0x40a7e0 and the stack object as lParam. The callback attaches the object to HWND property FIZBIN during WM_INITDIALOG. Its two-stage message table maps WM_INITDIALOG 0x110 → 0x40b143 → vtable +0x20 and WM_COMMAND 0x111 → 0x40b158 → vtable +0x14. The command thunk separates LOWORD(control ID), lParam(control HWND), and HIWORD(notification). Those indirect slots have exact original targets:
| Object vtable | Init slot | Command slot | Real use |
|---|---|---|---|
0x4119e8 |
0x403810 |
0x403910 |
DirectX dialog 117 |
0x4117f8 |
0x403120 |
0x403600 |
Installation-directory dialog 114 |
0x411228 |
0x401fa0 |
0x4022a0 |
Installation progress dialog 113 |
DirectX dialog 117 has only two statics, both ID65535, and no answer buttons. Init centers it and posts WM_COMMAND ID109 (0x6d). Its command handler calls 0x403870, shows/updates the dialog, sets setup field +0xec to its HWND, and calls 0x4074e0. Resource 7000 declares enable=1 and resource 7500; this helper therefore calls 0x409470(7500). This is actual deferred work through the dialog message pump, not a user answer to an imagined DirectX menu. The DX executor attempts SetDlgItemTextA on 1008, which is absent in original dialog 117 (it exists in progress dialog 113); this call does not establish a visible status update.
Directory dialog 114, created by 0x4049f0 → 0x40a730, presents edit 1015, Browse 1013, OK 1, Cancel 2, title The Neverhood Installation. The original text permits typing a directory or choosing Browse, and says Cancel exits installation. Init copies the current default install path to edit 1015 and computes required bytes through 0x40a030. It attempts to read/format/write descriptive control 1017, which is absent from this original resource; a visible size label is therefore not established. That size helper enumerates the ten records and sums available opcode-3 source-file sizes; it is not a constant admission number.
0x403600 routes OK to 0x403280, Cancel to EndDialog(2), Browse to 0x4034a0. OK reads edit 1015, obtains destination free bytes through 0x407170, and compares against setup +0x118. Too little space selects string 43 and keeps the chooser open. Existing directory detection is 0x407240 (GetFileAttributesA). If absent, strings 40/41 create the original OK/Cancel directory-creation message; Cancel returns to the chooser, otherwise 0x4067e0 recursively creates directories and failure reports string 11. Accepted directory ends with EndDialog(1). The wrapper copies it into setup +0xc8, calls 0x409e50 to write Installed Directory, then returns success; it does not test that registry helper’s return.
Browse calls 0x401c90(39,...) → SHBrowseForFolderA with BIF_RETURNONLYFSDIRS=1, callback 0x401c60 (on BFFM_INITIALIZED=1 it centers the browse window). A returned PIDL is converted by SHGetPathFromIDListA, then SHGetMalloc supplies IMalloc::Free (+0x14) and Release (+0x08). No default folder selection is injected. The original wrapper does not check every shell return before dereferencing the allocator; correct HRESULT/output behavior matters. Dialog 116 separately uses the same edit/Browse IDs for locating the source disk, with its own OK validation; its resource text and title are retained in pe.json.
Exact DirectX and child boundary
Resource 7500 decodes as opcode 1, selection flags 3, zero additional predicates, path setup, and flags DWORD 0x10000a3f. Parsing 0x407a40 combines source directory +0xcc with that path and appends a backslash. Execution 0x409260 → 0x407af0 saves CWD, changes CWD to that source setup directory, builds its DSETUP.DLL pathname, and calls LoadLibraryA at 0x407bb1. It resolves literal DirectXSetupA through GetProcAddress at 0x407bdc, then makes the actual indirect call 0x407c30 with (progress HWND, source setup directory, flags). Existing Installed state ORs 0x80 into the flags. It restores CWD and frees the DLL afterward.
The raw return is stored in setup +0x114. Values 0, 1, -12 are accepted by the record executor’s boolean result; 1 also sets restart-required +0xe0. Other returns select mapped original DirectX errors (strings 18–26/48) or the raw error selector and return false. Importantly, 0x404ad0 returns raw +0x114, ignoring the modal result; missing-library or other pre-call failures do not establish that field. The constructor does not initialize +0x114 in the retained code. Also, the GetProcAddress result is called without a null check. Neither branch may be described as a safely handled successful DirectX check.
The manifest identifies SETUP/DSETUP.DLL, 24576 bytes, SHA-256 7327040443ec90228b4fbd9f424b32528aff61d49c772a3d7ad16fc76aa3f14a, offset 650375168. The same hash/length is listed at SETUP/DIRECTX/DSETUP.DLL. Sibling DSETUP6E/DSETUPE and localized copies are manifest entries only. None was recovered or parsed here. Consequently DSETUP’s actual export table, imported/dynamic DLLs, 16-bit/COM requirements, possible child launches, version detection, INF/driver selection and internal user prompts are unknown. Names in dependency-members.json do not prove any of those calls. The exact next static dependency is that original 24576-byte DSETUP member, requiring separately authorized recovery/analysis; no guessed replacement or success stub closes it.
There is a generic child opcode 4 in the dispatcher: executor 0x408930 → 0x406910 → CreateProcessA, with null application name, supplied command line and creation flags 0x04000020. That helper returns CreateProcess’s BOOL without waiting or checking child exit. No opcode 4 appears in the selected 8000–8009 records. Record 8004 is opcode 5, writing Run File=%eNHC; it does not launch it during Install. Separately, the enabled Play control 108 → 0x4052d0 reads the formatted Run File via 0x409fb0, refreshes/checks source state and calls 0x406910 at 0x405317. On CreateProcess success it posts Exit command 40007 to the launcher; on failure it reports original string 42. This proves the later child boundary, not NHC startup or a successful installation.
Copy, shortcuts, registry and completion
After accepted choices, 0x404d90 opens progress dialog 113. Init 0x401fa0 initializes progress control 1006 with PBM_SETRANGE/SETPOS/SETSTEP (0x401/0x402/0x404) and posts command 109. Command slot 0x4022a0 → 0x4020e0 loops 8000+i, i < setup[+0xd8] = 10. Each iteration calls 0x409470, which loads/parses the exact record through 0x409090, selects active flags/predicates, executes 0x409260, and cleans up. False execution stops with EndDialog(0); successful iterations send PBM_STEPIT (0x405). These posted command IDs are internal installer work, not original visible controls the user should click.
| Record | Opcode / ordinary install effect |
|---|---|
| 8000–8003 | 3: copy setup\nhc.exe, setup\smackw32.dll, root setup95.exe, data\HD.BLB into chosen install directory, using each basename |
| 8004 | 5: write formatted %eNHC as product Run File |
| 8005 | 6: shortcut %mDreamWorks\The Neverhood.lnk targeting %esetup95.exe, description The Neverhood |
| 8006 | 3: copy root readme.txt into install directory |
| 8007 | 6: shortcut %mDreamWorks\The Neverhood Read Me.lnk targeting %ereadme.txt, description Read Me |
| 8008 | 8, install-only flag 1: source %dDATA\t.blb read-speed test, numeric parameter 550; warning string 31 is a possible outcome |
| 8009 | 9, uninstall-only flag 2: *.nev deletion route; inactive on ordinary install |
Flags 3 select both install/uninstall modes; 0x409117..0x40915f evaluates the actual flags and predicate count, and 0x409274 skips inactive records. The generic conditional evaluator can use the setup object’s internal virtual container (+0x108, slots +0x20/+0x24); the selected records have zero additional predicates. Mutable object/container correctness and exceptional paths remain unexecuted.
Copy is 0x407d10 parse → 0x408000 execute → helper 0x406ca0 at call site 0x4080d0. The latter checks attributes/file version/time conditions; original VERSION imports and CRT helpers remain part of that conditional work. The copy helper constructs parent directories via 0x4067e0, then calls CopyFileA(source,destination,FALSE) at 0x40828d. Failure can take 0x407510, which copies to a Windows-directory temporary pathname and writes the original delayed-rename INI entry, setting restart-required. Other conditional paths adjust attributes/shared-DLL counts. Thus copying is not just five names and a boolean; failed/replacement/locked-file cases can defer work to reboot. No installed bytes or delayed-rename entries were produced.
Shortcut execution 0x408530 → 0x4066e0 proves concrete COM calls, with GUID bytes retained:
- CoInitialize(NULL), then CoCreateInstance(CLSID_ShellLink
{00021401-0000-0000-C000-000000000046}, NULL, CLSCTX_INPROC_SERVER=1, IID_IShellLinkA{000214EE-0000-0000-C000-000000000046}). - IShellLinkA SetPath (+0x50), SetDescription (+0x1c), QueryInterface for IID_IPersistFile
{0000010B-0000-0000-C000-000000000046}. - MultiByteToWideChar to a MAX_PATH buffer, IPersistFile::Save (+0x18, remember=TRUE), and both interfaces’ Release (+0x08). No SetWorkingDirectory/SetArguments/Resolve call is demonstrated in this helper. Some original error paths, including CoCreateInstance failure, return zero from this HRESULT-style helper; its wrapper therefore cannot prove a shortcut exists merely from reported success.
After all record booleans succeed, 0x402160 → 0x401680 writes HKLM’s standard Windows Uninstall product metadata (DisplayName and formatted UninstallString); then 0x40216e → 0x409690(TRUE) writes the product’s Installed REG_DWORD=1. Both must return nonzero for EndDialog(1). This is the concrete completion condition. It does not provide rollback for earlier filesystem/registry mutations. PID, Data Drive and Installed Directory were handled earlier, not atomically at the final marker.
The caller treats a nonzero progress-dialog return as success, updates launcher enables, and displays string 2, Installation of The Neverhood was successful. A DialogBox creation error (-1) is also nonzero at this test; observing just that message would not prove the successful EndDialog(1) route. If restart-required is set, dialog 112 offers original OK 1 / Cancel 2. OK may call 0x409770 to write startup metadata when +0xe8 is set, then ExitWindowsEx(EWX_REBOOT=2,0). Cancel leaves the original requirement to restart before play. Without restart-required it focuses Play; it does not automatically launch the game. Failure selects original string 5; chooser cancellation selects 36. All are declared original branches, not supplied answers.
Demonstrated calls versus current handlers
called-iat.txt and handlers.json bind 76 bounded call-site API names to current source bodies; this includes generic/conditional helpers and is not a dynamic invocation count. Source pins and relevant Git patches bind concurrent uncommitted source too.
| Requirement actually established | Current source and practical boundary |
|---|---|
| OSVERSIONINFOA layout and fields | src/09a0b-handlers-base-late.wat:80 fills fields from $winver; GetVersionExA returns 1. No version setting changed; selected environment/actual original branch remains unobserved. |
| Original modal objects, posted 109, progress messages | src/09a-handlers1-user.wat:2180 implements DialogBoxParamA through resource loading/modal callbacks. Existing message queue, EndDialog and common-control handlers exist. That does not demonstrate Neverhood’s stack object lifetime, FIZBIN dispatch, exact progress control or original visible UI working together. |
| Filesystem directory choice / allocator | src/09a7d-handlers-shell-file.wat:2481 creates the browse modal; SHGetMalloc creates an IMalloc object. SHGetPathFromIDListA decodes supported filesystem PIDLs. Original callback delivery, user selection, PIDL conversion and Free/Release composition remain untested. |
| Real DSETUP dynamic load and export | lib/dll-registry.js lists dsetup.dll as app-local/loadable PE; LoadLibrary/GetProcAddress have real-module paths. Path discovery under source setup, exact export/ABI/dependency execution and original outcome are unknown. The existing handle_DirectXSetup in src/09a8-handlers-directx.wat:2019 unconditionally returns 0. Its unsuffixed name and body neither prove DirectXSetupA resolution nor reproduce the original redistributable’s work. It must not be used as evidence or a substitute. |
| CopyFileA(FALSE), attributes, free-space and registry output | src/09a7-handlers-dispatch.wat:4222 forwards CopyFileA to lib/filesystem.js:3208, which handles path/overwrite/error work. Registry handlers reach typed storage in lib/storage.js. These implementations do not prove exact media presence, source/destination bytes, permissions, free-space comparisons, delayed replacement or persistence through restart. |
| Exact ShellLink / IPersistFile calls | src/09a7-handlers-dispatch.wat:2736 onward implements the concrete GUID/vtable family, stores path/description, and Save writes a Shell Link through shell_link_write. This is stronger than matching names, but no actual Neverhood shortcut was created or read back. Real mapped OLE32 selection can also change the route. |
| Later NHC CreateProcess and reboot | src/09a0b-handlers-base-late.wat:998 has CreateProcess command/directory/host launch handling; src/09a7d-handlers-shell-file.wat:2582 maps ExitWindowsEx to host exit and quit. Neither proves child execution or genuine reboot/deferred-copy completion. |
No production primitive was changed. The first exact unresolved native dependency is the original DSETUP.DLL call, including its unchecked export lookup and original decisions; it precedes choosing an install directory. Further unresolved obligations include internal file-version/CRT branches, installed-repair helper 0x4045b0, actual registry/file/COM outputs, delayed copies/reboot and the later original NHC/Smacker runtime. A broad API-name coverage claim cannot close these boundaries.
Checks and next work
194 static/pure checks pass, including 40 resource identities, raw-record hashes, 31 code-window hashes and overlap with sealed 2120 windows, 26 rel32 call edges, vtable/message selectors, actual and absent control IDs, record selection, DX flags, HTTP receipt and RAM removal. Mutants reject wrong HTTP status/range/length, an altered call displacement, changed DX opcode, changed vtable target and truncated record. None executes installer instructions. checks.json names each assertion.
Git is the source archive: identity.json, git-start.txt, relevant.patch, owned-doc.patch, new-helpers.patch and patch reverse-check receipts preserve exact Git identity, relevant uncommitted hunks and owned new files. Member/code/source hashes and artifact seals preserve custody without source snapshots or archives. Publication uses docs-only diffcheck and strict pull/push; full build and runtime tests were excluded by task scope.
Next static work needs authorization for the exact original DSETUP member and its actual dependencies; a later ordinary installation needs an authorized original runtime with full media and observed original choices/results. Preserve failures and partial state instead of injecting completion. Native installation, first frame, first room and gameplay remain OPEN; NO_NATIVE_RESULT. No VM/CPU/WASM/native/browser/GL/game/build, boxes, workers, capacity/reserve work or general cleanup occurred. Box ID none, state NOT_CREATED, expiry null, stop receipt N/A. Ownership is released when the docs-only commit is published; this single-task worker stops then.