Print

[chimpanzee]

or use netmask 255.255.0.0 on PC. The netmask controls how the TCP stack to determine if an ip is on local subnet(use arp) or through routing. since you share the 192.168 part, just cheat the PC to search for a larger subnet including 192.168.0.x

[ipodder2003]

ldots... you da man.  I am about to mod a friend's xbox, and I want to keep his original HD mainly intact, so he has a backup in case I screw up.  Your tool will work great for this... thanks!

[morpheous1777]

nice package, I just used it to mod 2 xboxs, it was pretty simple, you might wanna mention that the bfm bios is a modified one (to look for e:\evox\evoxdash.xbe) so if they wanna update their bios. why did you stick evox on the E: drive ? and what other modifications did you make (to bert-ate-ernie, bios's, folders, etc..).

[ldots]

OK, I updated the tut. to mention these things. Thanks for the feedback.

I put Evox on E: in a folder, as I like to keep things tidy. Personaly I dont like all sorts of files floating around in the root of C: or E:
Therefore the bios included loads E:\Evox\default.xbe as its primary dash.
Bert-ate-Ernie has been modified to load E:\pbl\pbl.xbe

So to replace the bios included, either edit the bios in xbtool or move the Evox installation to the root of C: (renaming the default.xbe to evoxdash.xbe).

[chimpanzee]

QUOTE (ldots @ Jun 6 2004, 08:06 AM)

OK, I updated the tut. to mention these things. Thanks for the feedback. I put Evox on E: in a folder, as I like to keep things tidy. Personaly I dont like all sorts of files floating around in the root of C: or E: Therefore the bios included loads E:\Evox\default.xbe as its primary dash. Bert-ate-Ernie has been modified to load E:\pbl\pbl.xbe So to replace the bios included, either edit the bios in xbtool or move the Evox installation to the root of C: (renaming the default.xbe to evoxdash.xbe).

Um, won't that be too PBL specific pointing to e:\pbl\pbl.xbe especially when some kernel would have problem loading it ? e:\default.xbe seems to be more neutral.

[ldots]

QUOTE (chimpanzee @ Jun 6 2004, 08:48 AM)

Um, won't that be too PBL specific pointing to e:\pbl\pbl.xbe especially when some kernel would have problem loading it ? e:\default.xbe seems to be more neutral.

Yes, it's PBL specific. The UDE part of the package is aimed at pre-5530 users. 5713+ users cannot run the update.xbe, so the "only" potential users who cannot use this are 5530 users.

The whole point of making a package was to provide an automatic install that doesn't give the user too many options. If you wanted to "experiment" (boot anything besides PBL on startup) I guess you wouldn't be using a package anyway.

But if anyone would like it - I could modify the UDE tool to make the installation of PBL optional, and if the user chooses not to install PBL, bert-ate-ernie could boot E:\default.xbe (evox) instead. Would that be better ?

[chimpanzee]

actually, it is not too hard to just replace e:\pbl\pbl.xbe with whatever someone wants for those who know what they are doing(just a bit odd). So it really is cosmetic and nothing else. My preference of e:\default.xbe simply follows the game convention. If I put in a DVD game, \default.xbe of that drive is loaded. So if I do a hack, e:\default.xbe is loaded. easier to follow :-)

[ldots]

[Dan Wysocki]

[ipodder2003]

[spongy]

I think I'm missing something here.

I downloaded ltools,transfered it to my HDthe same way I do all my gamesave exploits and installers(homemade usb to controller to M$ memory card).loaded MA>campaign>Run Linux...The LED turns orange the screen flickers red then goes black, then after 10 or 15 seconds the LED flashes orange and the box shuts down.

What am I doing wrong here?


              Thanks


EDIT: forgot to say, it's a clean V1.0 with C: from slayers 2.5

[ldots]

Sounds strange?
I just re-tried the package by ftp'ing it to a v1.0 xbox. Ran perfectly fine.

Only thing I can think of is that the package got corrupted on transfer. I would suggest trying this :
Get another MechAssault game save hack that just has Evox on it. Run this hack to get ftp-access. Once in, delete the E:\UDATA\4d530017 folder and upload the same folder from the ltools package. Try running the MA->Campaign->Run Linux hack again. If this works it's very likely that corruption was the cause of your problems.

