# Hardware Reference 001 — GDR-8050L / Red Faction II

## Source

`Evidence/GDR8050L_Red_Faction_II_reference_run.txt`

## Observed hardware

- drive: `HL-DT-ST DVD-ROM GDR8050L`
- drive letter: `E:`
- volume label: `SEP13011042072`
- title: Red Faction II
- title ID: `0x54510005`
- media ID: `TQ00501A`

## Observed workflow

The run demonstrated:

1. optical-drive enumeration;
2. TEST UNIT READY;
3. locked READ CAPACITY of 6992 sectors;
4. MODE SENSE page `0x3E`;
5. READ DVD STRUCTURE format `0xC0` / 1636-byte response;
6. both challenge/response exchanges;
7. partition-one unlock command;
8. sticky descrambling mode `0x31`;
9. unlocked READ CAPACITY of 3,431,264 sectors;
10. software eject and tray close;
11. START UNIT after the media transition;
12. a second complete authentication sequence;
13. volume refresh;
14. XDFS signature discovery and directory enumeration;
15. certificate-derived title metadata;
16. Xbox dual-layer geometry normalization;
17. presentation of raw and XISO dump options.

## Important attribution limitation

The build output created `bin/disc_dump.exe`, but the recorded hardware command
invoked `bin/unlockdrive.exe`.

The runtime text also contains a message associated with the older unlocker
binary. Therefore this run is a strong known-good behavioral reference, but it
is **not yet accepted as proof that the newly built merged `disc_dump.exe`
executed on hardware**.

## Required closure test

Run the freshly built merged binary directly:

```powershell
.\bin\disc_dump.exe /list
.\bin\disc_dump.exe e
```

Choose option `0` after metadata discovery.

Alternatively, preserve the prior executable, copy `disc_dump.exe` to the
canonical `unlockdrive.exe` name, verify equal hashes, and repeat the run.

## Trust classification

- hardware behavior: **validated**
- normal handshake workflow: **validated as a known-good reference**
- attribution to semantic-merge binary: **pending**
- dumping output: **not tested in this run**


## Closure

The attribution gap identified in this reference has now been closed by
`HARDWARE_VALIDATION_002_MERGED_DISC_DUMP_DIRECT.md`.

The freshly built merged `disc_dump.exe` was invoked directly and reproduced
the expected non-dumping hardware workflow.
