Not Using the new X2 Bios

[umpa]

After a sucsessful flash to 5031, and several boots, I decided to try and customize the .ini file.

I used the x2ool b2 to do it. I did not change the boot order or anything serious, I simply turnd off the animation and made the LED go red. The program uploaded the .ini for me.

When I re-booted the bios, the machine fragged with a scrambled screen and an error 13. I was able to boot from CD so I used Slayers 2.6 and re-flashed the chip.

Now my point is this :-

The bios is unstable, it would seem you can do some real damage with just a config file, and there seems to be no way to bypass the ini file at startup with a simple button press. (if there is I have not seen it documented).

So for the power the new X2 bios gives me (not a lot) - I'll wait till its safer.

Perhaps all the x2 bios should be 1meg with flashbios built into the second bank as standard that would give ppl a recovery if needed.

I know if I mess with this bios again - thats what I'll do.

 

[Xecuter]

there is nothing wrong with the bios. there is something wrong with how you use it

if i have to idiot proof it any more I would have to drive to everyones house to install it

my advice to you is this do not use our bios's. if we have to include flashbios in a 1mb file as a way for you to recover if you have a problem then you shouldnt be toying with this kind of stuff.

PS wtf are you even touching this bios for if you have an X3 ?? this bios is no where near as feature packed as an X3 bios is.

you say you cant recover and you have an X3 mod ?

another PS - if there was a problem with the ini file - maybe you should be sending msg's to the guys that make the apps - they are 3rd party tools. My guess is it was edited badly (older version ini with newer version bios - you are warned a dozen times to watch out for this)

plus you said error 13 is major damage - dude thats a bullshit user error - and the bios was doing its job - it let you boot to slayers and solve whatever issue you had

the bios is stable. its rock solid. your post is scaremongering and balony.

 

[Klutsh]

I have to agree, error 13 can be caused by 2 different thing's
1 a corrupt/incorrect x2config.ini
2 Dashboard is missing.

From what you have wrote it is 100% the wrong ini file.
If you noticed it's version 'x2ool b2' well, thats not made for the 5031 bios for a start.
X2ool only started to support 5031 in b3.
Next time before you complain make sure it is not 100% user error, in this case it is.

You cant blame Xecuter for your lack of reading.

For your info x2 Config Maker v2.5 and above or X2ool v1.0.1.b3 and above work with the newer style ini's.

 

[Big_Whoopin]

In umpa's defense, there is no mention of compatible bios versions on the x2ool web site until the 1.0.1b3 release notes...

BUT

*I haven't checked any readme's that may be included with x2ool. Maybe it is mentioned in there?
*Given how many places I have seen mentioned warnings to use the correct ini file with each bios, I don't trust the output of the programs until I've compared it to the ini that is included with the bios. (Sorry Klutsh, I even do this with your proggie too.) There's been 4 official or unofficial releases in the last week I think? Can you expect every 3rd party to keep that up to date?

It's like, measure twice, cut once. Try not to take your fingers off.

-Whoopin'

 

[umpa]

there is nothing wrong with the bios. there is something wrong with how you use it

if i have to idiot proof it any more I would have to drive to everyones house to install it

my advice to you is this do not use our bios's. if we have to include flashbios in a 1mb file as a way for you to recover if you have a problem then you shouldnt be toying with this kind of stuff.

PS wtf are you even touching this bios for if you have an X3 ?? this bios is no where near as feature packed as an X3 bios is.

you say you cant recover and you have an X3 mod ?

another PS - if there was a problem with the ini file - maybe you should be sending msg's to the guys that make the apps - they are 3rd party tools. My guess is it was edited badly (older version ini with newer version bios - you are warned a dozen times to watch out for this)

plus you said error 13 is major damage - dude thats a bullshit user error - and the bios was doing its job - it let you boot to slayers and solve whatever issue you had

the bios is stable. its rock solid. your post is scaremongering and balony.

I have an X2 as well - just because I dont mention it does not mean I dont have one ! get your head out your arse and think for a second!

I never said error 13 is major damage - I said one could do major damage with a poorly made .ini file, this sir is a fact plain and simple. You have not made the the bios able to boot failsafe, thats your fault not mine.

 

[umpa]

I have to agree, error 13 can be caused by 2 different thing's
1 a corrupt/incorrect x2config.ini
2 Dashboard is missing.

From what you have wrote it is 100% the wrong ini file.
If you noticed it's version 'x2ool b2' well, thats not made for the 5031 bios for a start.
X2ool only started to support 5031 in b3.
Next time before you complain make sure it is not 100% user error, in this case it is.

You cant blame Xecuter for your lack of reading.

For your info x2 Config Maker v2.5 and above or X2ool v1.0.1.b3 and above work with the newer style ini's.

What I say is still valid - a simple .ini file can make the xbox unusable. Thats just plain stupid. Mistakes happen and the x2 is not a chip that is forgiving at the best of time - but to produce a bios where getting a simple setting wrong make the unit not boot up is mad.

Can you just imagine what would happen if I changed the dvd boot part ? I would have had a brick.

 

[umpa]

To executer –
I see your upset, but the fact is, I was not criticising your bios or you at that time, I was simply making a statement.

It’s a shame you flew off on one like a child. for shame on you!

 

[Xecuter]

and your statement was a crock

saying we should include flashbios - you have any clu how noob that sounds.

i am shocked at how many noobs have come out of the woodwork since I released this bios - i kinda remember why I stoppd now.

you said the bios was unbstable - not once did you think or suggest that perhaps it ws the 3rd party ini file creator that was unstable

next time you post get your facts straight and take your head out of your ass before making accusations and scaremongering that your mistakes or someone elses are our mistakes

there i just released a new version for ppl that fcuk up their releases and dont know how to recover properly when they mess something up or check it properly.

thread closed - a waste of my time - again.

 

[Klutsh]

I'm glad to see you didnt take offence to my post, as none was intended.

Yes I do see your point, but for your personal use you would not have 'a brick', you have an X3, capable of booting flash bios in cases such as this.

There is also a last ditch recovery option of turnng the chip off and booting evox via a save-game hack, allowing you to repair or remove the x2config.ini file.

The only people who would struggle to recover are the ones that flash this to a TSOP, and to be honest if they are doing that then they should have the common sense to have unlocked the HDD before attempting a flash of a new bios, or adding a new config file in this case, that way if the config file is wrong/dead they would just need the temp usage of another xbox to remove the config file from the hdd.