Print

[d0wnlab]

Do any other XBEs work from OpenXDK?  Check with my wolf3d port, found:

http://th0mas.xbox-s...wolf3d-xbox.zip

Also, could you do a "make clean" and then a full rebuild of your app, and post the build output here?

Thanks,
Tom

[mokda]

Hi Superogue,

I had a *similar* problem recently and it was due to openxdk not supporting my hardware/video setup.  When i added that case to the video settings everything was peachy.

When your xbox crashes, does the light on the front flash?  

If so, I'll post the steps openxdkman had me do to troubleshoot the problem I had.

I highly recommend you get cygwin and compile the CVS version of openxdk.  The controller stability is a sanity saver.

If you really don't want cygwin though, I'll host my bins on my site (and PM the link to you)....let me know.

[superogue]

no flashing light i'm afraid
other people have the same problem here? its not just my xbe.

i wanted to  attach the xbe i compiled (the comingsoon example). so somebody here can check if it works on their box. but my site is down atm (its on my brothers server).

[superogue]

i tried to discover which bios i have installed. evox dashboard won't detect my bios, and i can't flash either (cannot write). i have it installed for a few years now, but i can't remember the model. i also cannot open the box since i don't own those special screwdrivers.

are there any tools that allow me to see which bios i have?

[d0wnlab]

I will rebuild the wolf3d XBE against the latest openxdk cvs and PM you a URL to download it (the update will also be included in the next actual wolf3d update I do, along with an update to the controller code and support for the registered version.. if I can find a copy of the data files).  Then you can try that and see if it works.

Other than that I have no clue what's wrong :/

Cheers,
Tom

[d0wnlab]

QUOTE(superogue @ Aug 30 2006, 05:51 PM)

no pm received.

Sorry, I forgot to add "when I'm back in the same city as my xbox", which will be post-labor day.  If anyone else can help before then feel free .

[openxdkman]

If you try to display pixels (see previous post) but a nasty reboot occurs preventing you from viewing pixels, you can force a hang (I think) by just doing a nasty divide by zero, just after last pixel drawing (and then, progressively do it earlier and earlier until xbox hangs instead of rebooting)

{
int z=0;
z=1/z;
}

[superogue]

i'm afraid the example won't boot at all even an empty project with just a reset commando.
seems it just won't go to the program's entry point.

if anyone knows a way to detect my modchip/bios version without opening the xbox let me know, this way i can let you guys know the type of chip that it doesn't work on (which could benefit the openxdk development). are there a lot more chips/bioses that won't work??? evox dashboard tells me 'uknown bios' on the settings page. all non openxdk apps work fine though.

[superogue]

in the meanwhile, is there any chance the CXBC emu will work with any of the examples?
i tried them (testVBL, my own and wolf3d), but all of them crash (causing emu to crash)
some original XBE's start but crash (not causing emu to crash). maybe this is because they have a seperate Media dir (xpong, etc.)

[Carcharius]

Sounds to me like it might be a chip/bios issue.

If you've got an early chip (Xtender or Enigmah for example), then it's possible the bios doesn't support booting of debug flagged xbe's.

I can't remember exactly what flags an openxdk xbe is set with by default. But you could try running xbepatch against the xbe's in question (to flag them as retail) and see if that helps.

Using MingW isn't a problem in itself - I've done openxdk development using it with no problems whatsoever.

Carcharius

[fghjj]

CXBX emulates API's and not hardware. For example it will hook Direct3D calls in the XBE and redirect them to the normal Windows DirectX runtime. It's only meant to emulate programs built with XDK.

[openxdkman]

someone able to produce a xbe working on his 'strange' bios version xbox (or dashboard version?)
should create the smallest xbe possible and then allow us to download it

this way we can try to compare binary

(also, I understand a bios version may affects which xbe can be launched when xbox boots, but does it really affect a xbe a dashboard chain executes? If not, they he should just try several dashboard versions)

[grovespaz]

Can you upload the XBE's you have compiled?

Hell, you can upload for free at rapidshare.de.

[superogue]

QUOTE

=================================
 XBE HEADER
=================================
MAGIC           : XBEH
SIGNATURE       : -
Base Address    : 00010000
Header Size     : 2316
XBE Size        : 726976
XBE Header Size : 376
Timestamp       : 3D2F5AC7
Cert.Offset     : 00010178
Section Count   : 00000009
Section Offset  : 00010348
Init Flags      : 00000000
Entrypoint      : 0002E88E
Stack Com. Size : 00010000
Heap Res. Size  : 00100000
Heap Com. Size  : 00001000
PE Base Addr.   : 00010C20
PE Image Size   : 000B8440
PE Checksum     : 00000000
PE Timestamp    : 3D2F5AC7
Debug Path Offs.: 0001060A
Debug File Offs.: 0001064E
Debug Uni Offs. : 000105F8
Kernel Thunk Tbl: 0005E4A0
Debug Import Tbl: 00000000
Library Count   : 00000007
Library Offset  : 00010588
Bitmap Offs.    : 00010658
Bitmap Size     : 000002B2

