# DOS Update System - Engineer Guide

Document Version: 1.0

Date: January 19, 2026

Audience: Engineers and System Administrators

Prerequisites: Network access to \\AD2\test\ share

## Quick Start

To deploy a software update:

1. Map network drive to `\\AD2\test`
2. Copy files to: `\\AD2\test\COMMON\ProdSW\`
3. Wait 15 minutes for sync to NAS
4. DOS machines download on next reboot

## Accessing the Test Share

### Map Network Drive

Windows File Explorer:

1. Open File Explorer
2. Click "Map network drive"
3. Drive letter: `T:`
4. Path: `\\AD2\test`
5. Credentials: `INTRANET\[your-username]`

Once mapped successfully, you'll see T: drive appear in File Explorer with access to the test share folders.

Command Line:

    net use T: \\AD2\test /persistent:yes

PowerShell:

    New-PSDrive -Name "T" -PSProvider FileSystem -Root "\\AD2\test" -Persist

### Direct UNC Path

    copy C:\MyFiles\*.BAT \\AD2\test\COMMON\ProdSW\

### Folder Structure

    \\AD2\test\
    ├── COMMON\
    │   ├── ProdSW\      ← Batch files, executables, configs
    │   ├── DOS\         ← System files (AUTOEXEC.NEW, CONFIG.NEW)
    │   └── NET\         ← Network client updates
    ├── TS-01\           ← Machine-specific folders
    ├── TS-02\
    └── TS-30\

When you open `\\AD2\test\` in Windows Explorer, you'll see the COMMON folder plus numbered folders (TS-01 through TS-30) for each test machine.

## File Placement Guide

File Type | Destination | Scope | Deployed To
--- | --- | --- | ---
Batch files (.BAT) | `\\AD2\test\COMMON\ProdSW\` | All machines | C:\BAT\
Executables (.EXE) | `\\AD2\test\COMMON\ProdSW\` | All machines | C:\ATE\
Config files (.CFG) | `\\AD2\test\COMMON\ProdSW\` | All machines | C:\ATE\
System files (.NEW) | `\\AD2\test\COMMON\DOS\` | All machines | Staged for reboot
Machine-specific | `\\AD2\test\TS-XX\ProdSW\` | Single machine | C:\BAT\ and C:\ATE\

### Deploy Batch File Update

1. Access: `\\AD2\test\COMMON\ProdSW\`
2. Backup existing file (rename to .BAK)
3. Copy new file to share
4. Verify file size and timestamp
5. Wait 15 minutes for sync
6. DOS machines download on next reboot

The file copy should complete instantly. You'll see the new file appear in the ProdSW folder with the current date and time.

## Sync Process

┌─────────────────────────────────────────────────────────────────┐ │ Step 1: Engineer places file on AD2 │ │ Location: \\AD2\test\COMMON\ProdSW\NEWFILE.BAT │ │ Time: 0 minutes │ └─────────────────────────────────────────────────────────────────┘ │ │ Automatic Sync (every 15 minutes) │ ▼ ┌─────────────────────────────────────────────────────────────────┐ │ Step 2: File syncs to NAS │ │ Location: /data/test/COMMON/ProdSW/NEWFILE.BAT │ │ DOS Access: T:\COMMON\ProdSW\NEWFILE.BAT │ │ Time: 0-15 minutes │ └─────────────────────────────────────────────────────────────────┘ │ │ DOS machine reboots │ ▼ ┌─────────────────────────────────────────────────────────────────┐ │ Step 3: NWTOC downloads to DOS machine │ │ Location: C:\BAT\NEWFILE.BAT │ │ Status: Ready to use │ └─────────────────────────────────────────────────────────────────┘

### Timing

Action | Time
--- | ---
Copy to AD2 | Instant
AD2 → NAS sync | 0-15 minutes
NAS → DOS machine | Next reboot

For urgent updates: Ask test staff to reboot machine or manually run NWTOC.BAT

## Troubleshooting

### Cannot Access \\AD2\test\

Solutions:

1. Verify credentials: `INTRANET\username`
2. Ping AD2: `ping 192.168.0.6`
3. Enable SMB1 if required (Windows 10+)
4. If still unable to access, contact IT

If the network path is not accessible, Windows will display an error: "\\AD2\test is not accessible. You might not have permission to use this network resource."

### File Not Updating on DOS Machine

Check:

1. File exists on AD2: `dir \\AD2\test\COMMON\ProdSW\FILENAME.BAT`
2. Wait 15+ minutes for sync
3. Verify on NAS: `DIR T:\COMMON\ProdSW\` on DOS machine
4. Check DOS clock (must be correct for XCOPY /D to work)
5. Force update: Delete file on DOS, run NWTOC

### Sync Not Happening

Check:

1. Scheduled task on AD2 is running
2. NAS is accessible from AD2
3. Ping NAS: `ping 192.168.0.9`
4. Contact IT to manually trigger sync

## Best Practices

### File Naming

Use:

- Uppercase: `MYFILE.BAT`
- 8.3 format: `FILENAME.EXT`
- Underscores: `MY_FILE.BAT`
- Dates: `FILE_20260119.BAT`

Avoid:

- Spaces: `MY FILE.BAT`
- Special characters: `FILE@#$.BAT`
- Long names: `VERYLONGFILENAME.BAT`

### Testing

Always test on TS-30 first:

1. Deploy to `\\AD2\test\TS-30\ProdSW\`
2. Wait for sync + reboot TS-30
3. Verify functionality
4. Deploy to COMMON if successful

### Backup

Before deploying:

1. Rename old file to .BAK
2. Or copy to `_backup\` folder
3. Include date in backup filename
4. Keep backups for 30 days

### Communication

Notify test staff:

- Email: What changed, expected behavior
- Urgent updates: Phone or Teams
- System file updates: Schedule during off-hours

## Quick Reference

Deployment time: 15 minutes to 24 hours (depending on reboot schedule)

File locations:

- COMMON: All 30 machines
- TS-XX: Specific machine only
- Machine-specific overrides COMMON

Emergency rollback:

    copy \\AD2\test\COMMON\ProdSW\_backup\FILE.BAK \\AD2\test\COMMON\ProdSW\FILE.BAT