Mike Swanson
3faf09c111
Implemented comprehensive DOS 6.22 update system for ~30 test stations with critical fix for test data database import routing. ## Major Changes ### DOS Batch Files (7 files) - NWTOC.BAT: Download updates from network to DOS machines - CTONW.BAT v1.2: Upload with separate ProdSW/LOGS routing (CRITICAL FIX) - UPDATE.BAT: Full system backup to network - STAGE.BAT: System file staging for safe updates - REBOOT.BAT: Apply staged updates on reboot - CHECKUPD.BAT: Check for available updates - DEPLOY.BAT: One-time deployment installer for DOS machines ### CTONW v1.2 Critical Fix Fixed test data routing to match AD2 sync script expectations: - Software distribution: C:\ATE\*.EXE -> T:\TS-4R\ProdSW\ (bidirectional) - Test data logging: C:\ATE\8BDATA\*.DAT -> T:\TS-4R\LOGS\8BLOG\ (upload only) - Subdirectory mapping: 8BDATA->8BLOG, DSCDATA->DSCLOG, HVDATA->HVLOG, etc. - Test data now correctly imported to AD2 database via Sync-FromNAS.ps1 ### Deployment Infrastructure - copy-to-ad2.ps1: Automated deployment to AD2 server - DOS_DEPLOYMENT_GUIDE.md: Complete deployment documentation - DEPLOYMENT_GUIDE.md: Technical workflow documentation - credentials.md: Centralized credentials (AD2, NAS, Gitea) ### Analysis & Documentation (15 files) - CTONW_ANALYSIS.md: Comprehensive compliance analysis - CTONW_V1.2_CHANGELOG.md: Detailed v1.2 changes - NWTOC_ANALYSIS.md: Download workflow analysis - DOS_BATCH_ANALYSIS.md: DOS 6.22 compatibility guide - UPDATE_WORKFLOW.md: Backup system workflow - BEHAVIORAL_RULES_INTEGRATION_SUMMARY.md: C: drive integration ### Session Logs - session-logs/2026-01-19-session.md: Complete session documentation ### Conversation Reorganization - Cleaned up 156 imported conversation files - Organized into sessions-by-date structure - Created metadata index and large files guide ## Technical Details ### AD2 → NAS → DOS Sync Flow 1. Admin copies files to AD2: \192.168.0.6\C$\Shares\test\ 2. Sync-FromNAS.ps1 runs every 15 minutes (AD2 → NAS) 3. DOS machines access via T: drive (\D2TESTNAS\test) 4. NWTOC downloads updates, CTONW uploads test data 5. Sync imports test data to AD2 database ### DOS 6.22 Compatibility - No %COMPUTERNAME%, uses %MACHINE% variable - No IF /I, uses multiple case-specific checks - Proper ERRORLEVEL checking (highest values first) - XCOPY /S for subdirectory support - ASCII markers ([OK], [ERROR], [WARNING]) instead of emojis ### File Locations - AD2: C:\Shares\test\COMMON\ProdSW\ (deployed) - NAS: T:\COMMON\ProdSW\ (synced) - DOS: C:\BAT\ (installed) - Logs: T:\TS-4R\LOGS\8BLOG\ (test data for database import) ## Deployment Status ✅ All 7 batch files deployed to AD2 (both COMMON and _COMMON) ⏳ Pending sync to NAS (within 15 minutes) ⏳ Pending pilot deployment on TS-4R 📋 Ready for rollout to ~30 DOS machines ## Breaking Changes CTONW v1.1 → v1.2: Test data now uploads to LOGS folder instead of ProdSW. Existing machines must download v1.2 via NWTOC for proper database import. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2.0 KiB
2.0 KiB
The user is referencing previous work. ALWAYS check session logs and credentials.md for context before asking.
Steps
1. Search Session Logs
Search session-logs/ directory for relevant keywords from user's message:
- Use grep to find matches in all .md files
- Check most recent session log first
- Look for credentials, IPs, hostnames, configuration details
2. Check credentials.md
The credentials.md file contains centralized credentials for all infrastructure:
- Read credentials.md for server access details
- Find connection methods, ports, passwords
- Get API tokens and authentication information
3. Common Searches
Based on user reference, search for:
- Credentials/API keys: "token", "password", "API", "key", service names
- Servers: IP addresses, hostnames, "jupiter", "saturn", "AD2", "D2TESTNAS", port numbers
- Services: "gitea", "docker", "MariaDB", container names
- Previous work: Project names, feature names, error messages
- Database: Connection strings, table names, migration files
4. Summarize Findings
Report what was found:
- Relevant credentials and connection details
- What was done previously
- Pending/incomplete tasks
- Key decisions that were made
5. Apply Context
Use the discovered information to:
- Connect to correct servers/services
- Use correct credentials
- Continue incomplete work
- Avoid re-asking for information already provided
Important
- NEVER ask user for information that's in session logs or credentials.md
- Session logs and credentials.md are the source of truth
- If information isn't in logs, it may need to be obtained and saved
- For ClaudeTools: Also check SESSION_STATE.md for project history
ClaudeTools Specific Context
For ClaudeTools project, also check:
- SESSION_STATE.md - Complete project history and current phase
- .claude/claude.md - Project overview and recent work
- credentials.md - All infrastructure and service credentials
- Database: 172.16.3.30:3306/claudetools (MariaDB)
- API: http://172.16.3.30:8001 (production)