Bowlsnapper

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?

Your HDD being "not locked" may be the reason for this error. The version number you are showing sounds like the dashboard kernel version. How are you modded, exactly? Softmod? Chip? TSOP?

Bump. I honestly need the money right now in preparation of the heart surgery I am going to receive this summer. If people would be willing to make offers I would greatly appreciate it. I will take them seriously.

Hmmm, no "Halo" jewels on the controllers. :p. Still awesome though. He must've said that it was rare about 24 times. lol.

What bios are you using and what service error is it? I have a feeling that your HDD locking may be disabled which will cause an error. Either that, or your C partition is a bit borked and needs to be setup again, which sometimes happens.

Really any executables in the "E:\Devkit\" folder can show up, as they are scanned when the dashboard loads. I would just create a folder called "Games" or whatever seems appropriate to you in the "devkit" folder and place game files in their own respective folders. Keep in mind that retail, signed executables cannot run when launched from the dashboard. This is not really intended to be a main dashboard. If you would like to install it as an "app" dashboard, the option is in the installer to do so. Or you could conversely load it as your main dash (also an option in the installer) and then use Pheonix Bios Loader to boot into a regular dashboard/modded setup, which is how I have my system set up currently... even though it's in pieces due to being in mid-construction right now

It requires a modded xbox to boot. ImgBurn is strictly for creating the disc on PC.

And MY thanks goes to dardestiny for being resourceful and thinking of many things to improve what he's done already.

@Naked Newt Red/Orange is a memory issue. For some reason, the Xbox's 64MBs of RAM memory is not working properly. Possible causes: Solder bridge between pins on one or more of the chips. LPC Debug port's LRESET# pin (pin #5) being held low (or in a floating state that's not registering as a logic '1' level - HIGH) which keeps the RAM memory and other peripheral chips in a reset state never allowing them to run. (Edit: xbox-hq.com's Fixing flashing red/orange tutorial) Dead RAM chip that requires replacement. It's possible that the electrolyte corrosion damaged something involving the RAM without actually being the RAM. Unless replacing all the modules fixes it, this board is probably a lost cause since there is too much to diagnose. There have been cases I have seen where replacing the troublesome ram chip (probably only one chip in many instances, as long as RAM chip(s) are the cause) remedied the issue.

I am taking this time to iron out the PC side of this. There are no real XP drivers for the USB FTDI serial host, so I think I'll have to add a serial (RS-232) port via PCMCIA and then add another RS-232 port to the xbox via the UART output of the SuperIO debugger. https://www.ebay.com/itm/264727392495?chn=ps&norover=1&mkevt=1&mkrid=711-117182-37290-0&mkcid=2&mkscid=101&itemid=264727392495&targetid=1493661221511&device=c&mktype=pla&googleloc=9031634&poi=&campaignid=19851828444&mkgroupid=145880009014&rlsatarget=aud-1412318123216:pla-1493661221511&abcId=9307249&merchantid=6296724&gad_source=1&gclid=CjwKCAjw8diwBhAbEiwA7i_sJfxniuhIlZOnTDQvyuX6-ksX9fzFcHCejxDt1JzZSYbTnitUuku7YRoCuTIQAvD_BwE https://www.amazon.com/RS232-Converter-interfacing-microcontroller-device/dp/B01M4PZA7R

Just burn the iso with imgburn and run it in the xbox. It has scripting that will take care of the job for you. It also has all the software you will need on the PC side, although I need to immediately post the link to the VMware XP/XDK image that's out there. It makes the process much easier if you wish to take the VM route (not my cup o tea. I like my setups difficult and impractical, lol.). Actually I will probably make an ISO of the PC-side software that isn't XISO so that it can just be inserted into the PC. I'll do so tonight. Should make things much easier for people.

Wow. You're going fast. Leave some ports for me! lol. Nice work, dude!

So for one reason or another, I am not getting the dubugger to work properly. Even on a 1.0 where LFrame is guaranteed to be working. I think I need to build another one and try again. This project is on hold I guess.