Question for our ROM cookers regarding program and storage memory of ROMS

[aaronvlee]

one thing I've noticed is that these roms are absolutely awsome that I'm testing except one thing is unclear to me...

I'm to believe that installing apps in the storage memory rather than the program memory is either impossible or not concerning...but that would in theory free up the program memory's space enabling higher pagepool possibilities right? Would this kind of achievment be found in the cabs or the xml file that preinstalls the apps during selfprovisioning? I'ma noob and very unclear on what controls the installation paths, but if I can get a little direction (if no one knows), I'll be happy to investigate this for the sake of our VZW users (and Sprint users with MEGA-LOADED ROMS).

Any suggestions or opinions?

[rstoyguy]

I have been unsucessful at accessing the internal/storage card memory when setting up a rom. I have tried with provxml and initflashfiles.dat. I tried doing this about 6 months ago....

[aaronvlee]

Originally Posted by rstoyguy

I have been unsucessful at accessing the internal/storage card memory when setting up a rom. I have tried with provxml and initflashfiles.dat. I tried doing this about 6 months ago....

So can you break down the process of how the apps are installed when the rom is first flashed? Is it cabs? What's a module btw?

[Kolano]

Originally Posted by aaronvlee

What's a module btw?

A module encodes a exe or dll file. I believe they provide details regarding memory placement/usage which can improve performance.

[Kolano]

Originally Posted by aaronvlee

one thing I've noticed is that these roms are absolutely awsome that I'm testing except one thing is unclear to me...

I'm to believe that installing apps in the storage memory rather than the program memory is either impossible or not concerning...but that would in theory free up the program memory's space enabling higher pagepool possibilities right? Would this kind of achievment be found in the cabs or the xml file that preinstalls the apps during selfprovisioning? I'ma noob and very unclear on what controls the installation paths, but if I can get a little direction (if no one knows), I'll be happy to investigate this for the sake of our VZW users (and Sprint users with MEGA-LOADED ROMS).

Any suggestions or opinions?

The way ROMs work anything they would install would have a copy within the ROM memory. Those copies usually defeat the purpose of installing files outside of ROM space.

Since storage cards are not impacted by flashing a ROM, you can usually set up shortcuts to reference things previously installed to the storage card. In some cases files may be spread around that would require restoration after a flash (or integration into a ROM), but this is typically not the case.

An other method of this is to use Teir Autoinstall to install from CABs on a storage card to storage memory during initialization.

[bestjudge]

There is ROM and there is RAM. You cant install programs to RAM.
Here is why:

RAM is short for Random Access Memory, RAM is used to run certain basic programs and functions that your PPC needs to operate correctly, and functions only while the PPC is receiving power. Programs you're using are written in RAM temporarily while the PPC is processing them. Think of RAM as a playing field, a large open area where your programs function. Each program takes up a certain amount of space; the field can accommodate one or several different programs at one time, but its capacity is limited (not so much on Sprint touch pro ). When you shut down a program, it disappears from RAM and (ideally) the space it occupied can be reused but WM won't properly relinquish the RAM space even when a program is closed. However, because stuff in the RAM is retained only while the PPC is powered up, soft reseting will always clear the RAM.

[Kolano]

Originally Posted by aaronvlee

So can you break down the process of how the apps are installed when the rom is first flashed? Is it cabs?

There are typically no CABs. The ROMs typically have files as if they had been installed to the \Windows folder. The process of flashing requires a copy of everything in the ROM to be there, so although some programs require files within certain subdirectories or locations outside of \Windows, any such files are typically copies of files from within \Windows.

Basic rundown would be...

• A set of OEM packages and other files are selected
• Kitchen tools parse these packages Merging some content/excluding some other content, but basically copying selected files together into a single folder.
• This set of files is processed into a ROM.
• Someone loads the ROM. Clearing their Storage/ROM memory, but leaving storage cards (or similar additional storage) untouched. Any actions taken from here on take up storage space.
• Initialization scripts run on initial bootup. These may copy files, run CAB installations, etc. However, most software is already in a pre-installed state, and does not require these steps.

[bestjudge]

Pagepool comes out of Ram memory (Random Access Memory) .Setting PP higher means you will have less Access memory left to run other programs. Programs are installed to some kind of storage memory....internal storage ,memory card or others.