Print

[chimpanzee]

do you have the original MechInstaller ? I would suggest to replace the linux files(vmlinuz/initrd) with that to first isolate if it is related to it or something else.

[ldots]

QUOTE (spongy @ Jun 7 2004, 05:38 PM)

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

That was sort of what I was suggesting with extracting the evox from my package. OK, try doing it this way :

• unzip the ltools package.
• get ftp access with your mechassaultwithevox hack.
• create a folder on E: called ltools
• Put everything inside the 62D648EBF155 folder of my package on E:\ltools
• Edit the evox.ini for your mechassaultwithevox hack to look for apps in E:\ltools by adding the line
  

CODE

AutoAddItem "e:\ltools"

to the "apps" section of you evox.

ftp this edited mechassaultwithevox game save to your xbox (E:\UDATA)

Run MA -> Campaign -> Run Linux

Once Evox runs you should have a "Linux" option the the "Launch Menu -> Apps" section.

[ldots]

Thinking about it, it seems more likely that some of the files have been corrupted somehow - from transfer, extraction,... what do I know?
Because the boot loader does run (LED color changes), meaning that the MA hack must be trickered. Maybe try re-downloading the package, maybe try another tool to extract the package, maybe even try the initial release (look in the _old folder at 'the usual places'). As i said it runs fine on my v1.0 (and v1.4).

[spongy]

QUOTE (chimpanzee @ Jun 7 2004, 10:46 AM)

do you have the original MechInstaller ? I would suggest to replace the linux files(vmlinuz/initrd) with that to first isolate if it is related to it or something else.

[ldots]

[spongy]

QUOTE (ldots @ Jun 7 2004, 12:09 PM)

Hmmm, so it boots with an older kernel/initrd. Only thing is with these old version you wont have my tools available (like the UDE installer).

your tools were what I wanted

QUOTE

Are you saing you also tried the _old versions of ltools and that didn't work either?

Yes I tried the old version of ltools.

QUOTE

If so, then for some reason the new kernel is not compatible with your xbox? But why? It works on my v1.0

I hope you're not asking me

Anyway, Don't worry about it too much as I have other ways into my box.I'm doing this mostly for fun(and the ease of use )
Not one other person has had this problem. We should definitly assume it's my fault until there's more reports of it.I'll keep messing with it and keep you updated.

 Thanks again

EDIT:spelling

[ldots]

But it would be nice to know what causes your problems. At the moment the only thing I can think of is that your "old" (no offense) xbox has some hardware not supported by the kernel in my package, but supported by the old kernel on the MechInstaller. Using that old kernel is not an option though as it doesn't have focus support.

[ldots]

Could you try to make a clean copy of my package again. Then extract the code below with Iceows, and try replacing the linuxboot.cfg of my package with the ones from the archive below and see if that makes you xbox boot the kernel in my package. I suspect the problems with your specific xbox is related to the framebuffer driver.

CODE

begin 644 test.tgz M'XL(`&CEQ$```^W52VZ#,!0%4(]9Q=M`P79L4`>L)<+@5!8$B/DHS>IKPJ!2 MJK:J*AI5N6=B/I9L_-X5<<(VQ[GBF=9AO+H=K]>"\U2(5.K=+CS/,B$9Z>VW MQM@TC(4G8K[KQJ_F???^GXJ3QK73V82OB\O#RUYLL`9?BJO4I_677+W77X0^ M$3*5&2.^P5X^>/#ZU]:WMJ'YN+3!)7*M&WU%ZQ`5?6_;]2Y?^\27M!Q$GE1V M3GQQY-27+C>N&YP_46VJ)V\'.U)HJ',^]4U75!2F56ZH]Z;IRGIP%YLK_IQ2 MM,PY&&JC>Y_!([O-O]Q@C9_D7^DU_^$W@/S_@3OFW[NY"/E_1?X!```````` 3``````````!^Z0U\$346`"@````` ` end

To everybody else. I think this is a rare case, so please go ahead and try the package. More reports on succes or failure are very welcome.

[spongy]

Sorry ldots, I think I'm having some trouble extracting the files.I'm kinda new at this.
Is it two different .cfg files?

EDIT: I'm not sure I'm doing it right but I keep ending up with "linuxboot.CFG_1" and "linuxboot.CFG_2". These won't load so copied the text from one over the text in the original "linuxboot.cfg". No dice, tried the other same result. Flashing orange then shutdown.

