Print

[janson]

I just don't get it. afaik the limit is set because xbox uses ATA33 which can only support 137gb because of the limit of the LBA mode. However, ATA/ ATAPI-6, the prevailing version of the ATA standard so far includes UltraDMA mode 5 and the expansion of the LBA mode from 28 bits (with a maximum of 137 GB per drive) to 48 bits, but xbox doesn't use ATAPI-6 afaik.

What is it that i haven't understood correct?

[loveisweakness]

QUOTE (janson @ Aug 28 2003, 10:11 AM)

I just don't get it. afaik the limit is set because xbox uses ATA33 which can only support 137gb because of the limit of the LBA mode. However, ATA/ ATAPI-6, the prevailing version of the ATA standard so far includes UltraDMA mode 5 and the expansion of the LBA mode from 28 bits (with a maximum of 137 GB per drive) to 48 bits, but xbox doesn't use ATAPI-6 afaik. What is it that i haven't understood correct?

from what i remember reading not long ago when i was looking up some info when putting linux on an old computer the lba48 addressing scheme isnt dependant on the controller
i never put that to the test tho as i was just running it off a 4 gig hard drive

[fixxxer]

keep up the good work cant wait to drop my 200gig special edition in  

[chinmi]

keep up the good work

[hamtitampti]

As some people think i am talking nonsense

Look.

We had this discussion in cromwell and was a long discussion inside the xbox-linux team
and i know cromwell very good, as i am the main programmer now there.

i see not a problem starting the dashbaord
not even linux.

but i see a problem in most of the new games.
most new games, like HALO, matrix ....
compleate exit the kernel in RAM
and have a new kernel inside

so this games are not playable anymore, as they get corrupted data

there are hdd's > 137 Gybte, who have a lba compability mode, where this could work.
but note, not every hdd.
and even then, the hdd is limited to 137 GB again, which makes your fatx partition corrutped again.

again, i not only came on 24. august when paul published it.
i told this now long time ago.

But it seems, it is still hard for some people (..) to belive that this is the truth.
so i wish you all luck in your attempt to create a non-working bios for most of the games.

[janson]

QUOTE (loveisweakness @ Aug 28 2003, 10:30 AM)

QUOTE (janson @ Aug 28 2003, 10:11 AM) I just don't get it. afaik the limit is set because xbox uses ATA33 which can only support 137gb because of the limit of the LBA mode. However, ATA/ ATAPI-6, the prevailing version of the ATA standard so far includes UltraDMA mode 5 and the expansion of the LBA mode from 28 bits (with a maximum of 137 GB per drive) to 48 bits, but xbox doesn't use ATAPI-6 afaik. What is it that i haven't understood correct? from what i remember reading not long ago when i was looking up some info when putting linux on an old computer the lba48 addressing scheme isnt dependant on the controller i never put that to the test tho as i was just running it off a 4 gig hard drive

I doubt that it's that way. Anyone can confirm this?

[Troed]

QUOTE (hamtitampti @ Aug 28 2003, 11:15 AM)

but i see a problem in most of the new games. most new games, like HALO, matrix .... compleate exit the kernel in RAM and have a new kernel inside

... so, following your argument, those games would be immune to kernel hacks ... like ... IGR?

Can't say I've tried - maybe you have? (I see no point in using an Xbox for games)

Or, do you mean to say that those games would use their own methods for accessing the HD?

[oz_paulb]

I think I understand what Franz is trying to say, but the very first > 137GB drive I tried (a Maxtor DiamondMax Plus 200GB 7200 RPM Ultra ATA/133 drive) seems to support the 'special compatibility mode, since it worked out of the box as a < 137GB drive (LBA-28 mode), and seems to be working so far in > 137GB mode.

QUOTE

but as people sure are "more intelligent" as i, please consult ATA/ATAPI 6.0 specification. It is written very clear there, why the "using in both worlds" is not possible.

