X2 5031 Bug Reports

Status
Not open for further replies.
Xecuter

Xecuter

Staff member
Top TX Brass
Dec 6, 2002
11,468
128
Asia
team-xecuter.com
Post all bugs here. (That does not mean ask questions in here it means POST REAL BUGS ONLY !)

REPEAT DO NOT ASK QUESTIONS IN THIS THREAD - AND A FRAG IS NOT A BUG !!!!

Read the xecuter.nfo before posting questions already answered !

Make sure you read lba48.txt

ALWAYS USE THE INCLUDED INI FILE AS THERE MAY BE NEW CHANGES

These are recommended x2 config apps
http://home.alltel.net/nghtshd/x2ool.html
http://x-projects.xbox-scene.com
http://www.teamxecuter.com/forums/showthread.php?t=30456

NOTE:
- YOU CHANGE ALL THE BIOS SETTINGS VIA THE INI FILE
- THERE IS NO APP OR OS ON SCREEN - THAT WILL BE A SEPERATE XBE LATER
- THIS BIOS WILL WORK ON ANY MODCHIP THAT CAN BOOT A 512k BIOS
- THIS IS A BETA BIOS THERE WILL BE BUGS - DO NOT ASK IN HERE FOR HELP - POST BUGS ONLY - DO NOT IGNORE THIS !!!

[5031]
- fixed: x2logo.bmp display bugs solved
- fixed: the wild rings game was not booting again ... fixed now (this game blows)
- fixed: made dash pathes a litte more tolerable, drive character is no longer case sensitive
- note: LedColor also supports other values than the ones listed - check out nghtshd's x2ool for more versatile led modes!

[5030 BETA]
- added: now can add full paths to dashboards in x2config.ini (e.g. c:dashes\evox\evoxdash.xbe), 255 chars max
- added: x2config.ini now first searched on F: and, if not found, on E: - if again not found then defaults are used
- added: dvd boot xbe filename can be changed now, 16 chars max for this setting - change boot xbe to e.g. "boot.xbe"
- fixed: fan speed setting
- fixed: eject led color settings
- fixed: x logo colors
- fixed: wireframe flubber setting
- note: if you have no .ini on hdd then the bios runs in default mode and default mode is NO DEBUG therefore it won't boot to xshell even if xdk installed!
- note: setting "xLogoBackgroundColor" is for x logo background only - no setting for flubber scene bg color (yet)
- note: always use the latest (included) .ini file!

[5029]
- fixed: incorrect detection of lba48 parameters if bios not flashed to bank 0 (lame bug - sorry)
- fixed: all games should boot again (quite handy workaround ;))
- fixed: default settings (e.g. wrong colors) working again if no .ini file present

[5028 GOLD]
- fixed: fan no longer defaults to 0 when no .ini found
- fixed: led color defaults now to green when no .ini found

[5027 BETA - NON PUBLIC]
- fixed: halo/halo2 now booting again
- fixed: no longer interferes with x3 mods (eeprom stored settings)
- fixed: now loads x2logo.bmp from E: instead of x3logo.bmp
- fixed: now correctly describes boot partitions in x2config.ini
- fixed: wild rings (jap) now boots - fixed some weird (and rare!) bug that ****ed up the first section header of an XBE
- added: partition table on disk is now used if found on hdd (auto-detection, .ini parameter removed)
- added: hdd partitioning mode can be set by setting byte 0x1b04 in bios.bin (get possible values from lba48.txt file)
 
X

XBoxgeek

Junior Member
Dec 8, 2003
18
0
XBMC still does not load if "startDebug = 1" (5028 worked okay). Please see my post in the "X2 5030 Bug Reports" thread for full details.
 
O

orakle

Junior Member
Apr 18, 2005
16
0
X, the bug from last night seems to be fixed now. I have no problems booting up with this config:

dash1Name = f:dash\unleashx\unleashx.xbe
dash2Name = f:dash\evox\evoxdash.xbe
dash3Name = f:dash\avalaunch\avalaunch.xbe
dash4Name = f:apps\xbmc\default.xbe
dash5Name = c:xboxdash.xbe

thanks for the fix, I really appreciate your work on this bios.
 
R

RocafellaSqualie

Full Member
Jun 30, 2004
40
0
Delaware, USA
Everything is perfect except for Xbox Media Center. At startup, it sometimes crashes when the BIOS is in normal mode, but when in Debug Mode, my Power/Eject flashes Red & Green (In my case Blue & White). Tested again using X2CL 5028 and EvolutionX M8 1.6, it works perfectly, no crashing.

Xbox NTSC 1.6
SmartXX v2
160GB Seagate Barracuda
Xbox Media Center Dashboard
 
M

majesticjester

Noob Account
Mar 12, 2005
9
0
pal xbox version 1.6 with xecuter 2.6ce
5031 on bank 2

enter the matrix pal (orginal) will not run propley from dvd with chip enabled (no video just sound)
ie the dvd is in the xbox and you turn it on to play game

it will play if you boot to evox dash and then choose to play the game off dvd, it also plays with the chip disabled
 
Xecuter

Xecuter

Staff member
Top TX Brass
Dec 6, 2002
11,468
128
Asia
team-xecuter.com
XBoxgeek said:
XBMC still does not load if "startDebug = 1" (5028 worked okay). Please see my post in the "X2 5030 Bug Reports" thread for full details.
Click to expand...
i tested this. nothing wrong at all - can boot debug on latest xbmc cvs build - tested on v1.0 and v1.6
 
Xecuter

Xecuter

Staff member
Top TX Brass
Dec 6, 2002
11,468
128
Asia
team-xecuter.com
RocafellaSqualie said:
Everything is perfect except for Xbox Media Center. At startup, it sometimes crashes when the BIOS is in normal mode, but when in Debug Mode, my Power/Eject flashes Red & Green (In my case Blue & White). Tested again using X2CL 5028 and EvolutionX M8 1.6, it works perfectly, no crashing.

Xbox NTSC 1.6
SmartXX v2
160GB Seagate Barracuda
Xbox Media Center Dashboard
Click to expand...
i have spoken to absolutley no one who can reproduce this.
 
Xecuter

Xecuter

Staff member
Top TX Brass
Dec 6, 2002
11,468
128
Asia
team-xecuter.com
ok, you CANT run xbmc.xbe off f:\apps\xmbc (as a dashboard), check the xbmc.ini file:

<!-- When using XBMC as dashboard, define home directory here !-->
<!-- and move the XBMC xbe plus this xml config file to C:\ !-->
<!-- Example: <home>E:\Apps\XBMC\</home> !-->

<home>f:\apps\xbmc</home>

so if you do so (as told here) then it works fine... so this is no bug, xbmc xbe just cant be run as boot-dash from e: or f: drive...

and, regarding the dash paths issue, here my test results

dash1Name = f:dashboards\avalaunch\avalaunch.xbe
dash2Name = c:xbmc.xbe
=> boots to avalaunch

dash1Name = F:dashboards\avalaunch\avalaunch.xbe
dash2Name = c:xbmc.xbe
=> boots avalaunch

dash1Name = C:xbmc.xbe
dash2Name = f:dashboards\avalaunch\avalaunch.xbe
=> boots XBMC

dash1Name = c:xbmc.xbe
dash2Name = F:dashboards\avalaunch\avalaunch.xbe

=> boots XBMC

so, wtf? works fine here, there MUST have 5030 on the mod banks! sorry, cant do more anything to fix a bug when there is no bug
 
K

Klutsh

1
VIP Member
Nov 9, 2004
233
0
South of the Humber, UK
www.klutsh.com
It can however be run from c:\xbmc\xbmc.xbe

with the tag <home>-</home>

and all the other files in the xbmc dir as if it was an app.

This is how I run my xbox.

From my x2config.ini dash1Name = c:xbmc\xbmc.xbe
 
R

RocafellaSqualie

Full Member
Jun 30, 2004
40
0
Delaware, USA
Xecuter said:
ok, you CANT run xbmc.xbe off f:\apps\xmbc (as a dashboard), check the xbmc.ini file:

<!-- When using XBMC as dashboard, define home directory here !-->
<!-- and move the XBMC xbe plus this xml config file to C:\ !-->
<!-- Example: <home>E:\Apps\XBMC\</home> !-->

