In 2010 the problems are much worst than in 2000!
The problem that I have is not that Poser can or crash, if Poser have not enough memory it will crash and the computer too. The problem is the wrong memory usage report.

What I found until now is that the task manager only reports the RAM used by a task and not the total memory used by this task and here begin a lot of troubles.
I watched the behaviour of Poser rendering the same scene with other application that shows the physical and disk memory (swap file) usage by a task or process and its maximum.
Beforore I start with what I found is to remember, for whom foesn't know, that a task running disk memory runs very much slower that if it was using RAM.

What I found:

• Poser doesn't use all the available physical memory (RAM).
• During the rendering RAM memory is allocated, it increase, but quickly is thansfered  to disk memory and the RAM memory usage decrease, very bad.
• Repeating the same rendering without changing anything less RAM is transfered to disk.
• Each time I repeat the same rendering it render faster.
• After several repetitions no memory is tranfered from RAM to disk, Poser use all the RAM it needs and the rendering is done using one RAM and so it is fast.

My conclussion is that Windows decides what to do with memory and what to keep in RAM and what in disk. It looks that the criteria is based on how often the memory is used. If used only once it will go to the swap file, if is used several times the memory will be kept in RAM.
Windows tries to keep the RAM usage a its minimum!
As the renderings you only do once, most of ot will be done using the swap file.!!!

The only solution that I find is, if you have enough RAM that is common today, is to disable all the swap files in all the drives forcing Windows to use only RAM.
Of course, in this case if you run out of RAM the computer will crash.

Stupidity also evolves!