[sc00b4s7eve]

Originally Posted by nomad_delta

what are modules all about anyway? never quite understood what the whole "files to modules" converter thing was for, or whether I ought to be using it...?

--nomad_delta

Originally Posted by mwalt2

If you use the 6.5 kernal for your CDMA TouchPro, then you don't need to be concerned about modules. I think you just need to click the 'real wm 6.5 aku' box in the kitchen (though I'm not 100% since my lowly diamond is still stuck with the 6.1 kernal).

Are you sure about that mwalt? 'Cause Da_G wrote this: http://forum.xda-developers.com/show...37&postcount=2
"When you create a module, you are telling Windows Mobile that you want that module to be memory-mapped, so that each time it loads, it's loading to the same, known area of ram - saving space in slot 0 - this is done on the computer-side, during 'cooking' and is the job of wmreloc, g'reloc, bepe's Platform Rebuilder, etc. Virtual allocations are aligned to a 64KB border, so if you memory map a .dll that's only 3Kb large, it's still going to eat up 64KB of memory space.

There are also pages that can be allocated to these slots, that are aligned to a 4KB boundry, and process/general allocations that take place during normal operation. The way the system handles this is that modules allocated on rom build-time (modules we allocate with g'reloc et. al.) are allocated from top-down (for slot 1 for example, starting at 0x03FFFFFF for the first module, taking up space to the nearest 64kb boundry, then the next module, in a line down to the 0x02000000 address, which is the beginning of the slot) - General allocations that take place during normal system operations are allocated in the remaining space, from the bottom-up (so again with slot 1 as an example, starting at 0x02000000 and ending at 0x03FFFFFF) - As you fill up these slots more and more with modules, that leaves less space for windows to dynamically allocate other, general allocations, which can, and does result in out of memory errors (even when the device has plenty of physical memory left, it cannot address this memory when virtual memory is full)...

...WinMo 6.5 improves on this by opening up Slots 60 and 61 to Modules - yielding an extra 64mb of potential Virtual Memory space. (the allocation order is now 1, 61, 60, 0 for modules, 60, 61, 0 for files) - In order for the Kernel to recognize these new Slots as being mappable for Modules, it must be updated to the 6.5 codebase. This is where the 6.5 nk.exe comes in, and why it's so important."

I think I've actually made too many modules, and I'm getting some weird memory leaks (only when I run programs though, LOL, the OS, itself, is solid)