Print

[StormLord]

QUOTE (elfey1 @ Sep 7 2003, 08:59 PM)

i followed this post (or one very similar) a month or two ago, and it didnt seem like it was ever gonna happen.    well im damn glad i didnt go out and get that 120GB drive i was gonna get. Does this work on all versions of the xbox (1.1), modchip (mines a x-ecuter 2 lite), and dashboard(evo-x 1.8.3752) Sorry if this has been covered but im very conscious of screwing up cus i seem to be so damn good at it. Thanx

It should work with no problems, just use NghtShd's XBtool Beta 1.0.8b9 to edit the BIOS (I suggest using X2 4977).

------------

Thanks Paul for the great work and Thanks NghtShd for the BIOS tools!! Great work Guy's!!!

Just a few things noticed from converting from LBA24 to LBA48 on a 160 Gig HD, and am not sure if its the LBA "thing" or a FATX "thing" that making some differences.

The first thing I noticed when I "rebuilt" my HD using Slayer's 2.1 installer was that with the new large F drive (i.e. not making a G drive) the file name lengths seem to have been shortened (i.e. was able to install the playlists that were up to 43 characters long on the old system, but now can only use 31 character long names).

some Example

02 International Space Cadet Groove (128k).sc
06 ungkar dotnet We came from NORWAY (160k).sc
02 Andreas Winamp bara fÿr (192k).sc   <-wont install because of ÿ, but was able to on old LBA24

I don’t know if this is from the LBA48 or if the FATX truncates files name lengths more when the HD space becomes larger

Second thing was I noticed was the apps don’t seem to be reading the larger drive correctly. (I know the app developers need to correct this for their apps, I am just posting this out of curiosity on why they all read the same space differently)

some Example

Evox v1.8.3752 say's ~155 GB <- this has to be wrong
Px HDD v1.2a say's ~145 GB
DVD2XBOX v0.4.3 say's ~140 GB
Nexgen v095 say's ~148 GB
Media X Menu v 0.9n4 say's ~147 GB
Avalaunch v0.47.4 wont load
BoXplorer V0.96 say's ~ 148GB

I do believe that they all should be reading 148GB

Thanks again Paul and NghtShd for all your hard work, Its very much appreciated!!    

[GuySmily]

I'm pretty sure that I am unable to use many non-alphanumeric characters (- and _ work, but many others won't even let me upload), and that I am limited to 31 character names, and I'm not using the lba 48 patch (only have 120gig drive).  

Does EvoX give space in gigabytes?  You may be looking at 155.xxx.xxx.xxx bytes.  Divide it by 1024^3 and you get ~144gigs.. It looks like it would give you the same as px hdd.  It certainly does look like the apps are all doing something wrong, since they give different reports. It's probably in the calculations..

[oz_paulb]

QUOTE (StormLord @ Sep 8 2003, 01:28 AM)

QUOTE (elfey1 @ Sep 7 2003, 08:59 PM) i followed this post (or one very similar) a month or two ago, and it didnt seem like it was ever gonna happen.    well im damn glad i didnt go out and get that 120GB drive i was gonna get. Does this work on all versions of the xbox (1.1), modchip (mines a x-ecuter 2 lite), and dashboard(evo-x 1.8.3752) Sorry if this has been covered but im very conscious of screwing up cus i seem to be so damn good at it. Thanx It should work with no problems, just use NghtShd's XBtool Beta 1.0.8b9 to edit the BIOS (I suggest using X2 4977). ------------ Thanks Paul for the great work and Thanks NghtShd for the BIOS tools!! Great work Guy's!!! Just a few things noticed from converting from LBA24 to LBA48 on a 160 Gig HD, and am not sure if its the LBA "thing" or a FATX "thing" that making some differences. The first thing I noticed when I "rebuilt" my HD using Slayer's 2.1 installer was that with the new large F drive (i.e. not making a G drive) the file name lengths seem to have been shortened (i.e. was able to install the playlists that were up to 43 characters long on the old system, but now can only use 31 character long names). some Example 02 International Space Cadet Groove (128k).sc 06 ungkar dotnet We came from NORWAY (160k).sc 02 Andreas Winamp bara fÿr (192k).sc   <-wont install because of ÿ, but was able to on old LBA24 I don’t know if this is from the LBA48 or if the FATX truncates files name lengths more when the HD space becomes larger Second thing was I noticed was the apps don’t seem to be reading the larger drive correctly. (I know the app developers need to correct this for their apps, I am just posting this out of curiosity on why they all read the same space differently) some Example Evox v1.8.3752 say's ~155 GB <- this has to be wrong Px HDD v1.2a say's ~145 GB DVD2XBOX v0.4.3 say's ~140 GB Nexgen v095 say's ~148 GB Media X Menu v 0.9n4 say's ~147 GB Avalaunch v0.47.4 wont load BoXplorer V0.96 say's ~ 148GB I do believe that they all should be reading 148GB Thanks again Paul and NghtShd for all your hard work, Its very much appreciated!!

It doesn't make sense to me that going to a larger hard drive size will change the allowed lengths/characters in filenames.

Note that FATX has a limit of 42 characters in a filename.  This shouldn't change on larger drives.

