As Varian says, curiouser and curiouser. I just tried a render to disk as a bmp, only a little one since I did not want to be there all day, stopped it in the middle and resumed, and when finished it was fine. Bloodsong, you mentioned .tif. I have never tried that before, so I am just rendering that to disk while I write this message. I will tell you how it does in a minute. But rendering to disk does at least let me type almost normally in this message while the render is going on, so I may yet use render to disk more ofen, when I do not want to abandon the whole computer to Vue. I have pressed ESC twice in Netscape/Renderosity, and Vue is still happily rendering. I had to go back to Vue to hit ESC to see whether it still resumes properly after a pause when using tif. Well, the tif finished, it is a bigger file than the bmp, took over twice as long to render, Vue crashed when it got to 100% and only the bottom third is properly rendered. I stopped and restarted it at 30%, so I wonder if it renders from the bottom up when rendering to disc, and the tif gets corrupted by a restart? It did not attempt to rename mine to bmp, but I wonder if it resumes as bmp after a stop, and that is why the rest of the image is corrupted? This is all speculation, of course, but it does seem to me that bmp is the safest file type to use in a render, and use PSP or PS to make a tif copy if that is needed. I did another render to screen and saved that as a tif, and the result was fine and the filesize much smaller than the bmp, while the render to disc one was much bigger. I still cannot get ESC pressed with Netscape as the current application to stop Vue's render, so I don't know why that behaves impeccably for me when it is a bug for others. My guess is that there is a bug in the render to disk tif saving, and bmp is the safer option to use.