Quote - Without reproducing an identical case on my system, I can only speculate.

Well, part of my reason to post here was for other people to check it.
Any scene will do, it just has to be big/complicated enough to make Poser go over the 1.5 GB limit while rendering. For checking memory usage, people can download the free "Process Explorer" app from System Internals (see my first post for link), or use Windows' task manager.

Quote - Please understand that I will leave announcements about future company and product plans to the product management and PR people.

I fully understand. My question was, can you hint to them that there might be a problem?
See below about e-frontier and filing bug reports.

Quote - If the scene renders fine without raytracing, that might be an indication of where to look.

Thanks, I'll check this ASAP.

Quote - uncheck "visible in raytracing" for objects about which you know that they will not appear in raytraced reflections or shadows.

Since I use raytraced shadows, everything counts...

Quote - I suggest you send a bug report to e frontier tech support so that this issue gets tracked and eventually ends up on the right desk.

I've already tried to file a bug report with e-frontier, on a reproductible bug which has been confirmed by other users on the DAZ forums.
All e-frontier had to say is "it's not Poser, it's your computer".   :-/
So that's a bug (fortunately minor) we'll find again in Poser 7, maybe even in Poser 8...

I really don't feel like wasting my time trying to help people who don't want to be helped, so I won't file any more bug reports with e-frontier, unless they show they really want to get Poser fixed, in which case I'm ready to spend as much time as needed to help get it solved.