=================================
 XBE CERTIFICATE
=================================
Size            : 000001D0
Timestamp       : 3D2F5AC7
Title ID        : FFFF051F
Title (uni)     : xsms
Title Alt.ID[00]: 00000000
Title Alt.ID[01]: 00000000
Title Alt.ID[02]: 00000000
Title Alt.ID[03]: 00000000
Title Alt.ID[04]: 00000000
Title Alt.ID[05]: 00000000
Title Alt.ID[06]: 00000000
Title Alt.ID[07]: 00000000
Title Alt.ID[08]: 00000000
Title Alt.ID[09]: 00000000
Title Alt.ID[0A]: 00000000
Title Alt.ID[0B]: 00000000
Title Alt.ID[0C]: 00000000
Title Alt.ID[0D]: 00000000
Title Alt.ID[0E]: 00000000
Title Alt.ID[0F]: 00000000
Media Flags     : 00000000
Game Region     : 00000000
Game Rating     : 00000000
Disc Number     : 00000000
Version         : 00000000
LAN Key         : 00000000000000000000000000000000
Sign Key        : 000000000502000007000080FFFFFFFF

and now the non-working testvbl :

QUOTE

=================================
 XBE HEADER
=================================
MAGIC           : XBEH
SIGNATURE       : -
Base Address    : 00010000
Header Size     : 2996
XBE Size        : 117204
XBE Header Size : 376
Timestamp       : 44F66211
Cert.Offset     : 00010178
Section Count   : 00000007
Section Offset  : 00010348
Init Flags      : 00000005
Entrypoint      : 00011250
Stack Com. Size : 00010000
Heap Res. Size  : 00100000
Heap Com. Size  : 00001000
PE Base Addr.   : 00010D60
PE Image Size   : 0001BC80
PE Checksum     : 00000000
PE Timestamp    : 44F66210
Debug Path Offs.: 0001050D
Debug File Offs.: 0001050D
Debug Uni Offs. : 0001050D
Kernel Thunk Tbl: 0002BD20
Debug Import Tbl: 00000000
Library Count   : 00000000
Library Offset  : 00000000
Bitmap Offs.    : 00010510
Bitmap Size     : 0000017B

=================================
 XBE CERTIFICATE
=================================
Size            : 000001D0
Timestamp       : 44F66211
Title ID        : FFFF0002
Title (uni)     : default.exe
Title Alt.ID[00]: 00000000
Title Alt.ID[01]: 00000000
Title Alt.ID[02]: 00000000
Title Alt.ID[03]: 00000000
Title Alt.ID[04]: 00000000
Title Alt.ID[05]: 00000000
Title Alt.ID[06]: 00000000
Title Alt.ID[07]: 00000000
Title Alt.ID[08]: 00000000
Title Alt.ID[09]: 00000000
Title Alt.ID[0A]: 00000000
Title Alt.ID[0B]: 00000000
Title Alt.ID[0C]: 00000000
Title Alt.ID[0D]: 00000000
Title Alt.ID[0E]: 00000000
Title Alt.ID[0F]: 00000000
Media Flags     : 00000000
Game Region     : 00000000
Game Rating     : 00000000
Disc Number     : 00000000
Version         : 00000000
LAN Key         : 00000000000000000000000000000000
Sign Key        : 00000000050200C007000080FFFFFFFF

i've noted a different sign key (but this could be perfectly normal, don't know:

Sign Key        : 000000000502000007000080FFFFFFFF        -> xsms
Sign Key        : 00000000050200C007000080FFFFFFFF        -> testvbl

and title ID:
Title ID        : FFFF051F  (xsms)  and FFFF0002 (testvbl)

Also, maybe the error message TLS -> 0xFFFF0000 refers to "Thread Local Storage" , as presented in the libraries section...

hopefully this helps.

[openxdkman]

We won't let you down even if it takes time to fix the issue...

About your will to detect wich bios you have, maybe adding as many signature as possible in evox.ini
can help to display the one you actually have...

