WINDOWS SOURCE CODE FOR BOTH NT4 AND WIN2K BUILDS WERE LEAKED.
Considering the massive knowledge base and amount of applications and hardware devices created to exploit the xbox system this source code can most definitley be used to create a full version of windows for the xbox that can be installed in a native, proper, and full fashion that is truly complete.
Has anyone considered these methods, resources, concepts

(1) Build a full Xbox Native Windows from the ground up: Using leaked Windows 2000 Source Code with the missing "non-leaked" components substituted with the relative parts from
(A) leaked Windows NT4 {this has boot code and kernel initialization code in \nt\private\ntos\private\boot\ and \nt\private\ntos\init\ which would allow for the construction of an XBOX specific NTLDR/OSLOADER.EXE and/or NTOSKRNL.EXE
( REACTOS source code: the REACTOS avenue appears great as it already has a Hardware Abstraction Layer with custom code for the XBOX.
(2) Windows CE.NET source code, samples, and binary image building - Dependent on the CE .NET framework to a large extent it nevertheless provides an execellent resource especially when it comes to the construction of pre-kernel (and as such pre WinCE) executions such as those that occur in the hardware enumerating OEM ADAPTION LAYER during boot: a DEFAULT.XBE boot loader has already been constructed for the XBOX and a WinCE NK.NB0 image has been released. Modification to WinCE source code, specifically to the XBOX WinCE image mentioned above (that already works) could lead us somewhere.
By injecting leaked NT/WIN2K code, BIOS/x86 Emulation code such as Bochs, and possibly code from the EFI firmware interface released from INTEL, one could create a glorified superBIOS: This would be a WinCE OS perhaps residing on a LPC module like normal modchips and would allow execution of a normal PC windows setup program (unmodified). This is quite a complex idea but essentially works by creating an intermediate layer between the XBOX and Windows and thus makes Windows think it is installing itself on a PC instead of an XBOX.
(3) Create a BIOS PE FILE to replace XBOXKRNL.EXE then package it up under CABinet protocol and insert it back into the BIOS BOOT ROM so that it is unpacked upon POST.
Obviously we would rebuild NTOSKRNL.EXE using leaked code, rename it as XBOXKRNL.EXE, reseal it with appropriate cryptography and compression and then flash it into the region where the XBOX exepcts such to be.
This would then expect a HAL and Device Drivers as well as a Session Manager Sub-System and further programs at least up to the Winlogon.exe point where a system boot officially comes to an end.