Record that the console format never creates the compatibility partition Two hardware results, and the second one qualifies a claim this wiki makes. A drive with a Windows 7 install on it was mounted by the bypass, shown as unformatted, and formatted from System Settings. That confirms the "no PC needed to prepare a drive" claim, which until now rested on nobody having tested it. But the console formats the content partition and stops there. The backward compatibility partition is left without a volume, so Aurora shows Hdd1 and no HddX and original Xbox games have nowhere to live. Microsoft never expected a drive to need one created - the drives it sold came with the emulator from the factory. That is a real limit on the argument for dropping the on-console formatter, so it is stated as one on the Two Builds page rather than buried. FATXplorer's Partition Tools or mkfs.fatx cover the gap. 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