Print

[Frox]

For whatever reason, when Ind-bios loads up Unleashx at boot, it reverts to the default skin, there is no network connection, and it won't recognize the F:
There may be other issues that I havn't found yet.
If I load up Unleashx manually after this, everything seems to work fine.
I tried moving the Unleashx files to a different directory, renaming the .xbe, removing items.xml, and deleting the Unleashx saves, but this did nothing.
I then set Ind-bios to load Avalaunch by default, and everything here seemed to work as it should.

Has anyone else had this issue, or do I have something setup wrong?

Other than that, this seems like a great bios. I especially like the option to disable the flubber.

[enzo]

no problems here...

[pdottz]

frox. im having the exact same problem.

[dzv]

I just tested the iND-BIOS, and had the same problem.

v1.1 Xbox
UnleashX 0.36.0620A launched from E:\evoxdash.xbe
Stock 10G Seagate HDD

[EDIT]  Here's a copy of the .cfg file I was using:

CODE

IGRMODE=2 AVCHECK=1 AUTOLOADDVD=1 INTRO=0 SHOWFLUB=0 BLOBSDEAD=1 MSLOGOTRANSCOLOR=0xFF00FF USEXBX=0 DASH1=\DEVICE\HARDDISK0\PARTITION1\evoxdash.xbe DASH2=\DEVICE\HARDDISK0\PARTITION2\xboxdash.xbe

This post has been edited by dzv: Sep 2 2004, 03:37 PM

[Frox]

Enzo, what does your config file look like?
What chip are you running?
Where are you launching Unleashx from?

I suppose I should have said that I'm running a Xenium with XOS Beta2 on a V1.4 xbox (as far as I know).
Ind-bios config file:

CODE

IGRMODE=2 IGRLOADSDASH=0 AVCHECK=1 IFILTER=1 FANSPEED=10 DISABLEDM=1 AUTOLOADDVD=0 BLOBTHROB=1 INTRO=0 SHOWFLUB=0 FOGON=1 SPIKEYBLOB=1 BLOBRADI=23 SKEWEN=1 YSKEWLOGO=-20 XSKEWLOGO=0 YSKEWXLOGO=0 XSKEWXLOGO=0 YSKEWTEXT=0 XSKEWTEXT=0 TMS=1 SHOWXEN=1 SHOWMSEN=0 USEXBX=0 DASH1=\DEVICE\HARDDISK0\PARTITION1\fback\dash.xbe

Unleashx is called dash.xbe right now.

[Psilocybe]

the problem with the f partition booting is actually a known error with unleash x itself, not the bios that you are using
the problem is that when the dash was developed it was more than likely tested out on an x2 bios which had a bug that made the partition table always boot from the bios and never from the apps, this meant that when using x2 bios the f partition would always boot, but the x3 bios and now ind-bios have this fixed and the error within unleashx shows itself

the skin switcher is also a common known error that you must actually change the xml file for your skins to actually change and stay as what you want them to

[Frox]

Alright, I've got it working.
I renamed the Unleashx .xbe file to avalaunch.xbe and disabled all the boot sequence overrides in the IND-bios config. Everything works peachy now (from my limited testing).
However, if you point the boot override to avalaunch.xbe, the same problems arise as before.
I also tested it by naming the file evoxdash.xbe and that worked fine also.
I guess there's something funky with the boot override process.

[pdottz]

psilocye. the skin switcher is fine as long as you press "A" twice like your supposed to. you dont have to edit the xml file.
also those people are having trouble booting from F or E. I should have mentioned that my unleashx.xbe is located in the C: drive.
also, it's not even reading my config when this happens. it boots unleashx to complete default all settings are lost. when I switch back to the x2, my config file loads.

i was just wondering how thats possibe, how my config.xml does not get overwritten when it boots back to default.(not even my Fgames folder shows up).

sweet bios though from what I did try out.

[Master_Chiefzor]

I have the same problem with UnleashX not working with Ind-BIOS...It also works perfectly if I launch unleashX from avalaunch.  I will try renaming the .xbe to avalaunch.xbe to see if it works for me.  I agree with you Frox...I think the boot override isn't working right...

[Schultz]

I am having the same problem as reported here.. I am using a Xenium ICE with Xenium OS 2.0 beta 2 and UnleashX.  

[Master_Chiefzor]

I tried renaming my unleashx.xbe file to avalaunch.xbe file, but for me that still doesn't work...just thought I'd let you know.

If Psilocybe is right, maybe this should be posted in the unleashX forum also so they are aware of it...for now, I suppose i'll have to revert back to avalaunch temporarily...

[Frox]

Master_Chiefzor, did you remember to remove ALL boot overrides?

For anyone who's interested, I'll post my current IND-bios config file

CODE

IGRMODE=2 IGRLOADSDASH=0 AVCHECK=1 FANSPEED=10 DISABLEDM=1 AUTOLOADDVD=0 BLOBTHROB=0 CUSTOMBLOBEN=0 INTRO=0 SHOWFLUB=0 FOGON=0 TMS=0 IND3DLOGO=0 SHOWXEN=0 SHOWMSEN=0 USEXBX=0

Unleashx is installed on the C:\ and the executable is renamed to avalaunch.xbe

[Master_Chiefzor]

Frox, thanks....you were right...I missed one of the boot overrides *...doh*
Hopefully they'll get this fixed pretty soon or something...it's going to get confusing having avalaunch named unleash and vice versa.

[Psilocybe]

ok what i was talking about with the f partition was actually mounting the f partition, if someone else was just simply talking about booting from the f partition then i'm sorry that i misunderstood, but there definately is a problem with the f partition mounting of unleashX

[modhs]

Frox  good work bud
thx alot