(flash)rom memory allocations
 

Ok please correct me if I am wrong but the 128megs of flash rom on the apache is split up into 3 areas

1. ~44 megs of user accessible "storage" that is mounted as main memory
2. ~10 megs 0f un-lockable/ un-hidable "extended rom" that is mounted as extend ROM
3. ~73 megs? of Rom that is only accessible during OS install(or flash) and that mounts to /windows

So the rush to 'cook' these roms to fill the static space of 'Rom' and not use the storage space, It seems a bit more eloquent solution would be to unlock this rom area in a similar way to the extend rom.

Eloquent? Sure, of course. But to my knowledge so far no one (not even the real pros at xda-developers) has succeeded in doing that.

So in the meantime, the next best thing we can do is fill up every bit of the OS partition with apps that would otherwise use up storage memory.

After that, the next goal would be merging the extrom and storage memory partitions--which has been accomplished for some other devices (mainly out of necessity since their storage memory was very limited).

Baby steps!

I can't agree more... with dynamic vanila rom built (need user to activated the needed feature that already in ROM), is the most efficient way in my experience... hv all the heavy weight app built in rom to safe space, but not activate till user need it to safe program memory...

Doc Repartitioning is indeed a cool idea.... but with a very high risk to kill ur device permanently just for 10mb addition (merge extended_rom to storage memory)...hmm... I don't think that worth to tried... well, just me...:)

Dump folder size before cooking
 

Anybody know the maximum size that your dump folder can be before creating the .nba file???

Who cares? You can UNLOCK and write to the extended rom. One of my biggest issues was the fact that MSVC 1.6 is a bloody 5 megs big. That's a big chunk of onboard memory, considering the other stuff I load. I simply backed up my extended rom folder to my storage card incase I need any files from there, then simply ERASED the extended rom. I loaded MSVC and some other stuff on the extended_rom and have yet to have a prob. Anytime I need to hard reset my phone, I can load any cab files from the folder I created on the storage card. So why now to we need to repartition the memory?

Re: (flash)rom memory allocations
 

You forgot the radio firmware, which is a failrly large chunk.
The OS partition is 64mb
The Store is 44, 10 for extended, 10 for radio.
I think that's it.

And yeah, moving these around would be making changes below the bootloader (or whatever they call the flash mode thing) level. Bad idea (tempting, but bad) as you are way more likely to brick it to the point that the bootloader can't reflash.

Re: (flash)rom memory allocations
 

Does anyone know, roughly, about how much of the 73MB of ROM is left available after a flash (let's say, Helmi's stock 3.3)?