Hi all, I've been googling and searching and not finding an answer to this.
I fired up my Xbox today (first time in a while) and got a notification that a new version was available. I went into the settings, updated the URL downloader and then did the XBMC4Gamers update.
After a bit, I got a message that "autoexec.py" or something like that failed. Now I'm stuck at a screen that says XBMC Fatal Error: No suitable skin version found (see screenshot)
I am able to FTP into the xbox just fine. I did find some mention of a guisettings.xml file but I can't seem to find where it might be and where I can get a replacement for it (if that's even the problem) My default dash is/was xbmc4gamers, BTW.
I would appreciate any help!
*Disclaimer: No links to file will be provided, this is for discussion only*
Not sure if anyone has yet, but I have been running a diff between Barnabus Kernel Repack and the 4400 leak Kernel Tree..
I've only just started looking through, and I have next to no C++, C and C# coding skills so bear with me lol
They seem somewhat the same, but there are quite a few files with parts of code removed or added, on both branches. But Barnabus is reliant on precompiled objects (obviously as it's a smaller, almost stripped down and made 'easy' release of the full tree)
There are some comments in Barnabus code that isn't in the full tree + CPXXUPD code, and some are recorded more 'formally'
(i.e private\ntos\init\init.c line 244 - 254 in both branches)
One other thing is the 4400 tree is set to have 'complex's' edits definable where possible, which there are a lot..
One thing that really interests me, is Barnabus uses BIOSPack to pack: 2bl, remainder and kernel into a 'Working' rom (I use that word loosely).
The 4400 tree uses rombld, which requires: preloaded, init table, bootloader, kernel and a rom decode file(I think).. this is a drastic difference to BIOSPack.. But the main issue with Rombld is it will not produce a full rom.. by default it will error on the 'preloader' being to big (9008 bytes not 1664 bytes)..
To get around that, we can either build for XDK Systems..
Or as I discovered today: modify 'private\sdktools\rombld\rombld.cpp' Line 879 from (2 * 1024) to (21 * 512), to allow rombld to accept the 9kb preloader file.. (I haven't tested a bios rom built with this edit yet)
Recommended Posts
Similar Content
I fired up my Xbox today (first time in a while) and got a notification that a new version was available. I went into the settings, updated the URL downloader and then did the XBMC4Gamers update.
After a bit, I got a message that "autoexec.py" or something like that failed. Now I'm stuck at a screen that says XBMC Fatal Error: No suitable skin version found (see screenshot)
I am able to FTP into the xbox just fine. I did find some mention of a guisettings.xml file but I can't seem to find where it might be and where I can get a replacement for it (if that's even the problem) My default dash is/was xbmc4gamers, BTW.
I would appreciate any help!
Not sure if anyone has yet, but I have been running a diff between Barnabus Kernel Repack and the 4400 leak Kernel Tree..
I've only just started looking through, and I have next to no C++, C and C# coding skills so bear with me lol
They seem somewhat the same, but there are quite a few files with parts of code removed or added, on both branches. But Barnabus is reliant on precompiled objects (obviously as it's a smaller, almost stripped down and made 'easy' release of the full tree)
There are some comments in Barnabus code that isn't in the full tree + CPXXUPD code, and some are recorded more 'formally'
(i.e private\ntos\init\init.c line 244 - 254 in both branches)
One other thing is the 4400 tree is set to have 'complex's' edits definable where possible, which there are a lot..
One thing that really interests me, is Barnabus uses BIOSPack to pack: 2bl, remainder and kernel into a 'Working' rom (I use that word loosely).
The 4400 tree uses rombld, which requires: preloaded, init table, bootloader, kernel and a rom decode file(I think).. this is a drastic difference to BIOSPack.. But the main issue with Rombld is it will not produce a full rom.. by default it will error on the 'preloader' being to big (9008 bytes not 1664 bytes)..
To get around that, we can either build for XDK Systems..
Or as I discovered today: modify 'private\sdktools\rombld\rombld.cpp' Line 879 from (2 * 1024) to (21 * 512), to allow rombld to accept the 9kb preloader file.. (I haven't tested a bios rom built with this edit yet)
I will post here anything else I discover!
128MB Ram
New Fan
Open Xenium Chip with Ryzee119's XEnium Spi2par2019
To be continued...
Board Life Status
Board startup date: April 23, 2017 12:45:48