[ldots]

OK - Spongy.

Until I figure out why there is an incompatebility issue with your specific xbox (though it's hard to debug when I cannot generate the problem myself ?), I would like you to try a custom package made for these problematic box's.

PM'ed you with details.

Still think it could be the framebuffer driver since that changed between the MechInstaller kernel and the kernel in my package. That's also supported by the fact that the crash occurs early in the boot proces, and that the screen is all garbled.

[ldots]

Sounds like you did everything correct.

Try to just get ftp access using a Mechassault-with-evox game save hack and ftp the extracted package to E:\UDATA to eliminate the possibility of the package being corrupted by the memcard.

Also :
- make sure you have no other files besides bert-ate-ernie.xtf with the *.xtf extension in the root of C: (that is when the hack is installed, when not installed you should have nothing but the original XBox Book.xtf and Xbox.xtf files there).
- make sure the fonts folder only contains the original *.xtf files (XBox Book.xtf and Xbox.xtf)
- make sure you have no folders called Evox and pbl in the root of E:, or answer 'y' when the UDE intaller asks you whether you want to replace the current Evox and pbl installations.

[ldots]

But nice to know your experiences. I will try to make the installer even more aware of previously installed hacks.

[spongy]

  Might I add what a GREAT package this is.Very simple and fast.I had a backup of eeprom / HDD password,a backup of C:,and had the UDE installed with a link to M$ dash in no time.Haven't had time to mess with everything(-uninstall,c-restore).

So I have a few questions.I assume the fastest way to get back to a Live! state would be UDE uninstall ?
Or would it be c-restore?
Can I use these from UDE or do I need to run the gamesave each time ?

   According to the poll on the home page 42% of people who voted so far have a 1.0 box.So there might me a few more cases like mine.Until then I will feel special "ldots made a package just for me"

Keep up the good work and  thanks again  

[ldots]

QUOTE (spongy @ Jun 9 2004, 12:37 AM)

According to the poll on the home page 42% of people who voted so far have a 1.0 box.So there might me a few more cases like mine.

Glad it worked out.
Apparently not all v1.0 boxes have the problems you have, so time will show how many users experience this. In any case you should also find this "replacement package" at the usual places now - with a note to try the standard packages first, and if these dont work try the replacement.

QUOTE (spongy @ Jun 9 2004, 12:37 AM)

So I have a few questions.I assume the fastest way to get back to a Live! state would be UDE uninstall ? Or would it be c-restore? Can I use these from UDE or do I need to run the gamesave each time ?

UDE -uninstall is the fastest way to get to an unmodded state. c-restore will uncompress the image of C, so that takes a bit of time (roughly 30 secs. or so). You dont have to run UDE -uninstall from the game save though. You can just run the mini-linux from Evox (should show in the apps menu). For re-enabling the UDE you have to use the game save hack though, or setup the Easter Egg exploit yourself. I thought about including an Easter-Egg switcher, but decided not to :

• The EE exploit will most likely have a limited lifetime.
• It would require people to pack one more 'correct' xbe (the prelive dash) and maintain another set of hacked fonts.

The game save hack will always work though. Some will find it a bit of a hazzle to reenable UDE from a game save hack (and some dont have an exploitable game), but I think I could run the save hack faster than typing <<Eggsßox>>.

[ldots]

the major change is that the UDE installer should be more aware of previously installed hacks and fonts.

• If the installer finds Evox or PBL on E: (case-insensitive), the user will be prompted if its ok to replace these installations with the ones from this package. The user is prompted, but I recommend answering 'y' to this question.
• After renaming Xbox.xtf and XBox Book.xtf in C: and the fonts folder, the installer will check for other occurances of *.xtf in the root of C: and back them up in an xtf_backup folder. Previously installed hacked fonts could interfere with the UDE.
• It should be safe to run UDE -install continuously. The installer will see that UDE is allready installed and take the nessecary precautions when re-installing.
• UDE -uninstall will check that it is possible to revert to a working unmodded state. If the nessecary files are not found, the uninstall will be aborted.

As usual, when using this package, dont mess with the exploit relevant files yourself. Let the installer/uninstaller handle it. I think I made it as safe as possible, but still removing/renaming files that the installer uses could cause problems.