well since the 2000 source code was leaked, has anyone tempted to make a fully compatible version for the xbox?

It wasnt the full thing. So, no.

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.

Yes the full source code was leaked for both of them, and actually the source code for MS-Dos 6 was also leaked!
PLowran

dos 6 was my favorite i remember when that came out

SWEET! DOS6 for Xbox!!! Who's with me?

Um, no it wasn't. Only a few gigabytes were leaked. The full source code is much larger (probably about 30gigs).

Actually, that's very interesting. With a few interupt patches and some modification it could be made to work pretty well. I'd like to play a bit of Wolfenstien 3D and Duke Nukem on the Xbox, myself. T'would be fun.

Naw, it's under fifteen. Compressed it fits on a DVD. Takes seriously large amounts of space to compile, though

The source leaked was certainly incomplete, though I don't know specifically what was missing (never looked at the leaked version) - but it's certain that it is, cuz the source of the leak never had the entire code to start with. MS don't give out certain parts of the code to normal Shared Source licencees. Even the copy I worked with that MS gave us on the academic shared source licence was missing a few key parts from higher level components.

that would be sweet...

for 1 do you post this in every topic about windows on xbox? i seen this now in 2 out of three topics that u replyed to STOP IT! and 2 no full source for any have been released.

...he posted those in Feb, i.e. months ago, and hasn't been back since I explained to him why his idea was totally unfeasible (and illegal). So, there's really no point in replying to it...

In the xboxlinux page have done it

ANyone know how to do it or is there any tutorial???

That's not running 2000 on the Xbox natively, that's running it under a virtualisation program on top of Linux. There are a number of topics in this forum talking about how to run Win98 under QEMU - for Win2000 you'd likely want to use virtualisation, not emulation, so just install a Linux distribution on your xbox, get the free VMWare Player, and install Windows under VMWare. It will perform quite badly, though, unless you have the 128MB ram upgrade - the overhead of running linux and vmware (or qemu, or any other virtualiser/emulator) will take a significant chunk of the Xbox's limited RAM and leave very little for Windows.

I couldn't agree more Torne. NT AUTHORITY should be ignored. Replying would be a waste of ENERGY !!!

Oh dear God !!!

Anyway I wanted to see if you need any help Torne. My name is Bill Gates and well, you see I was reading this thread somewhere sometime somehow which goes a little something like this:



And I started to think...

I agree with the first statement here: IT IS NOT NECESSARY TO MAKE IT ALL THAT COMPLICATED. (Getting Windows to Run on my XBOX). In respect to the EITHER PORT REACTOS AND FORGET ABOUT MS WINDOWS ALTOGETHER all I can say is this: use all resources available to you: SCIENTIA EST POTENTIA.

Those intelligent enough to decrypt such I am sure will tie me up to more conspiracies such as the NSAKEY in CRYPT32/ADVAPI32 DLLs but who knows ??? DARPA did invent the internet didn't it ??? Or was that I ???

Anyway, to continue:

"Incidentally, the differences between the Xbox and a regular PC are much less than the differences between an Intel-based Mac and a regular PC - but both the xponmac team, and Apple themselves, have managed to get XP to boot on the Intel Macs."

For heaven's sake: ANYONE CAN GET ANYTHING TO BOOT OF ANYTHING WITH MONEY !!! Even that xbox-scene user NT AUTHORITY who made some very bizzare posts in this thread (I agree with you Torne and thanks for telling him/her off for trying to use my source and reminding him/her such an operation was/is ILLEGAL) could (believe it or not) get Windows up on running on the XBOX and IN THE EXACT WAY HE/SHE DESCRIBED in his/her posts AS LONG AS HE/SHE HAD MONEY !!! All NT AUTHORITY or anyone else for that matter would have to do is get a $100,000 or so and PAY people like Torne and other professionals who have had the privilege of seeing full Windows Source to BREACH their NON-DISCLOSURE AGREEMENTS and BUILD XBOX FOR WINDOWS.

Now to the POINT:

"A similar approach to xom for the Xbox would actually be quite interesting; it wouldn't be *completely* impossible to write an Xbox executable that could function as a simulacrum of a PC real-mode bios (though this would have to be a freestanding executable that ran as if it were a BIOS and accessed the hardware directly, because it's not viable to call the Xbox's kernel services from real mode)."

It most certianly would NOT be completely impossible to write a DEFAULT.XBE that functions as a simulacrum of a PC real-mode BIOS and THIS IS THE ONLY WAY ANYONE WILL GET WINDOWS ON THE XBOX PERIOD; one smart cookie (or team of you lot on this forum) simply need to get together and write this executable to simulate a PC BIOS to the degree "That would get you quite far with booting NT.."

