Print

[RiceCake]

The more capability to recover from a hosed system, the better...

Pain in the ass to start swapping parts out...

[BenJeremy]

QUOTE (RiceCake @ Aug 25 2003, 11:22 AM)

The more capability to recover from a hosed system, the better... Pain in the ass to start swapping parts out...

Ah yes... EEPROM protection would also be equally nice, too. Another page that would be nice to steal from the Debug BIOSes.

[Xeero]

QUOTE (BenJeremy @ Aug 25 2003, 12:11 PM)

QUOTE (RiceCake @ Aug 25 2003, 11:22 AM) The more capability to recover from a hosed system, the better... Pain in the ass to start swapping parts out... Ah yes... EEPROM protection would also be equally nice, too. Another page that would be nice to steal from the Debug BIOSes.

Can a debug BIOS boot with a trashed EEPROM?

[BenJeremy]

QUOTE (Xeero @ Aug 25 2003, 12:17 PM)

QUOTE (BenJeremy @ Aug 25 2003, 12:11 PM) QUOTE (RiceCake @ Aug 25 2003, 11:22 AM) The more capability to recover from a hosed system, the better... Pain in the ass to start swapping parts out... Ah yes... EEPROM protection would also be equally nice, too. Another page that would be nice to steal from the Debug BIOSes. Can a debug BIOS boot with a trashed EEPROM?

Yes, it can. Seems like a simple thing.... downside is that if the HD password is trashed, you can't access the drive, but really, not a big deal, if you ask me (same problem on that count, no matter what, if the EEPROM is trashed - that's what EEPROM backups are for).

Looking back, I should have said "Trashed EEPROM protection"  

Right now, I have to recommend people boot using Evo-X D.6 (if they are installing a new HD, or lost their dashfiles) or the Debug BIOs (trashed EEPROM), because X2 handles neither situation gracefully - while doing everything else very nicely indeed.

[Xeero]

QUOTE (BenJeremy @ Aug 25 2003, 01:04 PM)

QUOTE (Xeero @ Aug 25 2003, 12:17 PM) Can a debug BIOS boot with a trashed EEPROM? Yes, it can. Seems like a simple thing.... downside is that if the HD password is trashed, you can't access the drive, but really, not a big deal, if you ask me (same problem on that count, no matter what, if the EEPROM is trashed - that's what EEPROM backups are for). Looking back, I should have said "Trashed EEPROM protection"   Right now, I have to recommend people boot using Evo-X D.6 (if they are installing a new HD, or lost their dashfiles) or the Debug BIOs (trashed EEPROM), because X2 handles neither situation gracefully - while doing everything else very nicely indeed.

Really?  I didn't know that.  I've been really lazy about getting a TA debug BIOS on my Chameleon (I had it on my X2 Pro), but it looks like I'm going to have to as a precaution.  I'd pick up an X2.2 Pro for the benefit of the fancy switches, but I'd rather wait until the next batch of chips (X3, X-B.I.T.) get a chance to flex their muscles before making that investment.

Also, what part of the missing-dashboard-files situation does the D.6 BIOS handle that an X2 BIOS can't?  To my recollection, if you are missing dashboard files but booting to a disc, it won't matter because it will check the disc's default.xbe before checking the HD for the required files; both BIOSes will do this.  If the disc is not bootable it will attempt to boot the dashboard with a dirty-disc error, and if files are missing you get an Error 16; again this is the same with both BIOS releases.  

Am I incorrect in my understanding of this?  Will D.6 boot a disc's default.xbe without Settings_Clock.xip while X2 won't?  I guess I'm confused.

[juan23]

I would totally love to see a boot sequence, so u can choose from dvd or HDD.

reason why if u have a toast hdd, boot the xbox via dvd so u can ftp over to xbox and just maybe be able to save a few files on it.  this would be a huge help.

[BenJeremy]

QUOTE (Xeero @ Aug 25 2003, 01:24 PM)

QUOTE (BenJeremy @ Aug 25 2003, 01:04 PM) QUOTE (Xeero @ Aug 25 2003, 12:17 PM) Can a debug BIOS boot with a trashed EEPROM? Yes, it can. Seems like a simple thing.... downside is that if the HD password is trashed, you can't access the drive, but really, not a big deal, if you ask me (same problem on that count, no matter what, if the EEPROM is trashed - that's what EEPROM backups are for). Looking back, I should have said "Trashed EEPROM protection"   Right now, I have to recommend people boot using Evo-X D.6 (if they are installing a new HD, or lost their dashfiles) or the Debug BIOs (trashed EEPROM), because X2 handles neither situation gracefully - while doing everything else very nicely indeed. Really?  I didn't know that.  I've been really lazy about getting a TA debug BIOS on my Chameleon (I had it on my X2 Pro), but it looks like I'm going to have to as a precaution.  I'd pick up an X2.2 Pro for the benefit of the fancy switches, but I'd rather wait until the next batch of chips (X3, X-B.I.T.) get a chance to flex their muscles before making that investment.

