Document Cache0 as the emulator's work area, and the dirty-disc first run Halo failed to load saves from an unsigned internal disk and then started working with nothing written to the drive by hand. The cause was Cache0 carrying no volume: the emulator copies the game into a cache there and keeps the emulated Xbox hard disk in the same place, saved games included, so with no volume there is nowhere to put any of it. The game boots and plays off Partition1 and SystemPartition, then fails the moment it needs the work area - which it reports as a read error on the disc. The console builds the cache partitions on demand, so the run that triggers it is the run that fails. Documented rather than worked around, plus a warning in the plugin, because someone hitting a disc error on their first attempt will reasonably conclude the whole thing is broken. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Document original Xbox compatibility, the capacity unlock and the two builds Compatibility is the headline: SystemPartition turns out to be the backward compatibility partition, so mounting it on an unsigned drive is all that was ever needed to run original Xbox games. Confirmed on hardware. Corrects two things this wiki got wrong. The capacity/avatars trade-off is gone - LB reaches the hidden capacity of a flashed drive without writing to it. And the claim that avatars are simply unreachable now carries the case where they do work: a console with 4 GB of internal flash, with the update installed there. The on-console format page stays as a pointer, since the formatter is debug only now. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Document unauthenticated disk support