Alright, so I made a new drive from scratch, but the exploit won't work for AUF cause of the missing kernal fonts. So I went back to XBOXHDM to unlock my drive and it's saying that the drive isn't on Primary Master, and which it is... Secondly I've also set the drive to master with the blockplug, still the same result... So why exactly has XBOXHDM not liking the drive any more?
Dunno, Ive only had positive experiences with XBOXHDM. Maybe try to set the HDD on cable select and make sure it is the only hdd in the machine? Only thing i can think of right now.
I've only had positive until this point... It's just decided to do this, really odd. So the setup this PC has is a DVD Drive set to slave in the BIOS, and the XBOX HDD set to Master on the Primary. I don't get it. Also when you get the Tux screen, it says "Drive Status Error" 4 times when loading the device list. Don't forget this drive worked FINE when I built it from scratch and locked.
Do you have the HDD jumper in the right place? Do you have it plugged into the master socket on the computer's IDE cable? I don't remember if the master socket is the grey one or the other one.
I did nothing different the first time, the second time is where it's been throwing up errors. I read some where if you set the drive jumpers to "Cable Select" in the XBOX after you've finished the process. So I'm guessing that needs to be done before I take it out? Seems weird though, as the other XBOX has never had a problem with XBOX HDM, it's just this one..
