xboxscene.org forums

Pages: [1] 2 3 ... 5

Author Topic: X3 With Unleashx  (Read 1232 times)

kezor

  • Archived User
  • Sr. Member
  • *
  • Posts: 367
X3 With Unleashx
« on: October 08, 2004, 03:00:00 PM »
hey guys i dunno my unleashx dash isn't showing my f drive i have confirmed it with 2 people
Logged

trentdadi

  • Archived User
  • Sr. Member
  • *
  • Posts: 442
X3 With Unleashx
« Reply #1 on: October 08, 2004, 06:27:00 PM »
First of all, make sure your F: is enabled which it probably is.  Try throwing another dash such as avalaunch on there and enable F:.  Before you go ahead and see the F: in there, make sure there is some space in there.

In UnleashX, you have to go to settings -> Storage.  Make sure there is a yes next to F: and than do a power cycle (turn xbox off and than on again).

If it still doesnt work, there is a chance that your bios isnt throwing all your extra space into F:.  If you have never gotten an F: before, thats probably the problem.  Go download the bios you want (i suggest x2 4981), open it up with xbtool, and towards the bottom left, make sure you pick either partition 6 takes rest, or partition 6 takes 137, 7 takes rest.  The 2nd option will give you a G: partition that will just take up any extra space that was left on your hard drive after F: filled up.  First one just throws it all into F:.
Logged

jdandc

  • Archived User
  • Newbie
  • *
  • Posts: 6
X3 With Unleashx
« Reply #2 on: October 08, 2004, 09:39:00 PM »
I have now witnessed this on 2 different Xbox's

After the installation of Unleashx after the reboot you cannot see drive F.
Yet if you try to enable it and save the setting, you receive error 123.

For some reason you cannot write any changes, no matter what you try and change. Both xboxs had a X3 installed.

Any ideas etc, would be greatly appreciated.

Cheers
Logged

FreeZerBurN66

  • Archived User
  • Newbie
  • *
  • Posts: 21
X3 With Unleashx
« Reply #3 on: October 09, 2004, 02:10:00 AM »
QUOTE (jdandc @ Oct 8 2004, 11:39 PM)
I have now witnessed this on 2 different Xbox's

After the installation of Unleashx after the reboot you cannot see drive F.
Yet if you try to enable it and save the setting, you receive error 123.

For some reason you cannot write any changes, no matter what you try and change. Both xboxs had a X3 installed.

Any ideas etc, would be greatly appreciated.

Cheers

 Having the same exact problem on my Xbox.
Logged

Vandiemen911

  • Archived User
  • Newbie
  • *
  • Posts: 21
X3 With Unleashx
« Reply #4 on: October 09, 2004, 03:16:00 AM »
ditto here...couldn't do anything.  I've made sure it's not right protected.  I've renamed it a couple of different things.  I've rebuild the hd a couple of different ways and nothing!  Must be a bug in there somewhere...
Logged

unleashx

  • Archived User
  • Hero Member
  • *
  • Posts: 621
X3 With Unleashx
« Reply #5 on: October 09, 2004, 03:48:00 AM »
If you don't have a custom config.xml, go to storage settings, disable then enable Drive F and save. To prevent the error, make sure you save some settings first, before changing skin. You can also edit config.xml manually.
Logged

Colonel_Schvats

  • Archived User
  • Newbie
  • *
  • Posts: 8
X3 With Unleashx
« Reply #6 on: October 09, 2004, 09:28:00 AM »
same here, everything works if i use xbmc or evox, i can see f just fine, also i can't ftp into unleashx or save settings, it must be some screwy compatibility thing with the new x3 bios
Logged

heinrich

  • Archived User
  • Hero Member
  • *
  • Posts: 2274
X3 With Unleashx
« Reply #7 on: October 09, 2004, 09:40:00 AM »
The same issue happens with ind-bios.
Logged

Master-Chief

  • Archived User
  • Hero Member
  • *
  • Posts: 1352
X3 With Unleashx
« Reply #8 on: October 09, 2004, 09:06:00 AM »
Some people just don't realize that the BIOS is what runs UnleashX. So even if you have an Aladdin Advance or any other mod-chip, if it runs the same BIOS.. the same outcome will occur.  wink.gif
Logged

SUBLOGIC

  • Archived User
  • Newbie
  • *
  • Posts: 49
X3 With Unleashx
« Reply #9 on: October 09, 2004, 11:42:00 AM »
I have the same problem... I even tried editing the config.xml but i didnt have to.. it still says F and G enabled... So as a test, I set them both to Disabled and then back again and still there is no F or G drive. They work and show in Avalaunch however, so I went to the extent of removing unleashx and is config file and re FTP'ed and still got the same result.

Also. If you try to change any settings through the dash and then SAVE them, you get an "unabale to save error" with the HDD locked or unlocked..(had to try it)

Also.. all the settings for the path to skins does not work either. Default skin is always loaded and show as "Skins" in the settings yet if you look at the config.xml it points to C:\unleashx-skins

Hope there is a fix for this..i love UX

This post has been edited by SUBLOGIC on Oct 9 2004, 06:44 PM
Logged

lmnoq

  • Archived User
  • Newbie
  • *
  • Posts: 7
