Files
claudetools/clients/valleywide/app-modernization/source-code
Mike Swanson 0f0f664e8e feat(valleywide): add drive 2 findings - 000_ASource + analyzer outputs
Drive 2 (label "Backup", 12 TB, 6.77 TB used) — second of N VWP
backup drives. Scanned via WizTree, analyzed with analyze_wiztree.py.

NEW source content:
- 000_ASource/ — Darv's active work-in-progress folder. Contains
  TEST_VWP.vbp (2021-08-16, only .vbp newer than the 2020-06-09 baseline),
  four frmLotInfo*.frm variants (2020-10 to 2021-08), and an
  MSSCCPRJ.SCC file confirming Darv used Visual SourceSafe.
- The accompanying Vwp.mdb (2022-10-19, 764 MB) stays on local disk
  per .gitignore — newest database snapshot we have.

Analysis CSVs:
- source-analysis/drive2-2026-05-16/ — per-category + per-keyword
  breakdown of drive 2's 3.95M files (vs drive 1's 1.87M). Categories
  largely match drive 1 but with ~2x volume.

Net findings vs drive 1:
- Confirmed 4-year gap: only 4 .vbp files newer than 2020-06-09 on
  drive 2, all the same TEST_VWP.vbp scaffold. Main ORDERS_C.vbp source
  remains 2020-06-09. Darv stopped active VB6 dev around mid-2020.
- 43 GB Win7 Backup-and-Restore set in D:\Archive\Darv-Win7-PC\ (2023)
  not copied — deferred to later drives, ZIPs extractable on demand.
- Master Darv folder is bit-for-bit duplicate of drive 1's master (135 GB,
  same file/folder counts). Skipped.

New helper scripts:
- find_newer_vbp.py — list .vbp files newer than a date, filter SDK noise
- drive2_inspect.py / drive2_priorities.py — drive-specific triage

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-16 17:42:19 -07:00
..

VWP Orders — Source Code Recovery from D: Backup Drive

Recovered: 2026-05-16 Source drive: D:\ (label Backup, 8 TB, 5.3 TB used) — one of several VWP backup drives in Mike's possession Provenance CSV: ../WizTree_20260516172207.csv (393 MB raw export, gitignored) Analysis CSVs: ../source-analysis/D-drive-2026-05-16/ (per-category, per-keyword)

What's in here

Full-Project/ — Darv's "Full" project tree

  • Source: D:\Office-Estimates\Darv\Full\Project\
  • Filtered to extensions: .vbp .vbg .vbw .frm .frx .bas .cls .ctl .ctx .res .rpt .ini .cfg .sql .qry .txt .md .doc .docx .pdf
  • Master copy (most files, older snapshot)
  • Latest ORDERS_C.vbp date: 2019-11-05

Kingston-Project/ — Darv's Kingston USB project tree

  • Source: D:\Office-Estimates\Darv\Kingston\Project\
  • Filtered (same extension list)
  • Newer ORDERS_C.vbp (2020-06-09) but fewer files — likely his current working snapshot from the USB stick
  • The "Kingston" naming refers to the Kingston-branded USB drive Darv used

Source/Darv\Source\ wholesale

  • Source: D:\Office-Estimates\Darv\Source\ (555 MB, 169 files)
  • Contains a History\Package\ and History\Package2\ (InstallShield packages?)
  • Has older files dating back to 1997 (C4dll1210.dll), 2002-2012 various
  • Likely a personal scratch / archive area, not the live source

SOURCE-HOLD/Darv\SOURCE HOLD\ wholesale

  • Source: D:\Office-Estimates\Darv\SOURCE HOLD\ (2 files only, < 1 MB)
  • Named "HOLD" suggests intentional snapshot