Yes, the Debug BIOS boots with a hosed EEPROM (I inadvertantly confirmed this    myself as well)

QUOTE

Also, what part of the missing-dashboard-files situation does the D.6 BIOS handle that an X2 BIOS can't?  To my recollection, if you are missing dashboard files but booting to a disc, it won't matter because it will check the disc's default.xbe before checking the HD for the required files; both BIOSes will do this.  If the disc is not bootable it will attempt to boot the dashboard with a dirty-disc error, and if files are missing you get an Error 16; again this is the same with both BIOS releases.

That's what you'd think.... but I've seen countless reports of people unable to boot their Xboxes with X2 BIOSes when the dash files got hosed or when changing to a new hard drive. Why? I'm not entirely sure, but I think the X2 BIOS does a few things to the HD before it attempts to boot the DVD (we know it checks for an IGR file, for example). All I know is that my advice of booting D.6 works every time for these folks.

QUOTE

Am I incorrect in my understanding of this?  Will D.6 boot a disc's default.xbe without Settings_Clock.xip while X2 won't?  I guess I'm confused.

Like I said.... don't know why it is. I guess Team Xecuter may have an idea... but they haven't fixed it yet. I'm sure once they recognize it may not be a few isolated cases, they'll look into it and fix it once and for all.

[Drexon]

QUOTE (feflicker @ Aug 23 2003, 09:13 PM)

QUOTE Hardly anybody uses the Evo-X IGR, due to compatibility issues, and the X2 BIOSes have IGR (they were first, you know). We were thinking along the lines of Xeero. We should add a x2bios.xml file somewhere and be able to specify bios options, such as hot-keys to launch xbe files, similar to how IGR mapping works in the EvoX dash.

Soo, does this mean I influenced that? With my IGA thing? =)

[janten]

1. no more 137 GB-Limit
2. built-in FTP, which you can access while playing
3. built-in dashboard (for faster IGR)
4. capability of loading plugins from HDD

[PlastiKK_]

QUOTE (janten @ Aug 28 2003, 07:03 AM)

3. built-in dashboard (for faster IGR)

Jesus, how fast do you want it?  You already get back to the dash in what, 3 seconds?

[Xeero]

QUOTE (PlastiKK_ @ Aug 28 2003, 08:40 AM)

QUOTE (janten @ Aug 28 2003, 07:03 AM) 3. built-in dashboard (for faster IGR) Jesus, how fast do you want it?  You already get back to the dash in what, 3 seconds?

Though I think it is of a lower priority than many other features, I guess I can understand why some people would want an IGR built into the kernel.  However, I agree with PlastiKK_ - faster IGR is probably not what's going to be the incentive that drives one of the dev teams to include it.  The difference in load times would be negligible.

[heinrich]

QUOTE (billybobz0r @ Aug 28 2003, 07:50 AM)

So if FTP is possible in bios maybe there could also be support to have XNS shares, so we can boot games from pc ?

No, see the FTP is an xbe, inside of the bios, to do what you want, an xbe would have to launch, transfer the entire game to the hd, and then boot the game, which would probably be *possible*, but not likely..  I think i can safely say that you will never be able to 'stream games' over a network.

[Pherf]

I'm not sure if this is a bios hack or not, or even if its possible, but 1080i support for DVD's would be incredible

[Tover]

Ok changed my mind, I would like a bios that would execute a list of programs off the hard drive.  

I thought I read somewhere, that someone had fixed the bios to load a launcher program that would read a list off the hardrive.  The main reason is I don't want to change the msdash, but would like to be able to pull up a menu and run DVDX, XBMP, Ftp server, or the like.  The launch feature has several possibilities and am looking forward to see what they do.  Just hope they don't go past the 1mb mark.

[PlastiKK_]

QUOTE (Tover @ Sep 3 2003, 11:23 AM)

Ok changed my mind, I would like a bios that would execute a list of programs off the hard drive.   I thought I read somewhere, that someone had fixed the bios to load a launcher program that would read a list off the hardrive.  The main reason is I don't want to change the msdash, but would like to be able to pull up a menu and run DVDX, XBMP, Ftp server, or the like.  The launch feature has several possibilities and am looking forward to see what they do.  Just hope they don't go past the 1mb mark.

That would be cool to have a list like that.  And I also hope they don't break the 1mb barrier.  If they do they're bastards.

I do believe that there is something similar to what you're talking about.  It works with an Xecuter BIOS.  When you press A one program loads up, when B is pressed, another, X, Y, ect.  I believe there's a total of 8 possible buttons to press.  Then if no button is pressed then the dash loads up.  You can set the buttons to any .xbe file you want and then the dash can be set to what you want too.

This way you could have the MS dash and also load up the program you want with the push of a button.