sync: auto-sync from GURU-5070 at 2026-07-04 12:23:18

Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-07-04 12:23:18

errorlog.md

@@ -43,6 +43,10 @@ Categories (the `[type]` tag): _(none)_ = skill/command execution failure ·
 
 2026-07-04 | Howard-Home | screenconnect | ScreenConnect API error [SendCommandToSession]: HTTP 500: {"errorType":"","message":"An session manager fault error occurred while processing your request. Please contact support if the problem persists."} [ctx: cmd=send-command]
 
+2026-07-04 | GURU-5070 | dataforth/ctonw-v5.1 | CONFIG.SYS collection used 'IF NOT EXIST T:STATUS%MACHINE%NUL MD ...' (the NUL dir-exists test is unreliable on a network/SMB drive) and COPY targets had NO trailing backslash -> MD skipped, COPY created FILES named after each machine instead of per-machine folders, and 'MEM /C > T:STATUS%MACHINE%MEM.TXT' wrote to a nonexistent path -> DOS 'T: write fault Abort/Retry/Fail?' HUNG unattended boot on production DOS test stations. Reverted CTONW to v5.0. Fix: pre-create per-machine dirs server-side on the NAS, use trailing backslash on COPY dir targets, never let a network write error reach the critical-error handler at boot; test on ONE isolated station before any fleet exposure. [ctx: ref=dos-network-drive-copy sev=production-boot-hang]
+
+2026-07-04 | GURU-5070 | deploy/dos-batch | [friction] reported CRLF via grep -c $'
+$' which misfired on an LF-only file the Write tool produced; staged an LF-only .BAT to the Dataforth NAS (DOS needs CRLF). Caught by Mike at the station. Fix: verify line endings with 'tr -cd 
  | wc -c' (must equal LF count) and CRLF-convert Write-tool batch files with 'sed s/$/
 /' before deploy. [ctx: ref=projects/dataforth-dos/.gitattributes file=NWTOC.v5.1]