I have a 1.4ghz pc, 730mb RAM with 32mb graphics, using Poser 4.03. I keep poser and all renders on a separate partition; it currently has just under 6gb free, and I have a page file on the partition of between 75 and 125mb in size. I usually render at 700x700, 100 resolution and every now and then I keep getting a "insufficient disk space to complete render at current resolution" message when it tries to render. Reducing the resolution and size makes no difference; sometimes I'm unable to render anything. I've already doubled the page file size, and given my large amount of RAM to begin with I'd thought I wouldn't have this problem. It's not like I'm rendering at 4000x4000. Any ideas? Cheers JoeBlack

Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=1172490

Joe,Do you have the memory patch? SWAMP

730 MB ... Do you use 3 RAM modules on your board(perhaps a motherboard with intel chipset?)? if yes, you must pay attention that all of these modules are single sided modules. If you use double sided modules, your chipset will run in trouble (only two double sided are allowed because the second and third module use the same adressing). Try to remove one of the modules and look what happens. Another question: How much free space on your system partition? Robert

Another little oddity on my system: I've tried all the suggested cures (reboot, defrag, memory patch, tons of RAM and huge Swap file) and none works consistently when this pesky error starts popping up. The one thing that has made it vanish the last 3 times (no kidding) is running a CD based flight-sim game. Just thought I'd add that one to the collective anecdotal database.

One thing you neglected to mention is which OS you are using. If it's 98, you're pretty much screwed because a combination of Poser, more than 512 MB of RAM and 98 do not sit well together. You'll get inconsistent results no matter what you try. And I really, really hope you're not using ME. If you are, the only thing you'll learn is how to cry. :) If you're using XP/2000/NT, you should be ok. That is, unless you're running other apps which grab RAM/Pagefile space. Photoshop is notorious for taking as much space as possible, even when it's not actually necessary. Another suggestion is to empty your web cache, which can get surprisingly top heavy in next to no time.

Re-reading your original post, I heartily recommend at least 15GB free space for rendering.

I have had this problem also. Solution is: 1) Set your virtual memory to 0 or as small as possible. 2) Reboot. 3) Set your virtual memory back to the original settings. 4) Reboot. You should be OK. If you don't know how to set your virtual memory, open HELP and search for vitual memory or pagefile.

OK: 1)I'm Using XP Home 2)My system partition is over 5.66gb in capacity, and has 2.41gb left (yes I know it's small, I didn't realise it should perhaps be bigger seeing how large XP is, and the system-sustained page file is over 1.1gb). I just keep an eye on it and restrict the amount of restore points it can store, as well as other rubbish that may build up on it. 3)Installing poser on a separate hard drive is not an option 4)In answer to my amount of RAM, I have 2 slots, using DIMM PC133 sticks - 256 and 512. It can take a max of 1gb. My onboard video card shares between 8 and 64mb. 5)I'm using Poser 4.0.3 but I'm not sure if I have the memory patch or not, seeing how I've reinstalled poser recently. 6)I defrag everyday, especially my poser partition. 7)Like I said I change the page file in the poser partition regularly but it's never enough. 8)I don't usually have any major memory-intensive programs open while using Poser, except maybe PSP. 9)My poser partition is 7.86gb, and has 5.88gb free. (Total hard drive size is 40gb) Thanks ppl JoeBlack

I've got the memory patch, but seeing how I have 736mb RAM plus 95-135mb virtual memory, that isn't above 1gb. Should I use it? JoeBlack

I recently "cleared" my virtual memory. By the way, this advice was given to me by Curious Labs about nine months ago. Thanks to Swamp, I obtained and installed the memory patch. So far, so good. The problem occurs "over time", so I guess I'll find out how good the patch is in a few months. I think you should increase your virual memory and use the patch. I have 512MB Ram and 704MB VM.

Ok Joe,If you do a search in the Poser forum on this subject you are going to find as many answers as they are members here.Most are based in myth,black magic,and uneducated replys....I know because I tried them all(on several machines). What works for me and other people that follow this 100% of the time is this.....Leave everything alone! Your computer and WindowsXP are pretty smart and know what to do.Its when you try to outguess them,(as many people do)that you run into problems.

Now for where you are getting into problems.. Before someone jumps in here withyea,but thats what I dothere is no reason to put Poser on a separate partition..It doesnt run any differently.and in your case you are limiting the amount of space it has to work in. When you set page file size for that partition,you are also splitting up your page file for your whole systemnot very efficient. I do have a 2.5gb partition used only for a swap file,but that is for Adobe Photoshop,Illustrator,and InDesignand that is from a special setting within the programs(Windows doesnt even know about it,and doesnt see it). Bottom linereinstall Poser on your C drive,reset all your page file/memory settings back to factorydefault,and install the memory patch. The only thing you might change is to use the free Xpantispy program..that will turn off Messager,those stupid popup ballons,and you can set it to clear out all your page/swap files when you shut downnice. I render 3000x2400 at 300dpi one right after the other,and work with 200mb+ files in Photoshop,and never,never have a problemwith less memory than you. Hope this helps..happy rendering,SWAMP

Got an "insufficient disk space to render at this resolution", yesterday. "Resetting" my virtual memory did not solve my problem. I reinstalled 4.03 update, which effectively "uninstalled" the memory patch and fixed my problem. The memory update does not work on my system -- Athlon 1200, 512MB Ram, 896MB Virtual.