Topic: Its Either Simple Or Complex But It Is Just Plain Weird! (Read 69 times)

quell · « **on:** February 19, 2007, 09:09:00 AM »

This is the last time I upgrade anyone elses xbox!

This is a mates box, utilising a modchip, booting into the latest evox.

This man knows nothing about modding except on how to get around the evox menu, so I say drop it over and ill update all your apps and install some new ones like mimesis, dsl, xbmc ect ect. And make the evox boot to xbmc using the default.xbe short cut and associated cfg file.

Well, here is the thing, I used his ip already configed in evox to ftp all the app updates to his apps folder in F: drive. I will write this in caps so people see it clearly:

I DID NOT TOUCH C:, I DID NOT EVEN LOOK AT C:

So my mate wants a game of halo2 and I power down the xbox and plug mine back in, get slaughterd on killtrocity v2 due to my poor connection I might add and then we finish up and I decide to continue with upgrading my mates box by installing xbmc and the shortcut ect, with the intent of replacing the evoxdash xbe and renaming the shortcut ect ect, but I could not get that far because from this point onwards the modchip bois refuses to boot to the evoxdash.xbe in c: drive. At this point it is unmoddified, I have not touched it and it worked before, I upgraded the apps in F:. It will only boot to the M$ dash from the hard drive and thats it.

But it will boot to evox on a disk so i can ftp

The configeration I was attempting to set up is identicle to the one running on my box, latest version of xbmc, shortcut and all the rest. Probly different chip but it shouldnt matter cos its the same bios.

Ive had some problems softmodding but jesus this takes the cake, this should not happen! lol

please help or post about similar experiences, I cant hand it back like this!

ThaCrip · « **Reply #1 on:** February 19, 2007, 09:33:00 AM »

what modchip does he have? ... if it's a Xecuter 2.x modchip just use FlashX v1.2 to update the bios to a new bios (X2.5032 (or 5035) ) ... but this might not work since you got to run this as a application and you said you can only boot from a cd so this probably aint gonna work.

but with this bios u can edit a x2config.ini file (which is stored on E) to tell it what to boot in terms of xbe files etc.... easy to configure instead of having it hardcoded in the bios itself.

although it does seem to have a weird problem... gotta agree with you there.

you pretty much seem to know what your doing so im sure you will figure something out (IMG:style_emoticons/default/wink.gif) ... just thought i would mention using a newer bios.

also what bios is currently on the modchip anyways? .... is it X2.4983? or what

This post has been edited by ThaCrip: Feb 19 2007, 05:39 PM

quell · « **Reply #2 on:** February 20, 2007, 04:27:00 AM »

I got the mod chip ID numer from within the system info of xbmc: SST49LF020A
I googled that and I believe it is an Aladdin XT, I assume it would be running the m8 bios due to the 160 gig hard drive, as for bios version number I dont know. Hope this helps. Thanks

quell · « **Reply #3 on:** February 20, 2007, 05:03:00 AM »

Problem solved more or less: I simply renamed the evoxdash and ini to xboxdash and renamed the xboxdash to msdash and created a shortcut in f:apps to link to the m$ dash so in effect all is well but with a bit of cross dressing going on with all the file names.

I still think it is extremley strange how the bios will detect the evoxdash.xbe on a disk and not the hard drive especialy when it had done so for months.

Thanks for the help!

ThaCrip · « **Reply #4 on:** February 22, 2007, 05:31:00 PM »

yeah it does sound pretty weird but atleast you got it going now.

have a good day

Author Topic: Its Either Simple Or Complex But It Is Just Plain Weird! (Read 69 times)