Some memory cards have problems handling large game saves. My memcard has previously worked fine with large game saves (even though it's an Action Replay card), but when testing these ltools packages I did run into the corruption problem a few times. So if the ltools packages do not work, either try another memcard, or try getting ftp-access with a small game save with evox, and ftp the ltools to the xbox instead.

[spongy]

QUOTE (ldots @ Jun 7 2004, 01:32 AM)

Get another MechAssault game save hack that just has Evox on it. Run this hack to get ftp-access. Once in, delete the E:\UDATA\4d530017 folder and upload the same folder from the ltools package. Try running the MA->Campaign->Run Linux hack again. If this works it's very likely that corruption was the cause of your problems.

  Bad news... I did as you said, ftp'ed the save in, but with the same results.

Any more suggestions?

   Thanks again.

[ldots]

OK - just brainstorming here :

• Does your xbox run fine otherwise - have you had any HDD troubles?
• Is it a stock HDD?
• When you ftp'ed the hack in, did your run Evox from a Mech game save hack? The reason I ask, is that I heard that for some people who has been on live with MA the hack stopped working. Most likely because some updates are downloaded that patches the flaw in MA. If you can run the Evox game save hack, that's not the problem though,. Related question, you do have the exploitable MA version right?
• If it is MA related then you should be able to 'Run linux' from Evox. You could try this by extracting the Evox included in the ltools package and using this. It adds a 'Linux' item to the 'Launch Menu -> apps'

What is really strange is that the LED does turn orange indicating that the linux boot loader does run?

You do have this file-structure in the UDATA folder right?

CODE

4d530017/    SaveImage.xbx    TitleImage.xbx    TitleMeta.xbx    62D648EBF155/        MASave.sav        SaveMeta.xbx        default.xbe        files        initrd        linuxboot.cfg        vmlinuz        xbsavegame.dat

[spongy]

 

QUOTE

Does your xbox run fine otherwise - have you had any HDD troubles?

  Xbox runs great otherwise,both stock and exploited(I've used audio,font and most recently the DD exploit).- no HDD troubles at all.
 

QUOTE

Is it a stock HDD?

  Stock HDD (never unlocked)
 

QUOTE

When you ftp'ed the hack in, did your run Evox from a Mech game save hack? The reason I ask, is that I heard that for some people who has been on live with MA the hack stopped working. Most likely because some updates are downloaded that patches the flaw in MA. If you can run the Evox game save hack, that's not the problem though,. Related question, you do have the exploitable MA version right?

  MA is the only way that I have to MOD my box.I have never connected MA to live.I deleted all MA gamesaves before adding this.
 

QUOTE

If it is MA related then you should be able to 'Run linux' from Evox. You could try this by extracting the Evox included in the ltools package and using this. It adds a 'Linux' item to the 'Launch Menu -> apps'

    I'm not sure what you mean here    so I tried this:  I extracted your gamesave and went to udata / 4d530017 / 62D648EBF155 / files,extracted evox and moved the "three files" to / 62D648EBF155 /. When I tried to run remoteX from evox it started to go to the loading screen,then jumped right back to evox.I also tried adding the three files to mechassaultwithevox gamesave with the same result.
 

QUOTE

What is really strange is that the LED does turn orange indicating that the linux boot loader does run?

    Yes, When I load your gamesave(as is) to the HDD. I boot MA>campaign>Run Linux...the LED instantly turns orange,the box goes quiet,about ten second later the LED starts flashing orange,the HDD spins up a few times,and the box just shuts down.
 
  That is the exact file structure except I also have an evox.ini in 62D648EBF155/

 

QUOTE

um, sounds like the kernel is compiled without VGA console support or the console device node is not in /dev/. My quick fix was just enable the VGA console support which xbox-linux's sample config doesn't have. Unfortunately, either you need to do the compilation yourself or wait for Idots to redo the package.

    I didn't really understand this.Could this be my problem too?

   Can I try to launch this from another exploit? DD or audio? and still be able to install UDE?

        Thanks again