Colonel's Custom 3.3 Rom - Page 28

tbhausen · #**271** (**permalink**) 01-30-2007, 08:11 PM

Let the treasure hunt begin

Todd/Indy

reese719 · #**272** (**permalink**) 01-30-2007, 08:13 PM

Ok, I'll try that then. Much appreciated. Oh, and just so you know, I freakin' love O2+, in fact I have it on my SD but never installed it. Tried SPB first, but since your ROM I'm never going back. Thanks!

**Maxx134** · #**273** (**permalink**) 01-30-2007, 08:22 PM

Quote:

Originally Posted by MitchA

After using both Colonel and Helskis 3.3 Ive came across a memory question.

Using the Helskis rom (and stock 2.2) I use more Storage memory than Program memory yet when I use Col's I use much more Program memory than Storage running the same apps installed to the same location. Why?

Thanks for the fun

Mitch

This leads me to believe that the 3.3roms may perform differently. Anyway remember .NET2 is in rom.

but what about what helmi_c says in kitchen thread:
"btw I havent see anyone talking about paging pool for Apache?
paging pool is seriously increase ur device speed, but u must choose the right size for ur device, cos It will effect ur free program memory.
fyi BA with 16mb Paging pool? run twice as fast as it original state (2.8mb)
Hima also the same...

here's how to patch APACHE Paging pool:

open nk.nba with hex editor, I use winhex for the simplicity purpose and find hex string 64B00000640000002E2E2E2E00002E2E where 2E is the joker string or wildcard in winhex. then U'll hv/go to this posisition as ilustrated in picture:

as u can see my AKU3.3 is using 8mb paging pool, the standar Apache if I'm not mistaken is 4-5-6mb.... go adventure... try to set it 10mb (A0 00), or 12mb (C0 00) or 16mb (00 01) and see if ur device fly or not...

hopes this info is usefull..."

Ya I too think it's usefull..So Colonel can you adjust or see this setting?

EDIT:
Then again, mayby its best to leave where it's at for now, being that Helmi C already increased it?

reese719 · #**274** (**permalink**) 01-30-2007, 09:14 PM

Hmmmm... I just noticed that when I re-installed the Sprint AKU ( version 2.0 I think? ) it showed me I was moving from what version to what before the upgrade. However, this didn't happene when I tried to install Colonel's AKU 3.3

I just installed Helmi's AKU 3.3 and it showed what version to which... and as I'm typing this I'm installing Colonels version again and it's working...

Well... so yeah, everything is alright then, sweet. Waiting for version 2 now I guess. Hehehe

**schettj** · #**275** (**permalink**) 01-30-2007, 09:28 PM

Page pool... yep. It's on the todo list, but I'm not even fully comfortable with the basic Rom Kitchen. Sheesh we have to crawl before we can fly

And the page pool at 8mb is probably pretty good

Quote:

The Page Pool
Applications use RAM in two ways. There is code that runs, and there is data that is created while it is running. On a NOR device, the code can run directly from the ROM and not be loaded into RAM first. This process is called XIP (eXecute In Place). NAND devices can't XIP, so their code is loaded into RAM and executed from there. If you don't have a Page Pool, this code is loaded into normal RAM. The Page Pool is a mechanism to limit how much code is loaded into normal RAM. With a Page Pool, we can unload code that hasn't been used in a while and reload it later if we need to. We can't do that without a Page Pool.

On a typical NAND-based WM5 device, the Page Pool is 4.5M.

So - page pool is used like normal RAM to run programs, and the OS as well... it's almost like shared memory of sorts.

If you pull memory out of general RAM and allocate it to the page pool, it would seem like its still used for exactly the same thing. So what's the advantage to having it be in the page pool???