yay! I thought it was buried too deep, lol "This is another trick you guys use a lot. You love comparing Poser's bugs with Photoshop, Windows, etc., but when you're called on it, you say it's "unfair" to compare poor little CL with those huge companies like Adobe, Microsoft, etc. If it's so unfair, why do people keep doing it?" Lack of effective reference points? Ignorance? Readiness of use? I think simply because they are the most common reference points for most people. "I know your answer to that one: these packages aren't as complicated as Poser. There's always an answer." True -- but validity of the answer is what's applicable. IT's a valid response to your comparatives. Dissect it and disprove it otherwise. Then I've got some for those (and ya know if I don't, I'll concede the point :)) "It doesn't necessarily have to be "common and everday." It should simply have to meet the program's specs, just like I said earlier. You must have missed that ;)" Apologies -- I did miss that. I also oversimplified, and that was an error. The point is conceded as I've lost the train of thought. The items didn't fall under P4, they fell under Item four in my list... And then I'm lucky in the same way the larger majority of folks are. Running under XP, using the method I described in my 5 Things posts, I have never had a crash (since SR2.1), do not have memory leaks (granted, my definition is pretty specific), and since sr4 it hasn't locked up once looking for a texture. I'm currently in a position where Poser is in use about 60% of my day on two systems (I use poser to make a living, since it's my primary animation tool for the training CD's I create), running simultaneously with Powerpoint, Photoshop 6, and Vegas Video (and sometimes Acid, as well).

thou and I, my friend, can, in the most flunkey world, make, each of us, one non-flunkey, one hero, if we like: that will be two heroes to begin with. (Carlyle)