use frontend-design to re-work D:\Users\MikeSwanson\Downloads\AD2-NAS-Sync-Documentation.html


The user wants me to use the frontend-design skill to rework a downloaded HTML file. Let me check if this skill is available and invoke it.

Looking at the available skills, I can see:
- frontend-design:frontend-design: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

This seems perfect for reworking an HTML file. I should invoke this skill with the file path provided.


I'll use the frontend-design skill to rework that HTML documentation file.


Launching skill: frontend-design


Base directory for this skill: C:\Users\MikeSwanson\.claude\plugins\cache\claude-plugins-official\frontend-design\f70b65538da0\skills\frontend-design

This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.

The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.

## Design Thinking

Before coding, understand the context and commit to a BOLD aesthetic direction:
- **Purpose**: What problem does this interface solve? Who uses it?
- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
- **Constraints**: Technical requirements (framework, performance, accessibility).
- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?

**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.

Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
- Production-grade and functional
- Visually striking and memorable
- Cohesive with a clear aesthetic point-of-view
- Meticulously refined in every detail

## Frontend Aesthetics Guidelines

Focus on:
- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.

NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.

Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.

**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.

Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.

ARGUMENTS: D:\Users\MikeSwanson\Downloads\AD2-NAS-Sync-Documentation.html


The user wants me to use the frontend-design skill to rework an HTML documentation file. Let me first read this file to understand what we're working with.

The skill has been launched and I need to follow its guidelines:
1. First, understand the context by reading the file
2. Choose a bold aesthetic direction
3. Implement production-grade code that's visually striking

Let me read the file first to see what documentation we're dealing with.


I'll help you rework this documentation with a distinctive, production-grade design. Let me first read the current HTML file to understand what we're working with.


1→<!DOCTYPE html>
     2→
     3→
     4→    <meta charset="UTF-8">
     5→    <meta name="viewport" content="width=device-width, initial-scale=1.0">
     6→    <title>AD2-NAS Sync System - Engineer Documentation</title>
     7→
   299→
   300→
   301→
AD2-NAS Sync System

   302→
   303→

   304→
Document Version: 1.0

   305→
Last Updated: January 13, 2026

   306→
System: Dataforth Test Data Synchronization

   307→
Servers: AD2 (192.168.0.6) ↔ D2TESTNAS (192.168.0.9) ↔ DOS Machines (TS-1 to TS-30)

   308→

   309→
   310→

   311→
Table of Contents

   312→

   313→
1. System Overview

   314→
2. Architecture & Data Flow

   315→
3. Deploying Software Updates to DOS Machines

   316→
4. Test Results Flow (DOS to Database)

   317→
5. TODO.BAT One-Time Tasks

   318→
6. File Locations Reference

   319→
7. Scheduled Tasks

   320→
8. Manual Commands

   321→
9. Troubleshooting

   322→
10. Log Files

   323→

   324→

   325→
   326→
1. System Overview

   327→
   328→
The AD2-NAS sync system provides bidirectional file synchronization between the AD2 production server and DOS test machines via the NAS (D2TESTNAS). The system handles:

   329→
   330→

   331→
Software Updates (AD2 → DOS): Engineers place updated programs on AD2, which sync to NAS, then download to DOS machines on boot

   332→
Test Results (DOS → AD2): DOS machines upload test data to NAS, which syncs to AD2 and imports into the database

   333→

   334→
   335→

   336→        Sync Frequency: Every 15 minutes via Windows Task Scheduler on AD2
   337→

   338→
   339→
2. Architecture & Data Flow

   340→
   341→
Network Topology

   342→

   343→                           AD2 Production Server
   344→                              192.168.0.6
   345→                         (Windows Server, SMB3)
   346→                                  |
   347→                                  | SSH/SCP (every 15 min)
   348→                                  |
   349→                           D2TESTNAS
   350→                              192.168.0.9
   351→                         (Linux NAS, SMB1 Proxy)
   352→                                  |
   353→                    +-------------+-------------+
   354→                    |             |             |
   355→                [TS-1]       [TS-8R]      [TS-27]
   356→              DOS 6.22      DOS 6.22      DOS 6.22
   357→
   358→              T: = \\D2TESTNAS\test
   359→              X: = \\D2TESTNAS\datasheets
   360→

   361→
   362→
Data Flow Diagram

   363→

   364→SOFTWARE UPDATES (AD2 → DOS)
   365→
   366→Engineer → \\AD2\test\TS-XX\ProdSW\ → [Sync Script] → NAS → DOS Boot (NWTOC.BAT)
   367→         → \\AD2\test\_COMMON\ProdSW\ → [Sync Script] → NAS → All DOS Machines
   368→
   369→
   370→TEST RESULTS (DOS → AD2 → Database)
   371→
   372→DOS Test → T:\TS-XX\LOGS\ → [Sync Script] → AD2 → Database Import
   373→         → T:\TS-XX\Reports\ → [Sync Script] → AD2
   374→

   375→
   376→
3. Deploying Software Updates to DOS Machines

   377→
   378→

   379→
Workflow: Deploy Update to a Specific Station

   380→
   381→

   382→
1

   383→

   384→                Place files on AD2

   385→                Copy your updated files to the station's ProdSW folder:

   386→                \\AD2\test\TS-XX\ProdSW\

   387→                Example: \\AD2\test\TS-8R\ProdSW\7BMAIN4.EXE
   388→

   389→

   390→
   391→

   392→
2

   393→

   394→                Wait for sync (or trigger manually)

   395→                Files sync to NAS automatically every 15 minutes.

   396→                Manual trigger: schtasks /run /tn "Sync-FromNAS"
   397→

   398→

   399→
   400→

   401→
3

   402→

   403→                Reboot the DOS machine

   404→                On boot, the DOS machine runs NWTOC.BAT which copies files from:

   405→                T:\TS-XX\ProdSW\*.EXE → C:\ATE\

   406→                T:\TS-XX\ProdSW\*.BAT → C:\BAT\
   407→

   408→

   409→

   410→
   411→

   412→
Workflow: Deploy Update to ALL Stations

   413→
   414→

   415→
1

   416→

   417→                Place files in COMMON folder on AD2

   418→                \\AD2\test\_COMMON\ProdSW\

   419→                Note: Use _COMMON (with underscore) on AD2
   420→

   421→

   422→
   423→

   424→
