I would highly discourage anyone from running Bryce on a system with only 32 megs of RAM - you can get away with 64 if you're running an older operating system, like Win95 or Mac OS 7.5. - and 32 megs of RAM can be had for about US$30-$40. If you're running Mac OS 9 or Win ME/2000, you really ought to have 128 megs of RAM anyway... these operating systems just don't perform stably with less than that. you're right though: RAM doesn't do a darn thing to speed up renders - EXCEPT if your system's virtual memory system has to get involved. You always want to have enough real RAM to keep the entire Bryce memory partition in real memory when running, plus a little extra: otherwise, the program will be swapping memory to disk regularly, which can cause huge slowdowns. lots of RAM is needed, however, when opening large scene files. I have a couple I'm working on right now that are over 50 megs, and several postings here on R'osity and other sites come from scene files measured in the hundreds of megabytes in size. If you can't fit the entire scene file into memory, Bryce will either fail to open the file, or crash ungracefully after opening it. Since Bryce doesn't take advantage of the G4's vector processing unit (which uses 32-bit floats: Bryce works in 64-bit doubles), if you want to render the absolute fastest possible, buy a PeeSee at 1.3GHz or more... I think the 1.6's from AMD are out. That should cure your slow-render blues :^D Hopefully Bryce 5 will fully support the G4's vector unit, Mac OS X and multiple-processors - resulting on screamin'-fast renders.