Re: Increasing physical memory in WinCE

Every WinCE process has a 32 MB virtual address space. All non-XIP dlls are
loaded in this space. Are you dlls taking up more space. 32 MB limit cannot
be increased as it is imposed by the Windows CE design.

Incase you really need more than 32 MB space, possible Solutions are:

1. Divide you application into two processes (total 64 MB). They can share
the loading of dlls.
2. In your application, don't load all dlls at once. Dynamically load the
dll whichever is required and after calling functions in the dll, unload it.
This will make space available for loading next dll. This techinique will
cause a not so good performance but the application will work.

Note:
If a Windows CE app require more memory than 32 MB virtual addess space,
then its not a good design.

Regards,
Parhar
http://cedeveloper.blogspot.com

"Parhar" <os_parhar@xxxxxxxxxxx> wrote in message
news:uNe0t7bJGHA.916@xxxxxxxxxxxxxxxxxxxxxxx
> Goto System applet in control panel and then goto Memory tab. Move the
> slider to the left side to increase the available program memory (This
will
> decrease the Object Store memory).
>
> Regards,
> Parhar
> http://cedeveloper.blogspot.com
>
> <sbegumpeta@xxxxxxxxx> wrote in message
> news:1138633138.134008.233500@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > Hi Guys,
> >
> > I am new to this group as well as WinCE. I have problem running the
> > test application developed by me.
> >
> > The application loads a set of dll's in a row as per my requirement,
> > but i am unable to load the dll's. After using GetLastError() function
> > i came to know that it was unable to load the dll's due to insufficient
> > memory.Is there any way to increase the physical memory of WinCE.
> >
> > Immediate reply will be greatly appreciated.
> >
> > Sathish.
> >
>
>


.

Relevant Pages

  • Re: Memory limit reached with Windows Mobile
    ... That would explain the memory problem - you just can't do that. ... Once I reached the 12 Mb limit, I cannot load any DLLs, yet if I ... Actually, simply by loading our 18 Native DLLs, we reduce the Virtual ...
    (microsoft.public.pocketpc.developer)
  • Re: Memory limit reached with Windows Mobile
    ... available memory, but oinbounded by the CF itself. ... MissingMethodException while loading Native DLLs when most of our ... 1- Load the same DLL over and over. ... we decided to pre-load all our Native DLLs ...
    (microsoft.public.pocketpc.developer)
  • Re: Memory limit reached with Windows Mobile
    ... I do understand what a test is, and I do understand how memory management ... ctacke: re-read Patrick's questions, ... 1- Load the same DLL over and over. ... Loading native DLLs takes at least 64k each. ...
    (microsoft.public.pocketpc.developer)
  • Re: Explicit loading does not work
    ... This utility just prints virtual memory layout for the application with XIP attributes if any. ... Application DLLs can not be loaded at the address where XIP dlls reside. ... when this space is out, HeapAlloc begins allocating virtual memory from the XIP ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: Memory limit reached with Windows Mobile
    ... ctacke: re-read Patrick's questions, ... 1- Load the same DLL over and over. ... Loading native DLLs takes at least 64k each. ... good thing due to the 64k minimum virtual memory size each will take. ...
    (microsoft.public.pocketpc.developer)
Loading