000_ASource/ — Darv's "active source" folder (from drive 2)

  • Source: D:\Office-Estimates\Darv\000_ASource\ (drive 2, label Backup, 12 TB)
  • 12 files, ~768 MB (mostly the Vwp.mdb which is gitignored — only ~4 MB of source/config goes to git)
  • TEST_VWP.vbp dated 2021-08-16 — the only .vbp on either drive newer than the 2020-06-09 ORDERS_C.vbp baseline. Likely an experimental scaffold (only 810 bytes).
  • frmLotInfo*.frm variants dated 2020-10 to 2021-08 — Darv was iterating on a form. The JJ and Z and 5JJ and 5Z suffixes are his variant-marker convention.
  • Vwp.mdb dated 2022-10-19 (764 MB) — newest database snapshot anywhere, two years more recent than what the prior session had. Gitignored; on local disk only. Useful for schema-evolution analysis.
  • MSSCCPRJ.SCC file — Microsoft Source Code Control project file. Confirms Darv was using Visual SourceSafe. There may be a SourceSafe repository (srcsafe.ini) on a later drive that contains full version history. Worth grepping for *.scc / srcsafe.ini on subsequent scans.

VMs/ — VirtualBox disk images (gitignored)

  • VWIN7-DW.vdi (8.3 GB) — Darv's actual Windows 7 Dev workstation
    • Source: D:\Office-Estimates\Darv\VirtualBox\VWIN7 DW.vdi
    • Boot this to get his full dev environment with VB6 IDE, paths, dependencies intact
  • XP-for-ORDERS_copy.vdi (2.8 GB) — XP runtime for compiled Orders
    • Source: D:\Office-Estimates\Darv\VM_VDI\XP for ORDERS_copy.vdi
    • Useful for runtime testing of the compiled Orders_10A.exe

Three VB6 project variants identified

Project Purpose Latest .vbp Location pattern
ORDERS_C.vbp Main Orders application 2020-06-09 (Kingston) Project\VWP_Current\
ORDERS_Cx.vbp Variant (possibly experimental) 2018-12-11 Project\VWP_Current\
ORDERS_I.vbp Invoicing module 2019-03-21 Project\VWP_Inv\

Also VWP_Current_0317/ and VWP_Update/ folders exist — likely interim dev branches.

What was intentionally NOT copied

Class Why skipped
Recovery\Darv\ (78 GB) Older copy of master Darv folder — same source, older snapshots
Estimating Archive 2024-04-23 01;46;22\Darv\ (135 GB) Bit-for-bit duplicate of master Darv per WizTree size/file count
635 .mdb Access DB backups (195 GB total) Live VWP.mdb already in source-analysis/; historical schema snapshots can be revisited on demand
14 OVA exports of VMs (58 GB) Largely duplicates of the two VDIs we grabbed; OVAs are portable but less efficient for running
Darv\Full\Program Files\ (large) Darv's installed dev tools — the VWIN7-DW.vdi already contains his complete installed environment
Darv\HD2 Info\Darv\ (6.25 GB) Secondary HD info, lower priority
97-Server-G-Drive\Users\Darv\ (7 GB) Older server snapshot, superseded by Office-Estimates\Darv\
VWP-ADSVR\Users\Darv\ (24 GB) AD server profile — the live copy (with the lone frmPayroll.frm) was already analyzed in 2026-04-27 session

Open question — the 4-year gap

Latest .vbp modification on D:\ is 2020-06-09. The production Orders_10A.exe was live in April 2024. Either:

  1. Darv stopped maintaining source after 2020 and made later changes some other way (unlikely)
  2. Newer source exists on other backup drives — re-run this scan on the next drives Mike connects, filter for .vbp mtime > 2020-06-09
  3. The 2020 source IS substantially the production code — minor or no functional changes since

Once additional WizTree CSVs are dropped in source-analysis/, re-run analyze_wiztree.py <csv> <out> to cross-reference.

Tools

  • ../source-analysis/analyze_wiztree.py — re-runnable WizTree CSV analyzer
  • ../source-analysis/size_candidates.py — folder-size triage script