xboxscene.org forums

OG Xbox Forums => Dashboard Forums => EvolutionX Forum => Topic started by: athlonoc on September 07, 2003, 11:39:00 PM

Title: Patched .xbe 137>
Post by: athlonoc on September 07, 2003, 11:39:00 PM
If I buy a 200gig HD to replace my 80gig HD, I presume I can just install evox as before and then patch it with the new patcher.
But will I need to alter the bios to support this, or does the patcher do all that is needed.
I have never got xbtool to work to alter bios, as I see the new one has a tick box for LB48 suport.

Thanks

Lee

Title: Patched .xbe 137>
Post by: athlonoc on September 08, 2003, 01:38:00 AM
I see if I refer back to x2 4977 bios I can add the LBA48 mode.

Again do I need to do this and use this bios in order for the evox >137gig to work.
Title: Patched .xbe 137>
Post by: heinrich on September 08, 2003, 02:50:00 AM
You need to:

Patch your bios for LBA48
AND
Either patch evox yourself, or find a patched one 'in the usual places'
Title: Patched .xbe 137>
Post by: athlonoc on September 08, 2003, 04:06:00 AM
Looking at XBtool - to use the whole of F should I tick the 'ignore partition table' as I'm going to use a new hard drive.

Thanks

Lee
Title: Patched .xbe 137>
Post by: Xeero on September 08, 2003, 04:23:00 AM
QUOTE (stormace @ Sep 8 2003, 07:29 AM)
Only question is, XtoolBox and BoxExplorer doesnt see the G drive.  If I had a choice, I'd put all the gigs on F.  Less hassle...but AutoItem all works, sees everything I put on the G.

Just like EvoX had to be patched to recognize the G partition, so do other apps like Xtoolbox and boXplorer.  I know development on boXplorer has halted, so if anything there will be a 3rd-party patch, and who knows when that will come.
Title: Patched .xbe 137>
Post by: logan6988 on September 08, 2003, 12:02:00 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.. beerchug.gif
Title: Patched .xbe 137>
Post by: Motocrossman on September 08, 2003, 03:11:00 PM
what are u doing with the old 80gb?
Title: Patched .xbe 137>
Post by: logan6988 on September 08, 2003, 06:10:00 PM
me?
Title: Patched .xbe 137>
Post by: heinrich on September 08, 2003, 06:15:00 PM
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.. beerchug.gif

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.
Title: Patched .xbe 137>
Post by: athlonoc on September 09, 2003, 02:43:00 AM
Ok people, I'm not quite there.

I have just installed new 180gig drive.

I have patched bios 4977.01 to allow lba48 (first tick only on xbtool only)

Looking at evox I shows me 129gig spare on 'F'

But free space on 'G' is blank

I didn't want 'G' there I wanted all assigned to 'F'

Can someone tell me what I did wrong.

Thanks

Lee
Title: Patched .xbe 137>
Post by: athlonoc on September 09, 2003, 04:36:00 AM
Hi there

Yes I did all you have mentioned.

I have flashed the bios for use with a new drive ( 1st tick only to use all of 'F' ) is that right.

Then put onto the drive the moddified dash and in the settings menu it shows 'G' as having no space allocated, but it shows up. Also is this right for sole use of 'F'

My HD is an IBM GXP180 180gig
I have tried using flashFXP to try and re-format either 'F' and or 'G' but is keeps telling me the site is not implented ---- what does this mean.

I am well frustrated to death, as I know this should work.

oz_paulb - do you have any suggestions
Title: Patched .xbe 137>
Post by: athlonoc on September 09, 2003, 04:39:00 AM
Oh - one other thing.

When I put in the fresh drive I used evox auto installer to to format and prepar the drive.

Used the option Format F with DHCP

Is this OK, as I looked at the evox ini with this installer and it said it does this

Info "Install 4034 Dashboard"
Warning "This will format all drives"
Warning "Install msdash 4034"
Warning "Flash BIOS to Evox 2.4"
Progress "Now Installing 4034 Dashboard"

????????????


Thanks

Lee
Title: Patched .xbe 137>
Post by: athlonoc on September 09, 2003, 05:40:00 AM
Thanks mate,

I will try the 2.1 installer first.

Also just to inform, I was using evox 3752 ( latest version )

And I used a bios that changed colour just to do just that - making sure it was actually different.

I'll come back if thats OK,

otherwise if I get sorted then thanks for your time and this known great program.

Lee
Title: Patched .xbe 137>
Post by: athlonoc on September 09, 2003, 06:09:00 AM
Just reflashed bios as a 1024.bin version on the X2pro
Changed colour and it shows up fine

Had a look again and still shows 'F' as 129gig spare and 'G' as 0

I have slayers 1.5 installer haven't got 2.1

I'll give that one a go first and if no luck get hold of 2.1

Lee
Title: Patched .xbe 137>
Post by: athlonoc on September 09, 2003, 07:02:00 AM
Just for the info in case others have similar problems. As it stands slayers 1.5 didn't work either. Will try 2.1 and start again with that one.

I'm beginning to think the worst, and that this IBM drive may not be compatible.

But I'm puzzled as to why my settings show a G drive with the modded evoxdash when the bios was created with only the first tick not to include a 'G' drive.

Maybe this is wrong?

Lee
Title: Patched .xbe 137>
Post by: athlonoc on September 09, 2003, 07:29:00 AM
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.


Title: Patched .xbe 137>
Post by: athlonoc on September 09, 2003, 08:12:00 AM
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
Title: Patched .xbe 137>
Post by: athlonoc on September 09, 2003, 09:36:00 AM
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
Title: Patched .xbe 137>
Post by: athlonoc on September 09, 2003, 10:29:00 AM
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.
Title: Patched .xbe 137>
Post by: heinrich on September 09, 2003, 12:27:00 PM
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)
Title: Patched .xbe 137>
Post by: pbot on September 09, 2003, 08:12:00 PM
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
Title: Patched .xbe 137>
Post by: logan6988 on September 10, 2003, 02:57:00 PM
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 beerchug.gif
Title: Patched .xbe 137>
Post by: logan6988 on September 13, 2003, 10:22:00 AM
ne one know ^^^^^^^^^^^^^^^^^^^^^
Title: Patched .xbe 137>
Post by: stormace on September 13, 2003, 10:25:00 AM
Take the format strings for other drives out...leave the format g: string in only in evox.ini.  should be good to go