One further thing to note: Poser was originally a port from Mac. Hence I sincerely doubt the coders put much attention into speed-related issues of the code - they just needed to port it to Win. It's not the fault of the computer industry in general if the software designers can't/won't take into account the possibilities offered. Poser in particular is not well known for it's capable code - on the contrary. No matter if you got Radeon9600 and 2 gigs of RAM... if the code can't take advantage of it, there's nothing you can do about it. Contrary to many others in this thread, I believe (and have seen it many times too) that, say, tripling capacity can increase execution speed to 10 times that of original. It all depends on the quality of the software used, hardware used and the weakest link of the said hardware. Many here are Windows-only users ... in many cases Windows itself is the cause of slowness and trouble. I've heard "upgrade to WinXP" comments, but I'd never upgrade from Win2k to WinXP in hoping to get better Poser-performance - it jsut won't happen - probably the other way around. I'm currently working with a 3-processor HP-UX Mainframe ... and I can tell you that using "grep" to find out text from a 500Meg text-file executes about 7-10-times faster after the system memory was doubled a while back. If I'd be using Poser in this environment, it probably would be slower ... :D