Mu.

Those hard disks will work, however you will require an adapter to go from the older IDE connection to the newer SATA connection those drives use. There are unbranded adapters out there and also ones made by companies like StarTech. I've had 100% success with the StarTechs while the unbranded ones can be just as good but its luck of the draw what you get.

You press the power button on the front of the Xbox console, wait for it to switch off. And then press it once more to start the boot process.

Probably the best solution for an on-console test would be to boot some form of Linux on it and then run a suitable hard disk related tool (I know 'dd' can be set up in a way to do this but I don't know the arguments off the top of my head).

You can simply reboot, I've had the same issue and it's gone away that way.

An unusual development: I ended up purchasing a second console (Another 1.2 w/ a Samsung drive). The philips drive works perfectly in the new system. I've also had issues booting from the hard disk on my original 1.2 so I think there's a bigger underlying issue here. But at least I'm certain I have 2 working drives now. EDIT: It's the cable, I feel like an idiot lol!

Thanks for letting me know, I extracted the 5003.67 XISO version from my OGX Installer 21 iso, should all be good now until I can find a drive. If anyone has a spare one going in the UK, hit me up (fat chance!).

Sounds about right, I was hoping it wouldn't come to that though. Can ind-bios get around the dvd check or is it just Evox that's capable of it?

As the title states, the Philips drive in my 1.2 is refusing to boot/read discs. In XBMC4Gamers it appears in the top right corner as you would expect, but the text that accompanies it just says "Busy". It says this as well in the file manager. In the retail dashboard it will throw up the usual "Could not read this disc" error. It also has the telltale 'hitches' during the flubber animation that appear whenever the DVD drive is disconnected. Is this indicative of a hardware issue with the drive? I'm confident its not my mainboard nor my cable. I'm really, really not up for cannibalising another Xbox to fix this one and listings for individual drives are non-existant.

I was looking at the typical Aladdin XT 2 Plus modchips that are still available/being produced for the Xbox a while ago, and I thought to myself that the wiring to permanently ground the BT pad seemed a little inelegant. I took a quick look at the traces on the PCB and lo and behold, they trace back to adjacent pins on the Lattice CPLD chip! Going forward should I ever need to install another XT 2 Plus, I'll forego the wire and just bridge those two pins.

There are also pads on the underside of the board which correlate to those two vias if they prove difficult to solder to. You'll need to use a multimeter to find these as I no longer have a 1.6 to refer to myself.

I put one of these together a few years back, it's probably the best affordable option for video on the Xbox. Though I wish I'd not cut off the composite video connector and instead wired that up to digital audio output.

I wonder if this issue with the OGX360 is because it uses different IDs to the standard Xbox One controllers, and so the OGX360 doesnt recognise it as such. This guy talks about a very similar issue to Philips in regards to using it with Linux (timecode is 1:39 to skip the introduction stuff), my guess is if the vendor/product IDs are changed on the OGX360 then it will detect it and work just fine.