# STARTNET.BAT Path Fix - DOS Update System

**Date:** 2026-01-20
**Issue:** Files reference old path C:\NET\STARTNET.BAT instead of C:\STARTNET.BAT
**Severity:** MEDIUM - Causes deployment to call outdated STARTNET version
**Status:** FIXED and DEPLOYED

---

## Problem Description

During deployment on TS-4R, the system attempted to call `C:\NET\STARTNET.BAT` which is an old version. The current, correct version is at `C:\STARTNET.BAT` (root of C: drive).

**Affected Operations:**
- AUTOEXEC.BAT - Calls wrong STARTNET during boot
- Error messages - Show wrong path to user
- DEPLOY.BAT - Documentation references wrong path

**Impact:**
- Machines may load outdated network configuration
- Users may attempt to run wrong version when troubleshooting
- Inconsistent network drive mapping behavior

---

## Root Cause

All batch files were created with references to `C:\NET\STARTNET.BAT` based on older Dataforth DOS machine configurations. However, the production machines have the current version at `C:\STARTNET.BAT` in the root directory.

The C:\NET\STARTNET.BAT version is outdated and should not be used.

---

## Files Fixed

**Changed references from `C:\NET\STARTNET.BAT` to `C:\STARTNET.BAT` in:**

1. **AUTOEXEC.BAT**
   - Line 37: `IF EXIST C:\STARTNET.BAT CALL C:\STARTNET.BAT`
   - Line 75: Error message showing correct path

2. **DEPLOY.BAT**
   - Line 133: Documentation text updated

3. **UPDATE.BAT**
   - Lines 71-72: Error message showing correct path

4. **CTONW.BAT**
   - Line 35: Error message showing correct path

5. **CHECKUPD.BAT**
   - Line 50: Error message showing correct path

6. **NWTOC.BAT**
   - Line 34: Error message showing correct path

7. **DOSTEST.BAT**
   - Lines 41, 42, 92, 117, 192: All references updated (5 occurrences)

---

## Deployment Status

**Deployed to AD2:** 2026-01-20

**Locations:**
- `\\192.168.0.6\C$\Shares\test\COMMON\ProdSW\` - All 7 files
- `\\192.168.0.6\C$\Shares\test\_COMMON\ProdSW\` - All 7 files

**Sync Status:**
- AD2→NAS sync runs every 15 minutes
- Files will be available on T:\COMMON\ProdSW\ within 15 minutes
- Machines will receive updates on next NWTOC run or reboot

---

## Testing Checklist

Before full rollout, verify on TS-4R:

1. **Check STARTNET.BAT location:**
   ```batch
   DIR C:\STARTNET.BAT
   DIR C:\NET\STARTNET.BAT
   ```
   Expected: C:\STARTNET.BAT exists, C:\NET\STARTNET.BAT may be old version

2. **Verify AUTOEXEC.BAT calls correct version:**
   ```batch
   TYPE C:\AUTOEXEC.BAT | FIND "STARTNET"
   ```
   Expected: Shows `C:\STARTNET.BAT` not `C:\NET\STARTNET.BAT`

3. **Test network startup:**
   ```batch
   C:\STARTNET.BAT
   ```
   Expected: Network starts, T: and X: drives map successfully

4. **Verify error messages show correct path:**
   ```batch
   REM Disconnect network first
   NET USE T: /DELETE
   C:\BAT\UPDATE
   ```
   Expected: Error message shows `C:\STARTNET.BAT` not `C:\NET\STARTNET.BAT`

---

## Combined Fixes in UPDATE.BAT v2.1

**UPDATE.BAT now includes TWO fixes:**
1. XCOPY /D parameter error (2026-01-20 morning)
2. STARTNET.BAT path correction (2026-01-20 afternoon)

**Version:** 2.1
**Changes:**
- Removed invalid `/D` flag from XCOPY command
- Changed `C:\NET\STARTNET.BAT` to `C:\STARTNET.BAT`

---

## Related Files

**Also deployed today:**
- UPDATE.BAT v2.1 (XCOPY fix + STARTNET path fix)
- Root UPDATE.BAT (redirect script, 170 bytes)

**File Structure:**
```
T:\ (root)
├── UPDATE.BAT → Redirect to T:\COMMON\ProdSW\DEPLOY.BAT
│
└── COMMON\ProdSW\
    ├── DEPLOY.BAT - Deployment installer
    ├── UPDATE.BAT - Backup utility (v2.1)
    ├── AUTOEXEC.BAT - Startup template
    ├── STARTNET.BAT - Network startup (v2.0)
    ├── NWTOC.BAT - Download updates
    ├── CTONW.BAT - Upload test data
    ├── CHECKUPD.BAT - Check for updates
    └── DOSTEST.BAT - Test deployment
```

---

## Verification on DOS Machine

When machines get the update, verify correct path is being used:

1. **After reboot, check AUTOEXEC.BAT:**
   ```batch
   TYPE C:\AUTOEXEC.BAT | FIND "STARTNET"
   ```

2. **Verify network starts correctly:**
   ```batch
   DIR T:\
   DIR X:\
   ```

3. **If network fails, manually run:**
   ```batch
   C:\STARTNET.BAT
   ```
   (Should work since AUTOEXEC now calls correct path)

---

## Rollback Plan

If issues occur with the new path:

1. **Verify C:\STARTNET.BAT exists and is current version**
2. **If C:\STARTNET.BAT is missing:**
   - Copy from T:\COMMON\ProdSW\STARTNET.BAT
   - Or revert to C:\NET\STARTNET.BAT temporarily

3. **If C:\NET\STARTNET.BAT is needed:**
   - Revert AUTOEXEC.BAT to call C:\NET\STARTNET.BAT
   - But verify why C:\STARTNET.BAT is missing

---

## Notes

**Why C:\STARTNET.BAT vs C:\NET\STARTNET.BAT?**

The batch files should reference wherever the CURRENT version is on the production machines. User confirmed that C:\STARTNET.BAT is the correct, current location and C:\NET\STARTNET.BAT is outdated.

**File placement flexibility:**
- STARTNET.BAT can be in either location
- AUTOEXEC.BAT just needs to reference the correct location
- The version at C:\STARTNET.BAT is version 2.0 (last modified 2026-01-19)

---

## Success Criteria

- Machines boot and call C:\STARTNET.BAT (not C:\NET\STARTNET.BAT)
- Network starts successfully on boot
- T: and X: drives map correctly
- Error messages show correct path (C:\STARTNET.BAT)
- No references to C:\NET\STARTNET.BAT in production files

---

**Deployment Summary:**
- 7 files fixed
- 14 total deployments (7 to COMMON, 7 to _COMMON)
- All deployments successful
- Ready for production use

**Next Session:** Monitor TS-4R after sync completes, verify UPDATE.BAT backup works correctly
