New HDD w/5035, am I missing something?

[Big_Whoopin]

Just got a good deal on a Seagate 'cuda 160GB, so I'm replacing my 80GB. I've got X2CL 5035 on the box with the default LBA settings, F gets all. Not having available time to do much messing around I used the same EvoX boot disc to install the 160GB that I had used to install the 80GB. This was created based on the sticky located in the HW mods forum, I think. I know there are limitations regarding 137+GB HDDs, but conditions didn't allow me to look it up at the time. Ran the setup and was expecting not to see the full remainder of the 160GB pick up on F. Well, once the drive was installed and the partitioning done EvoX reported that I have 150+GB on F. WTF? Is this correct and usable, or if I start packing data beyond that 137GB boundry will I have probs?

I've seen posts (here and xbox-scene) where the 137GB limit is mentioned and the use of a G drive is recommended, but nothing that tells me what to expect if I've got a 137+GB drive and *don't* use a G drive. Some of these threads were old and may be out of date, circa '02. From the X2CL features it sounds like I can have a hugo F drive (patched byte=1, F gets all), a large F drive with the rest to G (2, F up to 137, G gets rest) or a large F drive and the rest in limbo (3, F up to 137, no G). As it stands now, do I have anything to worry about?

Hate to be a thread starter but I didn't turn up anything useful in my searches.

-Whoopin'

 

[PFIDR34]

what version of evox 3935? Also the bios rar includes instructions on LBA48 patching.

 

[Big_Whoopin]

Without having it in front of me, best I can say is that it was the latest as of a couple months ago... 3935 sounds about right. I used this thread (http://www.teamxecuter.com/forums/showthread.php?t=23865) for the original upgrade to 80GB, then again with the same disc for the 160GB. I've read the LBA48.txt file, which contains about as much detail as in the bottom of the feature list here - http://www.teamxecuter.com/forums/showthread.php?t=29722. It tells me how to patch the BIOS, but doesen't go into any great detail as to why I should choose one setting over the other.

I guess the meat of my question is just how large can F be with the LBA48 set to default (1) where F gets all? Is EvoX reporting what is actually usable, or just what the size of F is based on the partition start and end points?

-Whoopin'

 

[PFIDR34]

I use a 250 GB maxtor and F gets and sees it all! I dont really remember if evox will see one that big... Try a better dash... XBMC

 

[Big_Whoopin]

EvoX is just what I had used for partitioning and formatting the drive and it was the first place I saw the numbers. It did report the correct amount of space for the partition created, I just didn't know if the file system properly supported it. Sort of like how MS DOS didn't support partitions over 2GB or something like that, although certian utilities would allow you to create them. I don't think it's a dash concern, and I use Avalaunch as my primary anyway.

I've since had time to poke around with a few file managers and everything looks ok. Free space + used space is adding up to about 150GB. Your confirmation that your 250GB has F picking up all the extra space seems to ice it. I assume the partition 7/G drive options are probably just around for personal preferenace or backwards compatibility with drives already formatted/partitioned in that fashion?

-Whoopin'