|
  |
Get It Running Efficiently!, Solution to running Windows! |
|
|
| edude03 |
Jan 25 2006, 11:03 PM
|
X-S Enthusiast
Group: Members
Posts: 28
Joined: 20-April 05
From: Brampton, Ontario
Member No.: 215057
Xbox Version: v1.6
360 version: v1 (xenon)

|
Hmmm... some one will probably beat me up for this, but has anyone seen www.linuxbios.org ? the is a section on that site about running other operation systems after linux boots.... something about using a glue layer called ADLO (iirc) maybe we can borrow ::steal:: some of there code :-P
Ok i'll go get my casket ready Michael
|
|
|
|
| |
| nt authority |
Feb 23 2006, 09:26 AM
|
X-S Enthusiast
Group: Members
Posts: 10
Joined: 23-February 06
Member No.: 273370
Xbox Version: unk
360 version: unknown

|
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.
|
|
|
|
| |
| thepureamrit |
Nov 22 2006, 02:08 AM
|
X-S Enthusiast
Group: Members
Posts: 2
Joined: 22-November 06
Member No.: 312953
Xbox Version: v1.2
360 version: unknown

|
Ahhh, Allow me to introduce my self. I am The Pure Amrit. When I first read this topic, I knew this was right for me. I am a Windows Geek. I have been reading this article since the begining. The thought of running Windows PE on an XBOX is not bad. I do not know if someone had suguested Bart PE, but it can work. In Bart PE, you can create plugins for Windows XP (OR 2003) and modify the whole OS. In my (worthless) ammount of experiance, I believe that Windows 2003, and Windows CE will be the bet choice for the XBOX. Shure, it is possiable that you can make drivers for the XBOX. The Dashboard (and the rest of the xbox software) is only a modified version of the Windows 2000 Kernel (and Direct X). If That Helps Out At All, I Would Like To Know. thanks ~The Pure Amrit P.S. If The XBOX is only Windows 2000, There is still hope for Windows XP... (  ,Hint Hint)
|
|
|
|
| |
| torne |
Nov 22 2006, 12:28 PM
|
X-S Expert
  
Group: Members
Posts: 684
Joined: 31-January 06
From: London, UK
Member No.: 270609
Xbox Version: v1.1
360 version: v1 (xenon)

|
QUOTE(thepureamrit @ Nov 22 2006, 01:15 AM)  In Bart PE, you can create plugins for Windows XP (OR 2003) and modify the whole OS.
Those are just convenient ways to include/exclude particular files, they don't patch OS files. QUOTE The Dashboard (and the rest of the xbox software) is only a modified version of the Windows 2000 Kernel (and Direct X). If That Helps Out At All, I Would Like To Know.
Nope. The Xbox kernel is not in any way useful to run Windows - it's not compatible in any way with the NT kernels, even though it's derived from them (the most fundamental issue: NT syscalls take wide Unicode strings, Xbox syscalls take ASCII, so all string-based APIs are immediately incompatible). Running Windows on the Xbox would have to work the same way as Linux - a loader replaces the existing kernel with something else.
|
|
|
|
| |
| jake09071990 |
Mar 17 2007, 06:51 PM
|
X-S Enthusiast
Group: Members
Posts: 1
Joined: 28-February 07
Member No.: 331859

|
Ok well i only read the first post and had an i dea pop into my head.  Well we can make windows not make the check by using nlite to modify the instalation disk. i have done this at least 10 times before and it can take out almost all of the minimum system requirements that are on the install disk. Just thought this would help alot. This is to modify windows XP only. This post has been edited by jake09071990: Mar 17 2007, 06:52 PM
|
|
|
|
| |
|
  |
|