QUOTE(Joshatdot @ Nov 30 2006, 07:30 AM)

what version of XBPartioner are you using?
Is the 4981.06 BIOS you are using modified with XBTool?
Hi Josh..
as far as using XBTool.. yes I did.. but LBA48 support is by default on the 4981 bios.. you can't even change it.. it's greyed out. But it IS supporting large disks..
as far as XBpartitioner.. I think I may have finally narrowed it down.. I'll know in another 2 days..
seems that I was mistaking XBpartitioner 1.0cr with 1.0
I was using both.. not really realizing it.. & I think this may be why I have been getting mixed results with the different boxes. I wasn't noticing any confirmation on the "forfmatting using 32k clusters".. but then I realized I was probably using the wrong version of XBPartitioner. I have just reformatted using XBPart 1.0 & I noticed the confirmation of the 32k clusters.. soooooo.. I hope this works.. I'll know in another 2 days..
But so far.. it seems like that may have been it.. I have one 500gb xbox fully loaded up.. (alot is just junk data to push the drive to it's limit..). I'm keeping my fingers crossed for this next one..
If this second goes works well.. I will be a happy man.. & this will confirm to me that YES a 256k bios - 4891.06 can properly support a 500gb drive all in F: with the use of XBPartitioner 1.0 (NOT 1.0cr)
QUOTE(AgentEB @ Dec 3 2006, 04:03 AM)

umm..yeah if you have a HDD that is greater then 250 GB, it is recommended you will have to use the 4981.67 bios and not the 4981.06 bios. the .67 bios is designed for larger hard drives. dunno if you have to go back in with xbtool and edit the bios. but what you really want the bios to do is "F gets up to 137GB, and G gets the rest" then you will want to use xbpartioner to set the clusters to 32k. this will rid you of your corruption problems. btw, the 4981.67 is also a 256k bios.
Thanks Agent.. Everything seems to be working ok now.
I have a 500gb drive fully loaded up & it seems to be working fine. All space is on F:. I wanted to keep it this way, which is why I was using the .06 & not the .67
It seems that the real problem was that I was confusing XBPartitioner 1.0 with XBPartitioner 1.0CR.
Here's what I got goin' on in that particular box...
xbox 1.4
TSOP
4981.06 (256k)
500gb drive
XBPartitioner 1.0 (not XBPartitioner 1.0cr)
all drive space is set to F: