I had Halo 2 on my original xbox hard drive and I could play it fine. Recently I upgraded the hdd in my xbox, and today I tried to play Halo 2 for the first time on it and the game starts and when it gets to the first screen telling you to press the start button, upon pressing a button it freezes. I figured I could have messed something up a while ago when I was modding, so I decided to re-rip it to the hdd. It still freezes. All of my other games that I have backed up play fine, but none of them were added until after I installed my new hdd. Halo 2 was copied along with all the files on the original hdd to my new one. I could get the original xbox hdd, open my xbox back up, switch it out with the new one, bolt everything back together, and then be able to play Halo 2 again, but it would be nice if someone knew of an easier way, such as changing the path of a file or something else that could be overlooked. Also, I almost forgot to mention that Halo 2 is freezing at the 'start' screen when I try and play it from the disc too. This happens regardless of whether or not I'm using the default xbox dashboard or avalaunch. And if it helps anyone to answer my question I have a v1.0 xbox with a xenium ice chip(with xenium os 2.0), using an evox bios and avalaunch dashboard with a 160gb hdd. Thanks for any helpful suggestions!
And if anyone knows anything about how to ftp .iso's so they will play off the xbox hdd or about why I am having troubles getting xbmc to play .avi's will you please post it in the threads I created a couple days ago. I have gotten no responses to those topics. They are a couple pages back and any help at all is greatly appreciated.
I have precisely the same problem with a newly purchased copy of Halo 2. It won't run from the DVD, and won't run from the hard drive. I have a 30GB drive with EvoX installed. My 8GB drive (the original XBox drive) also has Evox installed, and Halo 2 will run just fine with this drive in there.
I gleaned this from another thread, and I've not been home to test it, but another poster claims that this problem is solved by deleting (I plan to just move them, just in case) the files in e:\cache
