Print

[GrumpY]

Is there a way to make another forum for all the "stupid" questions people asked because they didn't read the original topic about drive > 137 Gb.

I really think this topic will be fucked up if pbs reports are coming in the same time that the "practical" questions every man who didn't read the rest will posts again and again.

A message to every one : Please read the FAQ, the threads. all the answers are already available for most of us and let oz_paulb have constructive return of his amazing work !!!!!!!!!!!!!!!

[Blastomy]

QUOTE ((>Stormy<) @ Sep 2 2003, 01:56 AM)

I thought that this was very funny in light of recent discoverys... Western Digital 200GB Internal drive look at the ATA/100* interface part of the descript.  "[Ultra ATA/100 interface*] *Includes Promise Technology Ultra ATA/100 card to break the 137.0GB barrier found on many PCs."   Does this mean something to anybody?  Would this be an ideal drive?   Anywho... thought it was interesting. Oh... and thank you very much for this gift, very clever

Yeah It means it comes with a controller card for your comp so you can plug it in and see all 200gb

[gabvey]

gabriel

[oz_paulb]

QUOTE (gabvey @ Sep 2 2003, 10:49 AM)

This is really an impressive work. Many thanks Paul ! I have a question about xboxlive. In order to reach xboxlive, I disable the my modchip, using the original bios on the main board. Therefore this bios will use lba32 to manage the disk. Is there any risk of data corruption ? I didnt fully understand the partition table stuff. Will the orginal bios be able to deal with this table ? I think that I'm gonna buy a new drive soon gabriel

An original bios will use LBA28, and doesn't "see" F: (partition6) or any extra partitions.

It should work fine when booting with the original bios - you'll be able to access the 'standard' partitions (C/E/X/Y/Z), but just not the new one(s).  Re-booting with the LBA48-enabled bios will make the new partition(s) visible again.

And, again, since this is 'beta', YES - there is risk of data corruption (please wait until more testing has been done if you are concerned about data loss).

- Paulb

[oz_paulb]

QUOTE (peach_nick @ Sep 2 2003, 06:47 AM)

Ok, thanks to Paul for the kernal. I got my 160 WD to be fully recognized. but........... I copied my f to my computer before flashing and reformating partition 6 with fxp and then dumped my f back after i had the drive fully recognized. When i tried to run any of my games or appz none ran the loading screen just stuck, every thing else seems to be fine. I'm gonna try to ftp over the original appz(not from backed up drive) 2morrow and see what happens then. if any body can help me out it would be appreciated.

I'd really like to hear back from you on whether/not this is still a problem.