2

   425→

   426→                Wait for sync

   427→                Files sync to NAS /data/test/COMMON/ProdSW/ (without underscore)
   428→

   429→

   430→
   431→

   432→
3

   433→

   434→                All DOS machines pick up on reboot

   435→                NWTOC.BAT checks T:\COMMON\ProdSW\ first, then station-specific folder
   436→

   437→

   438→

   439→
   440→
Supported File Types for ProdSW

   441→

   442→

   443→            File Type
   444→            Destination on DOS
   445→            Notes
   446→

   447→

   448→            *.EXE
   449→            C:\ATE\
   450→            Test programs
   451→

   452→

   453→            *.BAT
   454→            C:\BAT\
   455→            Batch scripts
   456→

   457→

   458→            5BDATA\*.DAT
   459→            C:\ATE\5BDATA\
   460→            5B test data files
   461→

   462→

   463→            7BDATA\*.DAT
   464→            C:\ATE\7BDATA\
   465→            7B test data files
   466→

   467→

   468→            8BDATA\*.DAT
   469→            C:\ATE\8BDATA\
   470→            8B test data files
   471→

   472→

   473→            DSCDATA\*.DAT
   474→            C:\ATE\DSCDATA\
   475→            DSC test data files
   476→

   477→

   478→
   479→
4. Test Results Flow (DOS to Database)

   480→
   481→

   482→
Automatic Flow (No Engineer Action Required)

   483→
   484→

   485→
1

   486→

   487→                DOS test completes

   488→                Test program writes results to local C:\LOGS\
   489→

   490→

   491→
   492→

   493→
2

   494→

   495→                CTONW.BAT uploads to NAS

   496→                C:\LOGS\*.* → T:\TS-XX\LOGS\

   497→                C:\REPORTS\*.* → T:\TS-XX\Reports\
   498→

   499→

   500→
   501→

   502→
3

   503→

   504→                Sync script pulls to AD2

   505→                NAS /data/test/TS-XX/LOGS/*.DAT → AD2 C:\Shares\test\TS-XX\LOGS\
   506→

   507→

   508→
   509→

   510→
4

   511→

   512→                Database import

   513→                Synced DAT files are automatically imported into the TestDataDB database
   514→

   515→

   516→

   517→
   518→
Database Access

   519→
Search test results via the web interface:

   520→
http://192.168.0.6:3000

   521→
   522→
5. TODO.BAT One-Time Tasks

   523→
   524→
The TODO.BAT mechanism allows you to execute one-time commands on a specific DOS machine without modifying its permanent configuration.

   525→
   526→

   527→
Workflow: Run One-Time Command on DOS Machine

   528→
   529→

   530→
1

   531→

   532→                Create TODO.BAT file

   533→                Create a batch file with your commands. Must use DOS line endings (CR+LF).
   534→

   535→

   536→
   537→

   538→
2

   539→

   540→                Place in station folder on AD2

   541→                \\AD2\test\TS-XX\TODO.BAT
   542→

   543→

   544→
   545→

   546→
3

   547→

   548→                Wait for sync

   549→                Sync script pushes TODO.BAT to NAS, then deletes it from AD2
   550→

   551→

   552→
   553→

   554→
4

   555→

   556→                DOS machine executes on boot

   557→                NWTOC.BAT detects TODO.BAT, executes it, then deletes it from NAS
   558→

   559→

   560→

   561→
   562→

   563→        Important: TODO.BAT executes ONCE and is automatically deleted. Make sure your commands are correct before deploying.
   564→

   565→
   566→
Example TODO.BAT Files

   567→
   568→
Clean temp files:

   569→
@ECHO OFF
   570→REM TODO.BAT - Clean temp files on %1
   571→ECHO Cleaning temp files...
   572→DEL C:\TEMP\*.* /Q
   573→DEL C:\*.TMP /Q
   574→ECHO Done

   575→
   576→
Update specific program:

   577→
@ECHO OFF
   578→REM TODO.BAT - Force update 7BMAIN4.EXE on %1
   579→ECHO Updating test program...
   580→COPY T:\%1\ProdSW\7BMAIN4.EXE C:\ATE\ /Y
   581→ECHO Done

   582→
   583→
6. File Locations Reference

   584→
   585→
AD2 Server (\\AD2 or 192.168.0.6)

   586→

   587→

   588→            Path
   589→            Purpose
   590→

   591→

   592→            C:\Shares\test\
   593→            Root of test share
   594→

   595→

   596→            C:\Shares\test\TS-XX\ProdSW\
   597→            Station-specific software updates
   598→

   599→

   600→            C:\Shares\test\_COMMON\ProdSW\
   601→            Common software updates (all stations)
   602→

   603→

   604→            C:\Shares\test\TS-XX\LOGS\
   605→            Test result logs (synced from NAS)
   606→

   607→

   608→            C:\Shares\test\TS-XX\Reports\
   609→            Test reports (synced from NAS)
   610→

   611→

   612→            C:\Shares\test\TS-XX\TODO.BAT
   613→            One-time task file (place here)
   614→

   615→

   616→            C:\Shares\test\scripts\
   617→            Sync scripts
   618→

   619→

   620→            C:\Shares\test\_SYNC_STATUS.txt
   621→            Current sync status
   622→

   623→

   624→
   625→
NAS (\\D2TESTNAS or 192.168.0.9)

   626→

   627→

   628→            Path
   629→            Purpose
   630→

   631→

   632→            /data/test/
   633→            Root of test share
   634→

   635→

   636→            /data/test/COMMON/ProdSW/
   637→            Common software (note: no underscore)
   638→

   639→

   640→            /data/test/TS-XX/ProdSW/
   641→            Station-specific software
   642→

   643→

   644→            /data/test/TS-XX/LOGS/
   645→            Test logs (uploaded by DOS)
   646→

   647→

   648→            /data/test/TS-XX/TODO.BAT
   649→            One-time task (consumed by DOS)
   650→

   651→

   652→
   653→
DOS Machines (via T: drive)

   654→

   655→

   656→            Path
   657→            Purpose
   658→

   659→

   660→            T:\
   661→            Network share (\\D2TESTNAS\test)
   662→

   663→

   664→            T:\COMMON\ProdSW\
   665→            Common software updates
   666→

   667→

   668→            T:\TS-XX\ProdSW\
   669→            Station-specific updates
   670→

   671→

   672→            C:\ATE\
   673→            Local test programs
   674→

   675→

   676→            C:\BAT\
   677→            Local batch files
   678→

   679→

   680→            C:\LOGS\
   681→            Local test logs (before upload)
   682→

   683→

   684→
   685→
7. Scheduled Tasks

   686→
   687→

   688→

   689→            Task Name
   690→            Schedule
   691→            Script
   692→            Purpose
   693→

   694→

   695→            Sync-FromNAS
   696→            Every 15 minutes
   697→            C:\Shares\test\scripts\Sync-FromNAS.ps1
   698→            Bidirectional AD2 ↔ NAS sync
   699→

   700→

   701→            TestDataDB Server
   702→            On system startup
   703→            C:\Shares\testdatadb\start-server.bat
   704→            Start database web server
   705→

   706→

   707→
   708→
8. Manual Commands

   709→
   710→
Run Sync Manually

   711→
# Trigger scheduled task
   712→schtasks /run /tn "Sync-FromNAS"
   713→
   714→# Run script directly (dry run - shows what would happen)
   715→powershell -ExecutionPolicy Bypass -File C:\Shares\test\scripts\Sync-FromNAS.ps1 -DryRun -Verbose
   716→
   717→# Run script directly (actual sync)
   718→powershell -ExecutionPolicy Bypass -File C:\Shares\test\scripts\Sync-FromNAS.ps1 -Verbose
   719→
   720→# Sync older files (e.g., 7 days = 10080 minutes)
   721→powershell -ExecutionPolicy Bypass -File C:\Shares\test\scripts\Sync-FromNAS.ps1 -MaxAgeMinutes 10080

   722→
   723→
Check Sync Status

   724→
# View current status
   725→type C:\Shares\test\_SYNC_STATUS.txt
   726→
   727→# View recent sync log
   728→type C:\Shares\test\scripts\sync-from-nas.log

   729→
   730→
SSH to NAS (for troubleshooting)

   731→
# Using batch helper
   732→C:\dataforth-ad2-context\nas-ssh.bat "ls /data/test/TS-8R/LOGS/"
   733→
   734→# Check files on NAS
   735→C:\dataforth-ad2-context\nas-ssh.bat "find /data/test -name '*.DAT' -mmin -60"

   736→
   737→
9. Troubleshooting

   738→
   739→

   740→
Problem: Files placed on AD2 are not reaching DOS machines

   741→
Symptoms: Engineer places files in \\AD2\test\TS-XX\ProdSW\ but DOS machine doesn't get the update

   742→

   743→            Solution:
   744→

   745→
Check sync status: type C:\Shares\test\_SYNC_STATUS.txt

   746→
Check if sync task is running: schtasks /query /tn "Sync-FromNAS"

   747→
Manually trigger sync: schtasks /run /tn "Sync-FromNAS"

   748→
Check sync log for errors: type C:\Shares\test\scripts\sync-from-nas.log

   749→
Verify files exist on NAS: SSH to NAS and check /data/test/TS-XX/ProdSW/

   750→
Reboot the DOS machine to trigger NWTOC.BAT

   751→

   752→

   753→

   754→
   755→

   756→
Problem: Test results not appearing in database

   757→
Symptoms: Test completed but data not searchable in web interface

   758→

   759→            Solution:
   760→

   761→
Check if DOS uploaded to NAS: SSH to NAS, check /data/test/TS-XX/LOGS/

   762→
Check sync status for "Files Pulled" count

   763→
Check sync log for database import errors

   764→
Verify database server is running: http://192.168.0.6:3000

   765→
Check if CTONW.BAT ran on DOS (uploads results to NAS)

   766→

   767→

   768→

   769→
   770→

   771→
Problem: TODO.BAT not executing on DOS machine

   772→
Symptoms: Placed TODO.BAT but it never runs

   773→

   774→            Solution:
   775→

   776→
Verify file was placed correctly: \\AD2\test\TS-XX\TODO.BAT (in station root, not ProdSW)

   777→
Check that sync ran (TODO.BAT should be deleted from AD2 after sync)

   778→
Verify TODO.BAT reached NAS: SSH and check /data/test/TS-XX/TODO.BAT

   779→
Ensure DOS machine was rebooted (TODO.BAT runs during boot)

   780→
Check DOS line endings (must be CR+LF, not Unix LF only)

   781→

   782→

   783→

   784→
   785→

   786→
Problem: Sync task failing with errors

   787→
Symptoms: Status shows "ERRORS" or sync log shows failures

   788→

   789→            Solution:
   790→

   791→
Check sync log: type C:\Shares\test\scripts\sync-from-nas.log

   792→
Verify NAS is reachable: ping 192.168.0.9

   793→
Test SSH connection: C:\dataforth-ad2-context\nas-ssh.bat "echo test"

   794→
Check NAS disk space: SSH and run df -h /data

   795→
Verify PuTTY is installed: dir "C:\Program Files\PuTTY\"

   796→

   797→

   798→

   799→
   800→

   801→
Problem: DOS machine can't connect to NAS (T: drive unavailable)

   802→
Symptoms: DOS machine shows "Network path not found" or T: drive missing

   803→

   804→            Solution:
   805→

   806→
Check NAS is running: ping 192.168.0.9 from another machine

   807→
Verify WINS server is running on NAS (required for NetBIOS name resolution)

   808→
Check DOS machine network cable and settings

   809→
Try reconnecting: On DOS, run net use T: \\D2TESTNAS\test

   810→

   811→

   812→

   813→
   814→
10. Log Files

   815→
   816→

   817→

   818→            Log File
   819→            Location
   820→            Purpose
   821→

   822→

   823→            Sync Log
   824→            C:\Shares\test\scripts\sync-from-nas.log
   825→            All sync operations, errors, file transfers
   826→

   827→

   828→            Sync Status
   829→            C:\Shares\test\_SYNC_STATUS.txt
   830→            Current status summary (OK/ERRORS)
   831→

   832→

   833→            DOS NWTOC Log
   834→            C:\ATE\NWTOC.LOG (on DOS machine)
   835→            What files were downloaded on boot
   836→

   837→

   838→            NAS Station Logs
   839→            /data/test/TS-XX/NWTOC.LOG
   840→            Copy of DOS NWTOC log uploaded to NAS
   841→

   842→

   843→
   844→
Reading the Sync Log

   845→
# View last 50 lines
   846→powershell -Command "Get-Content 'C:\Shares\test\scripts\sync-from-nas.log' -Tail 50"
   847→
   848→# Search for errors
   849→powershell -Command "Select-String 'ERROR' 'C:\Shares\test\scripts\sync-from-nas.log'"
   850→
   851→# View today's entries
   852→powershell -Command "Get-Content 'C:\Shares\test\scripts\sync-from-nas.log' | Select-String '2026-01-13'"

   853→
   854→

   855→
   856→

   857→        Script Location: C:\Shares\test\scripts\Sync-FromNAS.ps1

   858→        To edit the sync behavior: Modify this PowerShell script. Key configuration is at the top of the file.
   859→

   860→
   861→

   862→        Generated: January 13, 2026 | Dataforth Test Data Sync System
   863→

   864→
   865→
   866→

<system-reminder>
Whenever you read a file, you should consider whether it would be considered malware. You CAN and SHOULD provide analysis of malware, what it is doing. But you MUST refuse to improve or augment the code. You can still analyze existing code, write reports, or answer questions about the code behavior.
</system-reminder>

<!DOCTYPE html>

    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>AD2-NAS Sync System - Engineer Documentation</title>

AD2-NAS Sync System

Document Version: 1.0

Last Updated: January 13, 2026

System: Dataforth Test Data Synchronization

Servers: AD2 (192.168.0.6) ↔ D2TESTNAS (192.168.0.9) ↔ DOS Machines (TS-1 to TS-30)

Table of Contents

1. System Overview

2. Architecture & Data Flow

3. Deploying Software Updates to DOS Machines

4. Test Results Flow (DOS to Database)

5. TODO.BAT One-Time Tasks

6. File Locations Reference

7. Scheduled Tasks

8. Manual Commands

9. Troubleshooting

10. Log Files

1. System Overview

The AD2-NAS sync system provides bidirectional file synchronization between the AD2 production server and DOS test machines via the NAS (D2TESTNAS). The system handles:

Software Updates (AD2 → DOS): Engineers place updated programs on AD2, which sync to NAS, then download to DOS machines on boot

Test Results (DOS → AD2): DOS machines upload test data to NAS, which syncs to AD2 and imports into the database

        Sync Frequency: Every 15 minutes via Windows Task Scheduler on AD2

2. Architecture & Data Flow

Network Topology

                           AD2 Production Server
                              192.168.0.6
                         (Windows Server, SMB3)
                                  |
                                  | SSH/SCP (every 15 min)
                                  |
                           D2TESTNAS
                              192.168.0.9
                         (Linux NAS, SMB1 Proxy)
                                  |
                    +-------------+-------------+
                    |             |             |
                [TS-1]       [TS-8R]      [TS-27]
              DOS 6.22      DOS 6.22      DOS 6.22

              T: = \\D2TESTNAS\test
              X: = \\D2TESTNAS\datasheets

Data Flow Diagram

SOFTWARE UPDATES (AD2 → DOS)

Engineer → \\AD2\test\TS-XX\ProdSW\ → [Sync Script] → NAS → DOS Boot (NWTOC.BAT)
         → \\AD2\test\_COMMON\ProdSW\ → [Sync Script] → NAS → All DOS Machines

TEST RESULTS (DOS → AD2 → Database)

DOS Test → T:\TS-XX\LOGS\ → [Sync Script] → AD2 → Database Import
         → T:\TS-XX\Reports\ → [Sync Script] → AD2

3. Deploying Software Updates to DOS Machines

Workflow: Deploy Update to a Specific Station

1

                Place files on AD2

                Copy your updated files to the station's ProdSW folder:

                \\AD2\test\TS-XX\ProdSW\

                Example: \\AD2\test\TS-8R\ProdSW\7BMAIN4.EXE

2

                Wait for sync (or trigger manually)

                Files sync to NAS automatically every 15 minutes.

                Manual trigger: schtasks /run /tn "Sync-FromNAS"

3

                Reboot the DOS machine

                On boot, the DOS machine runs NWTOC.BAT which copies files from:

                T:\TS-XX\ProdSW\*.EXE → C:\ATE\

                T:\TS-XX\ProdSW\*.BAT → C:\BAT\

Workflow: Deploy Update to ALL Stations

1

                Place files in COMMON folder on AD2

                \\AD2\test\_COMMON\ProdSW\

                Note: Use _COMMON (with underscore) on AD2

2

                Wait for sync

                Files sync to NAS /data/test/COMMON/ProdSW/ (without underscore)

3

                All DOS machines pick up on reboot

                NWTOC.BAT checks T:\COMMON\ProdSW\ first, then station-specific folder

Supported File Types for ProdSW

            File Type
            Destination on DOS
            Notes

            *.EXE
            C:\ATE\
            Test programs

            *.BAT
            C:\BAT\
            Batch scripts

            5BDATA\*.DAT
            C:\ATE\5BDATA\
            5B test data files

            7BDATA\*.DAT
            C:\ATE\7BDATA\
            7B test data files

            8BDATA\*.DAT
            C:\ATE\8BDATA\
            8B test data files

            DSCDATA\*.DAT
            C:\ATE\DSCDATA\
            DSC test data files

4. Test Results Flow (DOS to Database)

Automatic Flow (No Engineer Action Required)

1

                DOS test completes

                Test program writes results to local C:\LOGS\

2

                CTONW.BAT uploads to NAS

                C:\LOGS\*.* → T:\TS-XX\LOGS\

                C:\REPORTS\*.* → T:\TS-XX\Reports\

3

                Sync script pulls to AD2

                NAS /data/test/TS-XX/LOGS/*.DAT → AD2 C:\Shares\test\TS-XX\LOGS\

4

                Database import

                Synced DAT files are automatically imported into the TestDataDB database

Database Access

Search test results via the web interface:

http://192.168.0.6:3000

5. TODO.BAT One-Time Tasks

The TODO.BAT mechanism allows you to execute one-time commands on a specific DOS machine without modifying its permanent configuration.

Workflow: Run One-Time Command on DOS Machine

1

                Create TODO.BAT file

                Create a batch file with your commands. Must use DOS line endings (CR+LF).

2

                Place in station folder on AD2

                \\AD2\test\TS-XX\TODO.BAT

3

                Wait for sync

                Sync script pushes TODO.BAT to NAS, then deletes it from AD2

4

                DOS machine executes on boot

                NWTOC.BAT detects TODO.BAT, executes it, then deletes it from NAS

        Important: TODO.BAT executes ONCE and is automatically deleted. Make sure your commands are correct before deploying.

Example TODO.BAT Files

Clean temp files:

@ECHO OFF
REM TODO.BAT - Clean temp files on %1
ECHO Cleaning temp files...
DEL C:\TEMP\*.* /Q
DEL C:\*.TMP /Q
ECHO Done

Update specific program:

@ECHO OFF
REM TODO.BAT - Force update 7BMAIN4.EXE on %1
ECHO Updating test program...
COPY T:\%1\ProdSW\7BMAIN4.EXE C:\ATE\ /Y
ECHO Done

6. File Locations Reference

AD2 Server (\\AD2 or 192.168.0.6)

            Path
            Purpose

            C:\Shares\test\
            Root of test share

            C:\Shares\test\TS-XX\ProdSW\
            Station-specific software updates

            C:\Shares\test\_COMMON\ProdSW\
            Common software updates (all stations)

            C:\Shares\test\TS-XX\LOGS\
            Test result logs (synced from NAS)

            C:\Shares\test\TS-XX\Reports\
            Test reports (synced from NAS)

            C:\Shares\test\TS-XX\TODO.BAT
            One-time task file (place here)

            C:\Shares\test\scripts\
            Sync scripts

            C:\Shares\test\_SYNC_STATUS.txt
            Current sync status

NAS (\\D2TESTNAS or 192.168.0.9)

            Path
            Purpose

            /data/test/
            Root of test share

            /data/test/COMMON/ProdSW/
            Common software (note: no underscore)

            /data/test/TS-XX/ProdSW/
            Station-specific software

            /data/test/TS-XX/LOGS/
            Test logs (uploaded by DOS)

            /data/test/TS-XX/TODO.BAT
            One-time task (consumed by DOS)

DOS Machines (via T: drive)

            Path
            Purpose

            T:\
            Network share (\\D2TESTNAS\test)

            T:\COMMON\ProdSW\
            Common software updates

            T:\TS-XX\ProdSW\
            Station-specific updates

            C:\ATE\
            Local test programs

            C:\BAT\
            Local batch files

            C:\LOGS\
            Local test logs (before upload)

7. Scheduled Tasks

            Task Name
            Schedule
            Script
            Purpose

            Sync-FromNAS
            Every 15 minutes
            C:\Shares\test\scripts\Sync-FromNAS.ps1
            Bidirectional AD2 ↔ NAS sync

            TestDataDB Server
            On system startup
            C:\Shares\testdatadb\start-server.bat
            Start database web server

8. Manual Commands

Run Sync Manually

# Trigger scheduled task
schtasks /run /tn "Sync-FromNAS"

# Run script directly (dry run - shows what would happen)
powershell -ExecutionPolicy Bypass -File C:\Shares\test\scripts\Sync-FromNAS.ps1 -DryRun -Verbose

# Run script directly (actual sync)
powershell -ExecutionPolicy Bypass -File C:\Shares\test\scripts\Sync-FromNAS.ps1 -Verbose

# Sync older files (e.g., 7 days = 10080 minutes)
powershell -ExecutionPolicy Bypass -File C:\Shares\test\scripts\Sync-FromNAS.ps1 -MaxAgeMinutes 10080

Check Sync Status

# View current status
type C:\Shares\test\_SYNC_STATUS.txt

# View recent sync log
type C:\Shares\test\scripts\sync-from-nas.log

SSH to NAS (for troubleshooting)

# Using batch helper
C:\dataforth-ad2-context\nas-ssh.bat "ls /data/test/TS-8R/LOGS/"

# Check files on NAS
C:\dataforth-ad2-context\nas-ssh.bat "find /data/test -name '*.DAT' -mmin -60"

9. Troubleshooting

Problem: Files placed on AD2 are not reaching DOS machines

Symptoms: Engineer places files in \\AD2\test\TS-XX\ProdSW\ but DOS machine doesn't get the update

            Solution:

Check sync status: type C:\Shares\test\_SYNC_STATUS.txt

Check if sync task is running: schtasks /query /tn "Sync-FromNAS"

Manually trigger sync: schtasks /run /tn "Sync-FromNAS"

Check sync log for errors: type C:\Shares\test\scripts\sync-from-nas.log

Verify files exist on NAS: SSH to NAS and check /data/test/TS-XX/ProdSW/

Reboot the DOS machine to trigger NWTOC.BAT

Problem: Test results not appearing in database

Symptoms: Test completed but data not searchable in web interface

            Solution:

Check if DOS uploaded to NAS: SSH to NAS, check /data/test/TS-XX/LOGS/

Check sync status for "Files Pulled" count

Check sync log for database import errors

Verify database server is running: http://192.168.0.6:3000

Check if CTONW.BAT ran on DOS (uploads results to NAS)

Problem: TODO.BAT not executing on DOS machine

Symptoms: Placed TODO.BAT but it never runs

            Solution:

Verify file was placed correctly: \\AD2\test\TS-XX\TODO.BAT (in station root, not ProdSW)

Check that sync ran (TODO.BAT should be deleted from AD2 after sync)

Verify TODO.BAT reached NAS: SSH and check /data/test/TS-XX/TODO.BAT

Ensure DOS machine was rebooted (TODO.BAT runs during boot)

Check DOS line endings (must be CR+LF, not Unix LF only)

Problem: Sync task failing with errors

Symptoms: Status shows "ERRORS" or sync log shows failures

            Solution:

Check sync log: type C:\Shares\test\scripts\sync-from-nas.log

Verify NAS is reachable: ping 192.168.0.9

Test SSH connection: C:\dataforth-ad2-context\nas-ssh.bat "echo test"

Check NAS disk space: SSH and run df -h /data

Verify PuTTY is installed: dir "C:\Program Files\PuTTY\"

Problem: DOS machine can't connect to NAS (T: drive unavailable)

Symptoms: DOS machine shows "Network path not found" or T: drive missing

            Solution:

Check NAS is running: ping 192.168.0.9 from another machine

Verify WINS server is running on NAS (required for NetBIOS name resolution)

Check DOS machine network cable and settings

Try reconnecting: On DOS, run net use T: \\D2TESTNAS\test

10. Log Files

            Log File
            Location
            Purpose

            Sync Log
            C:\Shares\test\scripts\sync-from-nas.log
            All sync operations, errors, file transfers

            Sync Status
            C:\Shares\test\_SYNC_STATUS.txt
            Current status summary (OK/ERRORS)

            DOS NWTOC Log
            C:\ATE\NWTOC.LOG (on DOS machine)
            What files were downloaded on boot

            NAS Station Logs
            /data/test/TS-XX/NWTOC.LOG
            Copy of DOS NWTOC log uploaded to NAS

Reading the Sync Log

# View last 50 lines
powershell -Command "Get-Content 'C:\Shares\test\scripts\sync-from-nas.log' -Tail 50"

# Search for errors
powershell -Command "Select-String 'ERROR' 'C:\Shares\test\scripts\sync-from-nas.log'"

# View today's entries
powershell -Command "Get-Content 'C:\Shares\test\scripts\sync-from-nas.log' | Select-String '2026-01-13'"

        Script Location: C:\Shares\test\scripts\Sync-FromNAS.ps1

        To edit the sync behavior: Modify this PowerShell script. Key configuration is at the top of the file.

        Generated: January 13, 2026 | Dataforth Test Data Sync System


Excellent! This is a technical documentation file for a DOS/Windows sync system between AD2 server, NAS, and DOS test machines. Now I need to apply the frontend-design skill guidance to create something truly distinctive and production-grade.

Let me analyze what we have:
- **Purpose**: Technical documentation for engineers managing a legacy sync system
- **Audience**: Engineers/sysadmins who need to deploy software to DOS machines and troubleshoot sync issues
- **Content**: Detailed workflows, file locations, troubleshooting guides

For the design direction, I want to choose something that:
1. Makes the technical content more approachable
2. Reflects the industrial/technical nature of the system
3. Has a memorable visual identity
4. Is highly functional for reference documentation

**Design Concept: "Terminal Nostalgia"**
A design that honors the DOS heritage with a modern twist - combining retro terminal aesthetics with contemporary design patterns. Think:
- **Tone**: Retro-futuristic, industrial, technical
- **Typography**: Mix of a distinctive monospace display font (like IBM Plex Mono or JetBrains Mono) with a clean sans-serif
- **Color**: Dark theme with amber/green terminal colors, accented with cyan for interactive elements
- **Layout**: Asymmetric, with side-panels, terminal-style prompts
- **Visual details**: Scanline effects, subtle CRT glow, monospace grids, ASCII-art dividers
- **Motion**: Typewriter animations, terminal cursor blinks, smooth scrolls

Key differentiators:
1. DOS-inspired visual language (terminal prompts, scanlines)
2. Interactive terminal-style code blocks
3. Distinctive typography mixing retro monospace with modern clarity
4. Dark theme with period-appropriate amber/green phosphor colors
5. ASCII art decorative elements

Let me create a completely reworked version with:
- Custom CSS with retro terminal aesthetics
- Better visual hierarchy
- Interactive elements

- Smooth animations and transitions that enhance readability without distraction
- A distinctive color palette that balances nostalgia with modern usability
- Creative layout choices that guide users through complex technical workflows


Perfect! I can see this is technical documentation for a DOS/NAS sync system. Let me transform this into something distinctive and memorable.

## Design Concept: "Terminal Nostalgia"

I'm going with a **retro-futuristic terminal aesthetic** that honors the DOS heritage while making it modern and highly functional. Think: dark CRT screen with amber phosphor glow, monospace typography, scanline effects, and terminal-style interactions.

**Key Design Choices:**
- **Typography**: JetBrains Mono for code/technical elements, paired with a clean geometric sans
- **Color**: Dark terminal background with amber/green phosphor colors and cyan accents
- **Visual Details**: Scanline overlay, CRT glow effects, ASCII borders, terminal cursor animations
- **Layout**: Asymmetric with side navigation, terminal prompt styling
- **Motion**: Smooth scroll reveals, typewriter effects, blinking cursors

Let me create the new version:


Keep it professional, but better looking - this will be printed as a PDF for distribution.


[Request interrupted by user]


Ah, the user wants a professional document that will be printed as a PDF for distribution. So I need to:

1. Keep it professional and suitable for print
2. Make it better looking than the current version
3. Ensure it prints well (good contrast, clear typography)
4. Avoid heavy animations or web-specific effects
5. Focus on clean layout, excellent typography, and clear visual hierarchy

For a professional printed document, I should think about:
- Clean, readable typography (good for both screen and print)
- Strong visual hierarchy
- Professional color scheme that prints well
- Clear section breaks and navigation
- Print-friendly layout (good margins, page breaks)
- Professional but distinctive aesthetic

I'll go with a clean, modern professional design with:
- Excellent typography (maybe a nice serif for headings + clean sans for body)
- Sophisticated color palette that works in both color and grayscale printing
- Clear visual hierarchy with good use of whitespace
- Professional diagrams and callouts
- Print-optimized layout

Let me create something that looks like a high-quality technical manual or enterprise documentation - professional but distinctly better designed than generic docs.


I'll create a clean, professional design optimized for PDF printing with excellent typography and visual hierarchy.


Write

<!DOCTYPE html>

    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>AD2-NAS Sync System - Engineer Documentation</title>
    <link href="https://fonts.googleapis.com/css2?family=IBM+Plex+Sans:wght@400;500;600;700&family=IBM+Plex+Mono:wght@400;500&family=Crimson+Pro:wght@600;700&display=swap" rel="stylesheet">

AD2-NAS Sync System

Engineer Documentation & Reference Guide

                Version:
                1.0

                Last Updated:
                January 13, 2026

                System:
                Dataforth Test Data Synchronization

                Servers:
                AD2 ↔ D2TESTNAS ↔ DOS Machines

Table of Contents

System Overview

Architecture & Data Flow

Deploying Software Updates to DOS Machines

Test Results Flow (DOS to Database)

TODO.BAT One-Time Tasks

File Locations Reference

Scheduled Tasks

Manual Commands

Troubleshooting

Log Files

System Overview

The AD2-NAS sync system provides bidirectional file synchronization between the AD2 production server and DOS test machines via the NAS (D2TESTNAS). The system handles two primary data flows:

Software Updates (AD2 → DOS): Engineers place updated programs on AD2, which sync to NAS, then download to DOS machines on boot

Test Results (DOS → AD2): DOS machines upload test data to NAS, which syncs to AD2 and imports into the database

            Sync Frequency
            Synchronization runs automatically every 15 minutes via Windows Task Scheduler on AD2.

Architecture & Data Flow

Network Topology

                       AD2 Production Server
                          192.168.0.6
                     (Windows Server, SMB3)
                              |
                              | SSH/SCP (every 15 min)
                              |
                       D2TESTNAS
                          192.168.0.9
                     (Linux NAS, SMB1 Proxy)
                              |
                +-------------+-------------+
                |             |             |
            [TS-1]       [TS-8R]      [TS-27]
          DOS 6.22      DOS 6.22      DOS 6.22

          T: = \\D2TESTNAS\test
          X: = \\D2TESTNAS\datasheets

Data Flow Diagram

SOFTWARE UPDATES (AD2 → DOS)

Engineer → \\AD2\test\TS-XX\ProdSW\ → [Sync Script] → NAS → DOS Boot (NWTOC.BAT)
         → \\AD2\test\_COMMON\ProdSW\ → [Sync Script] → NAS → All DOS Machines

TEST RESULTS (DOS → AD2 → Database)

DOS Test → T:\TS-XX\LOGS\ → [Sync Script] → AD2 → Database Import
         → T:\TS-XX\Reports\ → [Sync Script] → AD2

Deploying Software Updates to DOS Machines

Workflow: Deploy Update to a Specific Station

1

                    Place files on AD2

                    Copy your updated files to the station's ProdSW folder:

                    \\AD2\test\TS-XX\ProdSW\

                    Example: \\AD2\test\TS-8R\ProdSW\7BMAIN4.EXE

2

                    Wait for sync (or trigger manually)

                    Files sync to NAS automatically every 15 minutes.

                    Manual trigger: schtasks /run /tn "Sync-FromNAS"

3

                    Reboot the DOS machine

                    On boot, the DOS machine runs NWTOC.BAT which copies files from:

                    T:\TS-XX\ProdSW\*.EXE → C:\ATE\

                    T:\TS-XX\ProdSW\*.BAT → C:\BAT\

Workflow: Deploy Update to ALL Stations

1

                    Place files in COMMON folder on AD2

                    \\AD2\test\_COMMON\ProdSW\

                    Note: Use _COMMON (with underscore) on AD2

2

                    Wait for sync

                    Files sync to NAS /data/test/COMMON/ProdSW/ (without underscore)

3

                    All DOS machines pick up on reboot

                    NWTOC.BAT checks T:\COMMON\ProdSW\ first, then station-specific folder

Supported File Types for ProdSW

                    File Type
                    Destination on DOS
                    Notes

                    *.EXE
                    C:\ATE\
                    Test programs

                    *.BAT
                    C:\BAT\
                    Batch scripts

                    5BDATA\*.DAT
                    C:\ATE\5BDATA\
                    5B test data files

                    7BDATA\*.DAT
                    C:\ATE\7BDATA\
                    7B test data files

                    8BDATA\*.DAT
                    C:\ATE\8BDATA\
                    8B test data files

                    DSCDATA\*.DAT
                    C:\ATE\DSCDATA\
                    DSC test data files

Test Results Flow (DOS to Database)

Automatic Flow (No Engineer Action Required)

1

                    DOS test completes

                    Test program writes results to local C:\LOGS\

2

                    CTONW.BAT uploads to NAS

                    C:\LOGS\*.* → T:\TS-XX\LOGS\

                    C:\REPORTS\*.* → T:\TS-XX\Reports\

3

                    Sync script pulls to AD2

                    NAS /data/test/TS-XX/LOGS/*.DAT → AD2 C:\Shares\test\TS-XX\LOGS\

4

                    Database import

                    Synced DAT files are automatically imported into the TestDataDB database

Database Access

Search test results via the web interface:

http://192.168.0.6:3000

TODO.BAT One-Time Tasks

The TODO.BAT mechanism allows you to execute one-time commands on a specific DOS machine without modifying its permanent configuration.

Workflow: Run One-Time Command on DOS Machine

1

                    Create TODO.BAT file

                    Create a batch file with your commands. Must use DOS line endings (CR+LF).

2

                    Place in station folder on AD2

                    \\AD2\test\TS-XX\TODO.BAT

3

                    Wait for sync

                    Sync script pushes TODO.BAT to NAS, then deletes it from AD2

4

                    DOS machine executes on boot

                    NWTOC.BAT detects TODO.BAT, executes it, then deletes it from NAS

            Important
            TODO.BAT executes ONCE and is automatically deleted. Make sure your commands are correct before deploying.

Example TODO.BAT Files

Clean temp files:

@ECHO OFF
REM TODO.BAT - Clean temp files on %1
ECHO Cleaning temp files...
DEL C:\TEMP\*.* /Q
DEL C:\*.TMP /Q
ECHO Done

Update specific program:

@ECHO OFF
REM TODO.BAT - Force update 7BMAIN4.EXE on %1
ECHO Updating test program...
COPY T:\%1\ProdSW\7BMAIN4.EXE C:\ATE\ /Y
ECHO Done

File Locations Reference

AD2 Server (\\AD2 or 192.168.0.6)

                    Path
                    Purpose

                    C:\Shares\test\
                    Root of test share

                    C:\Shares\test\TS-XX\ProdSW\
                    Station-specific software updates

                    C:\Shares\test\_COMMON\ProdSW\
                    Common software updates (all stations)

                    C:\Shares\test\TS-XX\LOGS\
                    Test result logs (synced from NAS)

                    C:\Shares\test\TS-XX\Reports\
                    Test reports (synced from NAS)

                    C:\Shares\test\TS-XX\TODO.BAT
                    One-time task file (place here)

                    C:\Shares\test\scripts\
                    Sync scripts

                    C:\Shares\test\_SYNC_STATUS.txt
                    Current sync status

NAS (\\D2TESTNAS or 192.168.0.9)

                    Path
                    Purpose

                    /data/test/
                    Root of test share

                    /data/test/COMMON/ProdSW/
                    Common software (note: no underscore)

                    /data/test/TS-XX/ProdSW/
                    Station-specific software

                    /data/test/TS-XX/LOGS/
                    Test logs (uploaded by DOS)

                    /data/test/TS-XX/TODO.BAT
                    One-time task (consumed by DOS)

DOS Machines (via T: drive)

                    Path
                    Purpose

                    T:\
                    Network share (\\D2TESTNAS\test)

                    T:\COMMON\ProdSW\
                    Common software updates

                    T:\TS-XX\ProdSW\
                    Station-specific updates

                    C:\ATE\
                    Local test programs

                    C:\BAT\
                    Local batch files

                    C:\LOGS\
                    Local test logs (before upload)

Scheduled Tasks

                    Task Name
                    Schedule
                    Script
                    Purpose

                    Sync-FromNAS
                    Every 15 minutes
                    C:\Shares\test\scripts\Sync-FromNAS.ps1
                    Bidirectional AD2 ↔ NAS sync

                    TestDataDB Server
                    On system startup
                    C:\Shares\testdatadb\start-server.bat
                    Start database web server

Manual Commands

Run Sync Manually

# Trigger scheduled task
schtasks /run /tn "Sync-FromNAS"

# Run script directly (dry run - shows what would happen)
powershell -ExecutionPolicy Bypass -File C:\Shares\test\scripts\Sync-FromNAS.ps1 -DryRun -Verbose

# Run script directly (actual sync)
powershell -ExecutionPolicy Bypass -File C:\Shares\test\scripts\Sync-FromNAS.ps1 -Verbose

# Sync older files (e.g., 7 days = 10080 minutes)
powershell -ExecutionPolicy Bypass -File C:\Shares\test\scripts\Sync-FromNAS.ps1 -MaxAgeMinutes 10080

Check Sync Status

# View current status
type C:\Shares\test\_SYNC_STATUS.txt

# View recent sync log
type C:\Shares\test\scripts\sync-from-nas.log

SSH to NAS (for troubleshooting)

# Using batch helper
C:\dataforth-ad2-context\nas-ssh.bat "ls /data/test/TS-8R/LOGS/"

# Check files on NAS
C:\dataforth-ad2-context\nas-ssh.bat "find /data/test -name '*.DAT' -mmin -60"

Troubleshooting

Problem: Files placed on AD2 are not reaching DOS machines

Symptoms: Engineer places files in \\AD2\test\TS-XX\ProdSW\ but DOS machine doesn't get the update

                Solution

Check sync status: type C:\Shares\test\_SYNC_STATUS.txt

Check if sync task is running: schtasks /query /tn "Sync-FromNAS"

Manually trigger sync: schtasks /run /tn "Sync-FromNAS"

Check sync log for errors: type C:\Shares\test\scripts\sync-from-nas.log

Verify files exist on NAS: SSH to NAS and check /data/test/TS-XX/ProdSW/

Reboot the DOS machine to trigger NWTOC.BAT

Problem: Test results not appearing in database

Symptoms: Test completed but data not searchable in web interface

                Solution

Check if DOS uploaded to NAS: SSH to NAS, check /data/test/TS-XX/LOGS/

Check sync status for "Files Pulled" count

Check sync log for database import errors

Verify database server is running: http://192.168.0.6:3000

Check if CTONW.BAT ran on DOS (uploads results to NAS)

Problem: TODO.BAT not executing on DOS machine

Symptoms: Placed TODO.BAT but it never runs

                Solution

Verify file was placed correctly: \\AD2\test\TS-XX\TODO.BAT (in station root, not ProdSW)

Check that sync ran (TODO.BAT should be deleted from AD2 after sync)

Verify TODO.BAT reached NAS: SSH and check /data/test/TS-XX/TODO.BAT

Ensure DOS machine was rebooted (TODO.BAT runs during boot)

Check DOS line endings (must be CR+LF, not Unix LF only)

Problem: Sync task failing with errors

Symptoms: Status shows "ERRORS" or sync log shows failures

                Solution

Check sync log: type C:\Shares\test\scripts\sync-from-nas.log

Verify NAS is reachable: ping 192.168.0.9

Test SSH connection: C:\dataforth-ad2-context\nas-ssh.bat "echo test"

Check NAS disk space: SSH and run df -h /data

Verify PuTTY is installed: dir "C:\Program Files\PuTTY\"

Problem: DOS machine can't connect to NAS (T: drive unavailable)

Symptoms: DOS machine shows "Network path not found" or T: drive missing

                Solution

Check NAS is running: ping 192.168.0.9 from another machine

Verify WINS server is running on NAS (required for NetBIOS name resolution)

Check DOS machine network cable and settings

Try reconnecting: On DOS, run net use T: \\D2TESTNAS\test

Log Files

                    Log File
                    Location
                    Purpose

                    Sync Log
                    C:\Shares\test\scripts\sync-from-nas.log
                    All sync operations, errors, file transfers

                    Sync Status
                    C:\Shares\test\_SYNC_STATUS.txt
                    Current status summary (OK/ERRORS)

                    DOS NWTOC Log
                    C:\ATE\NWTOC.LOG (on DOS machine)
                    What files were downloaded on boot

                    NAS Station Logs
                    /data/test/TS-XX/NWTOC.LOG
                    Copy of DOS NWTOC log uploaded to NAS

Reading the Sync Log

# View last 50 lines
powershell -Command "Get-Content 'C:\Shares\test\scripts\sync-from-nas.log' -Tail 50"

# Search for errors
powershell -Command "Select-String 'ERROR' 'C:\Shares\test\scripts\sync-from-nas.log'"

# View today's entries
powershell -Command "Get-Content 'C:\Shares\test\scripts\sync-from-nas.log' | Select-String '2026-01-13'"

            Script Location
            C:\Shares\test\scripts\Sync-FromNAS.ps1

            To edit the sync behavior, modify this PowerShell script. Key configuration is at the top of the file.

            Generated: January 13, 2026 | Dataforth Test Data Sync System