Expert
Posts: 1645
   
| MorphGear + Destiny + EmuEngine + Morph = ~ 680k. Of course, once they start allocating RAM I suppose it could be a different story, but I don't see how that combination (when no game is loaded) could possibly not fit within the 32 MB confines the article discusses. You would need to have a lot of other applications loaded (and running) to hit that limit. The other thing to keep in mind is that MorphGear does not keep all of the MorphModule DLLs loaded when they're not in use. MorphModules are loaded on demand, so the only time they're put into memory is when you either load a game or go to one of the settings dialogs, and then they're unloaded immediately after.
----
I just saw this in an article on MSDN:
"The developers inside Microsoft responsible for the Pocket PC 2002, which is based on Windows CE 3.0, took advantage of multiple XIP regions to the extreme. Most Pocket PC implementations have five or more XIP regions. The problem is that the gaps between the regions are far too large. The lowest based XIP DLL in a Pocket PC 2002 image is typically based below 0x0100000. Because Windows CE places RAM based DLLs below the lowest XIP DLL, the space available for RAM based DLLs, the application code, its heaps and stacks is not limited to the 32 MB virtual address space but the space below the lowest XIP DLL, which is less than 16 megabytes.
...
With corporate applications processing vast amounts of data, corporate developers are forced to use large databases in their Windows CE applications. Usually the database engine is implemented as a DLL and it is usually quite large. In the example above, the database DLL is the troublemaking DLL C. With the combination of less than 16 megabytes of virtual memory space available for a Pocket PC 2002 application and the requirements of large, RAM-based DLLs, many developers are discovering that their applications will not run due to lack of space—not RAM, but virtual memory space."
It's possible MorphGear is running into that, but then I find it odd for this to be isolated to specific devices like the PPC6601. That article also states that this issue only affects Pocket PC 2002 (and earlier devices). The PPC6601 runs WM2003, and from what I understand, Microsoft has corrected the issue so that this doesn't happen with WM2003. If it was a DLL virtual space issue, I would expect my old iPAQ 3650 with only 32MB RAM to have issues, and it does not. |
Figured out why the PPC6601 gets memory and DLL errors.
