Noel,

> > [You] could be pretty much okay; all that's needed is to
> > "bridge the gap" between old and young space during GC
> 
> What gap?  There is no gap.  The whole point is to give 
> Squeak exactly what it expects: a single, contiguous, allocated
> region for the object space.

Sorry, I misunderstood you here. I thought you wanted to map the image file
but then run out of heap space. I wasn't aware that you were trying to run
the entire thing out of the memory mapped portion.

> You might want to check the 3rd link I put in the prior
> message.  You'll find a layout of the WinCE memory 
> architecture; pictures and everything.

Yup. Very useful stuff (so let's recite it :-)

http://msdn.microsoft.com/library/periodic/period98/memory.htm

BTW, one thing that got me scratching my head was the following:

	"Memory-mapped files that are backed up by named files currently are
supported only for read-only access. Unnamed memory-mapped files-those
typically backed up by the page file-are supported. This is a little strange
since Windows CE does not support a page file."

A little??? Oh well. I interpret the first part basically as you cannot
write to pages of files mapped from the disk. Which in turn would imply that
you can't use it for mapping the Squeak image in. Or is this outdated
information?!

Cheers,
  - Andreas