Again, not all types of work can take advantage of dual procs, and even those that can may not be faster as a result. In the real world, there are some jobs that aren't faster if you have two people do them. An example of this might be boiling a single egg. It doesn't matter how many people are in the kitchen, the egg still cooks at the same rate. There are some jobs that can be faster if there are more people, but only if conditions are right. An example is washing dishes by hand. Two people at a sufficiently large sink can get the job done roughly twice as fast. If, however, the sink is small, it won't get done twice as fast because they'll constantly have to be getting out of the way. Finally, there are some jobs that don't make sense to get done "faster". For example, it wouldn't be better to divide up a single piece of music between two musicians just so you could finish playing it faster. In the computer, things are very similar. There are some jobs that don't go faster no matter how many processors you have, like copying a file. There are some jobs that might be faster if you have enough resources, like rendering from a raytracer (where memory is the "sink" in the above example...if you have enough RAM, you could get better speed, but if not then the two processors just get in each other's way). Finally, there are jobs that don't make sense to speed up with a second proc (like playing back an animation). Poser doesn't take advantage of a second proc, but even if it did, I'd be surprised if it made a practical difference in any but the most powerful boxes. If you want to speed up Poser with hardware, you'd be much better served with by a faster processor, faster and larger supply of RAM, and a very fast set of disks (three is ideal...one for your OS, one for your swap file, and one for your applications and data). These things can shave minutes off your render times, but dual proc support probably cannot. (Disclaimer: I don't know the internals of Poser, so there may be more opportunities for multi-proc support than I can see. I base the above comments on a general Computer Science background and some basic understanding of graphics problems and ray tracing.)