Bowlsnapper

Well, It's basically done. I didn't get the DVD "Ready" light to work (it kept fucking with my DVD ROM drive and making it act funny), but I did get the activity light going, separate from the HDD activity LED. LAN is there as well. The two on the left are the RX and TX LEDs for the Super IO debugger. I'll test more tomorrow with the XDK and debugging through LAN, but it looks like this project is good

The relocated debugger RX and TX LEDs are working.

I got the debugger working. First, some pins were loose on the SMSC chip linking to the LPC pins. Now, it will not work with the 1.4 board I'm trying to use, because the LFrame via is borked. I already know, man. I gouged the shit out of it. Anyway, if I have to use the 1.0 that I used here to test the unit, then I will, but I'm gonna try to get the 1.4 Lframe working. Project is back on track and the BOM I posted is good.

Ah, okay. So if all that has happened, then I would reapply a thermal coupling solution.

It will be made easier to go into a modded dash with a retail BFM bios from the XDK dashboard and just launch games from XBMC, UnleashX, etc.. In order to launch retail games from the XDK dash, it's kind of a pain (it can be done a certain way) and honestly would not really serve a purpose.

If your temperatures are normal, then thermal paste is not necessary and it will not fix this. Also, if the graphical errors are present immediately upon boot, then the artifacting is not being caused by overheating. Really, in the case of the Original Xbox, the thermal glue that is used is pretty much fuckin' bulletproof. That stuff is incredibly durable. In fact, if your temperatures are good, I would not remove the stock cooling compound setup. It just would serve no purpose. If you have never removed those sinks and they have never been apart from the motherboard, I would assume that your thermal compound is intact and is still doing the job it was doing 20 years ago.

Yes you can... However, you will be limited to UDMA 2 speeds, reliably. You can either flash the UDMA 2 version of Cerbios for the time being, or flash UDMA 6 to get prepared for the cable and just boot into safe mode using the eject button to power on. Using UDMA 6 will definitely result in an error.

Very briefly, could you just tell me where to put it and anything else that may be necessary first? I use XBMC4XBOX. I'm just not familiar with addons. Sad, because the profiles I'm seeing in this thread are no longer active after 5 years. lol.

Would somebody be willing to detail how to do this and exactly what it is? I'm not entirely sure based on reading the thread. Seems like it's basically a file that points to files hosted on a server somewhere. Can I just drop this in a directory and go? It's kinda' funny to see all these profiles that I don't recognize... and a little sad.

Could you maybe detail a bit where this acquired, what it's original specs were, what the CPLD flash was supposed to do (1MB upgrade maybe?) and whatever else? I'm interested.

As far as I know, Aladdins made in this decade don't have a working D0.

Please be a bit more detailed. What installer are you using? Which partition are you telling the installer to install your dash to? I would honestly not continue using this chip, as it's kind of a headache, to be honest. But that is only my opinion. Maybe consider an XBlast Aladdin or an OpenXenium. I would try to flash Cerbios. Evox is outdated and not really as useful anymore. There is no reason to use it as your bios. I do not know the flashing process for the DuoX, but it may be able to be flashed with the XBE version of XBlastOS.

This is a general dash error. See if running an installer such as the OGXbox installer and "Setting up" C resolves your issue. Formatting C and reinstalling the general files there is not a risk as longas you are not softmodded.

There is no BT wire, as it serves no purpose with the OX. D0 is on the top right of the chip. It has a separate Lframe pad to ensure that it is operated correctly as a means of LPC booting. It appears that TSOP booting or "disabling" the chip is done by booting into XeniumOS and choosing to boot from the onboard flash. https://consolemods.org/wiki/Xbox:OpenXenium "Ability to boot from the onboard BIOS (colloquially known as TSOP booting). This will completely disable OpenXenium and release D0/LFRAME(1.6) to boot the Xbox as if it is stock."

Actually, if you're booting a modded bios to the MS dash, I think that it should not be giving an error about drive locking. What is the error number in the top left?