<home>f:\apps\xbmc</home>

so if you do so (as told here) then it works fine... so this is no bug, xbmc xbe just cant be run as boot-dash from e: or f: drive...

and, regarding the dash paths issue, here my test results

dash1Name = f:dashboards\avalaunch\avalaunch.xbe
dash2Name = c:xbmc.xbe
=> boots to avalaunch

dash1Name = F:dashboards\avalaunch\avalaunch.xbe
dash2Name = c:xbmc.xbe
=> boots avalaunch

dash1Name = C:xbmc.xbe
dash2Name = f:dashboards\avalaunch\avalaunch.xbe
=> boots XBMC

dash1Name = c:xbmc.xbe
dash2Name = F:dashboards\avalaunch\avalaunch.xbe

=> boots XBMC

so, wtf? works fine here, there MUST have 5030 on the mod banks! sorry, cant do more anything to fix a bug when there is no bug
Click to expand...
I'm confused on what you're explaining :lol:

Are you saying that XBMC's xbe can't be ran off the F: Partition, only C: or E:? I have mines set up like this (xboxmediacenter.xbe & xboxmediacenter.xml on the root of F:)
<!-- When using XBMC as dashboard, define home directory here !-->
<!-- and move the XBMC xbe plus this xml config file to C:\ !-->
<!-- Example: <home>E:\Apps\XBMC\</home> !-->

<home>F:\Dashboards\Xbox Media Center\</home>
Click to expand...
I have my x2config.ini & x2debug.ini (2 separate BIOS, one hex edited to look for x2debug.ini) set as:
dash1Name = f:xboxmediacenter.xbe
dash2Name = f:dashboards\unleashx\default.xbe
dash3Name = f:dashboards\avalaunch\default.xbe
dash4Name = f:dashboards\evolutionx\default.xbe
dash5Name = c:xboxdash.xbe
Click to expand...
I've never used X2CL 5030 on my SmartXX so i'm compiling a new build now to see if it's at fault with the build itself

-RocSqualie
 
X

XBoxgeek

Junior Member
Dec 8, 2003
18
0
I don't boot xbmc as a dash. I load it as an app.

Not sure whats up but as I said x2 5028, IND 5003 & TATX all load xbmc in debug. It's not realy an issue for me so no worries.

As a side note We finaly got our XIG 2app to grab Halo2 screen shots on a 64MB xbox with the IND bios. Gonna check the x2 5031 in a mo.

*** Edit ***
No joy with Halo2 nad 5031. Now before you say HALO2 DOES NOT WORK in debug mode. Yes it does :)

 
Last edited:
B

Big_Whoopin

VIP Member
Jan 29, 2004
811
0
SE Pennsylvania, USA
Xecuter said:
...and, regarding the dash paths issue, here my test results

dash1Name = f:dashboards\avalaunch\avalaunch.xbe
dash2Name = c:xbmc.xbe
=> boots to avalaunch

dash1Name = F:dashboards\avalaunch\avalaunch.xbe
dash2Name = c:xbmc.xbe
=> boots avalaunch

dash1Name = C:xbmc.xbe
dash2Name = f:dashboards\avalaunch\avalaunch.xbe
=> boots XBMC

dash1Name = c:xbmc.xbe
dash2Name = F:dashboards\avalaunch\avalaunch.xbe

=> boots XBMC

so, wtf? works fine here, there MUST have 5030 on the mod banks! sorry, cant do more anything to fix a bug when there is no bug
Click to expand...
I don't know what it is either, but it's happening on my box. To more or less start from scratch I again downloaded the rar of 5031, extracted the bios and ftp'd it to my box. Flashed banks 1 and 2 with FlashX (sucessfully, 13 seconds I think) and rebooted. Loaded Avalaunch and EvoX, both are reporting a 5031 kernel. (1.0.5031.1 in Ava and 1.00.5031.01 in EvoX) With this config-

dash1Name = E:dashes\avalaunch.xbe
dash2Name = e:dashes\evoxdash.xbe
dash3Name = e:dashes\nuthin.xbe
dash4Name = e:dashes\nuthin.xbe
dash5Name = c:xboxdash.xbe

I get EvoX. With this config-

