CydandClaude Fable 5
377047f37d
The RIO cockpit board now runs sustained sessions with button mashing; dropouts self-heal in ~1-3s. Documented in RIO-NOTES.md: - directserial RIO_TAP=<path> (host env): logs every TX/RX byte with host-us + emu-ms timestamps, plus config/RTS/DTR/break lines. This instrument found every root cause below. - Confs: rxburst:16 restored (no-burst reply pacing made the game ACK ~14ms late -> board dropped on the first long analog stream; the old 'rxburst corrupts boot' belief was the then-unpatched PCSPAK crash). priority=highest,highest (unfocused DOSBox was demoted and blew the ACK deadline). - BTL4OPT.EXE patch lineage (in ALPHA_1/, zip left pristine): v2 full DISABLE_AND_DIE NOPs (v1 left the IRQ/RTS-retract prologue live -> first protocol error deafened the driver), v3 TXMAXIDLE 4->32 (kills the button-press ACK-window livelock), v4 analog retry limit 15s->0.5s (dev value was 0.2s; recovery now near-instant). - Board firmware patch plan recorded for the EPROM-dump route. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Modified DOSBox-X serial passthrough (RIO latency options)
Drop these over src/hardware/serialport/ in the DOSBox-X source tree
(v2026.06.02). They add two directserial options for the VWE RIO cockpit
board's few-millisecond ACK deadline (see ../../RIO-NOTES.md):
rxpollus:<us>(50-1000) - host-port receive poll tick in microseconds (stock = 1000). Discovers inbound bytes sooner.rxburst:<n>(1-64) - deliver host-buffered received bytes n times faster than emulated wire speed (they already paid wire time on the real cable).
Usage: serial1=directserial realport:COM1 rxpollus:100 rxburst:16