From the CL website: {After some intense investigation we believe we have a work around. It turns out that Windows NT 4, 2000 and Windows XP must be using some space for the pagefile.sys file on the same partition that Poser is installed, to render large images.} This answer would assume that you installed Poser on the C drive and that you also use the C drive to store the pagefile.sys file. Therefore, you should not get this error if you install Poser on the D drive (where the pagefile.sys file is not located). Unfortunately, this is not the case. Poser's rendering engine is susceptible to a number of factors beyond whether you have it installed on the same partition as your pagefile.sys. This workaround is more of a "placate the user with Windows tech talk" than an in-depth solution. Some examples: If you have Photoshop open when using Poser, you probably will not be able to do a "Render to new window" (even at a small size like 600x600). Closing Photoshop may allow the new-window render. Closing Photoshop, closing Poser, and re-starting Poser may solve this. This is due to Photoshop's use of a scratch disk and its memory usage. If you have too many programs open, rendering to a new window may not work... even if you have a lot of memory (512M) and a lot of disk space. Again, other programs take up memory space and may conflict with Poser's memory needs. Recommendation: 1) Close ALL programs when you need to do a "render to new window"- including any virus scanners, IE, and Windows Explorer. 2) Close and restart Poser, especially if you've been using a lot of characters and texture. Keep in mind that Poser "caches" all textures that you have used while it has been open... including textures that you aren't currently using in your scene. So, if you loaded that 4000x4000 body map earlier (but are not using it now), it is still taking up space in Poser's memory. 3) Close Poser 4 and render the scene in Poser 5, using the P4 Renderer. Sure, it may be a little slower, but it gets the job done. I have personally experience MANY times when Poser 4 refused to render an image to a new window (even after multiple close & re-opens), yet Poser 5 rendered it with no problem. 4) Advanced users only Open the Task Manager, click on the Processes tab, find poser.exe, right click and set "Priority Level" to "High". This tells Windows to give Poser all the processing power. Keep in mind that this may or may not affect the stability of Windows if you try to use any other program (including switching to the Desktop or Windows Explorer). Remember to switch the Priority Level back to "Normal" if you want to work with any other program (such as IE or e-mail). The answer to the "blank characters" or "blank scene" is this: do a "Save As" and save the scene with a new name. Then close Poser. Re-open Poser and re-open this scene. If everything is back to normal, great! If something did get messed up (beyond a document-window-view issue), then you still have the original version of your scene. The bottom line is this: Poser 4 was just not designed to handle "modern" computers and its memory-mangement system is not the best. CL can issue all kinds of the "workarounds", but these only offer a temporary "band-aid" and not a solution to the issue. (And this doesn't address the poorly worded error message, which includes a statement to "Allocate more memory to Poser"... which a hold-over from the Mac and is something that can't be done on Windows.) P.S. Write this on your monitor in permanent ink: If you care about your scene, always save BEFORE rendering. If something happens during the render process, you can always re-open your scene later and try again. But, if you didn not save the scene and something happens during the render, then you are... (well, you know).