Print

[DocOblivion]

Not sure if I should be posting this here, or in the XBMC specific section; hopefully someone will move my topic if I've chosen incorrectly!

I've had a soft-modded Xbox with XBMC as the dash for almost two years now. I upgraded fairly regularly, but always via the manual methods of overwriting the folder then restoring a backed up UserData folder.

A few months ago I was lazy, and tried using one of the automated T3ch update scripts, and after rebooting, got the annoying error 13. When I found that I could still boot up Splinter Cell, I ran the save exploit and renamed an old UnleashX xbe to xboxdash.xbe, and it worked fine! Booted right into UnleashX. I grabbed the "Shortcut" xbe and cfg that came with the latest XBMC, renamed it to xboxdash.xbe, and rebooted... and back to Error 13!

Curious, I booted Splinter Cell again, got to File Manage via the exploit, and manually ran the XBMC-shortcut xboxdash.xbe... and it started up without a hitch!

So, my problem in a nutshell? XBMC will start from xboxdash.xbe in the root directory when we manually run it, but the Xbox won't boot using it. The Xbox will, however, boot when the UnleashX xbe is renamed to xboxdash.xbe.

Any thoughts? I just upgraded to the latest "bleeding edge" T3ch XBMC, and the issue persists!

Thanks for any help in advance!

Edit - After reading my post, it occurs to me... is it possible that drive letters are being assigned differently when I boot from Splinter Cell? Would I be able to change the shortcut to \\partition0\disk2(or whatever)\apps\XBMC\default.xbe instead of E:\apps\xbmc\default.xbe? I'll have to try that when I get home from work...

[DocOblivion]

Never mind, I decided to stop being stubborn and take the seemingly ubiquitous advice to re-mod with Krayzies 1.1.1, and everything's fine now!

[Heimdall]

That's why it's ubiquitous advice - it cures 99% of all known softmod problems at a stroke...!!