Print

[Timan]

Yea would be cool "if" there is a quick easy way to use another dash, like UnleashX

[OliG]

QUOTE (OliG @ Jun 21 2004, 11:34 AM)

Well I supose you could try replacing the contents of Evox.tgz with the dash you like there instead.

It does work, just create your own evox.tgz with the dash of your choice, making sure that the default.xbe is not in a folder in the archive.
(I had to create a zip file and then convert it).

Place it in the same directory with the other .tgz files. UDATA/4541000d/000000000000/files/evox.tgz
The package seems to work a treat and the game save didn't corrupt for me this time.

I like it, I like it a lot!!!!!

OliG

[Timan]

You know if there is a way to do it after you already installed evox though?

[spongy]

QUOTE (Timan @ Jun 21 2004, 11:52 AM)

You know if there is a way to do it after you already installed evox though?

It is very easy...

Taken from ldots post

QUOTE

But changing from Evox to any other dash is very easy. The bios that PBL loads boot E:\Dashboard\default.xbe as the default dashboard. So just ftp in. Clean the Dashboard folder and upload your desired dashboard. Remember to rename the executable to default.xbe. No signing needed. If you should mess up. Just boot with eject button to reach the ltools menu. Ftp in and fix the problem.

So just empty the dashboard folder and insert your dashboard files.

For anyone having trouble with the .tgz files,I found some freeware that handles it great.It's called "TUGzip".Not sure if I am allowed to link to it so I won't.

@ldots, I have 1.4 working great. I don't use your supplied dashboard, so are there any other reasons to upgrade to 1.5

[adil786]

QUOTE (ldots @ Jun 21 2004, 07:51 AM)

The game reboots because the hacked bios is set to look for D:\default.xbe and execute it on IGR/reset. Simply fix is hit the eject button right after you do the IGR. A slightly more advanced approach is editing you bios (E:\pbl\Bioses\xboxrom.bin) to not look for D:\default.xbe. Xbtool can do this, though maybe not on all bioses. I remember doing it on the M7 bios though. If not, you can hexedit the bios to change default.xbe to something else.

cant you put in a bios in 1.5 that lets you IGR correctly back to evox easily?

Regards

[RestrainedChaos]

Wow is my xbox pissed at me...

So I had mordens installed at one point and tried to do this over FTP. Game me some scripting error. So I uninstalled Mordens and like everything I had, trying to get back to as clean an original state as I could short of replacing the original dash (I kept 4920 installed). Got the installer to run from Mechassault, did the backup, ran the installer. This is where all hell breaks loose.

Booting with the power button gets me flubber and then hangs at a black screen. Nothing. Nada. Doesn't seem to be a clock loop of any kind (althogh I've never seen one and know my xbox is prone to them, the clock dies ALL the time) cause it never breaks out. Hitting some buttons caused the xbox logo to flash onscreen (not the whole flubber, just the ending), btu I have never been able to reproduce this effect.

Booting with the eject button gets me back to MXM to the Idots tools. Which is brilliant, by the way, and is currently keeping my xbox from being semi-hosed (I probably could go through Mechassult again since it'll boot original games. For that matter, I haven't tried booting backup games but I doubt it would since it never gets to EvoX). Where I got curious and went to "Dashboards" and selected EvoX dash, to see if I could switch to it from there, and got the black and green screen of death ("Your xbox requires service... please contact yada yada" in six languages).

Since I can get into Idots tools I can run the unistaller and reinstall. I'm not sure if I should do that yet thought, because I simply can't imagine it solving the problem. In THEORY I'm actually better off than I was when I had mordens, because I can just hit eject to boot straight to MXM and cause I can probably use custom soundtracks. BUt I don't know if this thing is suceptible to clock loop so I'm afraid to unplug it and move it, and it's obviously not thrilled with me.

Anybody had any of these results before? What happened? How can I fix it? Should I give up on the UDE? Is there something fundamentally screwy about my system?

edit: one last note. After each time it went to Linux and ran scripts, it gave me a weird error message. First it would say I could now safely turn off my xbox, but then it said "sh: can't access tty. job control turned off"

I know -very- little linux, but from what I can see that's the script telling me it can't do something it's trying to. was that the problem?

[ldots]

If you did manage to get that during its 4 hour lifetime there is no need to get 1.5.1. The functionality is the same. As I rarely use my memcard I was not aware that files are unzipped when stored on the memcard. The new release would not fit on a 8mb memcard if the update.xbe was added, so I compressed some folders internally, and implemented the option to add the update.xbe as a zipped file (update.xbe.zip). The complete package should now be less that 7mb, including the update.xbe.zip.

New Features :

• The latest fonts from Rmenhal. Both known update.xbe versions will work. This means that if you already have dash 4920 the installer will work as it is since :
• The installer looks for a user-added update.xbe first, but if this is not found it will try to use the update.xbe from the current dashboard (C:\xodash\update.xbe). Of course the installer will abort of the version is not 4920.
• On installation you can choose between PBL and nkpatcher (for 5530 users)
• NOTE that both PBL and nkpatcher use the E:\BiosLD directory in this latest release, where previously E:\pbl was use by PBL.
• On installation you can choose between Evox and MXM as the default dash.
  MXM has a different skin than when it running as the installer.
  If you regret your choice you can rerun the installer.