If it is, please give details of exactly how you formatted the drive, whether/not you re-booted after formatting (I don't know if this is important or not), etc.

If you're re-starting by reformatting again, please try copying just one app/game, running it, and (if it works) add a few more apps, try running them, etc.  Maybe there's a barrier where data corruption is happening.

- Paulb

[the joker]

gonan try to make a .3 of avalaunch that had added support for this. Wonder if r0wdy would test that format command.

[oz_paulb]

Will someone please post a list of standard drive letters for the Xbox (including memory card drive letters)?  It was posted before (in the super-long 137GB forum, I think).

I think that we should come up with a 'standard' drive letter for "partition7" (and maybe "partition8", ...), as opposed to every app/dashboard coming up with its own letter assignments.  I think (the obvious choice of) "G:" is already used by memory cards, so that probably shouldn't be used.

(As I've said before, I think the better long-term solution is to show the user a list of partitions/let them choose, but near-term drive letters are easier).

- Paulb

[peach_nick]

Well I used fxp to remove my problemed appz and games from my last post and ftpd over my origanal downloaded appz and they work fine.

Paul,
I am almost positive that i flashed new bios, then formatted with fxp and did not reboot before i dumped my old f drive data over to my box. im sure this had something to do with my problem.

[phoenix-lizard]

The memory cards hold "partitions"  H,I,J,K,L,M,N,O.
Hope this helps.

[Noobicide]

OK, A: and B: are available as always

I might suggest something here though.

the so called drive letters don't have to be a single letter.

its a carry through from back when you could only make 32MB partitions and would have an ungodly number of them on a 200mb drive (yes there were people who ran fat12 on 200mb drives, usgovt being one of them)
in that situation you would have AA: AB: and so on. (assuming multiple drives in the same system) also for when you mounted a few dozen network shares

in actuality, you can have anything up to IIRC 11 characters as a device name, although it may be longer.

anywho, I've sucessfully tested long device names, and nexgen uses them in 1.0 and my new dash/os project uses similar names:

System:  - Xbox dashboard & data files
DVD: - First / Single dvd drive
DVD2: - Second dvd drive
Storage: - 5GB E:
Extended: - Rest of drive to 137GB
Expanded: - Drive above 137GB

It would be nice if someone could post the long device names for the memory cards so they could be mounted on meaningful names ass well such as MU1A: MU3B: and so on.

[KiLaHuRtZ]

C - System Files - Approx. 500MB
D - DVD-ROM
E - Game Saves - Approx. 5GB
F - Media - Rest Of HDD
G - [POSSIBLE PARTITION 7]
H - MU 1A - Approx. 8MB
I - MU 1B - Approx. 8MB
J - MU 2A - Approx. 8MB
K - MU 2B - Approx. 8MB
L - MU 3A - Approx. 8MB
M - MU 3B - Approx. 8MB
N - MU 4A - Approx. 8MB
O - MU 4B - Approx. 8MB
X - Cache - Approx. 750MB
Y - Cache - Approx. 750MB
Z - Cache - Approx. 750MB

[KAC]

QUOTE

I have a 160gb and chose option to have partition 6 take rest of drive just to see what happened. The good news is that sure enough, I got and extra 20 or so GB!! But all my games, etc that were on partition f: were gone!! Or were they? If this happens...DON"T WORRY!! Just reflash your bios with option to use >137gb on partition 7 and all your items will reappear.

Am I understanding this correctly?

1.  You had a 160GB hard drive with 23GB's not being used because of the 137GB
     limit.
2.  You edited a BIOS using Xbtool and chose the "partition 6 take rest of drive"
    option.
3.  Flashed your BIOS and found that you now had the full 160GB usage with the
    extra 23GB on F: but you couldn't see any of your games.
4.  So you reflashed your BIOS again and now all games were visible?

In essence, you just have to flash the BIOS twice to have all the 160GB's recognized with the extra space on F: without messing up any of your existing data?

Please confirm!!!

PS...YOU DA MAN OZ_PAULB!!!  

[oz_paulb]

QUOTE (KAC @ Sep 2 2003, 06:25 PM)

QUOTE I have a 160gb and chose option to have partition 6 take rest of drive just to see what happened. The good news is that sure enough, I got and extra 20 or so GB!! But all my games, etc that were on partition f: were gone!! Or were they? If this happens...DON"T WORRY!! Just reflash your bios with option to use >137gb on partition 7 and all your items will reappear. Am I understanding this correctly? 1.  You had a 160GB hard drive with 23GB's not being used because of the 137GB      limit. 2.  You edited a BIOS using Xbtool and chose the "partition 6 take rest of drive"     option. 3.  Flashed your BIOS and found that you now had the full 160GB usage with the     extra 23GB on F: but you couldn't see any of your games. 4.  So you reflashed your BIOS again and now all games were visible? In essence, you just have to flash the BIOS twice to have all the 160GB's recognized with the extra space on F: without messing up any of your existing data? Please confirm!!! PS...YOU DA MAN OZ_PAULB!!!

The second time he flashed, he chose a different Xbtool option (Partition 6 up to 137GB / Partition 7 rest of drive).  This made Partition6 the same size as it was before LBA48 support was added, so the FAT file structures were valid/everything re-appeared.

After doing this, the extra 23GB is in Partition7 (not part of F:).

Basically, he shouldn't have chosen "Partition 6 takes rest of drive") if he wasn't planning on re-formatting F: (I think he did this before I made that clear).

- Paulb

[boxorox]

QUOTE (KAC @ Sep 2 2003, 06:25 PM)

QUOTE If this happens...DON"T WORRY!! Just reflash your bios with option to use >137gb on partition 7 and all your items will reappear. Am I understanding this correctly? 1.  You had a 160GB hard drive with 23GB's not being used because of the 137GB      limit. 2.  You edited a BIOS using Xbtool and chose the "partition 6 take rest of drive"     option. 3.  Flashed your BIOS and found that you now had the full 160GB usage with the     extra 23GB on F: but you couldn't see any of your games. 4.  So you reflashed your BIOS again and now all games were visible? In essence, you just have to flash the BIOS twice to have all the 160GB's recognized with the extra space on F: without messing up any of your existing data? Please confirm!!! PS...YOU DA MAN OZ_PAULB!!!

KAC:  He wrote that he reflashed with the option to use >137gb on part 7

It sounds to me like he added the extra space to part 7, after he couldn't see is data in F.

[juan23]

I know you mentioned this before, but what is the likleyhood that the remainder of the 160 gig hdd to be added to partition E, making f showing the full 137gb, and thremainder showing up in E?