Kathleen, I've seen both those fatal error messages on my Mac. The "out of memory" error seems to occur whenever Poser (or the processor) doesn't know what else to do with a file, especially if it can't find a required .obj thingie. Sometimes, if you look closely at that "can't find..." box, it'll give you the path it's looking for to the .obj; you can hide Poser, put the bits in the proper folder(s), paying close attention to capitalization, spelling, spaces, etc., and then try again. Sometimes the readme files spell out where stuff should go; sometimes they don't. And assign as much memory as you possibly can to Poser; it doesn't seem to mind RamDoubler, at least on my machine, so crank it up! Give me a shout at texboy@earthlink.net if you want to talk further. Don't give up!! Paul