Print

[phatdak]

Hi guys,

I've been researching for a week now with now luck..


I have 4981.06 bios and am looking to stay with a 256k bios.



I have all extra space to F:


I have used xbpartitioner even though it gives the error message for this bios (but I keep hearing that it should still work... to ignore the warning..)


seems like I cant get xbpartitioner to make an f & G (havent tried yet with .67 bios).. but I keep reading about how F: with a 32k cluster size should work..


here is what I have gotten so far.. I hve reformatted various times & have had to load up the drive twice (2-3 days of FTPing files) yet I still seem to get corrupt data.


what can I try? please keep in mind I am looking to stay with a 256k bios which is why I am not talking about the larger bioses like the 5035.

If I use the .67 bioses xbpartitinoer still gives me the "not supported" message.. should I still try it? Has anyone used a 500gb drive with any luck? Can I keep it all in F:? (I know that theoretically the answer is yes.. but has anyone tried it? with this bios?


I have modded many boxes.. but never with this large of a drive.. now I have been modding a few with 400gb + up sizes.. but seems the only ones that are coming through with no problem are the soft mods which use f&G.


Please help.. I do not wnat to keep trying to ftp files into the box only to see them going corrupt..


(one other thing i noticed.. some games do not load on my box.. but the same exact files load on a new box i am working on... is this due to the corruption? The files at the beginning of the drive still seem fine though.. arent the first files usually the ones that go bad as you keep adding data..?)



Thanks guys.. i totally appreciate any help you can offer!!!

[phatdak]

wanted to add this comment..

I am working on a version 1.4 box using a TSOP mod with a 256k bios.

what bios will be the correct one to use when installing a 500gb drive? I know it sounds simple enough.. but I continue to get corrupt data

[phatdak]

So it seems like I may have finally gotten my 500gb drive to work properly..  I guess xbpartitioner did it's job.. (i must have been confusing a few non-booting games for a corrupted drive..)


BUT check it.. It stilldoesnt make sense to me...


I am currently working on a different box.. same scenario.. 256 k bios.. after seeing that my other 500gb seemed to be working I did it all over again fo this new box.

flashed chip, formatted the drives using evox... added my xbmc..

NOW.. I used xbpartitioner to format my f: into one large drive. I read the warning saying  "will not create custom partitions on this unsupported bios" (i am using 4891.06) it also says.. "will format F; as one large drive".. so cool.. so far ok. so here goes.. I run xbpartitioner.. BUT i see NO confirmation of 32k clusters or anything... (well I never saw this when I did mine either.. so i kept on). Just to be safe.. I ran xbpartitioner again..

so.. i would assume it's all working...


well... 2 days of ftp-ing files have gone by.. I am at about 260gb so far in filling this new drive.. when all of a sudden i am getting transfer rate drops (my first sign of something wrong), performance drops & my first game loaded is now no longer booting up...



any ideas guys..?!?!?

Please help... I am not an inexperienced modder.. I just can't seem to figure out these larger drives..


Thanks..


BT

[Joshatdot]

what version of XBPartioner are you using?

Is the 4981.06 BIOS you are using modified with XBTool?

This post has been edited by Joshatdot: Nov 30 2006, 07:32 AM

[phatdak]

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)

[AgentEB]

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.

This post has been edited by AgentEB: Dec 3 2006, 04:04 AM

[phatdak]

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: