War Wind (USA) and War Wind II — Human Onslaught (Europe)

Both are DreamForge / SSI RTS games shipped as CD images (.cue/.bin) with InstallShield 3 setups. Verified 2026-09-28: both install from the mounted CD and reach real gameplay with the CD still mounted.

Discs

Game	Setup	Installed exe	Notes
War Wind	IS3 Win16 `SETUP.EXE`	`WARWIND\WW.EXE`	music streams from `D:\warwind\data\res.003` at runtime, so the CD must stay mounted
War Wind II	IS3 `SETUP.EXE` → `_ins0432._mp` engine	`C:\WarWind II\warwind2.exe` + `smackw32.dll`	data in `data\res.000/001/008`, `network\*.lvl`

Bugs fixed to get here

War Wind setup: OpenFile(OF_CREATE) alone was read-only. The Win16 SETUP creates its engine stage file with style 0x1000 (access bits = OF_READ) and then _lwrites into it. DOS create (INT 21h AH=3Ch) always opens read/write; $handle_OpenFile now does the same whenever OF_CREATE is set. Covered by test/test-openfile-create.js.
War Wind II setup spun forever in SdAskOptions. The IS3 engine's startup (_ins0432._mp 0x408cc9 → 0x408d29 → 0x40931f) registers GDI32, KERNEL32, USER32 into a DLL list at [0x4964ac] by GetModuleHandleA for system DLLs, stopping at the first NULL. GetModuleHandleA("GDI32") returned 0, so USER32 was never registered, and every script call into USER32 (resolved by 0x408f7f, lstrcmpiA over that list) was silently dropped — the dialog never appeared. gdi32 is now in $STATIC_SYS_DLL_NAMES (before the DirectX tail; $STATIC_SYS_DLL_FIRST_DX is 4, and the DPLAYX/DSOUND ordinal rules in 08b-dll-loader.wat derive their positions from it). Covered by test/test-wide-api.js.

Headless commands

The CLI resolves import DLLs beside the host exe, so for War Wind II copy smackw32.dll out of the install overlay next to a host copy of warwind2.exe (otherwise: UNIMPLEMENTED API: <ord>).

# install (drive with tools/ctl.js on the control port)
node test/run.js --media-mount="<disc>.cue" --media-exe=SETUP.EXE \
  --overlay-dir=/tmp/ww2-overlay --screen=800x600 --quiet-api \
  --control=8133 --frozen --max-seconds=3000

# run the installed game with the CD mounted
node test/run.js --exe=<host>/warwind2.exe --exe-guest-path='c:\warwind ii\warwind2.exe' \
  --media-mount="<disc>.cue" --media-exe=SETUP.EXE --cwd='C:\WarWind II' \
  --overlay-dir=/tmp/ww2-overlay --screen=800x600 --no-build --quiet-api \
  --control=8133 --frozen

Driving it (screen/PNG coordinates at `--screen=800x600`)

Both games poll GetKeyState for the button, so a bare ctl click is lost: send mousemove, step ~60, mousedown, step ~60, mouseup.

WW2 install: Welcome Next (494,454) → options (Suggested) Next → destination C:\WarWind II Next → "create directory?" Yes (334,363) → copy → DirectX prompt No (434,336) → README prompt → setup exits 0.
WW2 game: main menu star button (677,108) → mission screen → Start Game (450,32) → loading → tip dialog (right button 436,314) → "Start Game?" Yes (354,456) → gameplay.
WW1 game: race circle (150,120) → Begin New Campaign (472,543) → campaign map → the black box at (665,540) is "Begin the scenario" (its art is missing — open question) → briefing → army screen → checkmark (665,535) → zoom-in transition (static for a few thousand batches while the level initialises in 0x4252xx) → tip dialog. The round-arrow button (437,317) closes the tip; the checkmark on the left is "Next tip" → gameplay.

Open questions

$handle_ICOpen returns 0 (no codecs), so WW1's Cinepak intro AVIs (LOGOS.AVI, WWOPEN.AVI) are skipped. Real Win98 ships Cinepak.
WW1's "Begin the scenario" button draws as a black box.