Print

[wildonrio]

QUOTE(Bomb Bloke @ Mar 14 2008, 06:49 PM)

I already quoted the line that sets the initial cluster size to 16kb.

If you want to find lines that mess with the cluster size, you search for the relevant variable... "g_iClusterSize".

You see my logic though, thinking there might be more, given that according to lordvader even when changing that code it still shows 16k?

[lordvader129]

QUOTE(wildonrio @ Mar 14 2008, 07:23 PM)

You see my logic though, thinking there might be more, given that according to lordvader even when changing that code it still shows 16k?

it shows 16, but formats 32

[Bomb Bloke]

Ok, ok, back to basics.

When you get the time, compile the source as NightShade released it. No tweaks, no patches.

Load it up, format with 16kb, check the results. Rinse and repeat but tell it to use 32kb clusters.

At this stage I'd be surprised if it works as it's supposed to.

[lordvader129]

QUOTE(Bomb Bloke @ Mar 14 2008, 07:52 PM)

Ok, ok, back to basics.

When you get the time, compile the source as NightShade released it. No tweaks, no patches.

Load it up, format with 16kb, check the results. Rinse and repeat but tell it to use 32kb clusters.

At this stage I'd be surprised if it works as it's supposed to.

it lets me select 16k or 32k, didnt test that it actually formats that but i can do that tomorrow (id be surprised if it didnt, we'd be seeing a lot of posts on it if that was the case)

wish we could get NghtShd to chime in on this, but he was last active on the forums over a year ago


EDIT: i just realized the irony, i dont even care about using big HDs, im perfectly happy with my 250, but i like having a project of sorts to work on, lol

[Movax]

From what I can discern from the code, if you change the cluster size, then immediately format that same partition, without doing anything else, it should format with the size given. If you format the entire drive, or select a different partition, xbpartitioner will automatically select 16kb or 32kb clusters depending on the partition size.

If this method is being followed, then what is needed, is more detail on the function that does the actual work: XapiFormatFATVolumeEx()

There's an entry for it at line 81: BOOL WINAPI XapiFormatFATVolumeEx( PANSI_STRING VolumePath, ULONG BytesPerCluster );

I can't find it anywhere else, so I assume it's part of the XDK? Or maybe a built in Kernel function?

Is there any documentation on it?

[Bomb Bloke]

That's exactly how I read it. The size XBPartitioner says it's going to use, should be the size that it uses.

Hence why I wanna see how a re-compile of the virgin source acts... Or what happens if the type of g_iClusterSize is also changed to a ULONG.

Heh, it'd be a laugh if even the compiled version NShade released does this. It may be we've only been thinking it uses 16/32kb clusters, when really it's been doing something entirely different...  

[lordvader129]

has anyone found a way to check cluster size besides the roundabout way im doing it? lol

[Movax]

QUOTE(Bomb Bloke @ Mar 15 2008, 11:02 AM)

g_iClusterSize is also changed to a ULONG.

I don't see how this would matter, since the value is being passed to the function I mentioned, after being shifted left by 10 (the same as multiplying by 1024 - [turning 16 into 16k for example]).

It's being stored in a ULONG at that point.

[Bomb Bloke]

What gets passed might be ULONG, I'm just not sure if what gets bitshifted is a ULONG.

You're probably right though (given that the problem occurs even with 16kb clusters selected). That shouldn't be the issue.

[lordvader129]

QUOTE(wildonrio @ Mar 15 2008, 06:54 PM)

Check your free space, send over 1kb file, then check free space again and subtract new free space from original free space.  Is that what you're doing?

yeah, thats how im doing it, was hoping there was an app to check the cluster size, or at least show size and "size on disk" like windows does, lol

[lordvader129]

1k = 4k
2k = 4k
4k = 4k
8k = 8k
16k = 16k
32k = 32k
64k = 64k
128k = F drive not present (MXM and XBMC)
256k = F drive not present (MXM and XBMC)


i think 3.something kilobytes are used even with no files on the drive, which is why 1-4k all appear as 4k (this is also why when i formatted 16k and 64k previously i thought it was 32k and 64k, when i put the file on the drive it was taking a second cluster, thus appearing to double cluster size)

i changed the code to just give the options for 16, 32 and 64, since 128 and 256 didnt seem to work (not sure why i ended up with something last time i tried to use 256k, maybe i had accidently hit Y again) and below 16k is unnecessary IMO

QUOTE

case 3:
if (g_iFunction == 2)
{
if (g_iClusterSize == 32) {g_iClusterSize = 64;}
else if (g_iClusterSize == 16) {g_iClusterSize = 32;}
else if (g_iClusterSize == 64) {g_iClusterSize = 16;}
m_iWaitRelease = 1;
}
break;

this code worked properly for all 3 cluster sizes

[Bomb Bloke]

Well done.

[xdlabax]

xbox 1.6 i dont know the rest how can i get the info? bios unknown (running on evo 3935)

modchip aladdin xt

hdd instaled 500gb






Hello guys

i am total newbie so can you answer me some questions?

1. instaled 500gb disc. 1a)do i need to flash neww bios? to get F: and G: drive or is it 1b)possible to format it with xb prtitioner, and use only F:  if 1b) where can i get the xb partitioner tool ? my my e mail is xdlabax\centrum.cz

