LawnDart, I can't personally attest to the MacOS versions of Poser 4/PP (and even P5 ;-) - they may well be better than "crap code." But the Windows "interface" code that ports it from Mac to Windoze clearly is sadly lacking. It was marginal in it's day - which granted was fairly common, even Adobe had problems with their proprietary memory manager back then. But it's woefully poor now and makes the whole product appear to be "craply" coded, but it hasn't even been touched since, in any release or SR. This means a) existing bugs remain through at least the last 3 major releases even though some appear to be fairly localized if not relatively simple, b) it's not remained current as Windows has moved through many, many versions - some significant ones like NT, and c) new latent bugs have come to the surface due to b). Not addressing these in order to put in new features, is just asking for your customers to rebel IMHO. What is it about this Windows interface code - which new features in Poser 5 clearly avoid using? Is it really too hard to fix? Or did, as seems more probable, CL lose the legal right to fixes/updates to it somewhere along the line? Just wondering...