@echo off
REM podprobe.bat -- XP-SAFE fallback probe for the pod / crash cart.
REM
REM Use this when tools\podprobe.ps1 will not run (no PowerShell, or an
REM XP/2003-era box where .NET/PS is absent).  Uses only tools that shipped
REM with Windows XP.  Writes podprobe_bat.txt next to itself.
REM
REM   podprobe.bat
REM
REM It answers the first question that matters: WHAT IS THIS MACHINE, and can
REM our build run on it at all?  (Modern MSVC toolset => Windows 7 SP1+.)

setlocal
set OUT=%~dp0podprobe_bat.txt
echo ==================== BT411 POD PROBE (bat fallback) ====================> "%OUT%"
echo host: %COMPUTERNAME%   session: %SESSIONNAME%>> "%OUT%"
date /t >> "%OUT%"
time /t >> "%OUT%"
echo.>> "%OUT%"

echo ---- OS ---->> "%OUT%"
ver >> "%OUT%"
wmic os get Caption,Version,BuildNumber,OSArchitecture /format:list >> "%OUT%" 2>&1
echo.>> "%OUT%"

echo ---- GPUs / drivers ---->> "%OUT%"
wmic path Win32_VideoController get Name,DriverVersion,DriverDate,CurrentHorizontalResolution,CurrentVerticalResolution /format:list >> "%OUT%" 2>&1
echo.>> "%OUT%"

echo ---- Monitors (attached) ---->> "%OUT%"
wmic path Win32_DesktopMonitor get DeviceID,Name,ScreenWidth,ScreenHeight,Availability /format:list >> "%OUT%" 2>&1
echo.>> "%OUT%"

echo ---- Serial ports (RIO board) ---->> "%OUT%"
wmic path Win32_SerialPort get DeviceID,Name /format:list >> "%OUT%" 2>&1
echo.>> "%OUT%"

echo ---- Full DirectX report (monitor rects, D3D caps) ---->> "%OUT%"
echo (dxdiag is writing podprobe_dxdiag.txt -- may take ~30s)>> "%OUT%"
dxdiag /whql:off /t "%~dp0podprobe_dxdiag.txt"

type "%OUT%"
echo.
echo Wrote %OUT%
echo Wrote %~dp0podprobe_dxdiag.txt  (send BOTH back)
endlocal