2. i am usin evox auto instaler 2.7 final. am i able to flash my ALADDIN XT chip with one of those evox-m8


xbox 1.6 i dont know the rest how can i get the info? bios unknown (running on evo 3935)

modchip aladdin xt

hdd instaled 500gb






Hello guys

i am total newbie so can you answer me some questions?

1. instaled 500gb disc. 1a)do i need to flash neww bios? to get F: and G: drive or is it 1b)possible to format it with xb prtitioner, and use only F:  if 1b) where can i get the xb partitioner tool ? my my e mail is xdlabax\centrum.cz

2. i am usin evox auto instaler 2.7 final. am i able to flash my ALADDIN XT chip with one of those evox-m8
    or evox-m8+ or such fo 1.6 version?. why is the written (

Info "Flash MOD CHIP ONLY ON v1.6! Xbox"
Warning "With Evox-M8 v16 *FC* F: & G: (67)"
Warning "This will give you G: if your HD >137GB"
Warning "Boots F:&C:evoxdash.xbe / C:avadash.xbe
Warning "Once Complete the Xbox will self Reset"
Warning "To BE USED on v1.6 Xbox ONLY!"
Warning "Unit Must be operating without a Mod Chip"
Warning "If Uncertain, Turn Off Xbox to Abort!"
flashbios "\SYSTEM\ALL\NewBioses\EvoX_M8_v16_FC_67_Blue_256. bi

what should i do?

reflash and then start with ms dash??


3) aladdin xt chip is 256kb or what send me info



EMAIL [email protected]

thanks so much


much much much


please help

[Bomb Bloke]

QUOTE

g_iClusterSize = (PartTbl.TableEntries[g_iCurrentPart].LBASize > 0x20000000) ? 32 : 16;

If each of these could have this line added beneath them, like so:

QUOTE

g_iClusterSize = (PartTbl.TableEntries[g_iCurrentPart].LBASize > 0x20000000) ? 32 : 16;
if (PartTbl.TableEntries[g_iCurrentPart].LBASize > 0x40000000) g_iClusterSize = 64;

This should cause XBP to autodetect partitions larger then 512gb and assign them 64kb clusters by default.

[lordvader129]

QUOTE(Bomb Bloke @ Mar 20 2008, 10:24 PM)

One more suggestion...

There are two lines that read like this:
If each of these could have this line added beneath them, like so:
This should cause XBP to autodetect partitions larger then 512gb and assign them 64kb clusters by default.

heh, i was just going to bump this thread and ask if you had any ideas on how to accomplish this, lol