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>
This commit is contained in:
2026-01-19 19:30:25 -07:00
parent 8b33a42636
commit 9fd6a7751c
4 changed files with 3154 additions and 0 deletions

617
docs/SCREENSHOT_GUIDE.md Normal file
View File

@@ -0,0 +1,617 @@
# Screenshot Guide for DOS Update System Documentation
**Document Version:** 1.0
**Date:** January 19, 2026
**Purpose:** Guide for capturing screenshots for all three documentation PDFs
**Audience:** Documentation Team, Engineers
---
## Overview
This guide describes all screenshots needed for the three DOS Update System documentation files. Each screenshot placeholder in the documentation should be replaced with the actual screenshot as described below.
**Total Screenshots Needed:** 14 screenshots across 3 documents
---
## Equipment Needed
- Windows 10/11 PC for AD2 share access screenshots
- DOS machine (TS-01 through TS-30) for DOS screen captures
- Screen capture tool (Snipping Tool, Snagit, or camera for DOS screens)
- Image editing software (optional, for cropping/annotations)
---
## Screenshot Specifications
### Format:
- **File Format:** PNG (preferred) or JPG
- **Resolution:** Minimum 1024x768 for Windows, as-is for DOS
- **Color Depth:** 24-bit color minimum
- **File Size:** Maximum 2 MB per image
### Naming Convention:
```
docs/screenshots/[document-abbreviation]-[number]-[description].png
Examples:
- docs/screenshots/CHANGELOG-01-file-flow-diagram.png
- docs/screenshots/HOWTO-01-map-network-drive.png
- docs/screenshots/DEPLOY-01-dos-prompt-ready.png
```
### Quality Guidelines:
- Clear, readable text in all screenshots
- No personal information visible (passwords, usernames)
- Crop to relevant area only
- Add borders if needed for clarity
- Include mouse cursor only if demonstrating interaction
---
## Engineer How-To Guide Screenshots (6 total)
### Screenshot HOWTO-01: Map Network Drive Dialog
**Location:** Section "Accessing the Test Share" → "Option 1: Map Network Drive"
**Platform:** Windows 10/11
**What to Capture:**
- Windows "Map network drive" dialog
- Drive letter field showing: `T:`
- Folder field showing: `\\AD2\test`
- "Reconnect at sign-in" checkbox (checked)
- "Finish" button visible
**Steps to Capture:**
1. Open File Explorer
2. Click "This PC" → "Map network drive"
3. Fill in T: and \\AD2\test
4. Check "Reconnect at sign-in"
5. Take screenshot before clicking Finish
6. Crop to dialog box only
**Placeholder Text:**
```markdown
![Screenshot: Map Network Drive Dialog]
*Screenshot placeholder: Windows "Map network drive" dialog showing \\AD2\test path*
```
**Suggested Dimensions:** 600x400 pixels
---
### Screenshot HOWTO-02: Test Share Folder Structure
**Location:** Section "Accessing the Test Share" → "Verifying Access"
**Platform:** Windows 10/11 Explorer
**What to Capture:**
- Windows Explorer showing: `\\AD2\test\`
- Folders visible:
- COMMON (with folder icon)
- TS-01 through TS-30 (first 5-6 visible is fine)
- Address bar showing: `\\AD2\test`
- Standard Explorer view (Details or List view)
**Steps to Capture:**
1. Navigate to \\AD2\test in Explorer
2. Ensure folders are sorted alphabetically
3. Show COMMON folder and several TS-XX folders
4. Take screenshot
5. Crop to Explorer window (include address bar, exclude ribbon if possible)
**Placeholder Text:**
```markdown
![Screenshot: Test Share Folder Structure]
*Screenshot placeholder: Windows Explorer showing \\AD2\test\ folder structure with COMMON and TS-XX folders*
```
**Suggested Dimensions:** 800x600 pixels
---
### Screenshot HOWTO-03: File Copy Operation
**Location:** Section "File Placement Guide" → "Step-by-Step: Deploy Batch File Update"
**Platform:** Windows 10/11 Explorer
**What to Capture:**
- Windows Explorer copy dialog
- Source showing: (local file path)
- Destination showing: `\\AD2\test\COMMON\ProdSW\`
- File being copied: `CHECKUPD.BAT` (or similar .BAT file)
- Progress bar (if possible, otherwise just the dialog)
- "Replace" or "Overwrite" prompt if visible
**Steps to Capture:**
1. Navigate to \\AD2\test\COMMON\ProdSW\
2. Drag a .BAT file to the folder
3. If prompted to replace, take screenshot
4. OR take screenshot of file mid-copy (if large enough)
5. Crop to relevant dialog
**Placeholder Text:**
```markdown
![Screenshot: File Copy Operation]
*Screenshot placeholder: Windows Explorer copying CHECKUPD.BAT to \\AD2\test\COMMON\ProdSW\*
```
**Suggested Dimensions:** 500x300 pixels
---
### Screenshot HOWTO-04: Network Path Not Found Error
**Location:** Section "Troubleshooting Guide" → "Issue 1: Cannot Access \\AD2\test\"
**Platform:** Windows 10/11 Error Dialog
**What to Capture:**
- Windows error dialog showing:
- Title: "Network Error" or similar
- Message: "\\AD2\test is not accessible" or "Network path not found"
- Error icon (red X or yellow warning)
- OK button
**Steps to Capture:**
1. **Option A:** Disconnect VPN and try to access \\AD2\test (will generate error)
2. **Option B:** Type invalid path like \\INVALID\test in Explorer
3. **Option C:** Mock up the error dialog (if real error unavailable)
4. Take screenshot of error dialog
5. Crop to dialog only
**Placeholder Text:**
```markdown
![Screenshot: Network Path Not Found Error]
*Screenshot placeholder: Windows error dialog showing "\\AD2\test is not accessible"*
```
**Suggested Dimensions:** 450x250 pixels
---
### Screenshot HOWTO-05: Sync Process Diagram
**Location:** Section "Sync Process Explained" → "How Sync Works"
**Platform:** N/A (Already ASCII diagram in document)
**Action:** **NO SCREENSHOT NEEDED**
- The sync process is already shown as an ASCII art flowchart
- This renders well in PDF as-is
- Keep existing text diagram
---
### Screenshot HOWTO-06: Sync Timing Table
**Location:** Section "Sync Process Explained" → "Sync Timing"
**Platform:** N/A (Already a table in document)
**Action:** **NO SCREENSHOT NEEDED**
- Sync timing is already in table format
- Renders well in PDF as-is
- Keep existing markdown table
---
## Deployment Guide Screenshots (7 total)
### Screenshot DEPLOY-01: DOS Prompt Ready
**Location:** Section "Initial Deployment" → "Step 1: Boot Machine"
**Platform:** DOS 6.22 machine
**What to Capture:**
- DOS screen showing:
- `C:\>` prompt
- Previous line showing: `Dataforth Test Machine: TS-04` (or similar)
- Clean screen (not mid-process)
- Blinking cursor at prompt (if possible)
**Steps to Capture:**
1. Boot DOS machine
2. Let it reach C:\> prompt
3. Clear screen if needed (CLS command)
4. Type nothing (clean prompt)
5. Take photo or screen capture
6. Crop to terminal area only
**Placeholder Text:**
```markdown
![Screenshot: DOS Prompt Ready]
*Screenshot placeholder: DOS C:\> prompt with machine name displayed*
```
**Suggested Dimensions:** Full screen DOS (typically 640x480 or 720x400)
**Note:** For DOS screenshots, use a camera or DOS screen capture utility. Ensure text is readable.
---
### Screenshot DEPLOY-02: T Drive Contents
**Location:** Section "Initial Deployment" → "Step 2: Verify Network Access"
**Platform:** DOS 6.22 machine
**What to Capture:**
- DOS screen showing:
- Command entered: `DIR T:\`
- Output showing:
- `Volume in drive T: is test`
- Directory listing with folders:
- `COMMON <DIR>`
- `TS-01 <DIR>`
- `TS-02 <DIR>`
- (several more TS-XX folders)
- File count and bytes free at bottom
**Steps to Capture:**
1. At DOS prompt, type: `DIR T:\`
2. Press Enter
3. Wait for directory listing to complete
4. Take photo/screenshot
5. Ensure all text is readable
**Placeholder Text:**
```markdown
![Screenshot: T Drive Contents]
*Screenshot placeholder: DOS DIR T:\ output showing COMMON and TS-XX folders*
```
**Suggested Dimensions:** Full screen DOS
---
### Screenshot DEPLOY-03: Running UPDATE.BAT
**Location:** Section "Initial Deployment" → "Step 3: Run Deployment Command"
**Platform:** DOS 6.22 machine
**What to Capture:**
- DOS screen showing:
- Command line: `T:\UPDATE.BAT TS-04`
- Cursor at end of line (before pressing Enter)
- OR: Just after pressing Enter, showing first line of output
**Steps to Capture:**
1. Type: `T:\UPDATE.BAT TS-04`
2. **Before pressing Enter:** Take screenshot (shows command entry)
3. OR: Press Enter and immediately screenshot (shows command + first response)
**Placeholder Text:**
```markdown
![Screenshot: Running UPDATE.BAT]
*Screenshot placeholder: DOS screen showing T:\UPDATE.BAT TS-04 command being entered*
```
**Suggested Dimensions:** Full screen DOS
---
### Screenshot DEPLOY-04: Deployment Starting
**Location:** Section "Initial Deployment" → "Step 4: Watch Deployment Progress"
**Platform:** DOS 6.22 machine
**What to Capture:**
- DOS screen showing:
- Header: `DOS Update System - Deployment`
- Machine name: `Machine: TS-04`
- Text: `Installing automatic update system...`
- File list:
- AUTOEXEC.BAT (startup configuration)
- NWTOC.BAT (download updates)
- etc. (all files listed)
- Bottom line: `Press any key to continue . . .`
**Steps to Capture:**
1. Run deployment: `T:\UPDATE.BAT TS-04`
2. Wait for initial screen to appear
3. When you see "Press any key to continue", take screenshot
4. DO NOT press a key yet
**Placeholder Text:**
```markdown
![Screenshot: Deployment Starting]
*Screenshot placeholder: DOS deployment screen showing file list*
```
**Suggested Dimensions:** Full screen DOS
---
### Screenshot DEPLOY-05: Deployment Progress
**Location:** Section "Initial Deployment" → "Step 5: Deployment Progress"
**Platform:** DOS 6.22 machine
**What to Capture:**
- DOS screen showing:
- Progress messages:
- `[1/3] Creating C:\BAT directory...`
- `[OK] C:\BAT directory ready`
- `[2/3] Copying batch files to C:\BAT...`
- ` [OK] NWTOC.BAT`
- ` [OK] CTONW.BAT`
- (multiple [OK] lines)
**Steps to Capture:**
1. During deployment, watch for [OK] messages
2. Take screenshot mid-deployment (several [OK] visible)
3. Or take screenshot near end of file copy phase
**Placeholder Text:**
```markdown
![Screenshot: Deployment Progress]
*Screenshot placeholder: DOS screen showing [OK] messages as files copy*
```
**Suggested Dimensions:** Full screen DOS
---
### Screenshot DEPLOY-06: Deployment Complete
**Location:** Section "Initial Deployment" → "Step 6: Deployment Complete"
**Platform:** DOS 6.22 machine
**What to Capture:**
- DOS screen showing:
- Header: `Deployment Complete!`
- Machine name: `Machine: TS-04`
- Text: `The automatic update system is now installed.`
- List: `What happens on next reboot:`
- Bottom: `REBOOT NOW`
- Final line: `Press Ctrl+Alt+Del to reboot`
- Very bottom: `Press any key to continue . . .`
**Steps to Capture:**
1. Let deployment complete
2. Wait for final screen
3. Take screenshot of completion message
4. DO NOT press any key yet
**Placeholder Text:**
```markdown
![Screenshot: Deployment Complete]
*Screenshot placeholder: DOS screen showing "Deployment Complete!" message*
```
**Suggested Dimensions:** Full screen DOS
---
### Screenshot DEPLOY-07: Normal Boot Sequence
**Location:** Section "Daily Operations" → "Normal Boot Sequence"
**Platform:** DOS 6.22 machine
**What to Capture:**
- DOS screen showing:
- Machine header: `Dataforth Test Machine: TS-04`
- Network status: `[OK] Network started`
- Network drives listed
- Update progress: `[1/4] Updating batch files...`
- Multiple [OK] status lines
- Final: `System Ready`
- Prompt: `C:\>`
**Steps to Capture:**
1. Reboot DOS machine after deployment
2. Watch boot sequence
3. When you see "System Ready" and C:\> prompt, take screenshot
4. This should show end of boot with several status messages visible
**Placeholder Text:**
```markdown
![Screenshot: Normal Boot Sequence]
*Screenshot placeholder: DOS screen showing complete boot process with all status messages*
```
**Suggested Dimensions:** Full screen DOS
**Note:** This may require multiple screenshots if the boot sequence scrolls. Capture the final screen showing "System Ready" and C:\> prompt with as much of the boot process visible as possible.
---
### Screenshot DEPLOY-08: CHECKUPD Output
**Location:** Section "Manual Operations" → "Manual Update Check"
**Platform:** DOS 6.22 machine
**What to Capture:**
- DOS screen showing:
- Command entered: `C:\BAT\CHECKUPD`
- Output:
- Header: `Update Check: TS-04 from Network`
- `[1/3] Checking T:\COMMON\ProdSW for updates...`
- `[FOUND] 2 newer batch files available:`
- File list with dates
- Summary: `2 updates available`
- Instruction: `To download updates: C:\BAT\NWTOC`
**Steps to Capture:**
1. Run: `C:\BAT\CHECKUPD`
2. Wait for output to complete
3. Take screenshot showing results
4. If output is longer than one screen, capture the summary section
**Placeholder Text:**
```markdown
![Screenshot: CHECKUPD Output]
*Screenshot placeholder: DOS screen showing CHECKUPD results with 2 updates available*
```
**Suggested Dimensions:** Full screen DOS
---
### Screenshot DEPLOY-09: Manual NWTOC
**Location:** Section "Manual Operations" → "Manual Update Download"
**Platform:** DOS 6.22 machine
**What to Capture:**
- DOS screen showing:
- Command entered: `C:\BAT\NWTOC`
- Output:
- `Downloading updates: TS-04 from Network`
- `[1/4] Updating batch files from T:\COMMON\ProdSW...`
- `[OK] Batch files updated from COMMON`
- More update progress messages
- Final: `Update Complete`
**Steps to Capture:**
1. Run: `C:\BAT\NWTOC`
2. Wait for updates to download
3. Take screenshot when complete (showing "Update Complete")
4. Or take mid-process screenshot showing [OK] messages
**Placeholder Text:**
```markdown
![Screenshot: Manual NWTOC]
*Screenshot placeholder: DOS screen showing NWTOC downloading updates manually*
```
**Suggested Dimensions:** Full screen DOS
---
## Engineer Change Log Screenshots (1 total)
### Screenshot CHANGELOG-01: File Flow Diagram
**Location:** Section "System Architecture Overview" → "File Flow Diagram"
**Platform:** N/A (Already ASCII diagram in document)
**Action:** **NO SCREENSHOT NEEDED**
- The file flow diagram is already shown as ASCII art
- This renders well in PDF as-is
- Keep existing text diagram
---
## Summary
### Total Screenshots by Document:
| Document | Screenshots Needed | Notes |
|----------|-------------------|-------|
| **ENGINEER_CHANGELOG.md** | 0 | All diagrams are ASCII art (no screenshots needed) |
| **ENGINEER_HOWTO_GUIDE.md** | 4 | Windows Explorer and error dialogs |
| **DEPLOYMENT_GUIDE.md** | 9 | DOS screen captures (boot, deployment, commands) |
| **TOTAL** | **13** | Mix of Windows and DOS captures |
### Screenshot Priority:
**High Priority (Required for Guide Usability):**
1. DEPLOY-01: DOS Prompt Ready
2. DEPLOY-02: T Drive Contents
3. DEPLOY-04: Deployment Starting
4. DEPLOY-06: Deployment Complete
5. DEPLOY-07: Normal Boot Sequence
6. HOWTO-01: Map Network Drive Dialog
7. HOWTO-02: Test Share Folder Structure
**Medium Priority (Enhances Understanding):**
8. DEPLOY-03: Running UPDATE.BAT
9. DEPLOY-05: Deployment Progress
10. HOWTO-03: File Copy Operation
11. DEPLOY-08: CHECKUPD Output
**Low Priority (Optional, For Completeness):**
12. DEPLOY-09: Manual NWTOC
13. HOWTO-04: Network Path Not Found Error (can be mocked)
---
## Capture Session Workflow
### Recommended Order:
**Session 1: Windows Screenshots (30 minutes)**
1. Set up Windows PC with AD2 share access
2. Capture HOWTO-01 (Map Network Drive)
3. Capture HOWTO-02 (Folder Structure)
4. Capture HOWTO-03 (File Copy)
5. Capture HOWTO-04 (Error Dialog - if possible)
**Session 2: DOS Deployment Screenshots (45 minutes)**
1. Set up DOS machine (TS-04 recommended for consistency)
2. Prepare for deployment
3. Capture DEPLOY-01 (DOS Prompt)
4. Capture DEPLOY-02 (DIR T:\)
5. Run deployment and capture:
- DEPLOY-03 (Running UPDATE.BAT)
- DEPLOY-04 (Deployment Starting)
- DEPLOY-05 (Deployment Progress)
- DEPLOY-06 (Deployment Complete)
6. Reboot machine
7. Capture DEPLOY-07 (Normal Boot Sequence)
**Session 3: DOS Manual Operations Screenshots (20 minutes)**
1. Use deployed DOS machine
2. Capture DEPLOY-08 (CHECKUPD)
3. Capture DEPLOY-09 (Manual NWTOC)
---
## Post-Processing
After capturing all screenshots:
1. **Rename files** according to naming convention:
- `docs/screenshots/HOWTO-01-map-network-drive.png`
- `docs/screenshots/DEPLOY-01-dos-prompt-ready.png`
- etc.
2. **Crop images** to relevant area:
- Remove taskbars, extra whitespace
- Keep borders if helpful for context
- Ensure text is fully visible
3. **Add borders** (optional):
- 1-2px gray border around screenshots
- Helps distinguish from document background
4. **Check image quality:**
- All text readable when zoomed to 100%
- No blur or artifacts
- Proper contrast
5. **Update markdown files:**
- Replace placeholder lines with actual image references
- Add figure numbers if desired
- Test in PDF conversion tool
---
## PDF Integration
### Markdown to PDF Conversion:
**Option 1: Pandoc**
```bash
pandoc DEPLOYMENT_GUIDE.md -o DEPLOYMENT_GUIDE.pdf --pdf-engine=wkhtmltopdf
```
**Option 2: VSCode + Markdown PDF Extension**
1. Install "Markdown PDF" extension
2. Open document in VSCode
3. Right-click → "Markdown PDF: Export (PDF)"
**Option 3: Online Converter**
- Use: https://www.markdowntopdf.com/
- Upload markdown + screenshots folder
- Download generated PDF
### Testing:
1. Convert to PDF after adding screenshots
2. Verify all images appear correctly
3. Check page breaks don't split important sections
4. Ensure tables and code blocks format properly
---
## Contact for Screenshots
**Primary Contact:** Engineering Team Lead
**Backup Contact:** Test Team Lead
**Technical Questions:** IT Support
**Equipment Location:**
- **Windows PC:** Engineering workstation with AD2 access
- **DOS Machine:** TS-04 or TS-30 (designated test machines)
- **Screen Capture Tools:** Available in IT storage
---
**Document End**
*Once screenshots are captured and integrated, all documentation will be ready for PDF distribution to engineering and test staff.*