X3 With Unleashx
« Reply #10 on: October 09, 2004, 01:52:00 PM »
Having same problem.. Did everyone here format the HD through X3Live?  that may be a cause of the problem..  i have 250GB drive, set to have all space on F and no G... having the same problems as everyone here-- it wont read the config.xml and it wont let me save any changes-- error 123
Logged

Vandiemen911

  • Archived User
  • Newbie
  • *
  • Posts: 21
X3 With Unleashx
« Reply #11 on: October 09, 2004, 01:14:00 PM »
QUOTE (Master-Chief @ Oct 9 2004, 05:09 PM)
Some people just don't realize that the BIOS is what runs UnleashX. So even if you have an Aladdin Advance or any other mod-chip, if it runs the same BIOS.. the same outcome will occur.  wink.gif

I'm using the same hard drive that I used with my x2.3.  It's gotta be something with the bios.  Whoever said just disable it/enable it...do you even have an x3?  I'm running the 1.6 x3 bios (if it matters...)  You can't save ANYTHING...you get the 123 error.  You can try editing the config file manually, and to me anyways, it doesn't even seem to recognize that I've changed anything.  Any updates?
Logged

SUBLOGIC

  • Archived User
  • Newbie
  • *
  • Posts: 49
X3 With Unleashx
« Reply #12 on: October 09, 2004, 09:55:00 PM »
Hell no.. no formatting for me as F and G works fine in Avalaunch. So just must be a Ux bug.
Logged

unleashx

  • Archived User
  • Hero Member
  • *
  • Posts: 621
X3 With Unleashx
« Reply #13 on: October 09, 2004, 10:21:00 PM »
Hmn, this looks to be a real problem then. Error 123 is ERROR_INVALID_NAME, meaning it's not constructing the proper filename (path is relative). Can anyone bring up the system info (Press Y on the main menu) and tell me what UX is reporting for the path? Also, what does X3 use for its BIOS (Sorry, don't have X3 and wasn't following the scene that much, so don't know if TX released their own BIOS already). Like I said, I don't have X3, so whatever BIOS they're using, I must be able to run it as bfm. Heinrich said it does happen with ind-bios too, so I'll give that a try.

<edit>
I didn't see it anywhere, but for those experiencing this kind of problem, are you running it as the default dash? If not, where is it located (Drive E, F...etc)?
</edit>

This post has been edited by unleashx on Oct 10 2004, 05:24 AM
Logged

lmnoq

  • Archived User
  • Newbie
  • *
  • Posts: 7
X3 With Unleashx
« Reply #14 on: October 09, 2004, 10:39:00 PM »
QUOTE (unleashx @ Oct 10 2004, 04:21 AM)
Hmn, this looks to be a real problem then. Error 123 is ERROR_INVALID_NAME, meaning it's not constructing the proper filename (path is relative). Can anyone bring up the system info (Press Y on the main menu) and tell me what UX is reporting for the path? Also, what does X3 use for its BIOS (Sorry, don't have X3 and wasn't following the scene that much, so don't know if TX released their own BIOS already). Like I said, I don't have X3, so whatever BIOS they're using, I must be able to run it as bfm. Heinrich said it does happen with ind-bios too, so I'll give that a try.

<edit>
I didn't see it anywhere, but for those experiencing this kind of problem, are you running it as the default dash? If not, where is it located (Drive E, F...etc)?
</edit>

UX, here's the information for my system that is experiencing this issue:

xbox V1.6
Xecuter3 Final using LPC rebuild and alternate 5v adapter
250 GB hard drive-- of note may be that I used ConfigLIVE to format/prepare the partitions...
bios is X3ConfigLiveBios_BetaBuild1859
UX loading from C:\evoxdash.xbe

Now for what I've tried/experienced in UX dash...
When I first installed the drive, I copied over my old config.xml to the drive as well.  UnleashX was set to be the primary dash and it booted just fine.  However, none of the settings from the config.xml were applied.  I tried changing settings and it would error out on me.. error 123.
So, I deleted the config.xml and rebooted, thinking to let UX create a new one when I put my settings in by hand.  Same thing, error 123 when i tried saving settings.  
Additionally to be thorough, I grabbed the original/default .xml from the install package.. As i'm sure youve guessed by now-- same thing

The way I formatted my drive was to put all free-space into F partition and no G.  In other dashboards, this space shows up fine.  In the storage menu under system in UX, "use drive f" is on, "use drive g" is off, and in the listing of partitions, there is no "f" partition listed... to UX, that partition is not visible...

the following information is pulled from the system summary information:
the F and G drive information shows the following:
Drive F/G (they show the same thing)  Total: 0 free /0% free
--rest of drives show proper space

path      \device\harddisk0\partition2
phy loc  \device\harddisk0\partition2\evoxdash.xbe

ok so this is all done when loading the dash as primary...

Now, here's the kicker--  when i load up Avalaunch first, then load UX from within, it will read/write config.xml and drive F shows up like it should...  note that even after loading it this way though, when you set it as primary dash and reboot-- it will not read your config.xml you just created/edited/etc..  

Hopefully this gives you something to go on... I know there are many more that are itching to get this figured out so we can get UX set back up like we had it   wink.gif
Logged
Pages: [1] 2 3 ... 5
« previous next »