Difference between revisions of "Run Xbox Games on ReactOS"

From ReactOS Wiki
Jump to: navigation, search
(Move XBox 360 games to separate page)
(Renew the article (thanks to JayFoxRox))
Line 1: Line 1:
 +
ReactOS has an original [[Xbox Port|Xbox port]] but it can run only Windows applications and lacks ability to run actual original Xbox games.
 +
 +
A new non-Desktop ReactOS kernel target must be created for running Xbox games. It would be specificly meant to run on Xbox hardware, and would have to support Xbox kernel functionality.
 +
 +
Specifically, the XBE loading must be implemented but probably also various other tasks related to memory management and more.
 +
 +
==Problems==
 +
Xbox OS uses a radically different software architecture from Windows:
 +
* Xbox Executables (XBE) are used instead of Executable (EXE) files.
 +
* XBE run in ring 0 and no ring 3 exists. This may require some changes to ReactOS.
 +
* XBE expect to locate HAL and other kernel API functions in a single statically linked kernel.
 +
* XBE are also statically linked.
 +
* XBE access hardware directly, so support can only be provided for ReactOS running on an original Xbox.
 +
* The kernel uses cryptography and stores keys to encrypt various data (network traffic, saved games, etc.), these keys must be dumped, and key derivation must be recreated.
 +
* The kernel only provides some critical hardware support (mostly video Encoder and IDE controller).
 +
 +
These changes mean that a custom desktop-less OS variant of ReactOS, specifically for original Xbox, has to be made.
 +
 +
This variant would be equivalent to the original <code>xboxkrnl.exe</code> by Microsoft. It would be binary-compatible with original Xbox games (but incompatible with non-Xbox hardware and Windows applications).
 +
 +
==Related projects==
 +
 +
===XQEMU===
 +
XQEMU is an original Xbox emulator that emulates the hardware level. XQEMU is targeting computers running Linux, Mac OS X and Windows.
 +
 +
Because it emulates hardware, it requires ROM images (some of which are hard to obtain) to be able to boot.
 +
 +
The code in XQEMU can be used to understand some of the hardware, which will have to be supported by ReactOS.
 +
 +
Additionally, XQEMU could possibly be used to test ReactOS.  However, this might not work correctly, as XQEMU only supports hardware access methods as used by Microsoft's original kernel. Some legacy devices or device access methods might not be supported (PIO vs. DMA, for example).
 +
 +
===Cxbx-Reloaded===
 +
Cxbx-Reloaded is an original Xbox emulator that emulates the kernel level. It also hooks into the game code (by using a pattern-search) to avoid direct hardware access.
 +
 +
As Cxbx-Reloaded is targeting computers running Windows, most of the kernel re-implementation are simple adapters to Windows functions; however, the implemented variants are confirmed to work with some original Xbox games.
 +
 +
Other kernel functionality is implicitly documented in code and might be useful (such as key derivation on XBE load).
 +
 +
Hardware emulation isn’t present, so it can’t be used to emulate a virtual Xbox for testing ReactOS.
 +
 +
===NTOSDrop===
 
