# Historical HTML Claim Review — Batch 09

## Scope

Reviewed the final three unique historical HTML contents:

- `HTML-039` — BR-H816 EL02-04 updater page;
- `HTML-040` — BR-H816 EL02-05 updater page;
- `HTML-041` — DVSM-D5812 FWA117 updater page.

## Result

Batch-09 claims: **40**  
Cumulative historical claims: **504**  
Historical HTML review batches complete: **9 of 9**  
Unique HTML contents reviewed: **41 of 41**

| Status | Count |
|---|---:|
| negative_knowledge | 5 |
| open_question | 1 |
| partially_corroborated | 4 |
| rejected | 5 |
| superseded | 1 |
| validated | 24 |

## BR-H816 Revision-Page Lineage

The EL02-04 and EL02-05 pages are exactly identical after replacing the single
updater executable filename with a common placeholder.

| Page | Executable |
|---|---|
| EL02-04 | `OEL02_BH08NS20_EL02-04.exe` |
| EL02-05 | `buffalo_el02-05_bh08ns20_090330.exe` |

This validates the page lineage and shared operational instructions. It does
**not** establish payload equality, supported-drive tables, or internal update
protocol. The `090330` token is preserved without promoting it to a confirmed
date.

## DVSM-D5812 FWA117

The page names `4120A117.exe`, Windows 2000/XP, Administrator access, removal of
packet-writing software, Intel Application Accelerator, and Intel Ultra ATA
Storage Driver, target-drive selection, an approximate three-minute operation,
and restart after completion.

The executable name and workspace provenance support a 4120/A117 and
GSA-4120B association, but do not prove that every DVSM-D5812 unit uses one
mechanism or revision.

## Authority Boundary

These pages are primary vendor authority for:

- branded package scope;
- exact updater executable names;
- historical end-user prerequisites;
- update preparation and completion steps;
- warnings against interrupting power or hardware connections.

They do not provide primary evidence for:

- ATA/ATAPI command sequences;
- loader-stub behavior;
- firmware payload bytes or hashes;
- flash algorithms, memory maps, checksums, or encryption;
- present-day compatibility or safety.

The HTML-only collection also omitted the named updater executables and
referenced screenshots. UI screenshot content and binary behavior therefore
remain outside the evidence available to Batch 09.

## Claim Index

