uh... actually Sharon, I think that means that you would agree that the problem does NOT lie with memory settings & availablility as BB suggested, but rather something to do with available disk space.

I'm still using 4.03 as loneranger20 is, with the Extended Memory Upgrade and, when watching Poser's use of memory resources during a render I don't recall ever having seen it gobble up much over 1Gb of memory during a render (well under my 1Gb RAM + 2GB fixed-size pagefile).

On the other hand, when it does occasionally still complain of insufficient memory, it happens at different memory usage levels, but often when using just a couple of hundred Mb, nowhere near the 3000 available. All of this with over a hundred gigs of empty disk space. (And remember, P4's "poserTemp" files created during a render were rendered to disk, not to RAM or Virtual memory)

So, while certainly not disputing BB's experiences, when a defrag, with a fixed-size pagefile, makes the problem go away , (for me at least) it tends to indicate the actual source must not lie in a RAM or Virtual memory problem, but rather to disk space, (and, --my wild guess--, perhaps the apps inability to write its poserTemp files to disk in multiple fragments).

I know we've had this thread a zillion times. Can't say what really made me dive into it this time around -- nothin' truly new to add.