[BIOS]
ROM = "Original 3944",0x542C62CB976A4993C8C5027DFF9638CE
ROM = "Original 4034",0xF20CD7574BB4B2A69810B2E9F766A90D
ROM = "EvoX V2.0",0x76FD88337B8D8C1F116F85F3984B98B6
ROM = "EvoX V2.1",0x99487615BB30670CB65993388FCF2A63
ROM = "EvoX V2.2 No Logo",0x220ADE778785CFC3C98BB5EA8BBD8608
ROM = "EvoX V2.2",0x220ADE778785CFC3C98BB5EA8BBD8608
ROM = "EvoX v2.3 Fast Animation",0x220ADE778785CFC3C98BB5EA8BBD8608
ROM = "EvoX v2.3 No Animation",0x92BB4AFBBCBF4CF7DC376418286A8930
ROM = "EvoX v2.3 No Logo",0x855EF706E264351B056124CB538BDF56
ROM = "EvoX V2.3",0x220ADE778785CFC3C98BB5EA8BBD8608
ROM = "EvoX V2.4",0xE3CE66B99957A92FDAC40AF951C3F1FD
ROM = "EvoX V2.4.err.noani",0xE03C7AF969933C821B4375E0D3DB6022
ROM = "EvoX V2.4.err.noani.nologo",0xE0109F21892D475D1DA1CBECC244C601
ROM = "EvoX V2.4.err.noani.nologo.ybox",0x3E66E6832BC2C5D19C0637AEF00C7EDD
ROM = "EvoX V2.4.err.noani.ybox",0xD4CC70976EAE2D849627ADDC02997819
ROM = "EvoX V2.4.err.ybox",0x6B1EA5E0B1691C4E0B759AE26B4554A3
ROM = "EvoX V2.5",0xE3CE66B99957A92FDAC40AF951C3F1FD
ROM = "EvoX V2.5.colormod.err",0x688497922D63AF6385C8E37E1C19EADA
ROM = "EvoX V2.5.colormod.err.evox",0x097C581438C69DE515A346D19A9D9C41
ROM = "EvoX V2.5.colormod.err.noani",0xE1BF3D54A5F347C01645D4CA713568A6
ROM = "EvoX V2.5.colormod.err.noani.evox",0x48626499F85FBAF53A6DFE360F8CDE2E
ROM = "EvoX V2.5.colormod.err.noani.ybox",0x8BC27C5CBE5810B9C6A53C9D95B1DE14
ROM = "EvoX V2.5.colormod.err.ybox",0xFFDCCDDF7DDCF0ADB0C2FC70752BC7A1
ROM = "EvoX V2.5.err.noani.nologo",0x1ABC74B2B154160FFEE366A8479BF7B7
ROM = "EvoX V2.5.err.noani.nologo.ex",0xDDF255F5D4F4F3912A419FE278116C2D
ROM = "EvoX V2.5.err.noani.nologo.yx",0x3F752E5381C9CC53D5DF8C28F4D68F71
ROM = "CPX v1.02",0x70B54E6CD91F59D4932E7ED776F9267E
ROM = "CPX v1.02 no logo",0xA993FCC9D41FAE1C7AB7759077CC77BF
ROM = "CPX v1.02 no ani",0x3621FE90ED6438DFA9E57897B0631E2D
ROM = "Trapflags v1",0x80EE2CFBF7AF617BB42256B572AC6640
ROM = "Trapflags v2",0xAEE3AEA34AC62C823A165DB632A22709
ROM = "Pandora",0xF8D2682275B2EA41EE213FFAAF2FC96A
ROM = "Xtender v1.0",0xE89B1A394E21D07E54864C229E9763F0
ROM = "Xtender v1.1",0x542C62CB976A4993C8C5027DFF9638CE
ROM = "Xtender v1.3",0x96015F442D345A6FDC9915CAFCBC63A4
ROM = "X-ecuter",0x5D540DFBA44B8C7EE3826CBADFA04491
ROM = "E-X Final 4034",0xE78262E21CE24644415D96D9DF6F64E4
ROM = "E-X Beta 4034",0xF9BA842542D980CB3186FA6EC55F9909
ROM = "E-X Beta2 4034",0x563830D746868117D5AD57AA67203CA2
ROM = "CPX v1.02 Debug",0x8E5C811CCC3C6875FD90C4D0ED6A8ABF
ROM = "CPX 1.02 Debug no ani",0xAC65F68F2706235A578FE1C5FB1E41B1
ROM = "Complex 4627 v1.02 Debug",0x70D6F0B58D5A7EB84611B76225AD4E08
ROM = "Complex 4627 v1.02",0x70B54E6CD91F59D4932E7ED776F9267E
ROM = "EliteX version 1.0 4034",0xF20CD7574BB4B2A69810B2E9F766A90D
ROM = "EliteX version 1.1 beta 4034",0xF20CD7574BB4B2A69810B2E9F766A90D
ROM = "EliteX version 1.1 final 4034",0xF20CD7574BB4B2A69810B2E9F766A90D
ROM = "EliteX v2 colormod.err.noani",0x85D27E5B36A7CB42D1E7EF4E22C04770
ROM = "EliteX v2.colormod.noani.err",0xB1D24990F1C5EB30483B6242A4F86982
ROM = "X2_v1_1024",0xa61dfd2361487c059f81f272c9857396
ROM = "X2_v1_256",0x8ed3428fd664a999914c40702bf4126c
ROM = "X2_v1_512",0x32885b14c08ab936fe240564509d8392
ROM = "X2_v1_noani_1024",0x9c0c21603e457457fcb44cef47f29bec
ROM = "X2_v1_noani_512",0x8fc03ae9acd4f0cf41f5af6c2abcfe4d
ROM = "X2_v1_noani_256",0x98fd3f4ba71e593a47f0409abc77abea
ROM = "X2_v1_noani_blue_1024",0xb9ec2167e7b54fc418e5422386c6d3bd
ROM = "X2_v1_noani_blue_512",0xe6db85f8478b52e8f52dd4cfcfbd8eb8
ROM = "X2_v1_noani_blue_256",0x23f0867c60846e20272ce9e33bdd7121
ROM = "X2_v11_1024",0x604a2acaf16837c5b596995bd328b731
ROM = "X2_v11_512",0xbce442c9340aeb7a82697cd3f176c8ff
ROM = "EvoX V2.6 - V1.0_256",0xdd3de3542bff7b36cdb0dbe078c27fbe
ROM = "EvoX V2.6 - V1.0_512",0x306d87421f418b2a624eca4b83045fda
ROM = "EvoX V2.6 - V1.0_1024",0x4651e664c6df319419e76c04e023f218
ROM = "EvoX V2.6_EjectFix - V1.0_256",0x2e1ec59dc8c295b462d5bffa73feaecc
ROM = "EvoX V2.6_EjectFix - V1.0_512",0x65b80cb7a99df867356c681cf6095582
ROM = "EvoX V2.6_EjectFix - V1.0_1024",0x22c7bce9dffe2f10791bf7770dd2885d
ROM = "EvoX V3.6 - V1.1_256",0xcb73b4914bb6c70b66e21377989726a0
ROM = "EvoX V3.6 - V1.1_512",0xc018feaa5b717c19a32f5ee470d73143
ROM = "EvoX V3.6 - V1.1_1024",0x5c5df45ec83e6c10ff8a863cc06552a7
ROM = "EvoX V3.6_EjectFix - V1.1_256",0xf754767b388ce7a08bf57304e24c9ae9
ROM = "EvoX V3.6_EjectFix - V1.1_512",0x1fd5296d288ff5061af91ff495d0fb28
ROM = "EvoX V3.6_EjectFix - V1.1_1024",0x5704301962580af0364dac762166cbef
ROM = "x2_4972_final_v1.0",0x94928743972D443385721E5B92E5F7FB
ROM = "X2_v1_noani_blue_err_final_1024",0x1860903c6237e11d6c1676328dbfbf74
ROM = "xecuter2_xbox1.1_256k",0xa154577a223e2de097195dae062a4f10
ROM = "xecuter2_xbox1.0_noani_blue",0x120fe9f88aaaa2b18d260906ac92b1e1
ROM = "xecuter2_4973_xbox1.1",0xB4F9A0C9F363C49751268ED0BD4126E4
ROM = "xecuter2_4973_xbox1.0",0x7137C693E67554B92873D3EC5CDBB1D8
ROM = "EvoX D.6",0xc349c2b047a3d6c2de2e1c10185ecf86  
ROM = "EvoX D.6ef",0x74c6235497f474bf88b54b3fc52a20b2
ROM = "x2_4974_MultiVer",0x24bff933c4ee6178040ab4b4daf6c6a8
ROM = "EvoX.D.6.noani.blue",0xcd3158097fd98aa65ba271024fb6c23a
ROM = "x2_4974_noani_blue",0xaa5fe4306525b8e951fbe0069022572e
ROM = "x2_4976_err",0x1e259481510639d69c8223f75bd79b9b
ROM = "x2_4976_noani_blue",0x2d667670ef9493b0211a13ed3ce7fc02
ROM = "x2_4977",0x92987e26edd5833921c9b0e539ea091e
ROM = "x2_4978",0x6e77d14a22f7235a2da3f67e809d1c6b
ROM = "x2_4977_noani_blue",0xa2e41332fb5a8ae7dadcc0a5e9ef1c9a
ROM = "EvoX D.6",0xc349c2b047a3d6c2de2e1c10185ecf86  
ROM = "EvoX D.6ef",0x74c6235497f474bf88b54b3fc52a20b2
ROM = "EvoX M8 MagiChip",0x35ff4c1e2cf26fccd9b1dbf493bf442b
ROM = "EvoX M7 MagiChip",0xb602dbaf433a1bc61d03fae8bdefdbc3