fix: Preserve CRLF line endings in DOS BAT files during sync

Critical fix for DOS 6.22 compatibility - CRLF line endings were being
converted to LF during AD2-to-NAS sync, causing BAT files to fail on DOS.

Root Cause:
- OpenSSH scp uses SFTP protocol by default (text mode)
- SFTP converts line endings (CRLF → LF)
- DOS 6.22 requires CRLF for batch file execution

Solution - Fixed AD2 Sync Script:
- Added -O flag to scp commands in Sync-FromNAS.ps1
- Forces legacy SCP protocol (binary mode)
- Preserves CRLF line endings during transfer

Created deployment scripts:
- fix-ad2-scp-line-endings.ps1: Updates Sync-FromNAS.ps1 with -O flag
- deploy-all-bat-files.ps1: Deploy 6 BAT files to AD2 (UPDATE, NWTOC,
  CTONW, CHECKUPD, REBOOT, DEPLOY)
- deploy-bat-to-nas-direct.ps1: Direct SCP to NAS with -O flag for
  immediate testing
- verify-nas-crlf.ps1: Validates CRLF preservation on NAS

Created diagnostic scripts:
- check-line-endings.ps1: Compare original vs NAS file line endings
- check-ad2-sync-log.ps1: Monitor sync log on AD2
- check-ad2-bat-files.ps1: Verify files on AD2
- check-scp-commands.ps1: Analyze SCP command usage
- trigger-ad2-sync-now.ps1: Manual sync trigger for testing

Verification:
- DEPLOY.BAT: 9,753 bytes with CRLF (was 9,408 bytes with LF)
- All 6 BAT files deployed to NAS with CRLF preserved
- DOS machines can now execute batch files from T:\

Files deployed:
- DEPLOY.BAT (one-time installer)
- UPDATE.BAT (backup utility)
- NWTOC.BAT (network to computer updates)
- CTONW.BAT (computer to network uploads)
- CHECKUPD.BAT (check for updates)
- REBOOT.BAT (reboot utility)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

diagnose-nas-ssh.ps1

@@ -0,0 +1,18 @@
+# Diagnose D2TESTNAS SSH connection issues
+
+Write-Host "[INFO] Testing SSH connection to D2TESTNAS (192.168.0.9)..."
+Write-Host ""
+
+# Try SSH with verbose output
+$Output = & ssh -v root@192.168.0.9 "echo 'Connection successful'" 2>&1
+
+Write-Host "[INFO] SSH Output:"
+$Output | ForEach-Object { Write-Host $_ }
+
+Write-Host ""
+Write-Host "[INFO] If key authentication is failing, you can:"
+Write-Host "  1. Access web interface: http://192.168.0.9/"
+Write-Host "     User: admin, Password: Paper123!@#-nas"
+Write-Host "  2. Check SSH service status"
+Write-Host "  3. Verify authorized_keys file"
+Write-Host "  4. Restart SSH service if needed"