That is the Bill Gates and MS APPROVED solution.

in respect to the dilemma:

... " though it's a toss-up as to whether that'd be more or less work than just hacking up the NTLDR boot process as I already described. (PC BIOSes are hard, mmkay). "

Bill Gates says this:

PC BIOSes are hard, mmkay, but for those of you who know Occam's Razor, hacking up the NTLDR boot
proces as I already pasted above is not THE PATH OF LEAST RESISTANCE:

Windows and it's CLEAN (non-hacked-up-proper-NTLDR-out-of-box) is what is released to manufacture: logic thus tells us that if a PC BIOS simulacrum DEFAULT.XBE can "trick" NTLDR into thinking it is running on a PC and receive the correct responses to enumerate hardware and create the registry and initialize the kernel and start loading devices then NO MESSY HACKING AND REVERSE ENGINEERING OF BOOT LOADERS is required: creating a simply DEFAULT.XBE simulacrum BIOS is OBVIOUSLY the only solution.

Then you can just run Windows as if it was meant to run on an XBOX from day zero.

My god, when I first designed the XBOX and added in the dummy boot loader in the TSOP as a throw-off I thought people would immediately click that the KEY TO IT ALL is creating a simulacrum BIOS.

Just KISS (Keep it simple stupid) and remember what BIOS stands for:

BASIC INPUT OUTPUT SYSTEM.

If someone does not have Windows on the Xbox within 3 months of me posting this thread here I swear god I AM GOING TO COMMIT SUICIDE !!!

What do you need to do other than create a BIOS default.xbe to get Windows on XBOX ???



NOTHING

Well, you're damned hilarious, I'll give you credit for that. Your forum etiquette leaves a little to be desired though; perhaps you're too used to being surrounded by flunkies who don't mind being abused?


Hardly decryption, and those of us who've read the source for crypt32 and advapi32 know that the NSAKEY debacle was entirely rubbish and there's no conspiracy there


They'd have to pay someone else, since I have standards to uphold. I hold a number of companies' intellectual property in my mind by this point and am not going to ruin things by spilling the beans for something as petty as money.


Oh, it's certainly not the only way; if you read my later posts I go into more detail about the NTLDR replacement approach which is entirely viable. It doesn't require modifying NTLDR but rather reimplementing an equivalent, which is actually not that difficult if you understand the couplings between NTLDR and the kernel. (my colleague and I did it for the Xen port of Windows XP: a userspace utility in Xen's Linux-based Dom0 loaded the kernel and other things that NTLDR would load into a newly created Xen domain's address space, and set up memory in the fashion that NTLDR would, including the results of the fake hardware probing).


You clearly haven't studied your own hardware very much if you believe this to be the case; it is impossible to run an unmodified NTLDR on the Xbox even if a perfect simulation of the PC BIOS is available, simply because PCI bus access does not use BIOS services (the PCI address space is programmed directly) and as soon as NTDETECT tries to enumerate 0:0.1 and 0:0.2 on the PCI bus the Xbox will freeze. There is nothing a BIOS simulation can do to prevent this; it's a hardware bug in the Xbox northbridge, as you would of course know *grin*. Avoiding it without modifying NTLDR/NTDETECT would require complete virtualisation of the hardware, not just a BIOS, which defeats the point of attempting to port the OS natively. There are other things that will cause problems (though not completely prevent booting) too: the different 8254 PIT frequency will screw up Windows' ability to keep time, for a start.


Go play with your hardware some more, rather than trusting the spec sheets.

I really must applaud you for amusing me, though.

:jester Of course ! I am too used to being surrounded by flunkies who don't mind being abused; I am the director of Microsoft (or M$ as I like to refer to the evil empire) and those flunkies are my employees {well they are actually demonic brainwashed monkeys with four anuses which are handcuffed to IBM typewriters and writing the great American novel whilst smoking cuban cigars and when I say "novel" I mean Windows Source Code ;-) } PS: the handcuffs don't really need to be there: it's just for my sexual satisfaction: we actually direct intracranial electronic stimulation of the brain to release phenethylamines and keep em happy: I learnt this from a TOP SECRET CLASSIFIED document that Allen Dulles wrote when he was in charge of the MKULTRA project as director of the CIA (I think that means Central Intelligence)...