[http://www.betaarchive.com/forum/viewtopic.php?f=6&t=11986 NTOSDrop] was/is a custom Windows Research Kernel that included the "Hiroshima/xe XBOX application layer". Unfortunately, that code cannot be looked at by any ReactOS developers due to the Windows Research Kernel being under a different license; additionally, while the coder could give advice to ReactOS, they can never contribute code.
 
[http://www.betaarchive.com/forum/viewtopic.php?f=6&t=11986 NTOSDrop] was/is a custom Windows Research Kernel that included the "Hiroshima/xe XBOX application layer". Unfortunately, that code cannot be looked at by any ReactOS developers due to the Windows Research Kernel being under a different license; additionally, while the coder could give advice to ReactOS, they can never contribute code.
  
==Problems==
+
==Related articles==
* The Xbox discs are recorded from the outside in, not inside-out like standard discs
+
* [[Xbox Port|ReactOS Xbox port]]
** See XDVDFS and [http://forums.ngemu.com/showthread.php?t=145975 XISO] formats
+
* [[Install ReactOS on Xbox]]
** May be possible to make an exact image of an Xbox DVD (by ignoring any standard disc file systems) then use software to read from the last sector forward and remake the ISO "reversed"
+
* [[Run XBox 360 Games on ReactOS]]
  
 
==See Also==
 
==See Also==
*[http://web.archive.org/web/20110928113820/http://www.xbox365.com/stories/xdkcomplete.shtml Xbox documentation]
+
* [https://github.com/XboxDev/XboxDev XboxDev information page (Xbox related projects and Discord server by hobbyists)]
*http://www.caustik.com/cxbx/progress.htm
+
* [https://xboxdevwiki.net/ XboxDevWiki (Platform documentation by hobbyists)]
*[http://www.ngemu.com/forums/forumdisplay.php?f=63 cXBx forum]
+
* [https://github.com/Cxbx-Reloaded/Cxbx-Reloaded/tree/develop/src/core/kernel/exports Emulation of original Xbox kernel functions in Cxbx-Reloaded]
*[http://forums.ngemu.com/showpost.php?p=552035&postcount=21 Resources]
+
* [https://github.com/xqemu/xqemu/tree/master/hw/xbox Emulation of original Xbox hardware in XQEMU]
*[http://forums.ngemu.com/showthread.php?t=130457 Some details on loading XBE executables]
 
* [[Run XBox 360 Games on ReactOS]]
 
  
  
 
[[Category:Ideas]]
 
[[Category:Ideas]]

Revision as of 17:47, 4 March 2019

ReactOS has an original Xbox port but it can run only Windows applications and lacks ability to run actual original Xbox games.

A new non-Desktop ReactOS kernel target must be created for running Xbox games. It would be specificly meant to run on Xbox hardware, and would have to support Xbox kernel functionality.

Specifically, the XBE loading must be implemented but probably also various other tasks related to memory management and more.

Problems

Xbox OS uses a radically different software architecture from Windows:

  • Xbox Executables (XBE) are used instead of Executable (EXE) files.
  • XBE run in ring 0 and no ring 3 exists. This may require some changes to ReactOS.
  • XBE expect to locate HAL and other kernel API functions in a single statically linked kernel.
  • XBE are also statically linked.
  • XBE access hardware directly, so support can only be provided for ReactOS running on an original Xbox.
  • The kernel uses cryptography and stores keys to encrypt various data (network traffic, saved games, etc.), these keys must be dumped, and key derivation must be recreated.
  • The kernel only provides some critical hardware support (mostly video Encoder and IDE controller).

These changes mean that a custom desktop-less OS variant of ReactOS, specifically for original Xbox, has to be made.

This variant would be equivalent to the original xboxkrnl.exe by Microsoft. It would be binary-compatible with original Xbox games (but incompatible with non-Xbox hardware and Windows applications).

Related projects

XQEMU

XQEMU is an original Xbox emulator that emulates the hardware level. XQEMU is targeting computers running Linux, Mac OS X and Windows.

Because it emulates hardware, it requires ROM images (some of which are hard to obtain) to be able to boot.

The code in XQEMU can be used to understand some of the hardware, which will have to be supported by ReactOS.

Additionally, XQEMU could possibly be used to test ReactOS. However, this might not work correctly, as XQEMU only supports hardware access methods as used by Microsoft's original kernel. Some legacy devices or device access methods might not be supported (PIO vs. DMA, for example).

Cxbx-Reloaded

Cxbx-Reloaded is an original Xbox emulator that emulates the kernel level. It also hooks into the game code (by using a pattern-search) to avoid direct hardware access.

As Cxbx-Reloaded is targeting computers running Windows, most of the kernel re-implementation are simple adapters to Windows functions; however, the implemented variants are confirmed to work with some original Xbox games.

Other kernel functionality is implicitly documented in code and might be useful (such as key derivation on XBE load).

Hardware emulation isn’t present, so it can’t be used to emulate a virtual Xbox for testing ReactOS.

NTOSDrop

NTOSDrop was/is a custom Windows Research Kernel that included the "Hiroshima/xe XBOX application layer". Unfortunately, that code cannot be looked at by any ReactOS developers due to the Windows Research Kernel being under a different license; additionally, while the coder could give advice to ReactOS, they can never contribute code.

Related articles

See Also