Lol - well, my apologies if you've taken anything I've said about Poser as "negative", the truth is I use Poser a great deal and I really like the application.

I do have some problems with the direction in which Smith Micro has decided to proceed with Poser development, personally I think there on the wrong track, but since I don't own any stock and I doubt they'd listen to me anyway not much point in getting into that discussion yet again here.

As to Poser itself, it's a really wonderful program that has brought me a great deal of enjoyment, but it does have some issues, and memory management is one of the biggest among them.  But I guess when it comes to things like this I tend to think like a programmer, if something in my code is causing problems I want to know, because I just want to get it fixed.  If nobody ever says anything then I don't know where the problems are and I can't fix em. 

I don't take it personally, and I don't assume that most other professional developers would either.  We get paid to code.  Dunno, maybe I spent too many years beta testing - I just don't consider bringing issues like that to light as a bad thing.

But rest assured I do really like and use Poser, even though at the moment I am at the beginning stages of working on an open source replacement for it.  Again this has more to do with what I feel are major problems that are going to arise with future development rather than any personal, deep seated grudge against the current incarnation of Poser.

So I hope that little tip works for you, it seems to do wonders for most people who are experiencing strange problems with Poser running under Windows (any version), and it's such an oddball fix - it's not something I think that is documented anywhere else to my knowledge, so I share it whenever I can.

-Never fear, RenderDog is near!  Oh wait, is that a chew toy?  Yup. ok, nevermind.. go back to fearing...