From 1b43b56b5b8cefed297d45c6616477d89e8611af Mon Sep 17 00:00:00 2001 From: PatrickvL Date: Wed, 2 Aug 2017 11:46:10 +0200 Subject: [PATCH] Updated Cxbx Reloaded overview (markdown) --- Cxbx-Reloaded-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Cxbx-Reloaded-overview.md b/Cxbx-Reloaded-overview.md index 7e33ca5..c948430 100644 --- a/Cxbx-Reloaded-overview.md +++ b/Cxbx-Reloaded-overview.md @@ -25,7 +25,7 @@ The advantage of this approach is, that Cxbx doesn't need to emulate the CPU at ## Xbox Kernel (BIOS) Cxbx-Reloaded contains it's own implementation of the Xbox kernel, which means there's no need to acquire a dump from your Xbox. -In it's currenty form, the Cxbx-Reloaded kernel forwards many of the 367 kernel API's towards the host Windows kernel API's. __This restricts running Cxbx-Reloaded to operating systems that contain the Win32 API's, so-far Windows only!__ +In it's currenty form, the Cxbx-Reloaded kernel forwards many of the 378 kernel API's towards the host Windows kernel API's. __This restricts running Cxbx-Reloaded to operating systems that contain the Win32 API's, so-far Windows only!__ Because many of the kernel API's are just forwards, some aspects of the Xbox kernel are not emulated well enough. Timings will differ, thread switching works differently, thread local storage must be patched, etc. etc. In the future, more API's will be replaced with an implementation that doesn't rely on Windows anymore, but will be build on top of an abstraction-layer, removing much of the dependancy on Windows.