• The ltools menu has a 'PBL configure' option to let you choose between a 1 sec. or 0 sec. timeout of PBL.
• Boxplorer has been added and is available from the ltools menu. This should let users without ftp access change the installation. If you want to upload UnleashX as your default dash, simply burn a CD with the files. Run Boxplorer on the xbox and replace the files in E:\Dashboard with the files on your CD. The executable must be called default.xbe

It will hopefully be some time before the next release. This is taking too much of my spare time

- Happy hacking  

[ldots]

@RestrainedChaos

Dont worry. This exploit does not suffer from clock loops. Also the linux output you quote is not the cause of any problems. You will not see them in the latest release

Now to your problem. When the xbox boots with the tray open the font hack must be trickering like it should, so it does sound like the installation is OK. It must be a pbl problem. Are you using a s-video cable? Could be that Mordens used PBL 1.3.5i that supported this, while I use 1.4.1 (because of the Focus chip support), which doesn't support s-video.

[ldots]

QUOTE (pdxkid @ Jun 21 2004, 08:21 PM)

im running the 1.4 version from 007.. works fantastic! however my only question is why cant i access the MSDASH? when i click it, it fades and brings me right back to EVOX menu. id like to still be able to use custom soundtracks.. any fixes or anything i can ftp onto it to make this so?

My guess is that you did not have a working MS dash installation before you installed UDE. Could be some settings-files are missing. To see if things look alright , try to run the mini-linux and post the output from the command : ls /mnt/C

If you have Slayers 2.5 and one of the exploitable games I would ftp in. Delete your C: and relace it by Slayers C-drive. Then rerun the UDE installation.

[RestrainedChaos]

I am using an S-Video cable, yes - except I'm not using the S-Video. I'm just using the composite plugs. Would this be the problem/solution anyhow?

[ldots]

I would think so yes. It's definitely worth a shot. You dont loose anything by trying since you still have the tray-open boot option.

[ClagGlue]

ive got slayers 2.5 and itools 1.4 (well i'll get a different version depending on what game i can ge a copy of) and it says i need to get the 4920 update.xbe, do i have to get this for it to work? i cant find it at the usual places and i dont really know how to use it. i think i read early on in this thread that i can use slayers for the update.xbe, is this true?

thanks for any help and nice work with the installer, was a bit hesitant to try the manual way cos i get confused easy lol

EDIT: ok i did a bit more reading and think i figured it out. can i just use itools to set up the UDE then put in slayers disk and delete old C: then create new C: from slayers? or is there another option on slayers to copy over the update.xbe?

[ldots]

QUOTE (RestrainedChaos @ Jun 22 2004, 12:25 AM)

On a side note, downgrading required several minihacks to get it to play nice - I had to change default.xbe to pbl.xbe as I copied it over, and I had to rename your bios to 4979_67.bin. Now it runs, boots, plays games.... but what's the likelihood that either of those renames are gonna come back to haunt me if something else tries to reference them or if they reference internally?

If you had used 1.5.1 it would have been E:\BisoLD\default.xbe and not E:\pbl\pbl.xbe.
The renaming of the bios is because you used the boot.cfg from Mordens. Instead of renaming the bios you could have opened the boot.cfg and changed 4979_67.bin to xboxrom.bin.
Your installation is fine though.

QUOTE (ClagGlue @ Jun 22 2004, 01:31 AM)

ive got slayers 2.5 and itools 1.4 (well i'll get a different version depending on what game i can ge a copy of) and it says i need to get the 4920 update.xbe, do i have to get this for it to work?

I would start by checking the version of your current dash. Do this in the Settings -> System Info menu of the MS dashboard. If you have version 4920 you should get ltools_v_1.5.1. Then you dont need to worry about the update.xbe.
If you dont have 4920. Then get an xiso tools like Qwix. Extract Slayers iso and you will find the update.xbe in SYSTEM/ALL/c/xodash
If you can setup a network between your PC and your xbox the easiest installation will be to just use the ltools package as it is. Run the (MA,SC,007) hack to get to the MXM menu. Now ftp the update.xbe in to the game save folder (E:\UDATA\xxxxxxxxxxx\xxxxxxxxxxxxx\files\update.xbe).
Then run the installation.

[ldots]

PBL, X2 bios, Evox, MXM, skins, Linux, BoXplorer. That's a lot to fit on 8mb

But actually you would be able to fit the entire package + update.xbe on 8mb without removing anything. It's just that on the first install of the UDE the package inflates. If you take a fresh copy of the package and add the update.xbe zipped (only 1.5.1 supports this), the package will not be more than 7mb.

This was the difference between 1.5 and 1.5.1 - having the installer inflate itself. I too believed it was important to be able to fit a working installer on a memcard, regardless of dashversion.

[adil786]

QUOTE (ldots @ Jun 22 2004, 06:47 AM)

When I started this project I though 8mb would be plenty of space for such a package - well, it's not PBL, X2 bios, Evox, MXM, skins, Linux, BoXplorer. That's a lot to fit on 8mb But actually you would be able to fit the entire package + update.xbe on 8mb without removing anything. It's just that on the first install of the UDE the package inflates. If you take a fresh copy of the package and add the update.xbe zipped (only 1.5.1 supports this), the package will not be more than 7mb. This was the difference between 1.5 and 1.5.1 - having the installer inflate itself. I too believed it was important to be able to fit a working installer on a memcard, regardless of dashversion.

Do we zip the update.xbe then put it in the files folder?

Thanks for the package idots, this is truly ULTIMATE!!!

boxplorer is a reallly nice addon!

Thanks again