As everyone here knows, there were two unavoidable problems with this. First, the stock hd is small, even for seven years old. Second, once you start a mod project, you tend to keep going.
SO! I pulled out a spare Samsung 160gb hd and ran xboxhdm2.1 again (my PC has only one PATA connector which defaults to IDE 4, so I can't use xboxhdm1.9 since it requires the hd to be the primary master). I ran through the process and plugged it into my xbox. But I forgot to lock it, so I went back to the pc with it and locked it, then plugged it into the xbox. Error 21. Before I suspected that it was because I simply missed a step in his Xbrowser360 tutorial (Delete xbox.xtf and xbox book.xtf in partition 3 root in step 4), I decided to just rebuild the hd from scratch using xboxhdm's option #1.
In the middle of this, I had to leave the house. The last thing on the console I saw was that it was making the F partition. When I returned home, my computer was off and other appliances indicated that my house lost powered while I was out.
I attempted to resume the process, preparing it as a new hd with xboxhdm yet again. Not only did I have no luck, I suspect a corrupted partition on a locked drive. In no particular order, I've tried:
- xboxhdm option 1 - says it can not find /dev/hda which isn't surprising as Slax spews errors about /dev/hda upon loading. They go by too fast for me to see what they are.
- unlockhd -p XBOXSCENE /dev/hda - gives an I/O error
- estool from Samsung for low-level format - sticks on infinite loop saying I/O error on LBA 40
- computer management in Vista Business 64bit says drive is Unknown with no option to initialize disk
- Gparted bootable cd won't even load - sticks on infinite loop attempting to access drive
- fdisk from FreeDOS returns I/O error
Does anyone have any other ideas? I have a WD 120gb drive that I can use, but that 33% more space is pretty attractive.
Edited by welandB, 11 December 2009 - 09:47 AM.