Have you picked apart the P5 code? Then how do you know it isn't a recode? While I appreciate that you're a relative newbie, I'm afraid it's pretty obvious to most of us, who have a lot more experience of Poser and 3D, that P5 is most definitely not a recode. And I honestly don't think your going to find many (or any insiders from CL) who are going to back you on this presumption. To be frank (and from a technically far more advanced and experienced standpoint than your own), any credible recode of the Poser core would have given us a substantially better program than we got with P5. Don't throw insults around, especially from a position of technical ignorance, it just makes you seem foolish. To clear up the "hardware incompatibilty" issue; there just isn't one. Poser is a pretty basic 3D application. Apart from the now defunct Interlok issue and ensuring that the virtual memory is set up properly on a reasonable (ie. NT based) 32 bit OS, Poser really doesn't need to use (and neither seems to) any but the basic (and standard) OS services. The display graphics are vanilla GDI and the codecs are MDI, and only really come into play post rendering. "Hardware incompatibility" is often just used a convenient excuse for poor programming standards. All of the functionality is strictly deterministic, if a scene won't render on one machine then it won't render on anyone else's either. But what's also apparent from the start is that people use Poser at very different levels. In many of the screen shots of folk who are still suffering crashes the application memory use is above 1.5GB, whereas many others (including some I know personally) rarely create scenes that require more than a couple hundred MB. And yes, I have sat at the desk of someone who swore blind that they had a "bug free" installation (pre-SR in fact) and demonstrated that their "version" is every bit as problematic and buggy as CL's most ardent critics. The difference is in what people are trying to achieve. What has pushed a lot of people over the edge is that P5's higher memory footprint (with no improvement in the memory management) means that people at the high end are getting even less mileage from the program than previously. Bill