![]() ![]() ![]() During my own research, I compared the source tree directories and files stored within to the Windows Research Kernel, and found that, for the most part, NT and XboxNT are very close cousins. There has been lots of speculation as to whether or not the OS was completely written from scratch, or if it was simply a modified form of the NT kernel. The underlying Kernel was designed specifically for the Xbox. Those are not things that I will talk about in this post, as they are secondary to the main idea behind this thread. Note: There are security systems in place that have been both defeated and bypassed due to failure to read Intel documentation on Microsoft's part. The entire kernel exists within the first 1MB of system RAM once it's fully booted. Internally, the OS consists of the bare-minimum boot code to transfer from x86 POST up through switching to protected mode and 32-bit kernel mode. It was designed around a heavily customized Windows Embedded line of Operating Systems. The Original Xbox Console's Operating System, herein called xboxkrnl, was based on Windows 2000 code. However, Error Code 04 would probably be the end for this particular console.Disclaimer: I will not provide links to sources, as per forum rules. I guess I'm hoping for a Error Code 02, as I could potentially recover from it by reflashing the EEPROM. Replacing the RAM chips could be a solution but is risky and time consuming. Remember, electrostatic shock can sometimes damage integrated circuit chips like RAM chips, so even if you can't see a problem, the RAM could still be fried. This could be from pins on the RAM chip(s) becoming bridged, possibly from an accidental splash of solder or a failed 128MB RAM upgrade. You will see the Xbox rebooting and flashing red and green lights (FRAG).Ĭause/Solution: RAM chip failure. This error is triggered by the bootloader and as a result does not display an error code on screen. ![]() If you recently did some soldering to your Xbox, check for any stray solder balls that may be present and carefully remove them. If you're using a modchip and you just flashed it, try again using a different BIOS. You will see the Xbox rebooting and flashing red and green lights (FRAG).Ĭause/Solution: You flashed something wrong or caused a short somewhere on your motherboard (possibly while soldering). I'm not too familiar with these consoles, so I'm wondering if anyone could tell me if removing the hard drive and/or the DVD drive would cause FRAG in an un-modded Xbox?Īlso - I do not have the original hard drive - would booting with a larger hard drive cause the FRAG issue? I've reflowed the solder on the LPC points I've touched the MCPX chip to see if it is getting very warm when powered - it does not I've measured the collector transistor voltage OK, at 3.25 V It has a modchip (Xecutor 2.3 Lite), so I tried de-soldering it to see if that was the cause of the FRAG, but it did not help.Ĭhecked for bad capacitors, but they all look fine. Here's what I've done to try to troubleshoot the issue: It reboots a couple of times and flashes red and green (FRAG) when I turn it on, and no video output is shown on the TV. I got an old original Xbox (v1.6) here and are having some issues trying to get it to boot. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |