Print

[athlonoc]

If I go into setting menu, then its in there.

Listing

C
D
E
F = 129gig
G = 0
X
Y
Z

I haven't put a new evox.ini in the root of 'C' just copied over the 3.5meg patched evoxdash.

I know my signature shows the true blue mod but this isn't back on at the moment just evox.

[athlonoc]

oz_paulb

I've come up against a brick wall

I've just used slayers 2.1 installer.
Selected install new large HDD.

Waited for it to finish.

Then copied over my patched evoxdash.

It is still showing in system utilities all 7 partitions and 'G' as having no free space and with 'F' as having 129gig

Should I replace the evox.ini after the new slayer install with a modded one?
When creating new bios I only tick enable LBA48 and not the other box - is this right for using only 'F' but larger than 137?

Can anyone send me a bios that they have that this works on.

Thanks

Lee

[athlonoc]

oz_paulb

I have just installed fresh 2.1 slayer evox.

I have only 129gig spare on 'F' but it should be around 170gig

Non-patched as you suggested.

How can I tell if the bios is good for this.

Can you guide me a little further, or even send your bios over to me, and I'll put that in.

Big thanks if you can.

Once I know the bios is definately OK, then it must be the drive I bought.

Lee

[athlonoc]

T H A N K S oz_paulb

It's now sorted.

I hope anyone following this thread has learned from it like I did.

Bios seems to have been the problem.

Now showing full hard drive free space.

What a bloke paulb is.

[heinrich]

QUOTE (oz_paulb @ Sep 9 2003, 11:09 AM)

Does the 'patched' EvoX that's 'in the usual places' include a new evox.ini/skin.ini file (with G: display in the skin)?  If so, it may always show "0" for G: - I don't think anything is 'smart' enough to recognize that G: doesn't exist/should not be shown.

No, but in the readme, it does say that evox.ini/skin.ini will need to be edited.  Even before you do this, G still shows up on the Settings page.

BTW: I patched 4977, works on 2 xbox's, both with maxtor 160gig drives. (different models though)

[pbot]

I also had problems with xecutor bios 4977 and a western digital 200gb HD.  I tried both allocating all the space on F and 137 on F and the rest on G, but neither would work at all.  I re-flashed with 4976.02, re-formatted G, and all is working now.

Thanks

[logan6988]

QUOTE

QUOTE QUOTE (logan6988 @ Sep 8 2003, 04:02 PM) so if i want to get the most out of my 160 gig hdd then i have to reformat the f partition with the bios patcher in xbtool? or do i just apply the patch to the bios in xbtool then patch the evox also? sorry if that was confusing..    That is your decision. You need to do one or the other. Either patch the bios for a larger F, and format F, or patch the bios and evox, and format G.

if i just patch my evoxdash.xbe, then format G, will i lose ne thing on F,, i mean will it automatically format F? I have a lot of backups and a 160 gig HDD, what do i need to do to not lose ne thing on F,C, or E, but make a G partition to allocate the remaining gigz too? thanks

[logan6988]

ne one know ^^^^^^^^^^^^^^^^^^^^^

[stormace]

Take the format strings for other drives out...leave the format g: string in only in evox.ini.  should be good to go