Ive been rendering for the last day or so @ 20"x36" at 150dpi without a problem. Now when it renders, it says insufficient disk space to render at the current resolution. I have abotu 100 gig on this hd alone left of free space. anyone goto a clue? is there som sort of poser 5 temp storage i have filled? Please respond asap IF YOU KNOW WHATS WRONG. THANKYOU!

I know of a similar error message in P4; never encountered it in P5, though. Are you rendering for print? If not, forget the 150 dpi, screen res is 72 dpi at best. If you are rendering for print, accept my apologies for being Captain Obvious. Both P4 and P5 have memory leak issues; you may get round your problem by rebooting. Also, look in your Poser 5 directory and delete a file called Posertemp. Otherwise, dunno.

1. yes its for print. 2. theres no such file or folder in the poser 5 directory 3. restarting didnt work, already tryed a few times. 4. I still need help!

itll let me render a little 72 DPI 500x500 but not a huge file. Ive been doing this for a few days now.. whats goign on... grrrr

Deep in the archives there was a solution for ProPak but I don't know if it would work for P5. The jist of it is, run scandisk then remove the swap file and from the safe mode run the de-frag. Now here's the part I'm not sure of with P5: move your runtime to another drive and re-install Poser( plus sr's). Now burn the 8 or so main files to cd, use as emergency. Re-set your swap and re-boot. Move runtime back. I used my emergency cd for just this thing on PP- let it overwrite the files and all was well.

The official recommendation is to adjust your swap file settings. You can also try installing Poser on a different hard drive from the one that handles your swap file.

can someone explain to me what a swap file is and how to adjust it? im runnin XP with poser 5

The swap file is virtual memory used by Windows. Windows swaps your memory out to the hard drive in order to work. The best place for help concerning Windows is to click on the Start button, then click on Help. I don't fiddle with the swap file. Instead, I put Poser on its own 160 GB hard drive, and it works just fine.

well poser on my pc is on its own 80 gig by iteself... thers about 70 of open space, thats why im gettin confused about no storage.

GODspeed, to find your swap file setting: note, I use the keyboard, faster. Winows key then s then c - brings up the control panel. Then s until the System icon is highlighted then Enter. Click on the Advanced tab then click on the Settings Button then click on the Advanced Tab. Under Virtual Memory click change. Uncheck let Windows manage Select the drive you want and enter these as a start value: 1024-2048. The max value you can use is 4096 but some machines don't like it and will display a white screen when Poser loads.

When was the last time you defragged your hard drive?

new harddrive. bout 3 weeks old.

This works in P4. Never tried it in P5, but it should work. BTW, this fix was posted by SWAMP. It's not something I invented. Oh, and it's better if you can do this with a clean install. 1. In the main poser folder (ie. the one above Runtime), make a copy of all system files (not readmes and other crap). Your Poser.rsr should always be set to 'read only'. If it isn't, change it (in properties). That's the file that continually corrupts when poser crashes. 2. Paste the copied files to a folder called 'Q fix' 3. The next time poser starts acting up, copy all the files from Q fix, and paste them into the main poser folder. This works for me in P4 every time. Once every few months, poser starts this 'insufficient blah, blah'. I just close poser, re-install the files, and when I open it, it's fine again. mac

When was the last time you defragged the hard drive? This is extremely important. Your hard drive gets lots of work in a single day. If you've had it for 3 weeks, and never defragged, you need to empty your recycle bin and defrag.

Attached Link: http://www.sysinternals.com/ntw2k/freeware/pagedefrag.shtml

Defragmentation doesn't work on certain important system files. Pagedefrag from Sysinternals [link] is a free utility that works at boot time, before Windows gets a lock on those files, so it's a very useful addition to normal defragmentation. The best way to avoid fragmentation of your swap file is to create a new partition solely for it. That's what I did, and 'insufficient disk space' is now a thing of the past. Pagedefrag should be a good second best, though. Set it to run at every boot.

I use Norton Systemworks and Speed Disk. I never fiddle with changing swap file settings, and I rarely have the Insufficient Disk Space problem. Maybe the last time I saw it was over a year ago. When I did get it, I used Norton Speed Disk, and was all set.