Print

[oz_paulb]

QUOTE (KiLaHuRtZ @ Sep 3 2003, 05:25 AM)

I have to agree that EvoX is going down the shitter.

I think I should have some patches for EvoX (to support G: drive) in the next couple of days.

- Paulb

[Heet]

there isnt a guarentee yet if thats what your lookin for.  Im sure as hell gonna test it tho.

[juan23]

okay this hdd was in my working xbox with bios 4977 in it, i decided i wanted to try this.  now after the 4977 bios flash with lg hdd doesnt work, then i can reflash with bios 4977 regular flash works great just no extra hdd size.

4977 and 4978.03 are not working for me on a version 1.0 xbox.

if anyone has a successfull x2 bios with the large hdd update please post on xbox NG

thanks

[juan23]

only thing i can think of is that maybe im using xbtool incorrect?

i open xbtool
open my 1 meg bios
change a couple thingd=s
set lba48 to take rest on partition 6
then save bios
burn to cdrw
load ozx flash
do the swap
then it shuts down

when booting back up colors are changed, slayers auto is in there, so it boots up drives read zero, i reformat then drives f reads 155 gig.

i shut down wait about 2 mins, reboot goes into loading without any cdrw or dvdr in no (x2 shows up under the xbox logo.  then it just freezez.

i reboot with slyers back in hdd reads all zeros again.

so just maybe im using xbtool incorrect, but all seems to be self exlanitory.

please let me know the steps people have done, so as this will probably help many others as well

[juan23]

paul check ur pm

[the joker]

SITE FORMAT g: should work in avalaunch 0.47.3, but I haven't actually had the possibillity to test it, since I'm lacking of great drives.

[phoenix-lizard]

oz_paulb,
Please explain to a fairly noob...
I have been able to do this succesfully using the have partition 6 use all remaining space option.
People seem fairly concerned about getting another partition (G perhaps) to read apps properly. What is the big advantage of this? Or is it more that people want to know for the sake of knowledge.
I had planned on installing all my >137gb hds in the same manner as my first, but if there would be an advantage to using 2 partitions (F and G), I will hold off.
Thanks again!

[oz_paulb]

QUOTE (phoenix-lizard @ Sep 3 2003, 04:45 PM)

oz_paulb, Please explain to a fairly noob... I have been able to do this succesfully using the have partition 6 use all remaining space option. People seem fairly concerned about getting another partition (G perhaps) to read apps properly. What is the big advantage of this? Or is it more that people want to know for the sake of knowledge. I had planned on installing all my >137gb hds in the same manner as my first, but if there would be an advantage to using 2 partitions (F and G), I will hold off. Thanks again!

I see no real advantage to having F: and G: partitions if you are installing to a new drive.  You can use sub-directories to separate/organize things if you're just trying to keep things separate.

The real reason for adding G: is for people who have already formatted their >137GB drive using a pre-LBA48 bios, and have lots of apps/data already loaded onto it.  It's not currently possible to make drive F: "grow" to the larger space, unless you re-format it (which would require re-installing everything on F:).

The G: option lets people get the extra space, while leaving their F: partition intact.

Even for brand-new installs onto a large  (>137GB) drive, people may want F: + G: if they think they may need to boot an old (pre-LBA48) bios in the future.  The old bios wouldn't know about G:, but at least it could use the F: drive without problems (assuming all of F: is below 137GB).

- Paulb

[juan23]

hey paul sorry had a sales call today, however i sent u both the original x2 bios and the modded bios, please if at all possible email me either 4977 updated bios, or preferably the 4978.03 bios

thanks

[juan23]

hey nightshade, actually, when i converted the 4977 bios and the 4978.03 bios i got unsupported bios kernal on both, however i can flash okay, but it doesnt keep, so as a quick fix i had to load dominnion x bios.

let us know when any of the x2 bios can be used.

also so u know what i am doing

open xbtool
open bios x2_4977.bin
make changes to color way i want, add lba48 rest on partition 6
save then reflash

then doesnt work

[oz_paulb]

QUOTE (oz_paulb @ Sep 3 2003, 07:51 AM)

Just a quick note: I've got EvoX dashboard mounting drive G: at startup, and it displays as a drive letter when I FTP to my Xbox.  "AutoAddItem=G:HDDLoader" works in the EvoX.ini file. My G: drive was already formatted (I did it by hand), so that made things easier.  I'll work on getting EvoX to support formatting G: next. But, it's time for bed now... it'll have to wait until after work tomorrow. - Paulb

Here's a link showing some screenshots of EvoX dash with G: (partition7) support:

http://forums.xbox-s...ST&f=16&t=98828

I think I'll be releasing a patch to EvoX in the next day or so.

- Paulb

[oz_paulb]

QUOTE (NghtShd @ Sep 4 2003, 07:27 AM)

QUOTE (juan23 @ Sep 3 2003, 11:28 PM) hey nightshade, actually, when i converted the 4977 bios and the 4978.03 bios i got unsupported bios kernal on both, however i can flash okay, but it doesnt keep, so as a quick fix i had to load dominnion x bios. let us know when any of the x2 bios can be used. also so u know what i am doing open xbtool open bios x2_4977.bin make changes to color way i want, add lba48 rest on partition 6 save then reflash then doesnt work juan, Might I ask where you got the 4977 BIOS from? It appears that someone may have leaked a BIOS patched with a test build. I would suggest you get a fresh copy of x2 4977 and patch that. My next XBtool release will fix problems like this and will also fix the problem with BIOSes patched for LBA48 not being recognized when reloaded into xbtool. If you get a fresh copy of x2 4977 it should work. If not the email me at xbtool at alltell dot net. The BIOS will not be recognized after being patched for LBA48 until I get this next xbtool release out, but so long at you start with a good 4977 it should be ok. (As an alteneative to downloading a fresh copy of 4977, you could unchecking LBA48 and saving the file, then reload it and patch it for LBA48.) I'll probably get 1.0.8b8 out tonight or in the morning.

I've confirmed that this was a pre-release version of the Xbtool/LBA48 code (with known bugs) that was causing juan the problems he was seeing.  I'm actually relieved by this fact - it tells me that there isn't a big/unknown problem with the officially released LBA48 code.

As NghtShd suggests, getting the released version of xbtool should solve your problems.

Edit: Oops - maybe I spoke too soon (I haven't had my coffee yet).  I think the released Xbtool may also have this problem with X2 4977)  I'll take some time to verify this/talk to NghtShd about a possible new release of Xbtool.

Edit2: I really should have coffee before making posts like this: the 'released' version of Xbtool is in fact OK/does not have any known problems with X2 4977.  Ignore my 'Edit:' comment above.

- Paulb

[juan23]

 

ill post my results once im done

[juan23]

actually 1 last question for you, when i do make my new bios, do i need to add the info to evox.ini? or not even worry about it?

[cgladue]

...