Print

[johnnywikked]

If a BIOS hack would allow that, it would have been done by now.

[slang123]

By the way guys this is actually being worked on, blackbolt mentioned xport skins was one of the side projects. Am looking forwards to it  

[Jezz_X]

QUOTE(slang123 @ Apr 13 2006, 11:51 PM)

By the way guys this is actually being worked on, blackbolt mentioned xport skins was one of the side projects. Am looking forwards to it  

Actually he never said he was doing that at all he simple said that they are doing Evox UnleashX and dvd2xbox and Noiw all they need is xport skins he didn't actually say he was doing them

QUOTE

The Evolution-X version is obviously just as interactive as any other evox skin, same with the Unleash X skin.

The Unleash-X skin has been in constant development and will be released when the xbmc is released, I can also confirm that a DVD2XBOX skin is also in developement and will release around the same time as the XBMC project.

The Evox one will be a day or so after XBMC version is out. Alls thats left now is to get some XPort skins done eh!

[netdroid9]

QUOTE(johnnywikked @ Apr 13 2006, 07:47 PM)

If a BIOS hack would allow that, it would have been done by now.

X3 Config Live has a config app built in to the BIOS (I think) and I've heard that Debug BIOSes can maintain two XBEs at once, so it might be possible. You can get modchips with up to two megs of space, and who knows what size BIOSes PBL can support.

We're talking about the BIOS here, the core of the xbox. Anything's possible, so long as you have enough space, time, skill and interest.

[JustinT9669]

I wonder who will spend so much time building a custom bios for a xbmc skin?

[Alex Atkin UK]

The problem is that with anything extra running in the background it will change how code runs on the X-Box.  It particularly id doubtful with games as they expect to have all the CPU and a certain amount of RAM to work with, having a home blade in RAM would reduce the amount available to below what is expected so is very unlikely to be possible.

Its only possible on 360 because MS decided that a certain amount of RAM and a certain amount of 1 of the CPU cores would always run an OS in the background.  If the 360 had only 1 CPU or less RAM it would have been a bad idea, but because it has 512MB of RAM (granted shared with GPU) and 3 cores there was ample spare capacity to do this.  You will notice however that the blade opens VERY slowly and at a low framerate when in-game.  The fact is its doubtful there would be enough spare CPU capacity on the X-Box to add this feature on top of the existing core OS and keep everything running as if it wasnt there - it simply would cause unexpected anomolies in games and probably stop some of them running at all.

So basically the original idea of having the blade coded into certain homebrew (giving the impression that its the same blade running but in fact its a completely different piece of code per homebrew app) is perfectly possible albeit time consuming when the time would be better spent optimising the emulators than arsing around with the GUI.

[netdroid9]

We could always fiddle with virtual memory and the like, but yeah, it's time better spent on other things .