Can you point me to a specific chapter/section # of the ATA-6 spec where it's written so clearly?  I haven't read the entire spec, but it doesn't appear to have any big warnings about incompatibility.

In the meantime, I'm continuing with my testing.  My test app has been running, filling the F: drive with unique files (has written about 60GB in LBA-48 mode so far without errors - when it's filled the disk, I'll go back and verify everything).

As with any Xbox hack, people should be careful.  I'm not going to make any guarantees that every > 137GB drive will work - maybe Franz is right and only certain "> 137GB" drives will work on the Xbox.  In that case, a list of 'known good' drives can be published - as more people experiment with the new KERNEL.

As someone else pointed out, Xbox-Linux seems to work with LBA-48 just fine - again, maybe they've been lucky with the specific brand/model of drive they purchased.

- Paulb

[oz_paulb]

I just looked at the side of the box for my Maxtor 200GB drive ("System requirements").  It says:

QUOTE

Drives larger than 137GB require Windows 2000 SP3 or higher, XP SP1 or higher, or ATA/133 PCI card

This certainly sounds to me like it'll work on any PC (including Xbox) as long as your software drivers are up to date (have support for LBA-48).  There doesn't seem to be any hardware incompatibilities with 'old' PC's (like Xbox).

Maybe the Maxtor drive is unique - if so it looks like I was lucky in my first purchase of a "> 137GB" drive.

- Paulb

[krawhitham]

QUOTE (hamtitampti @ Aug 28 2003, 09:02 AM)

Sorry to write here, paul but i hear this discussion now since weeks. and it is false. First, you should tell all people that if you enable lba48 (which is simple) you can not access the data with an normal kernel anymore From a Windows Support Site >If you enable 48-bit LBA support on a system that does NOT have a 48-bit LBA- >compatible BIOS, and a hard disk larger than 137 GB, you will experience data >corruption. but as people sure are "more intelligent" as i, please consult ATA/ATAPI 6.0 specification. It is written very clear there, why the "using in both worlds" is not possible. Good luck for your non-working & incompatible system . franz

you're not a dick or anything are you

not everyone will to use a "normal kernel".  I installed a homebrew mod and have never had a problem or a desire to load the "normal kernel" since

if you are talking about the soft mod users, he said he did not know if it would work.

Get a clue most users have a modchip or have flashed the tsop.  just the new kids on the block that are afraid to open the xbox are using the soft mods

[juan23]

DAMN ASS GREAT JOB!!!!!!!!!!

with a sigh of releif, I can invision my 200 gigger getting full to the max

keep us all posted

[krawhitham]

QUOTE (hamtitampti @ Aug 28 2003, 12:15 PM)

but i see a problem in most of the new games. most new games, like HALO, matrix .... compleate exit the kernel in RAM and have a new kernel inside so this games are not playable anymore, as they get corrupted data

if that was true, Why does Halo and Matrix both work off the HD, if they load a new kernel why would the new Kernal allow access to the F: partition?

just a question

also I put the halo game (retail) in the xbox loaded it and the IGR still worked.  why would the new kernel also have the IGR function

[Xeero]

QUOTE (krawhitham @ Aug 28 2003, 08:55 AM)

you're not a dick or anything are you not everyone will to use a "normal kernel".  I installed a homebrew mod and have never had a problem or a desire to load the "normal kernel" since if you are talking about the soft mod users, he said he did not know if it would work. Get a clue most users have a modchip or have flashed the tsop.  just the new kids on the block that are afraid to open the xbox are using the soft mods

FYI, Live requires the retail kernel...  

[Troed]

QUOTE (oz_paulb @ Aug 28 2003, 12:46 PM)

Maybe the Maxtor drive is unique - if so it looks like I was lucky in my first purchase of a "> 137GB" drive.

I have a Maxtor Diamondmax 9 Plus or something, 160Gb. To get it to work in Windows 2000 I hade to install a "big drive patch". That was it - could well have been superseeded with a service pack now.

[Blind_Samurai]

Keep up the great work!