XBOX

From ReactOS

Is XBOX support necessarily a good idea ? The answer is obviously YES. The XBOX must be realized as the only genuine computer ever to be born out of Microsoft and logic tells us that this machine and ReactOS itself share the same blood as they are both ultimately children of the Windows base.

(Fireball's comment: the text below is just an idea, and in fact I personally don't agree with it. Because no Xbox Subsystem is needed - it's the same CSRSS/Win32 stuff. So that you can use your xbox just as usual pc with windows. We already have freeldr which autodetects the architecture it's running on, and kernel also. Though different HAL is needed.)

ROS global design is very close to NT's, that is every supported o.s. is simulated by a plug-in module (=environment subsystem). For Win32 it is CSRSS.EXE and its DLLs. For POSIX it is PSXSS.EXE. Simply, for XBOX, the set up of an independent dev team to code a XBXSS.EXE is the best philosophy as the ROS dev team welcomes the development of other environment subsystems... I am making this "XBXSS.EXE" right now yet from a different perspective. This executable gives the XBOX the CreateProcess* powers which in turn can load into other subsystems given by ReactOS itself or for those who are up to a challenge maybe even SETUP.EXE to install a full version of Windows and make your XBOX serve up an Active Directory Domain !!!

My idea starts from, as stated above, the only real "Microsoft" computer ever created. My logic is as follows: the XBOX is powered-up and we get to the equivalent POST state and load into the on-board BIOSwhich is flashed with the debug enabled version 1.00 binary known as COMPLEX. From here we load into debug dashboard display which is also provided by team COMPLEX and have the debugger enabled and ready to lock itself to the next given process to be created. The file selected is, as in most cases, DEFAULT.XBE - in this system such is the Windows CE.NET BIOSLOADER recoded into XBE by the CE-XBOX project and such will load an NK.BIN image made by the CE.NET platform builder as it contains the necessary functions such as "Startup" which can also be used in the OAL to initialize the processor. Once we are in NK.BIN the XBOX's LPC DEBUG port is enumerated by code in the OAL. The LPC will have a module mounted that must simultaneously be capable of being used for debugging in compliane with the INTEL/Microsoft standards as well as allowing CE.NET Platform Builder image transfer and provisioning of SCSI and COM1 as well as any other peripheral devices. This simply requires modification of the Xecuter3CE and must give a SCSI port (and linked HDD) as well as a COM1 port which as stated will be automatically used by the debugger by providing a feed to a given terminal concentrator. Once the OAL has completed and the Kernel is loaded we eventually get to CE.NET's COREDLL.DLL which provides the ".NET manged code" version of KERNEL32.DLL and give us the function known as CreateProcess: This is where things get interesting as my system replaces the WinCE API Code with the Windows NT code from ReactOS.