From 7cd58d300005094d3986b516fba21c8efde016f3 Mon Sep 17 00:00:00 2001 From: Joe DiPrima Date: Mon, 10 Aug 2026 12:35:52 -0500 Subject: [PATCH] pod runbook: schtasks /end orphans the game (dead-RIO trap) + self-cleaning runpod.bat Co-Authored-By: Claude Fable 5 --- context/pod-hardware.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/context/pod-hardware.md b/context/pod-hardware.md index f624d57..e3c48d8 100644 --- a/context/pod-hardware.md +++ b/context/pod-hardware.md @@ -510,6 +510,16 @@ trailing-space payload) or use PowerShell `Add-Content`. Bit us arming BT_GLASS_ `Expand-Archive` → podkit → `schtasks /run` came up clean on the first try — rig config survived, newest-install auto-resolve worked, no hand-edits. The cab genuinely upgrades like a tester box. +**9. ⚠ `schtasks /end` ORPHANS the game — the dead-RIO trap (2026-08-10):** `/end` kills the +batch, but `runpod.bat` `start ""`s the exe DETACHED, so the old btl4.exe survives, keeps COM1 +open, and the NEXT launch boots with a dead cockpit board: `InitSerialPort() failed +[GetLastError() = 5]` (access denied) → `RIO initialization failed!` → buttons dead while the +banner still says "hardware RIO" (the banner is the PROFILE, not the init result). Diagnosis: +`tasklist /FI "IMAGENAME eq btl4.exe"` showing ≥2 instances. FIXED at the root the same day: +`runpod.bat` now `taskkill /F /IM btl4.exe`s FIRST (original saved as `runpod.bat.bak`), making +the BT411Run task an idempotent restart — but any hand-rolled launcher on a future cab needs the +same line, and a mid-mission `/run` now RESTARTS the game rather than failing quietly. + ## The 1995 player manual — alignment audit (2026-07-18) [T1, primary source] `reference/manual/Tesla40_BT_manual.pdf` (34pp, from Nick). CONFIRMS the reconstruction on every checked control behavior: