It's my opinion that P5 is written with its internal priorities all skewed. Proper programming protocol puts hardware events at the top of the priority food chain. Poser really doesn't have any of these to deal with, as the OS looks after the disks, etc. The next thing should be the keyboard and mouse. Then should come the screen updates. Renders and draping should be at the very bottom, given the remaining cycles after all these other tasks are taken care of. Someone at CL seems to think this would hamper performance, but it won't. High priority tasks should be things that happen rarely. Things that take a long time should be at the bottom of the chain. At least that's what I've been trying to tell them. Right now, if you start a hair drape with collisions on in P5, then go run an email client for a while and come back to P5, the screen will not update and it will look like P5 is gibbled. It probably isn't, but it will look that way. In note I got today from tech support, they claimed that you shouldn't multitask with P5. That's code for they are still not willing to change the priorities....despite having been told about it several times now. But the program does work. It's just clunky. I'm getting beautiful results now that SR3 has fixed the hair collision problm. But I have to wait hours for them on this PIII-550. And Firefly is a real memory pig, but what renderer is not? This is especially true with dynamic hair in a picture. The answer is more RAM. As much as you can put in the machine!