Oh Torne, I was hoping you were smarter than this obvious reverse psychology... You see that "Academic"
shared source licence agreement you have seen doesn't contain the REAL RTM SOURCE that does have the NSAKEY backdoor in crypt32 and advapi32; as if I would be stupid enough to release such to every damn University; then the NSA would come along and say "Bill, you just exposed our TOP SECRET ECHELON back door to every Windows system on the planet containing this code and now we are going to have to invent SELinux and get into some contract with VMWARE to help us restructure the OS powering all those acres of supercomputers in the basement AND then we are going to have to assasinate you..."

Hang on. What's this: http://news.com.com/2100-1001-251927.html

Did I hear Robert Lemos say:
"You wouldn't want to do it on Windows NT, because you know nothing about what is going on inside NT," :-O

Well Robert Lamos my comeback is "You Wouldn't want to do it on Windows NT, because Windows NT knows nothing about what is going on inside NT."

Hey, how come once I said that MSFT shares dropped in value to almost NOTHING !?!

Well at least I got to say ECHELON in this post: there are enough keywords in here to give some analyst at the NSA a coffee break once ECHELON detects this and puts it on his desk; I mean the poor agent was sitting around bored to death listening to the jihad phone and hearing bin laden rave to his mother about how he has this amazing box that beams his voice up to some inmarsat iridium satellite and let's him give order's to other al-qaeda commanders. Hmm, maybe I should invent Windows for Terrorists before I get assasinated...



HA ! For a start, I already KNOW you have sold illegal stolen source code and have proof of such. And come on man, do you really expect ANYONE to believe that ? If I paid you $1,000,000,000 you and everyone else in this forum (or the world) would obey my every ORDER.



Ok well I admit it's not the ONLY way and I did read your posts where you go into more detail about OSLOADER.EXE and the replacement approach is entirely viable but you did not understand what I was saying ( Ill get to that in a minute). Of course I understand the couplings between OSLOADER.EXE and the kernel. I am simply saying one could write a OSLOADER based on the \nt\private\ntos\boot\ sourcecode and make a OSLOADER for the XBOX.

This OSLOADER would work in the way one is made for the ARC/DEC/ALPHA architecture where NTDETECT.COM is never executed because the Alpha's firmware hands all this information of the hardware to the OSLOADER and then passes the loader block informations and other coupling to the kernel.

You see my point is if you FIRSTLY make a simulacrum BIOS as a DEFAULT.XBE which mimics the mentioned Alpha firmware hardware detection routines or in simpler terminology PASSES HARDWARE INFORMATION over to the OSLOADER as if it were stored in space contained in the Alpha frimware (but really held within the binary simulacrum XBE pretending to be the firmware) then the OSLOADER would be able to pass this over to the kernel and execute.

An alternative is to not use the Alpha's firmware but to instead make a DEFAULT.XBE simulacrum of the Unified Extensible Firmware Interface;

see www.uefi.org

whereby the xbox executes DEFAULT.XBE and brings up a UEFI environment which then loads a UEFI program such as the BAMBIOS.EFI program created by the OSx86 collaboration team and based on the Bochs X86 emulator: A legacy BIOS simulacrum used to get Windows working on X86 MACs which HAVE NO BIOS;

see http://www.osx86project.org/index.php?opti...40&Itemid=2

AND

see http://www.osxbook.com/book/bonus/misc/legacyboot/

Now, once the source code to make the UEFI simulacrum DEFAULT.XBE is re-built in the XDK you can then load the BAMBIOS.EFI which would do a good enough trick to load windows normally.

you can get the UEFI source from here:

http://www.intel.com/technology/efi/agreesource.htm

or IF YOU DONT WANT TO AGREE TO THE EULA FOR DOWNLOADING THE SOURCE GO HERE AND GET IT ILLEGALY:

ftp://download.intel.com/technology/efi/d...I1_10_14_62.zip

ftp://download.intel.com/technology/efi/d...i1_10_14_61.zip



Could I please have a copy of the abovementioned executable's sourcecode, seriously, thanks.
Email it to me at

noevent@gmail.com

:-)



Sorry but I am the director of M$: I didn't know; I have more important things to do like write this POST. And like I just posted above I would not use a perfect BIOS simulation: WHOEVER GETS WINDOWS ON THE XBOX WILL make a DEFAULT.XBE simulacrum to boot and instead of a BIOS they would use the concept above with UEFI.



How many times do I have to say this: You would have to modify OSLOADER and eliminate NTDETECT by doing such with the DEFAULT.XBE simulacrum of UEFI.

That is the answer to Windows on Xbox:

UEFI.

That's why the U stands for

UNIFIED.

Bored of responding to specific points now, since you're just regurgitating the same things. UEFI is not particularly relevant because it still does not encapsulate PCI bus access - UEFI only tells the OS how to access the PCI bus, not the details of what is there (more specifically in this case: what is not there).