Print

[HSDEMONZ]

There are no issues going on LIVE with the XENIUM.  Just boot the stock BIOS.. and play LIVE.

[pir8penguin]

I'm not asking for trade secrets, or even a psueod-code example, but I'd love to know more about what the chip does when you select the factory bios? IMO, it would disable itself (which would obviously only be a next-time disable) and reload. in this case, it's as though the chip isn't there when you load the factory bios (else how would it get to the factory bios?? ).

i hate the XeniumOS look. I'd want either invisible (black screen) when select time is 0sec, or the ability to make my OWN splash. otherwise, it's not really customized how i like it. isn't that the point of the scene to begin with?

[notkevin]

QUOTE (djlex @ Jan 23 2004, 08:26 AM)

The second concern that I have relates to XBL.  I haven;t seen a whole lot of detail reagarding the nuts and bolts of XOS, but I can say that I'm not confident that XBL or update games will not eventually be able to see it.  I much rather the option to completely remove/unplug/or disable the mod before logging into XBL.   I suppose I will attempt to add a D0 toggle switch.  If not, I will be uninstalling my Xenium (at least for a while until the dust settles) when I want to get on XBL.  I want my Xbox to be as close to factory/unmodded as possible when I connect.  As I read it now, there is no way to disable XOS with the chip installed and powered.

From what I can gather about the XBL situation, XBL checks the checksum of the bios to tell if a hacked bios is being used, it does not check for the existance of a mod chip. Therefor if you boot with the original bios (as selected from XOS) then you won't have a problem. I have not had any problems with XBL and the Xenium.