With any luck, the previous suggestions will have fixed the problem. In the event that they don't, how big is the file that was created by the save (you mention that they are small scenes, but how big are they in system terms)? I have seen the problem you describe in your initial paragraph and something similar to the one in your second item 2) :0. I have only seen the first one in Poser 6 and I have mainly seen the second one in Poser 5, but I never knew it to corrupt a saved Poser file (I thought that was a Vue trick). Something like this was discussed in a thread http://www.renderosity.com/messages.ez?Form.ShowMessage=2410026 and the URLs posted there did seem useful. Both these problems (in my case) do seem to me to have been linked to the actual size of the file on disk. This PC has 2GB of memory, which is as much as Poser knows what to do with, but it still hits the buffers when I try to render a large scene. Dizzi points out in the thread above that, if Poser gives up on a save, it's the lights that are first thing to get chucked overboard. I can't understand how the action of saving or rendering a subsequent save can corrupt a previous save, but I am NOT doubting that your previously saved files are corrupted. I suspect that they are saved intact, but that Poser can't re-load them. I tried deleting all of the unused morphs from figures in my scene. It did help, but I had to go back to an earlier save and re-do one whole figure from scratch. I hope that some of this helps!