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>
11 KiB
DOS Update System - Deployment Guide
Last Updated: 2026-01-19 Target Systems: ~30 DOS 6.22 test stations (TS-4R, TS-7A, TS-12B, etc.) Deployment Script: DEPLOY.BAT Status: Ready for Production Deployment
Overview
This guide walks through deploying the new DOS Update System to test station machines. The deployment is a one-time process per machine that installs batch files and configures the machine for automatic updates.
What Gets Installed:
- NWTOC.BAT - Download updates from network
- CTONW.BAT - Upload changes to network
- UPDATE.BAT - Full system backup
- STAGE.BAT - System file staging
- REBOOT.BAT - Apply updates on reboot
- CHECKUPD.BAT - Check for available updates
Installation Location: C:\BAT\
Prerequisites
Before You Start
-
Network Drive Must Be Mapped
- T: drive must be mapped to \D2TESTNAS\test
- Verify by typing
T:at DOS prompt - If not mapped, run:
C:\NET\STARTNET.BAT
-
Have Machine Name Ready
- Know this machine's identifier (e.g., TS-4R, TS-7A, TS-12B)
- Machine name must match folder structure on network
- Check with supervisor if unsure
-
Backup Current AUTOEXEC.BAT (Optional)
- Script will create C:\AUTOEXEC.SAV automatically
- Manual backup:
COPY C:\AUTOEXEC.BAT C:\AUTOEXEC.OLD
-
Ensure Free Disk Space
- Need ~100 KB free on C: drive
- Check with:
CHKDSK C:
Deployment Steps
Step 1: Navigate to Deployment Script
T:
CD \COMMON\ProdSW
DIR DEPLOY.BAT
You should see DEPLOY.BAT listed. If not found, contact system administrator.
Step 2: Run DEPLOY.BAT
DEPLOY
Expected Output:
==============================================================
DOS Update System - One-Time Deployment
==============================================================
This script will install the new update system on this machine.
What will be installed:
- NWTOC.BAT (Download updates from network)
- CTONW.BAT (Upload changes to network)
- UPDATE.BAT (Full system backup)
- STAGE.BAT (System file staging)
- REBOOT.BAT (Apply updates on reboot)
- CHECKUPD.BAT (Check for updates)
Press any key to continue...
Press any key to continue.
Step 3: Verification Phase
Script checks:
-
T: Drive Accessible
[STEP 1/5] Checking network drive... [OK] T: drive is accessible T: = \\D2TESTNAS\test -
Deployment Files Present
[STEP 2/5] Verifying deployment files... [OK] All deployment files found on network Location: T:\COMMON\ProdSW\
If either check fails, script stops with error message.
Step 4: Enter Machine Name
[STEP 3/5] Configure machine name...
Enter this machine's name (e.g., TS-4R, TS-7A, TS-12B):
Machine name must match the folder on T: drive.
Example: If this is TS-4R, there should be T:\TS-4R\
Machine name: _
Enter your machine name (e.g., TS-4R) and press Enter.
Expected Output:
[OK] Machine name: TS-4R
Checking for T:\TS-4R\ folder...
[OK] Machine folder ready: T:\TS-4R\
Script creates the folder on network if it doesn't exist.
Step 5: File Installation
[STEP 4/5] Installing update system files...
Backing up AUTOEXEC.BAT...
[OK] Backup created: C:\AUTOEXEC.SAV
Copying update system files to C:\BAT\...
[OK] NWTOC.BAT
[OK] CTONW.BAT
[OK] UPDATE.BAT
[OK] STAGE.BAT
[OK] CHECKUPD.BAT
[OK] All update system files installed
Step 6: AUTOEXEC.BAT Update
[STEP 5/5] Updating AUTOEXEC.BAT...
[OK] Added to AUTOEXEC.BAT: SET MACHINE=TS-4R
Script adds SET MACHINE=TS-4R to your AUTOEXEC.BAT file.
Step 7: Deployment Complete
==============================================================
Deployment Complete!
==============================================================
The DOS Update System has been installed on this machine.
Machine name: TS-4R
Backup location: T:\TS-4R\BACKUP\
Update location: T:\COMMON\ProdSW\
==============================================================
Available Commands:
==============================================================
NWTOC - Download updates from network
CTONW - Upload local changes to network
UPDATE - Backup entire C: drive to network
CHECKUPD - Check for available updates
==============================================================
Next Steps:
==============================================================
1. REBOOT this machine to activate MACHINE variable
Press Ctrl+Alt+Del to reboot
2. After reboot, run NWTOC to download all updates:
C:\BAT\NWTOC
3. Create initial backup:
C:\BAT\UPDATE
==============================================================
Deployment log saved to: T:\TS-4R\DEPLOY.LOG
Press any key to exit...
Post-Deployment Steps
1. Reboot Machine
REQUIRED: You must reboot for MACHINE variable to take effect.
Press Ctrl+Alt+Del
Wait for machine to restart and DOS to load.
2. Run Initial NWTOC
After reboot, download all available updates:
C:\BAT\NWTOC
Expected Output:
==============================================================
Download: Network to Computer (NWTOC)
==============================================================
Machine: TS-4R
Source: T:\COMMON\ProdSW and T:\TS-4R\ProdSW
Target: C:\BAT, C:\ATE
==============================================================
[1/2] Downloading shared updates from COMMON...
[OK] Shared updates downloaded
[2/2] Downloading machine-specific updates...
[OK] Machine-specific updates downloaded
==============================================================
Download Complete
==============================================================
3. Create Initial Backup
Backup your current system state:
C:\BAT\UPDATE
This creates a full backup of C: drive to T:\TS-4R\BACKUP.
WARNING: First backup can take 15-30 minutes depending on data size.
Daily Usage
Checking for Updates
CHECKUPD
Shows available updates without downloading them.
Downloading Updates
NWTOC
Downloads and applies updates from network. Run this:
- At start of shift
- After supervisor announces new updates
- When CHECKUPD shows updates available
Uploading Changes
CTONW
Uploads your local changes to network (machine-specific location).
CTONW COMMON
Uploads to COMMON location (affects all machines - requires confirmation).
Creating Backup
UPDATE
Creates full backup before making changes.
Troubleshooting
ERROR: T: drive not available
Problem: Network drive not mapped.
Solution:
C:\NET\STARTNET.BAT
Or manually map:
NET USE T: \\D2TESTNAS\test /YES
ERROR: MACHINE variable not set
Problem: AUTOEXEC.BAT not updated or machine not rebooted.
Solution:
- Check AUTOEXEC.BAT contains:
SET MACHINE=TS-4R - If missing, add line manually
- Reboot machine:
Ctrl+Alt+Del
Or set temporarily:
SET MACHINE=TS-4R
ERROR: Deployment files not found on network
Problem: Files not synced from AD2 to NAS yet.
Solution:
- Wait 15 minutes (sync runs every 15 minutes)
- Contact system administrator
ERROR: Could not backup AUTOEXEC.BAT
Problem: C: drive may be write-protected or full.
Solution:
- Check disk space:
CHKDSK C: - Continue deployment anyway (Choose Y when prompted)
- Backup AUTOEXEC.BAT manually after deployment
WARNING: MACHINE variable already exists
Problem: DEPLOY.BAT was run before.
Solution:
- Check current AUTOEXEC.BAT for existing MACHINE variable
- Choose Y to update, N to skip
- If updating, manually edit AUTOEXEC.BAT to change value
File Locations
Local Machine (DOS)
C:\BAT\ - Update system batch files
C:\ATE\ - Application programs and data
C:\AUTOEXEC.BAT - Startup configuration (modified)
C:\AUTOEXEC.SAV - Backup of original AUTOEXEC.BAT
Network (T: Drive)
T:\COMMON\ProdSW\ - Shared updates (all machines)
T:\TS-4R\ProdSW\ - Machine-specific updates
T:\TS-4R\BACKUP\ - Machine backups (created by UPDATE.BAT)
T:\TS-4R\DEPLOY.LOG - Deployment log
Backend (Automatic Sync)
AD2: C:\Shares\test\COMMON\ProdSW\ - Source for shared updates
AD2: C:\Shares\test\TS-4R\ProdSW\ - Source for machine-specific
NAS: /mnt/raid1/ad2-test/ - D2TESTNAS storage
Deployment Checklist
Use this checklist when deploying to each machine:
- Network drive T: is mapped and accessible
- Know machine name (TS-4R, TS-7A, etc.)
- Run DEPLOY.BAT from T:\COMMON\ProdSW\
- Enter machine name when prompted
- Wait for all files to copy successfully
- Verify deployment complete message
- Reboot machine (Ctrl+Alt+Del)
- After reboot, run C:\BAT\NWTOC
- Verify updates downloaded successfully
- Run C:\BAT\UPDATE to create initial backup
- Verify backup created on network (T:\TS-4R\BACKUP)
- Test CHECKUPD command
- Document deployment in system log
Deployment Status Tracking
Machines Deployed
| Machine | Date | Status | Notes |
|---|---|---|---|
| TS-4R | 2026-01-19 | Testing | Pilot deployment |
| TS-7A | Pending | ||
| TS-12B | Pending | ||
| ... |
Update this table as machines are deployed.
Rollback Procedure
If deployment causes issues:
1. Restore AUTOEXEC.BAT
COPY C:\AUTOEXEC.SAV C:\AUTOEXEC.BAT /Y
2. Remove Batch Files
DEL C:\BAT\NWTOC.BAT
DEL C:\BAT\CTONW.BAT
DEL C:\BAT\UPDATE.BAT
DEL C:\BAT\STAGE.BAT
DEL C:\BAT\CHECKUPD.BAT
3. Reboot
Ctrl+Alt+Del
4. Report Issue
Contact system administrator with:
- Machine name
- Error messages seen
- When the issue occurred
- T:\TS-4R\DEPLOY.LOG contents
Support Contacts
System Administrator: [Your contact info]
Deployment Issues: Check T:\TS-4R\DEPLOY.LOG first
Network Issues: Verify T: drive with NET USE
Appendix: Behind the Scenes
How Updates Flow
- System Administrator copies files to AD2 (\192.168.0.6\C$\Shares\test)
- AD2 Sync Script runs every 15 minutes, pushes to NAS
- NAS makes files available via T: drive to DOS machines
- DOS Machines run NWTOC to download updates
- Users run CTONW to upload machine-specific changes
Sync Schedule
- AD2 → NAS: Every 15 minutes (Sync-FromNAS.ps1)
- Maximum Propagation Time: 15 minutes from AD2 to DOS machine
- Sync Status: Check T:_SYNC_STATUS.txt for last sync time
File Types
Batch Files (.BAT): Update system commands Executables (.EXE): Application programs Data Files (.DAT): Configuration and calibration data Reports (.TXT): Test results uploaded from DOS machines
Deployment Version: 1.0 Script Location: T:\COMMON\ProdSW\DEPLOY.BAT Documentation: D:\ClaudeTools\DOS_DEPLOYMENT_GUIDE.md Last Updated: 2026-01-19