|
||||
Re: [UPDATED 9/27/08] v1.4 WDM's 2D Diamond ROM
Links are up....have fun, remember I am accepting Mirrors
__________________
http://sprint.com/global/images/logos/sprint_logo.gif
If I helped you or you appreciate my work, please feel free to https://www.paypal.com/en_GB/i/btn/btn_donate_LG.gif!!! |
This post has been thanked 1 times. |
|
||||
Re: [09/27/08] Juicy ROM 2.2 [CE OS 5.2.20755 | 16MB PP]
Quote:
This is how I see it: ROM is where the OS and programs are stored. It doesn't use up power, but is very slow. That's why if you restart your device, everything in your ROM is still there, all your data/programs/OS. The 4GB within the Diamond is also ROM. RAM is where the OS and programs and data are written into before that are run. RAM is very fast but uses up a lot of power. It needs to be constantly powered to continue containing the information stored there. So the way things work is that the Windows Mobile OS and programs and data are written from the ROM into the RAM and then run, BUT they have to be decompressed first before being loaded into the RAM. With a page pool (which is made of ROM), frequently used programs can be decompressed and saved into ROM and then run directly from there, saving RAM and the time needed to decompress the code (only code is saved into the page pool). Thus a larger page pool has the dual advantage of making programs run faster AND freeing up RAM (which is still used up by programs no matter how big your page pool is since the page pool only stores code). The main disadvantage to having a large page pool is having less ROM to work with (less space to save programs and data). I hope this helps, and I'll be the first to admit that I may be completely wrong. I have limited actual knowledge and experience with such memory architecture specifics, and what I do know has been gleaned from different MSDN topics, with the rest (hopefully) logically constructed in my head. Edit: I've done some further reading/thinking and the page pool may actually be contained in the RAM, not ROM. Again I'm not certain on this, maybe someone can clarify. If this is the case, then you don't save RAM, but it still allows programs to load up faster. Hopefully someone can clarify to see if having a larger page pool decreases RAM or ROM. Here's where I gathered most of my information from: http://msdn.microsoft.com/en-us/library/aa915332.aspx http://blogs.msdn.com/windowsmobile/...19/453784.aspx http://msdn.microsoft.com/en-us/library/aa915364.aspx http://en.wikipedia.org/wiki/Virtual_memory http://www.etenblog.com/2008/01/14/c...age-pool-size/ Last edited by thermodynamic; 09-27-2008 at 03:04 PM. Reason: Page pool may actually be in RAM |
This post has been thanked 1 times. |
|
||||
Re: [UPDATED 9/27/08] v1.4 WDM's 2D Diamond ROM
there is a version that worked in the past for the roms I was using? It without a doubt increased call volume and speakerphone volume.
|
|
||||
Re: [UPDATED 9/27/08] v1.4 WDM's 2D Diamond ROM
Good Job, that answers my previous question. I see the links. How long before the Full version is released?
|
|
||||
Re: [UPDATED 9/26/08] v1.3 WDM's 2D Diamond ROM
that is not true at all. You can not turn down the volume when I have it on speaker. Now if your talking about playing games when you say "in them" not all games have volume controls. The opal control is just broken period.
|
|
|
|