Print

[slumberpod77]

ok so can someone help me break this down so that i am certain i understand it properly:
way back, the hacked BIOSes in use did not have proper LBA support, so partitions larger than 137 GB would not work properly, resulting corruption when more than 137 GB of data was written to a given partition. basically all the BIOS's now in use have proper LBA support, and thus can deal with partitions up to 256 GB in size. the 256 GB limit is a limitation of the FATX file system, and thus cannot really be "fixed".

also, the partition table for the harddisk is not actually stored on the harddisk in the usual way, and is instead stored within the BIOS currently in use, which means that the way in which your harddisk is formatted and your BIOS MUST match or you'll have data corruption problems. this is why there "F only" and "F/G" versions of BIOS's.

i am currently using a 250GB harddisk with Krazy's Ndure softmod package installed. i believe i am using the nkpatcher BIOS utility. i know for certain my current BIOS is F: only.

i am thinking about swapping in a 320GB harddisk. given the above information, i think that i MUST switch to an F/G bios, and it would seem that i could use such a harddisk with such a BIOS without any issues, as the F: partition would be 137 GB, while the G: partition would be something like 170 GB.

is the above information correct?
also, does anyone have advice for how i would go about switching the BIOS loaded by nkpatcher? i am not very familiar with how it works as i previously used PBL and haven't had a need to get real close & friendly with nk yet.

[_iffy]

QUOTE(slumberpod77 @ May 4 2006, 09:50 PM)

basically all the BIOS's now in use have proper LBA support, and thus can deal with partitions up to 256 GB in size. the 256 GB limit is a limitation of the FATX file system, and thus cannot really be "fixed".

Newer bios' yes. FATX - no that can be fixed. You gotta change your cluster size from something to something else.

QUOTE(slumberpod77 @ May 4 2006, 09:50 PM)

also, the partition table for the harddisk is not actually stored on the harddisk in the usual way, and is instead stored within the BIOS currently in use

it's stored on both. When you format your HDD, it formats based on what your bios partition table says. Once your HDD is formated (eg: f:\ = 137gb) It doesn't change. You can however change your bios, but no conflicts will take place until the next time you format your HDD.

QUOTE(slumberpod77 @ May 4 2006, 09:50 PM)

...which means that the way in which your harddisk is formatted and your BIOS MUST match or you'll have data corruption problems. this is why there "F only" and "F/G" versions of BIOS's.

all wrong. Your HDD is formated based on what your bios wants. The reason for the .06 and .67 is so you don't have to edit the bios. ease of use. evox bios' you have to set it useing evtool.

QUOTE(slumberpod77 @ May 4 2006, 09:50 PM)

i am thinking about swapping in a 320GB harddisk. given the above information, i think that i MUST switch to an F/G bios, and it would seem that i could use such a harddisk with such a BIOS without any issues, as the F: partition would be 137 GB, while the G: partition would be something like 170 GB.

you got it.

QUOTE(slumberpod77 @ May 4 2006, 09:50 PM)

also, does anyone have advice for how i would go about switching the BIOS loaded by nkpatcher? i am not very familiar with how it works as i previously used PBL and haven't had a need to get real close & friendly with nk yet.

Here's were i can't help you... Your softmoded, not TSOP'ed or chiped... you shouldn't even have a bios to worry about.

Is this a BFM bios your useing?

[torne]

nkpatcher doesn't load a bios. Krayzie's NDURE installer has both versions of nkpatcher, one that uses a .06 partition config, one that uses .67. You can use the extras app that comes with the exploit to switch between them. Kingroach's PC NDURE installer lets you choose during the setup process. Other exploits you may have to compile a new nkpatcher yourself (or switch to krayzie/kingroach's setup). This isn't anything to do with bioses, go read the pinned topics in the XBE Exploits forum.

[heinrich]

You can use a .06 configuration, and format your F: drive with 32k clusters, using xbpartitioner.

[nachomans]

Sure...you have to use a bioss that doesnt ignore partition table (check this with xbtool/evtool)
And format your HD with xbpartitioner (this program makes 32k cluster partition automatically if detects more than 250gb...)
If you have your hd formatted with another program, sure you have 16k cluster....so the only way to fix, is format again your F drive, the other partitions could remain with 16k clusters...