[Bf-committers] Windows (XP) refuses to allocate > 1 GB

[Ilyes Gouta]

Oh yeah, one more thing, personally I would avoid the AWE thing...
It's too much specific, brand new and is supported only on XP and
above.

Regards,

On 6/30/06, Ilyes Gouta <ilyes.gouta at gmail.com> wrote:
> Hi!
>
> You can use the VirtualAlloc class of functions or better use a memory
> mapped region through CreateFileMapping and MapViewOfFile. Please note
> that the former will allocate the memory on the swap file then the
> latter will map that to a memory pointer so that you can access it as
> a normal memory block. It doesn't matter how much you have RAM, this
> will work providing you have enough disk space.
>
> Regards,
> Ilyes Gouta (blenderx)
>
> On 6/29/06, Ton Roosendaal <ton at blender.org> wrote:
> > Hi,
> >
> > See the thread here:
> > http://projects.blender.org/tracker/?
> > func=detail&atid=264&aid=4539&group_id=9
> >
> > And with some googling I found this:
> > http://www.stata.com/support/faqs/win/winmemory.html
> >
> > Apparently XP with SP2 refuses to give larger blocks than a gig. With
> > our floatbuffer approach that limits rendering to a resulution of about
> > 6000x9000 pixels.
> >
> > So... is this true? Should we move to a tilebased image structure or
> > so? That was something I had in mind anyway, for example to be able to
> > cache images (textures, shadowbuffers) to files while rendering.
> >
> > -Ton-
> >
> > ------------------------------------------------------------------------
> > --
> > Ton Roosendaal  Blender Foundation ton at blender.org
> > http://www.blender.org
> >
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at projects.blender.org
> > http://projects.blender.org/mailman/listinfo/bf-committers
> >
>