| Claim | Source | Status | Conclusion |
|---|---|---|---|
| HCLM-B09-001 | HTML-039 | validated | The EL02-04 page is a BR-H816-series vendor update instruction page that names OEL02_BH08NS20_EL02-04.exe as the updater executable. |
| HCLM-B09-002 | HTML-039 | validated | The EL02-04 instructions require the downloaded updater package to be expanded on the computer hard disk before operation. |
| HCLM-B09-003 | HTML-039 | validated | The EL02-04 instructions require operation from an Administrator or computer-administrator account. |
| HCLM-B09-004 | HTML-039 | validated | The EL02-04 instructions require packet-writing software such as InstantBurn, Drag-to-Disc, DLA, or B'sCLiP to be uninstalled or removed from resident operation before updating. |
| HCLM-B09-005 | HTML-039 | validated | The EL02-04 procedure requires removing media, closing applications, and saving work before launching the updater. |
| HCLM-B09-006 | HTML-039 | validated | The EL02-04 updater presents Update and Exit choices, and selecting Update begins the firmware update. |
| HCLM-B09-007 | HTML-039 | validated | The EL02-04 instructions warn not to power off or disturb the drive, interface cable, or keyboard during update because failure or an unusable drive may result. |
| HCLM-B09-008 | HTML-039 | validated | After a successful EL02-04 update, the page requires computer restart or a computer/drive power cycle before normal use. |
| HCLM-B09-009 | HTML-039 | validated | For a BR-H816SU2 used with its AUTO power switch in MANUAL mode, the EL02-04 page requires shutting down the computer and switching the unit off once after update. |
| HCLM-B09-010 | HTML-039 | partially_corroborated | The EL02-04 executable filename partially corroborates an association with BH08NS20 and firmware label EL02-04. |
| HCLM-B09-011 | HTML-039 | rejected | The EL02-04 page proves that every BR-H816-series product contains exactly an LG BH08NS20 mechanism. |
| HCLM-B09-012 | HTML-039 | negative_knowledge | The EL02-04 end-user page does not establish the updater command protocol, firmware payload format, architecture, flash map, checksum, or transformation algorithm. |
| HCLM-B09-013 | HTML-040 | validated | The EL02-05 page is a BR-H816-series vendor update instruction page that names buffalo_el02-05_bh08ns20_090330.exe as the updater executable. |
| HCLM-B09-014 | HTML-040 | validated | After substituting a common executable placeholder, the EL02-04 and EL02-05 HTML pages are exactly identical. |
| HCLM-B09-015 | HTML-040 | validated | EL02-04 and EL02-05 are distinct named vendor updater revisions, with EL02-05 following EL02-04 in the explicit revision-label sequence. |
| HCLM-B09-016 | HTML-040 | validated | The same Administrator, packet-writing-software, media-removal, application-closure, update-safety, restart, and BR-H816SU2 MANUAL-mode instructions apply to the EL02-05 page. |
| HCLM-B09-017 | HTML-040 | partially_corroborated | The EL02-05 filename partially corroborates BH08NS20 and EL02-05 package identity and preserves an additional token 090330. |
| HCLM-B09-018 | HTML-040 | open_question | The 090330 token in buffalo_el02-05_bh08ns20_090330.exe is conclusively a build or release date of 2009-03-30. |
| HCLM-B09-019 | HTML-040 | rejected | The two distinct BR-H816 updater filenames prove that their embedded firmware payloads differ only by the EL02-04 versus EL02-05 revision. |
| HCLM-B09-020 | HTML-040 | partially_corroborated | The three logical recovery paths for each BR-H816 page corroborate recovery of the same HTML content, but they are not three independent vendor publications and do not validate the updater executable. |
| HCLM-B09-021 | HTML-040 | negative_knowledge | The BR-H816 pages reference a stylesheet and three screenshots whose contents are not preserved in the HTML-only corpus. |
| HCLM-B09-022 | HTML-040 | rejected | The BR-H816 vendor pages prove the internal ATA/ATAPI flashing protocol used by the updater. |
| HCLM-B09-023 | HTML-041 | validated | The FWA117 page is a DVSM-D5812-series vendor update instruction page that names 4120A117.exe as the updater executable. |
| HCLM-B09-024 | HTML-041 | validated | For Windows 2000 or Windows XP, the FWA117 instructions require an Administrator or computer-administrator account. |
| HCLM-B09-025 | HTML-041 | validated | The FWA117 instructions require packet-writing software such as B'sCLiP to be uninstalled or removed from resident operation before update. |
| HCLM-B09-026 | HTML-041 | validated | The FWA117 instructions require Intel Application Accelerator to be uninstalled before update. |
| HCLM-B09-027 | HTML-041 | validated | The FWA117 instructions require Intel Ultra ATA Storage Driver to be uninstalled before update. |
| HCLM-B09-028 | HTML-041 | validated | The FWA117 procedure requires removing media and closing all running applications before launching the updater. |
| HCLM-B09-029 | HTML-041 | validated | The FWA117 procedure requires selecting the target drive and clicking Update, and the page estimates about three minutes for the operation. |
| HCLM-B09-030 | HTML-041 | validated | The FWA117 page warns not to power off or disturb the drive, interface cable, or keyboard during update because failure or an unusable drive may result. |
| HCLM-B09-031 | HTML-041 | validated | After a successful FWA117 update, the page requires clicking Restart before the DVSM-D5812 series is used. |
| HCLM-B09-032 | HTML-041 | partially_corroborated | The 4120A117 executable name and preserved workspace path partially corroborate an association with a 4120-family A117 firmware package and GSA-4120B research provenance. |
| HCLM-B09-033 | HTML-041 | rejected | The FWA117 page proves that every DVSM-D5812-series unit is exactly an LG GSA-4120B running A117. |
| HCLM-B09-034 | HTML-041 | superseded | The Windows 2000/XP, IAA, and Intel Ultra ATA Storage Driver requirements are historical package instructions and must not be treated as universal current-system prerequisites. |
| HCLM-B09-035 | HTML-041 | negative_knowledge | The two linked Intel support pages are contextual dependencies whose exact referenced content is not preserved in the PFES HTML corpus. |
| HCLM-B09-036 | HTML-041 | negative_knowledge | The FWA117 page does not establish the updater command protocol, loader behavior, firmware payload, flash algorithm, checksum, encryption, or CPU architecture. |
| HCLM-B09-037 | HTML-039 | validated | The three vendor pages are primary vendor authority for their package-specific end-user instructions and safety warnings, but only contextual evidence for internal firmware engineering. |
| HCLM-B09-038 | HTML-040 | validated | Updater filenames and revision labels are valuable provenance fields but are not substitutes for executable hashes, extracted payloads, target tables, or hardware validation. |
| HCLM-B09-039 | HTML-041 | negative_knowledge | Because the corpus collected HTML only, updater executable behavior and screenshot details cannot be independently verified from Batch 09. |
| HCLM-B09-040 | HTML-041 | rejected | The historical vendor pages prove that their updater packages are safe to run today on arbitrary hardware that merely resembles the named product family. |
