Help with UnleashX

[Kibe]

Hey guys,

I'm asking for some help here since I'm completly out of ideas on how to solve this.

I've been using Avalaunch for a while as my primary dashboard, but heard a lot about UnleashX from a friend and decided to try this one.

Got version 0.38.0515 Build 565, released 05.15, from the usual places and placed all the files in F:\dash\unleashx

The problem is whenever I try to launch UnleashX the screen keeps black for a while and then Avalaunch is loaded again.

I've already tryed to delete Unleasg savegame using MS Dashboard and tryed using X2 4983 Bios, but same results here. Oh, I haven't messed with its config.xml, since it was the first time I was gonna run UX.

The problem happened again when I tryed to launch from boXplorer and XBMC.

Thanks for any idea to make this work, now it's a matter of honor!

 

[blubaustin]

did u ever try placing it in C:\?

 

[kimosabe]

No idea if it will help...but go to X3CL > Customize X3 Bios > Change Boot Priority > Move Unleash to the top and rename your UnleashX "default.xbe" to "unleashx.xbe".

 

[kimosabe]

Also, yeah..put all of the Unleash files in C:\ as stated above.

 

[Martin C]

Do this:

1. Leave your unleashX files on F. Rename the UnleashX folder to ux.
2. Rename the xbe file for unleashx to ux.xbe.
3. Go into X3CL and change default dashboard drive to F.
4. Go into the dashboard filenames and change the unleashx.xbe to "dash\ux\ux.xbe" (no quotes). Move it to the top of the list.

I know 100% this works as I do it

Check my two images attached.

Martin

 

[Kibe]

did u ever try placing it in C:\?

Yeap, unfortunatly same results as before.

No idea if it will help...but go to X3CL > Customize X3 Bios > Change Boot Priority > Move Unleash to the top and rename your UnleashX "default.xbe" to "unleashx.xbe".

I'm now using X2 5035, since I have a X2 Chip installed. Tryed changing priority in x2config.ini but same rebooting issue as before.

Do this:

1. Leave your unleashX files on F. Rename the UnleashX folder to ux.
2. Rename the xbe file for unleashx to ux.xbe.
3. Go into X3CL and change default dashboard drive to F.
4. Go into the dashboard filenames and change the unleashx.xbe to "dash\ux\ux.xbe" (no quotes). Move it to the top of the list.

Did as you suggested (rename xbe and folder) and changed this in my x2config.ini:

dash1Name = f:dashs\ux\ux.xbe

After flubber and X logo, I get a UnleashX screen, black screen, UnleashX screen, black screen, UnleashX screen, black screen, UnleashX screen, black screen, UnleashX screen, black screen, UnleashX screen, black screen... and so one, like a loop in launching the xbe.

I've already tryed all these steps suggested in this post in X-Scene Forum without success.

Thanks again for your help guys, any ideas appreciated!

 

[Martin C]

The fact it's getting the UnleashX logo is good - what other files are in the same folder as ux.xbe?

BTW, the reason I used the file and folder names I did is because X3CL has a character limit for dashboard names. You can change these to better names for X2CL.

Martin

 

[Kibe]

Well, I went to UnleashX folder and deleted everything that was there but the ux.xbe file, since from what was told me in X-Scene Forum, a proper config.xml was going to be created. Also went to MSDash and delete UnleashX savegame that was there. Changed again the boot sequence in x2config.ini.

Got the same loop as described before.

I suspect now this might be a problem with UnleashX and Focus chip, just wonder why it wasn't reported before.

 

[Martin C]

Re-copy over the config.xml file from a fresh download and you should be fine.

I have it working on my 1.6, which is a totally different encoder than yours!

Martin

 

[Kibe]

Tryed to download all files again from xbins and nothing.

Still have the same behaviour here, completly out of ideas to solve this one...

 

[Martin C]

Try this:

I've made an UnleashX boot disk - try booting from it.

http://www.xbox-guru.pwp.blueyonder.co.uk/files/unleashxbootcd.rar

extract the ISO from the RAR file and burn with Nero 6. Instructions are in the readme.txt

If this works, then it has to be a syntax issue with the x2config.ini.

Martin

 

[Kibe]

Well, just need to thank you very much Martin!

It finally worked! I copyed all files from the CD to my HDD and now UnleashX is being launched from XBMC without any problems.

I just can't figure out what was the problem here, anyway the problem is now solved!

Thanks once more!

 

[Martin C]

Can't work it out either - must have been something wrong somewhere!

Glad it's working now

Martin

 

[Kibe]

Hey Martin,

Took some time but I was finally able to find out what was the issue.

I don't know why still had the old XBMP laying in my F:\Apps\XBMP folder and had its config.xml to autolist F:\Apps folder. So, UnleashX would hang trying to list it. I removed 1 by one program to make sure XBMP was causing this issue, and now I am 100% sure this was the problem.

Strange that both Avalaunch and XBMC would auto list my F:\Apps folder without any issue, but since XBMP is now completely obsolete after XBMC, this won't be a big issue anymore!

Thanks once more for your help Martin and hope this post might help some other users, ok?

Best regards!