dash1Name = e:dashes\avalaunch.xbe
dash2Name = e:dashes\evoxdash.xbe
dash3Name = e:dashes\nuthin.xbe
dash4Name = e:dashes\nuthin.xbe
dash5Name = c:xboxdash.xbe

I get Avalaunch. Sorry man, I'm srugging my shoulders with a WTF as well. 1.0 Xbox with a X2.3 lite, 5031 in 1/2, cromwell 3.03 in 3/4, stock HDD with a (now) MS virgin C:.

One thing that I do find is odd is that EvoX reports the hash as e36997f65e656de0d7dfd7197b699490. This does not match any of the hashes you listed in the MD5 post, or anything in the X2BM 2.3 list. Pulling a hash from the file on my PC gets me 7007ccc64406042f16c5b2dc7e9c7b9d, matching 5031_old in your post. If I ftp the bios back down from my box it still comes up as the correct 7007ccc64406042f16c5b2dc7e9c7b9d. Something whack in my flash or does EvoX calculate MD5s differently?

If I need to take this elsewhere you're welcome to tell me where, just don't get too creative. :D I've attached the config I'm using for reference. The only thing I've changed when testing is the case of the drive letter for dash1Name.

-Whoopin'
 
Last edited:
Xecuter

Xecuter

Staff member
Top TX Brass
Dec 6, 2002
11,468
128
Asia
team-xecuter.com
there may be a bug with

; stop bios from booting DVDs (straight to dash even with a disc inserted)
disableCdromBoot = 1

its possible that some users may not be able to boot to any dash or any unsignd xbe - so mke sure this option is set to 0 until we take a better look at it
 
Xecuter

Xecuter

Staff member
Top TX Brass
Dec 6, 2002
11,468
128
Asia
team-xecuter.com
XBoxgeek said:
I don't boot xbmc as a dash. I load it as an app.

Not sure whats up but as I said x2 5028, IND 5003 & TATX all load xbmc in debug. It's not realy an issue for me so no worries.

As a side note We finaly got our XIG 2app to grab Halo2 screen shots on a 64MB xbox with the IND bios. Gonna check the x2 5031 in a mo.

*** Edit ***
No joy with Halo2 nad 5031. Now before you say HALO2 DOES NOT WORK in debug mode. Yes it does :)

Click to expand...
why dont you email the bios that works and also the apps / method usd - so we can add this to X2 / X3 bios's - cus we cant get our bios's to boot halo or halo2 in our debug mode as we use we COMPLETE debug which takes up too much memory - or did you do something funky ? id like to know

use k3rn3ls gmail account

[email protected]

also i had 9 ppl in my beta test channel boot xbmc in debug mode using 5031 - not one single problem so i hve no clue what your problem is.
 
Xecuter

Xecuter

Staff member
Top TX Brass
Dec 6, 2002
11,468
128
Asia
team-xecuter.com
RocafellaSqualie said:
I'm confused on what you're explaining :lol:

Are you saying that XBMC's xbe can't be ran off the F: Partition, only C: or E:? I have mines set up like this (xboxmediacenter.xbe & xboxmediacenter.xml on the root of F:)


I have my x2config.ini & x2debug.ini (2 separate BIOS, one hex edited to look for x2debug.ini) set as:


I've never used X2CL 5030 on my SmartXX so i'm compiling a new build now to see if it's at fault with the build itself

-RocSqualie
Click to expand...
how can you be confused when it tells you exactley what to do in th xbmc.xml file ???

dit the home tags to the DIR where you hve all your xbmc sh*t then put the xbmc.xbe and xbmc.xml to the C: drive and point the dash to c:xbmc.xbe

thats not xecuter telling you to do tht - thats XBMC instructions telling you to do that.

if you hv any further questions tke it to the main forum - not in here thanks.
 
R

rdleader

Noob Account
Aug 17, 2004
5
0
USA
I am not sure if this is a bug but yesterday I tried to Load up Return to castle Wolfenstein and the first screen will show up then it just sits at a black screen and does nothing. I have a Version 1.1 XBOX with the 5031XCL. My ini file is sitting on the E: and the game worked fine prevoiusly with the x2 4981 BIOS.
 
Status
Not open for further replies.