Leaderboard

Good evening, I want to report a bug which I've seen with 2 Corona V2 (so 4GB, no 16mb nand) RGH I've done this week. I installed freeboot 2.0.16202 on it. Nothing special. Since FSD cannot boot directly from the OnboardMU on this console type, I used an USB fat32 formatted 500gb harddrive. launch.ini and fsd folder in the root of the harddrive, turn on the harddrive, turn on the xbox and it glitches and starts FSD3. Note that I have a folder XBOX360/games on the root of the USB harddrive. In that directory are a few games. I then go to the appropriate section in FSD to add USB0:\XBOX360\games to the game paths, select XBOX360 as type and press X to save it. And then it happens : not only is USB0:\XBOX360\games added to my game paths, but also SysExt:\XBOX360\games AND OnboardMU:\XBOX360\games. Thinking, ah.. bug.. never mind. I let the XBOX find the covers (which it does). When I then go to the games part to see if the covers were downloaded correctly I see the two games that are on my HDD. But.. in the details it says 'OnboardMU : <hexcode i forgot>'. Trying to start the game will fail, because OnboardMU of course doesn't have the game. Same applies to the other game. When I go back to the game path settings and remove the OnboardMU: reference, all three references are deleted ! Exact same procedure on a Trinity and a Falcon this week and not a single problem, so it would seem this is a 4GB nand console problem with FSD3 ? I don't know if this was already known, but here you go I tried the latest release of FSD3 as well as an older one (september 2012). I have now put the latest FSD 2.2 on this Corona V2 and that works a charm. If you need more info or want me to test something, shout. I've done resets, cleans and delete the FSD folder altogether but nothing helped.

THIS NEED TO BE STICKED