Topic: Xbpartitioner Release (Read 113 times)

heinrich · « **on:** August 04, 2004, 03:54:00 PM »

Just wanted to post publicly, great job NghtShd

Not sure if everyone realizes what can be done with this in the future (once totally custimizable partitions are allowed), but it is a fantastic development.

fff · « **Reply #1 on:** August 05, 2004, 01:05:00 AM »

Well, in fact, i'm not sure what this app can do.
Does it resize all the partitions (including C and E...but i don't think that's possible) or juste F and G?
I have a G drive, with this app and the bios changed, can i have only a big F drive?

Anyway NghtShd has already released great apps for the xbox scene...congrats

heinrich · « **Reply #2 on:** August 05, 2004, 03:47:00 AM »

with the fixed lba48 code, yes, you can change the partitions without have to reflash. The app only does 3 'schemes' right now, but yes, you will be able to resize all the partitions. Of course, resizing C, E, Z, Y, or Z will break compatibilty with retail bios's, but the choice is there

fff · « **Reply #3 on:** August 05, 2004, 05:31:00 AM »

Well, that's nice!
I will keep C,E,X,Y and Z size for the debug mode and so on, but i'll perhaps delete my G partition to have only one big F!
What is the exact way to do this without losing data? xbpartitioner and then bios change or i have to change my bios version and then use xbpartitioner?

nimbles · « **Reply #4 on:** August 05, 2004, 11:13:00 AM »

This sounds cool- would this mean people could run a HD >>137GB with just an F: or would the large F: partition problems around the 250GB mark still occur?

Also For dash's/Gamesaves to work properly, not to mention ingame music i assume and E: drive would have to remain?

nimbles · « **Reply #5 on:** August 05, 2004, 12:11:00 PM »

Thanks for clearing that up NghtShd

To be honest 120GB is plenty big for me (in that there are only so many games i would play at anyone time, and apart from a couple of multiplayer games i tend to wipe games off the hd once i'm done with them- i always have the originals if i really feel like a blast from the past- and for me it makes sense to stream my media from the LAN via xbmc)

but i can now see the possibilities for those with big fat hard drives- and those who want to put even bigger fatter hard drives in

fff · « **Reply #6 on:** August 05, 2004, 12:21:00 PM »

Thanks for the clearing NghtShd.
I think repartitioning c E X Y and Z would be a bad idea too. Data could get corrupt very fast if we select the wrong bios!
Anyway, thanks for this app that have a great future I think!
Funny to see that TX break the standards like ms does ^^

fff · « **Reply #7 on:** August 05, 2004, 01:23:00 PM »

I didn't meant to say they broke it intentionaly (not sure this is the exact english word ^^). It was a just a remark i found funny.

Scan-C · « **Reply #8 on:** August 06, 2004, 08:56:00 AM »

fff · « **Reply #9 on:** August 17, 2004, 12:44:00 AM »

i have read the end of the nfo since release 0.8. Now that we can modify partitions 1-5, what is really unsafe and in which case (under which bios in fact)?
Because i can't see how a bios can boot with a changed C partition

NghtShd · « **Reply #10 on:** August 17, 2004, 09:22:00 AM »

I'll put a full list in the next release, but you need to use any LBA48 BIOS except X2 4979 through X2 4983 (because X-ecuter did the LBA48 code on these and did not include the ability to read the table from the disk).

If the BIOS can read the partition table then it can boot with a changed C partition, though I don't really recommend changing C. The C partition's sectors are first on the disk so in order to change C you'd need to backup the entire disk. E is a good candidate for changing since, though it's partition 1, its starting sector is after the other standard partitions.

My E partition is currently 248GB and is working fine. However, I can't use a stock BIOS on this machine since the stock BIOS will think the E partition is the standard size. That's fine for me, because I never run a retail BIOS, but it's something you need to take into consideration.

The reason it can work is the partition table is always on sector 0 of the disk, so the kernel doesn't need to know anything about the filesystem in order to load the table.

fff · « **Reply #11 on:** August 17, 2004, 01:29:00 PM »

Thanks for the reply NghtShd.
Just another quick question : do develop your app, you boot on a debug bios. And this one too doesn't care that E partition is 248GB?
Thanks for this great app anyway

RiceCake · « **Reply #12 on:** August 17, 2004, 05:07:00 PM »

Guess debug BIOS'es are more friendly to corruption/differention from the standard setup.

Unlike retail where if one tiny thing is different you need to 'send it in', heh...

NghtShd · « **Reply #13 on:** August 18, 2004, 02:05:00 PM »

Kudos to X-ecuter for adding on-disk partition table support to their upcoming BIOS's. Even if you don't plan to repartition your drives, it will be good to have the table on the disk so the disk tells the BIOS what partition scheme it uses.

bucko · « **Reply #14 on:** August 18, 2004, 03:33:00 PM »

all is I can say is, wow.

Author Topic: Xbpartitioner Release (Read 113 times)