azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
54 Commits 1 Branch 0 Tags
dc7174a53dbf2763ca1b73c244a4a2af947f2e8e
Commit Graph

3 Commits

Author SHA1 Message Date
Mike Swanson
29e2df60c5 feat: Complete DOS machine deployment verification and AD2-NAS sync infrastructure 
This checkpoint establishes verified deployment infrastructure for the Dataforth
DOS Update System with proper file synchronization and documentation.

## Key Changes

### TS-4R Backup and Analysis
- Backed up complete TS-4R machine to D:\ClaudeTools\backups\TS-4R\
- Analyzed MENUX.EXE startup menu system (758-line QuickBasic program)
- Documented complete startup sequence: AUTOEXEC.BAT → STARTNET.BAT → MENUX.EXE
- Found MENUX.BAS source code (Feb 2008 version) from KEPCO ABC software archive

### AD2-NAS Sync Infrastructure Fixes
- Created junction: COMMON → _COMMON (single source of truth for software updates)
- Verified bidirectional sync logic prevents data backflow:
  * Test data: DOS → NAS → AD2 → Database (one-way, deleted from NAS)
  * Program updates: AD2 → NAS → DOS (one-way, files remain on AD2)
- Manually deployed correct BAT file versions to NAS after sync connection issues
- Verified all 9 BAT files deployed correctly (5.1KB-8.8KB each)

### Deployment Scripts Created
- check-junction.ps1: Verify COMMON/\_COMMON junction status
- compare-common-folders.ps1: Compare folder contents
- deploy-correct-bat-files.ps1: Deploy BAT files from local to AD2
- fix-common-junction.ps1: Create COMMON → _COMMON junction
- verify-bat-deployment.ps1: Verify file versions on AD2
- manual-push-to-nas.sh: Manual BAT file deployment to NAS
- read-sync-script.ps1: Read Sync-FromNAS.ps1 from AD2
- search-menux-ad2.ps1: Search for MENUX source files

### Documentation Updates
- Updated all deployment guides with MENUX startup sequence
- Added startup flow to credentials.md and session logs
- Documented junction requirement for COMMON/\_COMMON
- Added data flow verification confirming unidirectional sync

## Technical Details

**Files Deployed to NAS (2026-01-20 09:01-09:02):**
- UPDATE.BAT (5,181 bytes) - Machine backup utility
- DEPLOY.BAT (5,579 bytes) - One-time deployment installer
- NWTOC.BAT (6,305 bytes) - Network to Computer updates
- CTONW.BAT (7,831 bytes) - Computer to Network uploads
- CTONWTXT.BAT (1,504 bytes) - Text file version
- CHECKUPD.BAT (6,495 bytes) - Check for updates
- STAGE.BAT (8,794 bytes) - Stage system files
- REBOOT.BAT (5,099 bytes) - Apply staged updates
- AUTOEXEC.BAT (2,211 bytes) - DOS startup configuration

**Sync Logic Verified:**
- PULL: /data/test/TS-*/LOGS/*.DAT copied to AD2, then deleted from NAS
- PUSH: C:\Shares\test\_COMMON\ProdSW\* copied to /data/test/COMMON/ProdSW/
- No reverse flow in either direction (test data never returns to DOS)

**Junction Created:**
- Target: C:\Shares\test\COMMON → C:\Shares\test\_COMMON
- Eliminates duplicate file maintenance
- Backup saved to C:\Shares\test\COMMON.backup

## Files Modified
- DOS_DEPLOYMENT_GUIDE.md: Added automatic startup sequence
- docs/DEPLOYMENT_GUIDE.md: Updated post-reboot expectations
- docs/ENGINEER_HOWTO_GUIDE.md: Added MENUX menu loading step
- credentials.md: Documented startup sequence and MENUX interface
- session-logs/2026-01-19-session.md: Added startup documentation

## Files Added
- 8 PowerShell deployment/verification scripts
- 3 HTML documentation exports
- TS-4R complete backup (not committed to git)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
 2026-01-20 16:03:00 -07:00
Mike Swanson
9fd6a7751c docs: Add comprehensive DOS Update System documentation for engineers and test staff 
Created complete documentation suite for the DOS Update System with three
main guides plus screenshot specifications for PDF conversion.

Files Created:

ENGINEER_CHANGELOG.md (481 lines):
- Complete technical change log documenting all modifications
- File-by-file breakdown of changes (AUTOEXEC, NWTOC, CTONW, DEPLOY, UPDATE)
- DOS 6.22 compatibility verification details
- 24 NUL device reference fixes documented
- 52% code reduction in DEPLOY.BAT explained
- Workflow comparison (manual vs automatic)
- Performance impact analysis
- Testing results and rollback procedures
- Technical appendices (NUL device issue, multi-pipe issue)
- Change statistics and git commit references

ENGINEER_HOWTO_GUIDE.md (1,065 lines):
- Step-by-step procedures for engineers
- Network share access (map drive, UNC path)
- File placement guide with table (batch, exe, config files)
- Detailed sync process explanation with timing
- Update workflow (normal automatic, expedited manual, system files)
- Comprehensive troubleshooting guide (10 common issues):
  * Cannot access AD2 share
  * File copied but DOS not updated
  * Sync not happening after 15 minutes
  * Invalid path errors on DOS
  * DEPLOY.BAT failures
  * System files not updating
  * CTONW upload failures
  * Network drive not mapped
  * Backup files accumulating
  * Performance issues
- Best practices (naming, testing, backup, communication, version control)
- FAQ section (13 questions)
- 4 screenshot placeholders for Windows operations

DEPLOYMENT_GUIDE.md (994 lines):
- User-friendly guide for test staff and technicians
- "What's New" section highlighting automatic updates
- Daily operations walkthrough
- Initial deployment procedure (7 detailed steps)
- Boot process explanation with timing breakdown
- Component descriptions (AUTOEXEC, NWTOC, CTONW, UPDATE, CHECKUPD, STAGE, REBOOT)
- Manual operations guide (when and how to use)
- Troubleshooting section (7 common issues)
- FAQ for test staff (10 questions)
- Quick Reference Card at end
- 9 screenshot placeholders for DOS screens

SCREENSHOT_GUIDE.md (520 lines):
- Complete specifications for all documentation screenshots
- 13 total screenshots needed (4 Windows, 9 DOS)
- Detailed capture instructions for each screenshot
- Equipment requirements and capture tools
- Screenshot specifications (format, resolution, naming)
- Quality guidelines and post-processing steps
- Recommended capture session workflow
- PDF integration instructions (Pandoc, VSCode, online)
- Priority classification (high/medium/low)

Documentation Features:
- Professional structure with clear hierarchy
- Audience-appropriate language (technical vs non-technical)
- Comprehensive table of contents in how-to guides
- ASCII diagrams for system architecture and sync flow
- Code blocks with proper batch syntax
- Tables for quick reference
- Consistent ASCII markers: [OK], [ERROR], [WARNING], [INFO]
- Cross-references between documents
- PDF-ready formatting (proper headers, sections, page break hints)

Frontend Design Review Completed:
- All documents validated for PDF conversion readiness
- Structure and hierarchy confirmed excellent
- Readability verified for target audiences
- Screenshot placeholders properly marked
- Tables and code blocks confirmed PDF-compatible
- Minor recommendations provided for enhanced PDF appearance

Target Audience:
- Engineers: Technical change log and how-to guide
- Test Staff: Non-technical deployment guide
- Documentation Team: Screenshot capture specifications

Ready for PDF Conversion:
- All markdown properly formatted
- Screenshot placeholders clearly marked
- Can be converted using Pandoc, VSCode extensions, or online tools
- Suitable for distribution to engineering and test teams

This documentation suite provides complete coverage for deploying,
maintaining, and troubleshooting the DOS Update System across all
~30 DOS test machines at Dataforth.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
 2026-01-20 16:03:00 -07:00
Mike Swanson
06f7617718 feat: Major directory reorganization and cleanup 
Reorganized project structure for better maintainability and reduced
disk usage by 95.9% (11 GB -> 451 MB).

Directory Reorganization (85% reduction in root files):
- Created docs/ with subdirectories (deployment, testing, database, etc.)
- Created infrastructure/vpn-configs/ for VPN scripts
- Moved 90+ files from root to organized locations
- Archived obsolete documentation (context system, offline mode, zombie debugging)
- Moved all test files to tests/ directory
- Root directory: 119 files -> 18 files

Disk Cleanup (10.55 GB recovered):
- Deleted Rust build artifacts: 9.6 GB (target/ directories)
- Deleted Python virtual environments: 161 MB (venv/ directories)
- Deleted Python cache: 50 KB (__pycache__/)

New Structure:
- docs/ - All documentation organized by category
- docs/archives/ - Obsolete but preserved documentation
- infrastructure/ - VPN configs and SSH setup
- tests/ - All test files consolidated
- logs/ - Ready for future logs

Benefits:
- Cleaner root directory (18 vs 119 files)
- Logical organization of documentation
- 95.9% disk space reduction
- Faster navigation and discovery
- Better portability (build artifacts excluded)

Build artifacts can be regenerated:
- Rust: cargo build --release (5-15 min per project)
- Python: pip install -r requirements.txt (2-3 min)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
 2026-01-18 20:42:28 -07:00