Filenames in the FATX directory are terminated/padded-out with 0xff characters.  That happens to be the same value as the "ÿ" character.  So, that could explain why you can't have that character in a filename.  It wouldn't explain why it would have worked in the past, though.

What if you try copying/creating the same files on drive E:?  There should be no difference between E: and F: as far as filenames go.

As GuySmily pointed out, "GB" is computed differently by different apps.  1GB according to hard drive manufacturers is 1,000,000,000 bytes.  In 'binary', 1GB is actually 1,073,741,824 bytes.  That would explain some of the differences (EvoX vs others), but not all of the variations shown by the others.

- Paulb

[stormace]

Sorry for double posting, but can people post their 200GB hd up here?  Model # and lockable or not.  Looking to upgrade now.

[cgladue]

i have a Maxtor Diamondmax 200GB 7200rpm 8mb Cache lockable

[elfey1]

QUOTE (StormLord @ Sep 8 2003, 01:28 AM)

QUOTE (elfey1 @ Sep 7 2003, 08:59 PM) i followed this post (or one very similar) a month or two ago, and it didnt seem like it was ever gonna happen.    well im damn glad i didnt go out and get that 120GB drive i was gonna get. Does this work on all versions of the xbox (1.1), modchip (mines a x-ecuter 2 lite), and dashboard(evo-x 1.8.3752) Sorry if this has been covered but im very conscious of screwing up cus i seem to be so damn good at it. Thanx It should work with no problems, just use NghtShd's XBtool Beta 1.0.8b9 to edit the BIOS (I suggest using X2 4977).

ive aquired both of the items that you mentioned (the 4977 bios and XBtool) ive unrarred the bios and obviously i end up with a .bin file, when i try to open it up in XBtool a msg box appears saying "kernel extraction failed. See logfile for more information." does anyone know what is happening?
Cheers
-elfey1

[elfey1]

ive PM'd you with a couple of questions i have.
Cheers

[KAC]

QUOTE

(also, for anyone worrying about speed issues with the 300gb Maxtors (because they are 5400rpm/2mb cache drives), I have noticed no speed difference, with loading times or anything else, between my new Maxtor drive and my old 7200rpm 120gb drive -- i've played KOTOR on both drives (a game with a lot of loading screens), and if there is a difference in load times, I haven't been able to tell)

Thanks gggie, I was wondering this exact thing.

[StormLord]

[hotzenplotz]

I am having some problems with the patch. I installed a new Samsung SP1604N into my xbox. I then tried to patch an evolution-x bios (it was one with a color and no-animation hack if that matters, Evox.D6) with xbtool. I wanted to use just drive f so i took that option. I then saved the bios and flashed my chip. When I now boot with Slayers 2.1 Installer-Cd i still do not see the whole 160gb. I then tried rebuilding the harddrive - no success. The option "format only drive f:" didn't help either. I used the just released xbtool version 1.0.8b11.

Now something that wonders me: if i re-open the same Bios that i just patched before again with xbtool, the patches i made specifically for the hdd part are not saved. It now has the "ignore hd partition table" option checked (i am certain that i did not check this) and it is set to "partition 7 takes up rest" (i am again certain i did not check this when first patching the file).
Is this just a bug in the bios-reading part of xbtool or did he really patch the whole bios incorrectly ?

//edit:

well, i now tried an xecuter4677-bios and still i dont have the full 160. Or at least it doesnt show them in the drive overview. Am I missing something simple?

[NghtShd]

QUOTE

Now something that wonders me: if i re-open the same Bios that i just patched before again with xbtool, the patches i made specifically for the hdd part are not saved. It now has the "ignore hd partition table" option checked (i am certain that i did not check this) and it is set to "partition 7 takes up rest" (i am again certain i did not check this when first patching the file). Is this just a bug in the bios-reading part of xbtool or did he really patch the whole bios incorrectly ?

Yeah, it's a bug in reading back the BIOS options. I forgot to adjust that when I moved the LBA48 code to a higher address.

[streaker68]

I had the same thing occur for me. I put in a Maxtor 160 GB and It only shows 129GB in slayer's. When I open the bios up in XBTool it show that I wanted to put extra space in partition 7, which is not acurate. Also the "ignore HD partition table is selected" is enabled. I understand there is a bug there, but should that prevent my drive from exceeding  129GB?

Thanks

[hotzenplotz]

I have now tried 3 different bios versions, all with the same result. I think the next thing I will do is try an older version of xbtool, maybe that helps. Any help or tips would be great.

[NghtShd]

Ok, LBA48 was still broken in b11. Sorry about that, but I it worked for me. However, my drive is 100GB so I can't test > 137GB support.

I think I've really got it fixed now. I sent the a BIOS to someone to test for me and he reported that everything works. I'm just make some last minute checks and then I release b12 today. If anyone wants to test a new XBtool build you can email me at xbtool at alltel dot net. I may get confirmation from someone else that it's working, in which case I'll go ahead and do the release. If you mail be before the b12 release I'll send you a copy to try.

[gcoghlan]

xbtool-108b12 did the trick for me. Previously (with xbtool108b11 and X2 4977) my Seagate 160Gb was only showing 137Gb, now 155Gb. Yeah Yeah.....Now comes the Maxtor 300Gb!!!!!