2.6 CE works->disable chip error code->enable chip FRAG

[leon222]

Odd problem here -- looking for help.

I have a 2.6 CE on a 1.6 Xbox (wire install). The chip worked fine, flashed the bios to the latest X2, installed evox, etc. Renamed the msdashboard (which explains the error when trying to boot from the vanilla bios), and evox boots automatically.

I put in my first game today to play from evox and couldn't get the msdashboard to load -- I probably hosed something up and can fix that. However, when I enabled the chip and tried to boot back into evox, I now frag (green red).

Any idea what's up?

 

[Fantmx]

Why did you rename the original Microsoft Dashboard file? There is no need to do that.

When you say the latest X2, what do you mean? Take a look at the switches. It may be the connection between the switches and then cables, or one of the actual switches.

 

[leon222]

Yeah - I realized later that I didn't need to rename the dashboard. I did it since I didn't modify my bios before I flashed. Like I said, I'll fix that later.

I was simply refering to the latest version of the x2 bios when I said X2.

I think this may be a switch problem. I fiddled with them a bit and it 'fixed' it. No really happy with the solution, but I guess as long as it doesn't get worse I should be okay...

Thanks!

 

[Big_Whoopin]

I believe there is only one reason to modify the current X2 BIOS (current is X2CL 5035) and that is if you need to adjust the LBA48 settings to change how partitions F and G would be created. Everything else is controlled in the x2config.ini file. If you are not running this BIOS I would recommend you get it.

-Whoopin'