CydandClaude Opus 4.8
e65ff3f8d7
- net-boot/loop_rp.bat: GO.BAT-style netnub loop for RP (mirror of loop.bat, retargeted to rpl4opt). deploy/net_rp.conf.tmpl now calls it instead of the single-shot netnub + DOS pause -- the deployable runs in a loop until the supervisor kills DOSBox (per operator: no single-shot in the product). - DLL closure resolved: dosbox-x.exe is a 182MB STATIC build -- import table is only Windows system DLLs, delay-import table empty, libpng/SDL/zlib embedded. Nothing to bundle; wpcap.dll comes from the Npcap install. package.ps1's "no DLLs" case is now informational, and the plan/README note the static build. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
net-boot — networked pod boot support files
Files the DOSBox pod mounts as D: when booting on the network path
(emulator/net_full.conf, emulator/net_loop.conf). The pod receives its
mission egg from the ops console (SheepShaver) over TCP 1501 — no -egg bypass.
Contents
LSL.COM,NE2000.COM,ODIPKT.COM— Novell ODI stack: Link Support Layer → NE2000 MLID → ODI-to-Packet-Driver shim. WATTCP/NetNub find the packet driver by scanning INT 0x60-0x80 forPKT DRVR(odipkt lands at SINT 0x60).NET.CFG— ODI driver config.PORT 340(see below),INT 3,FRAME Ethernet_II.loop.bat— GO.BAT-style loop: keeps relaunchingnetnub -p -f btl4optso the pod stays connected and picks up whatever mission the console queues.
The 0x340 NIC base (important)
The VDB video splitter board is hardwired at I/O 0x300-0x31A (its palette
registers are at 0x300/0x308/0x310; VDB_BASE in vpxlog.cpp). If the NE2000
NIC is put at the usual nicbase=300 it claims that same range and swallows
the game's mid-mission VDB palette writes → every MFD/radar head decodes to
black, and the VDB traffic corrupts the NIC's registers so the console's
EndMission is lost (the mission overruns its timer). The NIC is therefore at
0x340 in both the DOSBox conf (nicbase=340) and here (PORT 340); they
must agree. The VDB keeps 0x300 (the game hardwires it — on the real pod the
NIC lived at a different base for exactly this reason).
Bridge / pcap notes
See ../NET-NOTES.md for the two-TAP Windows bridge, the bridge-miniport
realnic binding, and npcap DLL path requirements.